To:
Ray Plzak <plzak@arin.net>
cc:
dnsop@cafax.se
From:
Dean Anderson <dean@av8.com>
Date:
Mon, 31 Mar 2003 16:48:12 -0500 (EST)
In-Reply-To:
<004401c2f78a$454284d0$148888c0@arin.net>
Sender:
owner-dnsop@cafax.se
Subject:
RE: I-D ACTION:draft-ietf-dnsop-inaddr-required-04.txt
The goal of this draft is to dictate a change in policy at ARIN and other registry's. The authors know about that in-addr is not required. They are trying to change that. --Dean On Mon, 31 Mar 2003, Ray Plzak wrote: > > In paragraph 2 the following is stated: > > "ARIN's policy requires ISPs to maintain IN-ADDR for /16 or larger > allocations. For smaller allocations, ARIN can provide IN-ADDR for /24 > and shorter prefixes." > > The ARIN policy statement is: > > "All ISPs receiving a /16 or larger block of space (>= 256 /24s) from > ARIN will be responsible for maintaining all IN-ADDR.ARPA domain records > for their respective customers. For blocks smaller than /16, ARIN can > maintain IN-ADDRs through the use of the SWIP template for reassignments > of /24 and shorter prefixes." > > > The policy does not require in-addr service. What it means is that if > in-addr service is desired then the responsibility for allocations of > /16 or shorter prefixes is that of the ISP receiving the allocation. If > the prefix is longer than a /16 and shorter than a /24, then ARIN will > provide the service if desired. > > Ray > > #---------------------------------------------------------------------- > # To unsubscribe, send a message to <dnsop-request@cafax.se>. > #---------------------------------------------------------------------- # To unsubscribe, send a message to <dnsop-request@cafax.se>.