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 ]
Gert Doering
gert at space.net
Tue Feb 2 17:07:48 CET 2010
Hi, On Tue, Feb 02, 2010 at 04:58:36PM +0100, Shane Kerr wrote: > But the idea that no production networks can use RFC 1918 is a bit > disturbing, because in 2 years or so there won't be any IPv4 addresses > left, and people will be forced to use RFC 1918 addresses. Does that > mean there won't be any IPv4 production networks in 2013? IPv4 is clearly last century's IP protocol... you know that. In 2013, existing IPv4 production networks will continue to work, of course - and new IPv4 deployments will feel massive amounts of pains. And no, I don't consider "new IPv4 networks without available address space" to be "production networks". > My intention is not to make IPv4 available-but-less-useful, but rather > to begin using the same setup that all event organizers will have to use > in the future. Why should we run with the masses? What will be next, "turn off IPv6 because all the other event organizers don't have v6 either"? *shake head* > It's not that bad, really - I use RFC 1918 networks all > the time. I'm using one now (well, except for the 0.01% of the Internet > with working IPv6). The Internet seems to work pretty good with RFC 1918 > + IPv6. This is not "Internet". This is "I go out and pull stuff from servers that are run in real IP Space". Internet means "having machines that are reachable without major contortions on the devices in between" (= NAT forwardings). (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 Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 144438 SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
- 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 ]