November 2015 - ipv6-wg - mailman.ripe.net

New on RIPE Labs: Examining IPv6 Performance
by Mirjam Kuehne 26 Nov '15

26 Nov '15

Dear colleagues, For those of you who missed Geoff Huston's presentation during the IPv6 WG at RIPE 71, read it in more detail on RIPE Labs: https://labs.ripe.net/Members/gih/examining-ipv6-performance Kind regards, Mirjam Kuehne RIPE NCC

1 0

ripemtg-nat64 network at RIPE71: complain here ;)
by Jen Linkova 19 Nov '15

19 Nov '15

Hi guys, As you might have noticed there is a NAT64 SSID. This thread is for complains about that network. Please use ripemtg-nat64 SSID. Please let us know if smth goes wrong. if you have network issues while using that SSID and switching to dual-stack one fixes the problem - please reply to this thread (indeed you can create a new one, I was just thinking that keeping everything in one thread might make our life easier but I might be wrong...). -- SY, Jen Linkova aka Furry

15 29

New on RIPE Labs: Lost Stars: Why Operators Switch off IPv6
by Mirjam Kuehne 18 Nov '15

18 Nov '15

Dear colleagues, One of the measurements that we have been running for a long time is IPv6 RIPEness, where we measure the IPv6 activity of the RIPE NCC members. We award members with stars if they (for example) announce their IPv6 allocation in the global routing table. We discovered that 460 RIPE NCC members had recently stopped announcing their IPv6 prefix and asked them why. Please find the results on RIPE Labs: https://labs.ripe.net/Members/nathalie_nathalie/lost-stars-why-operators-sw… Nathalie Trenaman will present this in the IPv6 working group at RIPE 71. Kind regards, Mirjam Kuehne RIPE NCC

1 0

IPv6-only network during RIPE 71
by Ondřej Caletka 10 Nov '15

10 Nov '15

Dear WG, as the RIPE 71 approaches, I would like to revive discussion about the IPv6-only network during meeting, that has been kindly provided since RIPE 67. I think the technology is mature enough to be provided as a regular RIPE NCC service during the meeting - that means regular network name and, most important, a password that is propagated in the same way the normal Wi-Fi network password is. This is especially important for the one third of newcomers that have had a big troubles learning the password of the IPV6ONLYEXP network. After RIPE 70, I proposed a "drastic" approach [1], renaming the dual-stack meeting network to -legacy and promote the NAT64 network as the default. This is the same way they do it on FOSDEM since 2014 [2]. But maybe we could try a slow start first, keeping the dual-stacked network the default and offering the NAT64 network with some suffix like -v6only. Any ideas? -- Ondřej Caletka CESNET [1]: https://www.ripe.net/ripe/mail/archives/ipv6-wg/2015-May/002632.html [2]: https://archive.fosdem.org/2015/news/2015-01-31-ipv6-only-again/

22 38

Re: [ipv6-wg] RIPE Atlas and NAT64 (Was: IPv6-only network during RIPE 71)
by Jen Linkova 03 Nov '15

03 Nov '15

On Tue, Nov 3, 2015 at 3:18 PM, Gert Doering <gert(a)space.net> wrote: >> RIPE Atlas probe is a host. It should not care much if it's traffic is >> going via NAT64 box or not. > > Actually detecting NAT64 and flagging as such, and being able to run > tests on a group of NAT64-hidden probes might add value... I think there is a dirty hack to do it now: run a measurements from v6-enabled probes to v4-only host, check the results for the destination address they were using. But I agree, it would be nice to get a list of probes behind NAT64 w/o wasting time and credits ;) -- SY, Jen Linkova aka Furry

2 1

Re: [ipv6-wg] ipv6-wg Digest, Vol 50, Issue 3
by Timothy Roy 03 Nov '15

03 Nov '15

