Amendments to existing policy document ripe-581, "Policy For Reverse Address Delegation of IPv4 and IPv6 Address Space in the RIPE NCC Service Region"
How to read this draft document:
This document relates to the policy proposal 2016-03, “Locking Down the Final /8 Policy”. If approved, it will modify ripe-581. To show you how the new document would be different to the old one, we have highlighted any new text or changes to the existing text.
We indicate changes to existing text in the document like this:
| ORIGINAL TEXT | NEW TEXT |
|---|---|
The text from the current policy document that will be replaced is displayed here. |
The proposed text change will be displayed here. |
This document describes the policy for reverse delegation of IPv4 and IPv6 address space in the RIPE NCC service region.
Contents
1.0 Definition
2.0 Introduction
3.0 Reverse Delegation in the RIPE NCC Service Region
4.0 Procedures
5.0 References
6.0 Attribution
1.0 Definition
1.1 Reverse delegation: The process by which the authority for certain reverse DNS zones is assigned to a specific set of DNS servers.
1.2 Early registration: IPv4 address space assigned or allocated before the establishment of the Regional Internet Registries (RIRs).
2.0 Introduction
The RIPE NCC provides the necessary support to enable 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 [1] and [2].
3.0 Reverse Delegation in the RIPE NCC Service Region
The RIPE NCC provides reverse delegations for IPv4 and IPv6 address space that is registered by the RIPE NCC. The RIPE NCC also provides systems to control reverse delegation of early registrations that have been transferred to the RIPE Database. Address space holders may delegate authority to another party. |
The RIPE NCC provides reverse delegations for IPv4 and IPv6 address space that is registered by the RIPE NCC. The RIPE NCC also provides systems to control reverse delegation of early registrations that have been transferred to the RIPE Database. Address space holders may delegate authority to another party. For "ALLOCATED FINAL" IPv4 address space, authority may not be delegated to another party, and the reverse delegation will be limited to a total of a /22 of IPv4 address space. |
4.0 Procedures
The procedures related to reverse delegation and information about the requirements the RIPE NCC enforces are published at:http://www.ripe.net/reverse/
5.0 References
[1] [RFC 3172] "Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")"
[2] [RFC 3596] "DNS Extensions to Support IP Version 6", [RFC 3363] “Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System”, [RFC 3364] “Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version (IPv6)”
6.0 Attribution
This document is compiled from policies developed by the RIPE community.
The following people actively contributed to this policy by making proposals through the RIPE Policy Development Process:
Olaf Kolkman
Leo Vegoda