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/ipv6-wg@ripe.net/
[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] How polluted is 1/8?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Francis Dupont
Francis.Dupont at fdupont.fr
Sat Feb 6 14:29:50 CET 2010
In your previous mail you wrote:
The specific issue raised was for VPNs, so it's more like this:
=> it is not th standard VPN case but a particular case named
the road warrior VPN. Fortunately for obvious security reasons
the routing system is in general fully overwritten to disallow
"local" communications so the address collision is not an issue.
p.s. Note that 1.1.1.1 and 1.2.3.4 chosen as example addresses in honor
of this research: http://labs.ripe.net/content/pollution-18
=> I saw that: funny (if you have no prefix in 1.0.0.0/8).
Thanks
Francis.Dupont at fdupont.fr
- Previous message (by thread): [ipv6-wg] Re: RFC 1918 in "production networks"
- Next message (by thread): [ipv6-wg] How polluted is 1/8?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]