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] IPv6-only network during RIPE 71
- Previous message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
- Next message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benedikt Stockebrand
bs at stepladder-it.com
Wed Nov 4 10:19:30 CET 2015
Hi list, so far I've tried to stay out of this thread and do this face to face in Bucharest, but well... As I've said and written before, the responsibility for the operation of the network is with the NCC technical team, and as such it should really be their call when to change what. And I really appreciate Marco being extra careful with his wording (even if it reads like it's been written by a lawyer:-) On the other hand, I think it is our (as a WG) job to keep nudging them towards what the eventual outcome should be (which is an IPv6 only WLAN with as much IPv4 as there is IPX, SNA, or UUCP...). Maybe we can come to some sort of outline on how to get there during the meeting? After that we can then argue about actual timing without getting lost in the fog of detail. Cheers, Benedikt -- Benedikt Stockebrand, Stepladder IT Training+Consulting Dipl.-Inform. http://www.stepladder-it.com/ Business Grade IPv6 --- Consulting, Training, Projects BIVBlog---Benedikt's IT Video Blog: http://www.stepladder-it.com/bivblog/
- Previous message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
- Next message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]