[arin-ppml] ARIN-2011-5: Shared Transition Space for IPv4 Address Extension - Last Call

George, Wes E [NTK] Wesley.E.George at sprint.com
Mon Apr 25 08:46:37 EDT 2011

-----Original Message-----
From: wherrin at gmail.com [mailto:wherrin at gmail.com] On Behalf Of William Herrin
Sent: Monday, April 25, 2011 3:10 AM
To: Scott Leibrand
Cc: George, Wes E [NTK]; arin-ppml at arin.net
Subject: Re: [arin-ppml] ARIN-2011-5: Shared Transition Space for IPv4 Address Extension - Last Call

On Sun, Apr 24, 2011 at 10:12 PM, Scott Leibrand <scottleibrand at gmail.com> wrote:
> Ok.  So it sounds like you'd like to modify ARIN-2011-5 to add 
> language stating that, for purposes of NAT pools and internal 
> management, globally unique addressing would no longer be justified 
> unless there was a compelling technical reason this /10 couldn't be 
> used instead?
> Do you have any language suggestions?  (If not, I and probably a 
> number of others would be happy to help draft something if people feel 
> it's needed...)

"A requirement for IPv4 addresses used solely inside a single autonomous system shall not qualify an organization to receive or
retain an IPv4 address assignment or allocation."

I'd prefer something a bit more targeted. There's a lot of openings for interpretation in "used solely inside a single autonomous
system" and it would require its own set of definitions for staff guidance - for example, are router interfaces considered part of
this if they aren't on ASBRs? 
How do we define "internal management" in the context of this policy?
I don't have an idea of how to cover the "compelling technical reason" exception, and I'm not sure it's necessary. Typically
compelling technical reasons generate new policy (see also 6rd). I'm really looking for something that covers exactly what is said
in 2011-5 - " to be shared by Service Providers for internal use for IPv4 address extension deployments ... Examples of such needs
include: IPv4
addresses between home gateways and NAT444 translators."
My recommended text: IPv4 addresses used behind a NAT (inside pool) cannot be used for justification of new resources nor counted
towards utilization calculations for existing resources. NRPM 4.10.x (Shared Transition Space) defines a specific non-unique block
to  be shared among multiple networks for this purpose.

Wes George
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6753 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20110425/fe8c5fa7/attachment-0001.p7s>

More information about the ARIN-PPML mailing list