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] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)

Previous message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
Next message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)

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

Dmitry Burkov dburk at burkov.aha.ru
Tue Feb 2 19:43:48 CET 2010

On 02.02.10 19:07, Gert Doering wrote:
>
> (despite the religious aspects, there's a purely practical aspect - if
> you force RIPE attendees into RFC1918 space, you're going to kill VPN
> connects for those poor souls that have a home network in the *same*
> RFC1918 address range.  Which will break almost all VPN clients out there.)
>    
Gert,
seems you dramatize the situation
- there are more issues - to be honest.
The situations can be more complex.
But  I don't see any specific differences with access to corporate 
intranets and
still had no  problem in such mixed enviroments using appropriative 
tools for years.

Dima
> Gert Doering
>          -- NetMaster
>

Previous message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
Next message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)

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

[ ipv6-wg Archives ]