[arin-ppml] Updates to 2012-6
hannigan at gmail.com
Wed Nov 21 21:35:24 EST 2012
I think Rodney's comments are solid. Moves may also be involuntary and
forcing transactions through the transfer process seems like
unnecessary overhead that simply slows things down and could cause
The terminology "ICANN sanctioned" is in error as well. ICANN doesn't
sanction TLD's, they enter into agreements and become "contracted
parties". It is consistent with ICANN terminology which I think that
in this case it makes sense to align as much as possible and feasible.
On Wed, Nov 21, 2012 at 5:05 PM, Bill Sandiford
<bill at telnetcommunications.com> wrote:
> Hi Rodney,
> Please note that terminology is not new. It is the terminology that is currently in the NRPM today.
> Any suggested edits to the text are welcomed.
> -----Original Message-----
> From: Rodney Joffe [mailto:rjoffe at centergate.com]
> Sent: November 21, 2012 2:56 PM
> To: Bill Sandiford
> Subject: Re: [arin-ppml] Updates to 2012-6
> Sorry to be the potential bearer of bad tidings regarding the wording of this policy, but...
> I think the terminology needs to be cleaned up.
> Core DNS operators - Thats someone like me (UltraDNS/Neustar).
> core DNS service providers (e.g. ICANN-sanctioned root and ccTLD operators) - I guess thats confusing.
> We are a core DNS service provider. However we will be providing the services to over 300 of the new TLD registries. If you allocate the /23s to us, the registry is screwed if they move at some stage to another provider, or do it themselves. So you should be allocating to the TLD Registry itself, who can then temporarily assign the /23 to us, but can then move it when needed.
> On Nov 21, 2012, at 12:21 PM, Bill Sandiford <bill at telnetcommunications.com> wrote:
>> Since the conclusion of the Dallas PPM the AC has spent considerable time working on Draft Policy 2012-6. As a result, we have come up with modified text as below. You will note that the new policy text makes minimal changes to the existing policy in the NRPM, but still obtains the goals as intended by the author and expressed by the community in Dallas.
>> Please provide comments.
>> Policy text:
>> 4.4. Micro-allocation
>> ARIN will make IPv4 micro-allocations to critical infrastructure providers of the Internet, including public exchange points, core DNS service providers (e.g. ICANN-sanctioned root and ccTLD operators) as well as the RIRs and IANA. These allocations will be no smaller than a /24. Multiple allocations may be granted in certain situations.
>> Exchange point allocations MUST be allocated from specific blocks reserved only for this purpose. All other micro-allocations WILL be allocated out of other blocks reserved for micro-allocation purposes.
>> ARIN will make a list of these blocks publicly available.
>> Exchange point operators must provide justification for the
>> including: connection policy, location, other participants (minimum of two total), ASN, and contact information. ISPs and other organizations receiving these micro-allocations will be charged under the ISP fee schedule, while end-users will be charged under the fee schedule for end-users. This policy does not preclude exchange point operators from requesting address space under other policies.
>> ARIN will place an equivalent of a /16 of IPv4 address space in a reserve for Critical Infrastructure, as defined in section 4.4. If at the end of the policy term there is unused address space remaining in this pool, ARIN staff is authorized to utilize this space in a manner consistent with community expectations.
>> ICANN-sanctioned gTLD operators may justify up to the equivalent of an
>> IPv4 /23 block for each authorized new gTLD, allocated from the free pool or received via transfer, but not from the above reservation. This limit of a /23 equivalent per gTLD does not apply to gTLD allocations made under previous policy.
>> Additional ICANN-sanctioned DNS infrastructure is being added to the Internet and in quantities greater than anticipated when the micro allocation proposal was written and adopted.
>> The original CI pool was created to serve new IXP and new CI requirements. The pending need is estimated to be over 1000 new gTLD range, which may exhaust the current /16 reservation before the ARIN free pool is exhausted. Once the current /16 reservation is exhausted, CI providers would no longer be eligible to receive address space, either via the general free pool or via transfer.
>> The original proposal dealt with this by expanding the reservation to
>> /15 and allowing CI to draw from the free pool instead of the reservation until it gets down to a /8. The consensus coming out of the Dallas meeting seems to be that this is an inadequate solution. As the new expanded gTLD demand will obliterate any reasonable reservation, leaving no resources for the other IXP and CI demands that the original reservation was intended to serve. It is therefore, not possible to services them both out of a common reservation.
>> In order to ensure continued access to IPv4 number resources by new IXP and DNS operators alike, the AC is modifying the proposal going into last call to allow gTLD operators to continue to qualify for micro allocations from the general free pool or via transfer only, and leaving one /16 reserved for IXP, root, and ccTLD DNS operators.
>> As a result of the close examination of the CI policy brought about by this proposal, the AC has identified a number of issues in the original policy text that should be addressed. However, the AC is intentionally minimizing the overall changes to this proposal as much as possible for last call in keeping with the spirit of the PDP. The AC intends to make future proposals to deal with these other concerns. The current proposal addresses issues of some urgency and we did not want to delay it to another policy cycle as a result.
>> You are receiving this message because you are subscribed to the ARIN
>> Public Policy Mailing List (ARIN-PPML at arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> Please contact info at arin.net if you experience any issues.
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.
More information about the ARIN-PPML