Changes to European Internet Registry Policies And Procedures
| Legend | (+) Added | (-) Deleted |
|---|---|---|
| Changed | Tag Added | Tag Deleted |
Abstract insert: </h2>
insert: <p>This document describes the policy for reverse delegation of IPv4 and IPv6 address space in the RIPE NCC service region. insert: </p>
insert: <h3>Contents insert: </h3>
insert: <blockquote>insert: <p>insert: <h2>insert: <a class="anchor-link" href="#intro"> 1.0 Introduction insert: </a>
insert: </blockquote>
insert: <a class="anchor-link" href="#delegation"> 2.0 Obtaining Delegation of an in-addr.arpa or ip6.arpa sub-domain insert: </a> insert: <br />
insert: <a class="anchor-link" href="#procedures"> 3.0 Procedures insert: </a> insert: <br />
insert: <a class="anchor-link" href="#references"> 4.0 References insert: </a> insert: </p>
insert: <a name="intro"> insert: </a> 1.0 Introduction insert: </h2>
insert: <p>The RIPE NCC provides, as part of its services, the necessary support to enable the reverse resolution of IPv4 and IPv6 address space into domain names. This RIPE Document service is available implemented under the in-addr.arpa and ip6.arpa sub-domains described in a ASCII and PDF delete: </p> [ insert: <a class="anchor-link" href="#references"> 1 insert: </a> ] and [ insert: <a class="anchor-link" href="#references"> 2 insert: </a> ]. insert: </p>
insert: <p>Reverse delegations for IPv4 and IPv6 addresses allocated by the RIPE NCC are made to Local Internet Registries (LIRs) and further delegated by the LIRs to Internet Service Providers or End Users. insert: </p>
insert: <h2>insert: <a name="delegation"> insert: </a> 2.0 Obtaining Delegation of an in-addr.arpa or ip6.arpa sub-domain insert: </h2>
insert: <p>The RIPE NCC provides reverse delegation for address space that has been allocated or assigned by the RIPE NCC. It also provides systems to control reverse delegations relating to early registrations that have been transferred to the RIPE Database. Registrants of address space allocations or assignments may delegate authority for requesting reverse delegation from the RIPE NCC. insert: </p>
insert: <p>The RIPE NCC accepts requests for reverse delegation for address space that has been allocated by the RIPE NCC to an LIR or, in the case of PI address space, an assignment that has been made to an End User. insert: </p>
insert: <h2>insert: <a name="procedures"> insert: </a> 3.0 Procedures insert: </h2>
insert: <p>The procedures for requesting and modifying reverse delegation and information about the requirements the RIPE NCC enforces to maintain the quality of the reverse delegations are published at: insert: </p>
insert: <blockquote>insert: <p>insert: <h2>insert: <a data-val="275a3e401b56a46b5cf7b0a5a93c1492" href="resolveuid/275a3e401b56a46b5cf7b0a5a93c1492" data-linktype="internal" class="internal-link"> http://www.ripe.net/reverse/ insert: </a> insert: </p>
insert: </blockquote>
insert: <a name="references"> insert: </a> 4.0 References insert: </h2>
insert: <p> [1] "Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")" insert: <br />
[ insert: <a href="ftp://ftp.ripe.net/rfc/rfc3172.txt"> RFC 3172 insert: </a> ] insert: </p>
[2] "DNS Extensions to Support IPv6 Address Aggregation and Renumbering" [ insert: <a href="ftp://ftp.ripe.net/rfc/rfc2874.txt"> RFC 2874 insert: </a> ] insert: </p>
