New Draft in-addr.arpa Policy Document for Review

Dear LIRs,

We are pleased to announce the availability of the new draft "Reverse 
Address Delegation Under 'in-addr.arpa' in the RIPE NCC Service Region" 
document. The draft document can be found in the text to follow and is also 
available on the RIPE NCC website at:

http://www.ripe.net/ripencc/mem-services/registration/policies/draft-documents/

The deadline for comments and suggestions is Monday, 24 June 2002. After 
incorporating any suggested changes to the document the final document will 
be published as a RIPE Document. All comments and suggestions should be 
sent to <lir-wg at ripe.net>.

Regards,

Paul Rendek
RIPE NCC


===

Draft: Policy for reverse address delegation under in-addr.arpa in the RIPE 
NCC service region



Author(s):
Document ID: TBA
Date: June 2002
Obsoletes: [insert doc #]


Abstract
This document describes the policy for reverse delegation of IPv4 
assignments and allocations in the RIPE NCC service region.

Table of Contents
1.0 Introduction
2.0 Obtaining Delegation of an in-addr.arpa Sub-zone
3.0 Reverse Delegation for Provider Aggregatable (PA) Address Space
4.0 Reverse Delegation for Provider Independent (PI) Address Space
5.0 Duration of the Reverse Delegation

1 Introduction

The RIPE NCC provides, as part of its services, the necessary support to 
enable the reverse resolution of IPv4 addresses into domain names. This 
service is implemented under the in-addr subdomain described in the 
"Management Guidelines & Operational Requirements for the Address and 
Routing Parameter Area Domain ("arpa")"[RFC3172] document.

Delegations for IPv4 addresses contained in allocations made by the RIPE 
NCC (reverse delegations) are made by the RIPE NCC to the Local Internet 
Registries (LIRs) and further by the LIRs to ISPs or end users.

2 Obtaining delegation of an in-addr.arpa sub-zone

The RIPE NCC will only accept requests for reverse delegation under 
in-addr.arpa from LIRs. End users must send their requests to the LIR from 
which they obtained the addresses, or in the case of Provider Independent 
addresses, to any of the LIRs of their choice.A list of LIRs can be found at:

http://www.ripe.net/ripencc/mem-services/general/indices/index.html

The procedure for requesting the delegation of zones under in-addr.arpa is 
published at:

http://www.ripe.net/reverse

Advice on configuring name servers is available in "Common DNS operational 
and Configuration Errors" [RFC1912]

3 Reverse delegation for Provider Aggregatable (PA) address space

The RIPE NCC accepts requests for reverse delegation solely for address 
space that has been registered by the LIR as assigned to end users in the 
RIPE Whois Database.

The RIPE NCC will only make delegations on 8-bit boundaries (/16 or /24), 
though multiple delegations may be requested to cover CIDR blocks bigger 
than a /24.

LIRs should maintain DNS resource records for address space assigned to end 
users from their own address space, even if the user obtains connectivity 
from a different LIR.

4 Reverse delegation for Provider Independent (PI) address space

The RIPE NCC will reverse delegate a zone of in-addr.arpa to an end user 
that has been assigned PI space. However, the request must be sent to the 
RIPE NCC via an LIR, as described above.

For delegations of address blocks smaller than a /24 the method described 
in "Classless IN-ADDR.ARPA delegation"[RFC2317] will be used.

5 Duration of the reverse delegation

Provision of reverse delegation services by the RIPE NCC is a membership 
service. As such, the RIPE NCC will only accept requests for delegation and 
modifications of delegations from LIRs that are up-to-date with regard to 
their membership duties.

LIRs should provide reverse delegation corresponding to an assignment 
during the complete validity period of the assignment.

-- END