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 ]
Marc Manthey
marc at let.de
Thu Feb 4 21:20:30 CET 2010
Am 04.02.2010 um 20:59 schrieb Francis Dupont: > 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. +1 thanks Francis regards Marc -- Les enfants teribbles - research / deployment Marc Manthey- Vogelsangerstrasse 97 50823 Köln - Germany Tel.:0049-221-29891489 Mobil:0049-1577-3329231 project : http://opencu.org blog: http://macbroadcast.org Opinions expressed may not even be mine by the time you read them, and certainly don't reflect those of any other entity (legal or otherwise). Please note that according to the German law on data retention, information on every electronic information exchange with me is retained for a period of six months.
- 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 ]