This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] Cosmetic Surgery Project: Extended Review Period on New Draft, Document for Reverse Address Delegation of IPv4 and IPv6 Address Space
- Previous message (by thread): [address-policy-wg] Cosmetic Surgery Project: Extended Review Period on New Draft, Document for Reverse Address Delegation of IPv4 and IPv6 Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Thu Apr 26 15:35:56 CEST 2012
[https://www.ripe.net/ripe/readability/rad/reverse-address-delegation] I have a few suggestions: > 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 Reverse resolution: The process by which a recursive DNS resolver can look up the names of a given IP address by following a chain of referrals from the root zone to either the in-addr.arpa zone or the ip6.arpa zone. > 1.3 Early registration: IPv4 address space assigned or allocated before the establishment of the Regional Internet Registries (RIRs). this section is new. It defines "reverse delegation" as a process rather than the result, which is OK, but conflicts with the use in 4.0. > 2.0 Introduction > The RIPE NCC provides the necessary support to enable 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 [1] and [2]. The term 'reverse resolution' is rarely used. The RIPE NCC provides the necessary support to enable DNS reverse mapping for the IPv4 and IPv6 address space. This service is implemented in the in-addr.arpa and ip6.arpa 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 provides reverse delegation 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 original text read "Registrants of address space allocations or assignments may delegate authority for requesting reverse delegation from the RIPE NCC." and I am not sure what either wants to say. Is it about subdelegations? Is it about who is able to ask for the delegation? > 4.0 Procedures > The procedures for requesting and modifying reverse delegation and information about the requirements the RIPE NCC enforces are published at: > http://www.ripe.net/reverse/ > > 5.0 References > [1] "Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")" [RFC 3172] > [2] "DNS Extensions to Support IPv6 Address Aggregation and Renumbering" [RFC 2874] RFC 2784 has been declared "historic" and obsoleted by RFC 3596. Changing the reference does not change the policy (in fact, 2874 was all about IP6.INT). -Peter
- Previous message (by thread): [address-policy-wg] Cosmetic Surgery Project: Extended Review Period on New Draft, Document for Reverse Address Delegation of IPv4 and IPv6 Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]