[arin-ppml] IPv6 End-User Initial Assignment Policy (or: Please don't me make do ULA + NAT66)

Gary T. Giesen ggiesen at giesen.me
Tue Feb 17 12:21:19 EST 2015

My concern is that the thresholds for a direct assignment are already specified in a through d, which my example customer would not qualify under any of them. What I’m asking for is essentially a fifth criteria (other than reasonable technical justification) - “By having a network that has at least 13 sites” as I’m know sure you qualify “not wanting to renumber” as a reasonable technical justification.  Clearly c) and d) are in place to reduce the pain of renumbering for larger customers, I’m just arguing my example customer’s pain at renumbering is at least as great as anyone who qualifies under either c) or d) and deserves a direct assignment.


John, Are you able to speak to the specific scenario I’ve previously laid out (and whether ARIN would  approve such a request under




From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of John Curran
Sent: February-17-15 12:09 PM
To: David R Huberman
Cc: Gary T. Giesen; arin-ppml at 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.Huberman at 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 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.





John Curran

President and CEO



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20150217/36c58673/attachment.html>

More information about the ARIN-PPML mailing list