[ipv6-wg] IPv6 only network at RIPE 68
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Sat May 17 20:22:29 CEST 2014
Hi, On Sat, May 17, 2014 at 08:13:18PM +0200, Philip Homburg wrote: > In your letter dated Sat, 17 May 2014 12:17:18 +0200 you wrote: > >True. However, keep in mind that this was true for the main ESSID > >"ripemtg" this year too: People with devices that didn't support 5GHz > >had to connect to the secondary ESSID. > > > >We wouldn't be the first conference to do so, either: > >https://fosdem.org/2014/news/2014-02-01-pushing-ipv6/ > > Did a smiley get dropped? > > I know that IPv6 is boring enough that we need to come up with a new > tunneling protocol every year to keep things interesting. But really? The point is: while the RIPE meeting might be able to affort using a 1000 public IPv4 addresses on a conference network, not everyone will be able to do this in the future. So you'll see IPv6+NAT44 or IPv6+NAT64, and it's very good to make this crystal clear to application developers (= fosdem) and networking people (= ripe), so they can see if stuff needs fixing. [..] > So the problems caused by NAT64 can be fixed by doing NAT464. Great. > Then I need to ran NAT on my host and I get double NAT. Good luck trying > to debug networking problems in that setup. Why require IPv4 in the first place? Make sure the destination and the applications in question work over IPv6, done. > So where we now have native IPv4 and dual stack that is supported by all > devices (legacy devices that don't do IPv6 just work as before) the prosoal > is to add a huge amount of protocol complexity, needlessly kill support for > legacy devices. And complain about dual stack devices (like Android) that > just don't support the tunneling protocol of the day. A device that just plain fails to operate on an IPv6-only network has nothing to do with "tunneling protocol of the day". Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/ipv6-wg/attachments/20140517/09346bbf/attachment.sig>
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]