Changes to Policy For Reverse Address Delegation of IPv4 And IPv6 Address Space in the RIPE NCC Service Region

This document describes the policy for reverse delegation of IPv4 and IPv6 address space in the RIPE NCC service region.

Contents

insert: <a class="anchor-link" href="#definition"> 1.0 Definition insert: </a> insert: </p>

insert: <a class="anchor-link" href="#introduction"> 2.0 Introduction delete: <br /> delete: <a class="anchor-link" href="#delegation"> insert: </p>

insert: <a class="anchor-link" href="#reverse_delegation"> 3.0 Reverse Delegation in the RIPE NCC Service Region insert: </a> insert: </p>

insert: <a class="anchor-link" href="#procedures"> 4.0 Procedures insert: </a> insert: </p>

insert: <a class="anchor-link" href="#references"> 5.0 References insert: </a> insert: </p>

insert: <a class="anchor-link" href="#attribution"> 6.0 Attribution insert: </a> insert: </p>

insert: <a name="definition"> insert: </a> 1.0 Definition insert: </h3>

insert: <b> 1.1 insert: </b> insert: <b> Reverse delegation: insert: </b> The process by which the authority for certain reverse DNS zones is assigned to a specific set of DNS servers. insert: </p>

insert: <b> 1.2 Early registration: insert: </b> IPv4 address space assigned or allocated before the establishment of the Regional Internet Registries (RIRs). insert: </p>

insert: </p>

insert: </p>

insert: <a name="introduction"> insert: </a> 2.0 Obtaining Delegation of an in-addr.arpa or ip6.arpa sub-domain delete: </a> delete: <br /> delete: <a class="anchor-link" href="#procedures"> 3.0 Procedures delete: </a> delete: <br /> delete: <a class="anchor-link" href="#references"> 4.0 References delete: </a> delete: </p> delete: </blockquote> delete: <h2> delete: <a name="intro"> delete: </a> 1.0 Introduction delete: </h2> delete: <p> The RIPE NCC provides, as part of its services, insert: </h3>

The RIPE NCC provides the necessary support to enable the reverse resolution of IPv4 and IPv6 address space into domain names. This service is implemented under the in-addr.arpa and ip6.arpa sub-domains described in [ delete: <a class="anchor-link" href="#references"> insert: <a class="anchor-link" href="#ref1"> 1 ] and [ delete: <a class="anchor-link" href="#references"> 2 delete: </a> ]. delete: </p> delete: <p> insert: <a class="anchor-link" href="#ref2"> 2] insert: </a> . insert: </p>

insert: <a name="reverse_delegation"> insert: </a> 3.0 Reverse Delegation in the RIPE NCC Service Region insert: </h3>

The RIPE NCC provides 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. delete: </p> delete: <h2> delete: <a name="delegation"> delete: </a> 2.0 Obtaining Delegation of an in-addr.arpa or ip6.arpa sub-domain delete: </h2> delete: <p> The RIPE NCC provides reverse delegation for address space that has been allocated or assigned is registered by the RIPE NCC. It insert: </p>

The RIPE NCC also provides systems to control reverse delegations relating to delegation of early registrations that have been transferred to the RIPE Database. Registrants of address insert: </p>

Address space allocations or assignments holders may delegate authority for requesting to another party. insert: </p>

insert: </p>

insert: </p>

insert: <a name="procedures"> insert: </a> 4.0 Procedures insert: </h3>

The procedures related to reverse delegation from the RIPE NCC. delete: </p> delete: <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. delete: </p> delete: <h2> delete: <a name="procedures"> delete: </a> 3.0 Procedures delete: </h2> delete: <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: <a href="http://www.ripe.net/reverse/"> http://www.ripe.net/reverse/

4.0 5.0 References delete: </h2> delete: <p> insert: </h3>

insert: <a name="ref1"> insert: </a> [1] [ insert: <a class="external-link" href="ftp://ftp.ripe.net/rfc/rfc3172.txt"> RFC 3172 insert: </a> ] "Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")" delete: <br /> [ delete: <a href="ftp://ftp.ripe.net/rfc/rfc3172.txt"> insert: </p>

insert: <a name="ref2"> insert: </a> [2] [ insert: <a class="external-link" href="ftp://ftp.ripe.net/rfc/rfc3596.txt"> RFC 3172 3596 ] delete: </p> delete: <p> [2] "DNS Extensions to Support IPv6 Address Aggregation and Renumbering" [ delete: <a href="ftp://ftp.ripe.net/rfc/rfc2874.txt"> IP Version 6", [ insert: <a class="external-link" href="ftp://ftp.ripe.net/rfc/rfc3363.txt"> RFC 2874 3363 ] delete: </p> “Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System”, [ insert: <a class="external-link" href="ftp://ftp.ripe.net/rfc/rfc3364.txt"> RFC 3364 insert: </a> ] “Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version (IPv6)” insert: </p>

insert: <a name="attribution"> insert: </a> 6.0 Attribution insert: </h3>

This document is compiled from policies developed by the RIPE community. insert: </p>

The following people actively contributed to this policy by making proposals through the RIPE Policy Development Process: insert: </p>

Olaf Kolkman insert: <br />
Leo Vegoda insert: </p>