I agree with all on this one, It is time to rock and roll with IPV6 and as was stated earlier, if someone does not like they can choose the other one. I think it will be a boost for IPV6 (if all goes well). -----Original Message----- From: ipv6-wg [mailto:ipv6-wg-bounces@ripe.net] On Behalf Of ipv6-wg-request(a)ripe.net Sent: 03 November 2015 15:00 To: ipv6-wg(a)ripe.net Subject: ipv6-wg Digest, Vol 50, Issue 3 Send ipv6-wg mailing list submissions to ipv6-wg(a)ripe.net To subscribe or unsubscribe via the World Wide Web, visit https://www.ripe.net/mailman/listinfo/ipv6-wg or, via email, send a message with subject or body 'help' to ipv6-wg-request(a)ripe.net You can reach the person managing the list at ipv6-wg-owner(a)ripe.net When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6-wg digest..." Today's Topics: 1. Re: IPv6-only network during RIPE 71 (Sander Steffann) 2. Re: IPv6-only network during RIPE 71 (Sander Steffann) ---------------------------------------------------------------------- Message: 1 Date: Tue, 3 Nov 2015 11:54:33 +0100 From: Sander Steffann <sander(a)steffann.nl> To: Shane Kerr <shane(a)time-travellers.org> Cc: Marco Hogewoning <marcoh(a)marcoh.net>, "ipv6-wg(a)ripe.net IPv6" <ipv6-wg(a)ripe.net> Subject: Re: [ipv6-wg] IPv6-only network during RIPE 71 Message-ID: <72AAB357-AD25-4B1C-8BAC-4CC6F70836AE(a)steffann.nl> Content-Type: text/plain; charset=us-ascii Hi Shane, Op 3 nov. 2015, om 03:21 heeft Shane Kerr <shane(a)time-travellers.org> het volgende geschreven: > tl;dr Don't so cautious. Removing the "experimental" tag from IPv6 won't > ruin the RIPE meeting. +1 Well said :) Sander ------------------------------ Message: 2 Date: Tue, 3 Nov 2015 11:58:07 +0100 From: Sander Steffann <sander(a)steffann.nl> To: Philip Homburg <pch-ripeml(a)u-1.phicoh.com> Cc: "ipv6-wg(a)ripe.net IPv6" <ipv6-wg(a)ripe.net> Subject: Re: [ipv6-wg] IPv6-only network during RIPE 71 Message-ID: <C18918DD-63AC-4966-92C1-9CF78822E0FD(a)steffann.nl> Content-Type: text/plain; charset=us-ascii > (Can't wait for a request for Atlas to support NAT64, that's going to > be > interesting) Request! Cheers, Sander PS (in Dutch): iets met slapende honden wakker maken ;) End of ipv6-wg Digest, Vol 50, Issue 3 **************************************

1 0

: IGF Best Practice Forum document review “Creating an Enabling Environment for IPv6 Adoption"
by Marco Hogewoning 03 Nov '15

03 Nov '15

Dear colleagues, As mentioned in my email on 24 August, over the past few months we have been working on a project to document some high-level best practices on IPv6 adoption, titled “Creating an Enabling Environment for IPv6 Adoption.” This work is part of the Internet Governance Forum (IGF) inter-sessional efforts to create more tangible outcomes for the IGF by collecting and documenting best practices on a variety of topics. With the IGF 2015 taking place next week from 10-13 November, this project is drawing to a close and the final draft document is now published and open for review. The document is available at: http://review.intgovforum.org/?p=3987 You can use this same website to submit any comments. Comments will close on 14 November 2015, after which a final version of the document that incorporates any comments received will be released and made available for distribution. On day two of the IGF (11 November) from 09:00-10:30 local time (UTC-3) there will also be a session in which the main contributors will discuss the document and its main conclusions on what they believe are enabling factors that contribute to IPv6 adoption. Just like all sessions at the IGF, remote participation for this session will be available via http://www.intgovforum.org. Please follow the instructions that will be posted on that website. Finally I would like to thank all the RIPE community members that have contributed to this project, by responding to our survey or by making direct contributions on the mailing list or conference calls. Regards, Marco Hogewoning RIPE NCC - External Relations

1 0