[arin-ppml] ARIN-prop-127: Shared Transition Space for IPv4 Address Extension

George, Wes E [NTK] Wesley.E.George at sprint.com
Mon Jan 24 10:17:11 EST 2011

> -----Original Message-----
> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
> Behalf Of Owen DeLong
> Sent: Monday, January 24, 2011 4:20 AM
> To: Joel Jaeggli
> Cc: arin-ppml at arin.net
> Subject: Re: [arin-ppml] ARIN-prop-127: Shared Transition Space for
> IPv4 Address Extension

> On Jan 23, 2011, at 8:34 PM, Joel Jaeggli wrote:
> > Consider whose foot is beeing shot when you take some previously
> globaly scoped ipv4 space give it a private scope and don't give the
> host stacks time to figure it out.
> >
> Um, nobody's... At least that's what happened with RFC-1918. It was in
> wide use well
> before the RFC was finalized. To the best of my knowledge, nobody's
> host stack
> treats RFC-1918 space any different from any other global unicast. As
> such, I'm not
> sure what you're getting at here.
> >
> I'm not sure why you think NAT traversal hacks care about which
> addresses are
> private vs. public. If they do, then, they don't work in NAT cases
> where neither
> side of the NAT is within RFC-1918 today, which is a perfectly valid
> use case.

[WES] We have a syntax problem here. People are using private/public as
shorthand for globally unique vs not, and that's confusing the matter. 6to4
is the example that I use, but anything that needs to know if it has a
globally unique address to do some sort of direct connection to a remote
host cares rather a lot. The rub is that typically today people make the
(reasonable) assumption that if it's not in 1918 space, it's globally
unique. Else, not. I would expect that there are a lot of applications that
have something like:

If (RFC1918($address)) 
then nat-hack()
Else function()

/ for more discussion on the matter.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6793 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20110124/326a9050/attachment-0001.bin>

More information about the ARIN-PPML mailing list