[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: One socket per AF (Was: 6to4 using ::FFFF:0000:0000/96...)
Jeroen Massar wrote :
> Yes, IPv4-mapped/compat was a good idea, and using it correctly
internally in an application is probably a good move.
Yes. IMHO a nice and clean design.
But using it on
the wire or when presenting it to users is definitely not.
Consider in particular a dual stack site with a private IPv4 space.
Its CPE, which has a NATv4-v4, may also have a NATv6-v4.
If it has one, and if it uses it for outgoing packets that have 0::/64
destinations, IPv6-only hosts on the LAN can establish connections with
IPv6 *AND* IPv4 remote hosts.
IMHO this is nice and clean.
On the other hand, reasons for such a definite statement as "never a
mapped address on any wire" have to be presented.
The reference I know on the subject is
Is there a more recent one which would not be obsoleted ?
Objections of this one as far as I know don't apply to the above example.