This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[ipv6-wg] Re: RFC 1918 in "production networks"

• Previous message (by thread): [ipv6-wg] Re: RFC 1918 in "production networks"
• Next message (by thread): [ipv6-wg] Re: RFC 1918 in "production networks"

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Francis Dupont Francis.Dupont at fdupont.fr
Thu Feb 4 20:59:06 CET 2010

I'd like to kill this private address collision issue: at the
exception of some rare protocols designed to handle this case,
the schema:
 private-address - NAT - Internet - NAT - private-address
simply doesn't allow free communication between both end-points.
So it doesn't matter the private addresses collide...

Regards

Francis.Dupont at fdupont.fr

PS: note the key point is a private address is not routable in the
Internet, i.e., you can change "private address" by "not routed"
and all considerations still apply.

• Previous message (by thread): [ipv6-wg] Re: RFC 1918 in "production networks"
• Next message (by thread): [ipv6-wg] Re: RFC 1918 in "production networks"

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]