Replace the contents of 6.5.8.1 with:
6.5.8.1. Initial Assignment Criteria Organizations may justify an initial assignment for addressing devices directly attached to their own network infrastructure, with an intent for the addresses to begin operational use within 12 months, by meeting one of the following criteria: a. Having a previously justified IPv4 end-user assignment from ARIN or one of its predecessor registries, or; b. Currently being IPv6 Multihomed or immediately becoming IPv6 Multihomed and using an assigned valid global AS number, or; c. By having a network that makes active use of a minimum of 2000 IPv6 addresses within 12 months, or; d. By having a network that makes active use of a minimum of 200 /64 subnets within 12 months, or; e. By having a network that has at least 13 sites (as defined by NRPM 2.10) within one contiguous network, or; f. By providing a reasonable technical justification indicating why IPv6 addresses from an ISP or other LIR are unsuitable. Basically renumbered from e. to f. and added e. GTG From: arin-ppml-boun...@arin.net [mailto:arin-ppml-boun...@arin.net] On Behalf Of David Huberman Sent: February-17-15 1:00 PM To: Gary T. Giesen; 'John Curran' Cc: arin-ppml@arin.net Subject: Re: [arin-ppml] IPv6 End-User Initial Assignment Policy (or: Please don't me make do ULA + NAT66) Gary, That resonates with me. I agree with you that obtaining IPv6 from the RIR needs to be a sure thing, not a risk, for any network operator who needs PI v6 to sanely build their network. Do you have a general or any specific recommendation for capturing this in policy better than the current text does? David From: Gary T. Giesen [mailto:ggie...@giesen.me] Sent: Tuesday, February 17, 2015 9:55 AM To: David Huberman; 'John Curran' Cc: arin-ppml@arin.net Subject: RE: [arin-ppml] IPv6 End-User Initial Assignment Policy (or: Please don't me make do ULA + NAT66) David, I don’t necessarily disagree. Just trying to minimize the business risk of having to have virtually all of my customers qualify under e) with the risk of rejection because my use case isn’t specifically spelled out. And I realize perhaps my use case is a very small minority. But the barriers to adoption are real and if I can’t check a box and guarantee my customers get address space when they need it, they won’t adopt, plain and simple. Perhaps I’ll feel a bit better about it when I have a few 6.5.8.1e applications under my belt. GTG From: arin-ppml-boun...@arin.net [mailto:arin-ppml-boun...@arin.net] On Behalf Of David Huberman Sent: February-17-15 12:39 PM To: John Curran Cc: Gary T. Giesen; arin-ppml@arin.net Subject: Re: [arin-ppml] IPv6 End-User Initial Assignment Policy (or: Please don't me make do ULA + NAT66) Thank you John! So Gary: I understand your meta point. I am all for clarity and ease-of-use in the NRPM. As an AC member, I hope to drive the NRPM to more and more “easiness”. But (and perhaps I’m wrong), I feel that EU v6 policy is pretty needs-free and easy. You have 5 clauses to qualify under, and clause e) really is the ‘catch-all” bucket for “everything else”, including the case you brought up. Disagree? David R Huberman Microsoft Corporation Principal, Global IP Addressing From: John Curran [mailto:jcur...@arin.net] Sent: Tuesday, February 17, 2015 9:09 AM To: David Huberman Cc: Gary T. Giesen; arin-ppml@arin.net Subject: Re: [arin-ppml] IPv6 End-User Initial Assignment Policy (or: Please don't me make do ULA + NAT66) On Feb 17, 2015, at 11:54 AM, David Huberman <david.huber...@microsoft.com> wrote: But “something quite so fuzzy” is your interpretation, not ARIN’s. So let’s get ARIN’s interpretation and try and take the fuzziness out of the equation. Question for ARIN: In the general (normal) case when an application is made for EU v6 under clause e) and there’s a technical explanation for why they want RIR-issued space, will the application be approved ? Yes, so long as a technical explanation is provided. NRPM 6.5.8.1 provides a list of several situations that would warrant direct end-user IPv6 assignment, and others are accepted as well so long as a reasonable technical justification is provided. Thanks, /John John Curran President and CEO ARIN
_______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML@arin.net). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact i...@arin.net if you experience any issues.
