- ipv6-wg - mailman.ripe.net

New on RIPE Labs: IPv6 Adoption Statistics: a Comparison of Different Metrics
by Mirjam Kuehne 08 Jun '20

08 Jun '20

Dear colleagues, In this new article on RIPE Labs we're looking at IPv6 adoption statistics provided by various organisations. How far do they match, and if not, why not? https://labs.ripe.net/Members/wilhelm/ipv6-adoption-statistics-a-comparison… Please note the link to the interactive maps that allow for a quick visual comparison of the results. If you have any feedback or additional information about these results, we welcome input in the comment section below the article. Kind regards, Mirjam Kühne RIPE NCC

1 0

Fwd: slaac-renum: New rev of draft-gont-6man-slaac-renum (Fwd: New Version Notification for draft-gont-6man-slaac-renum-08.txt)
by Fernando Gont 19 May '20

19 May '20

Folks, This is one of the documents I presented at the last RIPE IPv6 WG meeting. Thought you might be interested. Thanks! Cheers, Fernando -------- Forwarded Message -------- Subject: slaac-renum: New rev of draft-gont-6man-slaac-renum (Fwd: New Version Notification for draft-gont-6man-slaac-renum-08.txt) Date: Tue, 19 May 2020 03:38:18 -0300 From: Fernando Gont <fgont(a)si6networks.com> To: 6man(a)ietf.org <6man(a)ietf.org> Folks, We have posted a revision of draft-gont-6man-slaac-renum. It is available at: https://www.ietf.org/internet-drafts/draft-gont-6man-slaac-renum-08.txt The main changes incorporated in this version are: * We have eliminated the counter-based algorithm from Section 4.5 Previous revisions of the draft contained two alternative algorithms in Section 4.5: a counter-based algorithm, and a timer-based algorithm. The timer-based algorithm is more robust and simple, so it didn't make sense to keep the counter-based algorithm. (Kudos to Philip Homburg for "pushing" us to improve the algorithm). * Clarified the terminology used in the document This is a rather minor detail. We simply have spelled out that throughout the document, "GUAs" refer to "globally reachable" addresses (as opposed to ULAs). The diff from the last rev is available at: https://tools.ietf.org/rfcdiff?url2=draft-gont-6man-slaac-renum-08.txt As always, your feedback will be appreciated. Thanks! Cheers, Fernando -------- Forwarded Message -------- Subject: New Version Notification for draft-gont-6man-slaac-renum-08.txt Date: Mon, 18 May 2020 23:25:39 -0700 From: internet-drafts(a)ietf.org To: Richard Patterson <richard.patterson(a)sky.uk>, Jan Zorz <jan(a)go6.si>, Fernando Gont <fgont(a)si6networks.com> A new version of I-D, draft-gont-6man-slaac-renum-08.txt has been successfully submitted by Fernando Gont and posted to the IETF repository. Name: draft-gont-6man-slaac-renum Revision: 08 Title: Improving the Robustness of Stateless Address Autoconfiguration (SLAAC) to Flash Renumbering Events Document date: 2020-05-18 Group: Individual Submission Pages: 24 URL: https://www.ietf.org/internet-drafts/draft-gont-6man-slaac-renum-08.txt Status: https://datatracker.ietf.org/doc/draft-gont-6man-slaac-renum/ Htmlized: https://tools.ietf.org/html/draft-gont-6man-slaac-renum-08 Htmlized: https://datatracker.ietf.org/doc/html/draft-gont-6man-slaac-renum Diff: https://www.ietf.org/rfcdiff?url2=draft-gont-6man-slaac-renum-08 Abstract: In renumbering scenarios where an IPv6 prefix suddenly becomes invalid, hosts on the local network will continue using stale prefixes for an unacceptably long period of time, thus resulting in connectivity problems. This document improves the reaction of IPv6 Stateless Address Autoconfiguration to such renumbering scenarios. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat

1 0

IPv4 Flag Day
by Niall O'Reilly 15 May '20

15 May '20

In https://ripe80.ripe.net/archives/chat/88/ 13:23 < luna> https://ipv4flagday.net/ 13:24 < chrbre_AS206228> https://github.com/ipviolations/ipv4flagday/issues Thanks, Luna and Christian, for pointing me at this, which is a fine idea. I’ve added an issue for false alarm when zone apex has no address record of either kind. Niall

4 5

RIPE 80 IPv6 wg session Wilhelms DSL broke, some unanswered questions
by Jetten Raymond 14 May '20

14 May '20

Hello All, Thank you all for watching the IPv6 WG virtually, at the latest minutes of Wilhelms presentation Q&A his dsl connection unfortunately went down, there were still some questions in the buffer, could you Wilhelm comment yet on these ? Any tips to get app developers on board to develop IPv6 enabled apps? It's not uncommon for companies to exclude IPv6 from minimum viable product as its "too hard" Could disabling SLAAC and better DHCPv6 support (eg in mobile devices) help the deployment? It would help with some migrations from IPv4 to IPv6 I think. (Mark Scholten / asking for myself) Rgds, Ray For Internal Use Only

8 8

Re: [ipv6-wg] RIPE 80 IPv6 wg session Wilhelms DSL broke, some unanswered questions
by JORDI PALET MARTINEZ 14 May '20

14 May '20

My view on the 2nd one: I think SLAAC is sufficient! I guess unless Android change their mind and develops/enables DHCPv6, this will not be useful. Regards, Jordi @jordipalet El 14/5/20 13:59, "ipv6-wg en nombre de Jetten Raymond" <ipv6-wg-bounces(a)ripe.net en nombre de raymond.jetten(a)elisa.fi> escribió: Hello All, Thank you all for watching the IPv6 WG virtually, at the latest minutes of Wilhelms presentation Q&A his dsl connection unfortunately went down, there were still some questions in the buffer, could you Wilhelm comment yet on these ? Any tips to get app developers on board to develop IPv6 enabled apps? It’s not uncommon for companies to exclude IPv6 from minimum viable product as its “too hard” Could disabling SLAAC and better DHCPv6 support (eg in mobile devices) help the deployment? It would help with some migrations from IPv4 to IPv6 I think. (Mark Scholten / asking for myself) Rgds, Ray For Internal Use Only ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

1 0

RIPE80 IPv6 WG Session
by Jen Linkova 08 May '20

08 May '20

Dear IPv6 Enthusiasts, The agenda for IPv6 WG at RIPE80 has been published: https://ripe80.ripe.net/programme/meeting-plan/ipv6-wg/ The instructions on how to attend the RIPE80 sessions could be found at https://ripe80.ripe.net/attend/how-to-participate/ See you there! -- SY, Jen Linkova aka Furry on behalf of IPv6 WG Chairs.

1 0

RIPE80 Call for Presentations
by Jen Linkova 01 May '20

01 May '20

Dear IPv6 Enthusiasts, As you might have noticed, RIPE80 is going to be a virtual meeting. So IPv6 WG is going to meet on Thu, May 14th, 13:00 - 13:45 CEST (Don't forget to convert to your local timezone). We are looking for talks. COVID-19 does not seem to be a reason good enough to slow down IPv6 deployments. I suspect it might be a reason for accelerate them, actually. So stories about 'IPv6 in the Time of Cholera' (or any other talks about IPv6) are appreciated. Please send your suggestions (the title, short summary, how much time you need) to ipv6-wg-chair(a)ripe.net. Thanks, -- SY, Jen Linkova aka Furry on behalf of IPv6 WG Chairs.

9 11

Fwd: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum
by Fernando Gont 04 Apr '20

04 Apr '20

Hello, folks, v6ops is WGLC'ing one of the documents (https://tools.ietf.org/html/draft-ietf-v6ops-cpe-slaac-renum-01) we have authored to improve the reaction of SLAAC to renumbering events. This document contains recommendations for Customer Edge Routers. For background, you may want to consult: https://tools.ietf.org/html/draft-ietf-v6ops-slaac-renum-01 If you have any comments/feedback, please do let us know. If possible, on the v6ops list (https://www.ietf.org/mailman/listinfo/v6ops) Thanks! Cheers, Fernando -------- Forwarded Message -------- Subject: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum Date: Mon, 30 Mar 2020 15:47:14 +0000 From: Ron Bonica <rbonica=40juniper.net(a)dmarc.ietf.org> To: v6ops(a)ietf.org <v6ops(a)ietf.org> Folks, This message initiates a WG Last Call on draft-ietf-v6ops-cpe-slaac-renum. Please submit comments by April 13, 2020. Fred and Ron Juniper Business Use Only -- Fernando Gont e-mail: fernando(a)gont.com.ar || fgont(a)si6networks.com PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1 -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

3 3

New on RIPE Labs: What’s the Deal with IPv6 Link-Local Addresses?
by Philip Homburg 11 Mar '20

11 Mar '20

Dear colleagues, Stephen Strowes, Emile Aben and I published a new article on RIPE Labs on how link-local addresses in IPv6, and specifically the '%eth0'-part of link-local addresses, can have an impact on RIPE Atlas measurements. https://labs.ripe.net/Members/philip_homburg/whats-the-deal-with-ipv6-link-… We think this will be an interesting read for network operators and others who are using RIPE Atlas measurement data or are interested in IPv6. Kind regards, Philip Homburg RIPE NCC

2 1

Can ripemtg SSID promotes NAT64 (at least) during RIPE80 ? :)
by Willy Manga 28 Feb '20

28 Feb '20

Hello, I was looking the trends of the last FOSDEM [1] and I recalled discussions before and during RIPE79. I humbly think you could give a try ... 1. https://blogs.cisco.com/getyourbuildon/fosdem-2020-trends-and-analysis -- Willy Manga @ongolaboy https://ongola.blogspot.com/

5 4