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] Re: RFC 1918 in "production networks"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dmitry Burkov
dburk at burkov.aha.ru
Fri Feb 5 06:30:00 CET 2010
On 05.02.10 3:02, Shane Kerr wrote: > -- > Shane > > 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 > > Sorry - but all this discussion reminded me about current situation too (http://labs.ripe.net/content/pollution-18 ) Such vpn solution/services as h a m a c h i, etc (easily can be fpound) intensifely use 5/8, 1/8 and may be some others /8s. Dima
- 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 ]