On 2/14/12 2:35 PM, Randy Bush wrote:
what silliness. it will be used as rfc 1918 space no matter what the document
says.
[...]
any thought that this is not just adding to rfc 1918 is pure bs.
Of course it will be used as 1918 space. That's not the point of the text.
The text is saying, "You could read 1918 to say that we somehow promised
that you would never be connected to a network run by someone other than
yourself and see 1918 addresses on it. That's not an entirely
intelligent reading, but we see how you can read it that way. So, if you
built yourself a device where it isn't able to deal with 1918 addresses
on its 'outside' interface that you were using on the 'inside'
interfaces, we could see how that might happen. It was not at all smart
of you to build your device that way, but you probably were technically
within spec. Now we're adding some address space to the pool. It's not
global and it's not routable, just the same as 1918 space. But we're
letting you know right now: You *will* see these addresses on networks
that you don't run. If you want to use this space the way that you used
1918 space, peachy, but understand that if you're unable to deal with
these addresses duplicating ones you're using, your device is toast.
Deal with it."
Any thought that the text is saying something more than this is nonsense.
pr
--
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf