May 2020 - ipv6-wg - mailman.ripe.net

Join us for the RIPE NCC Educa::IPv6-only
by Ondřej Caletka 08 Jun '20

08 Jun '20

Dear IPv6 working group, You are invited to join us for a deep-dive into an IPv6-only world! We’re hosting the fourth edition of a RIPE NCC::Educa - a one day online event, bringing together experts from around the world to take a deeper look at topics of interest. Registration is free. To mark the anniversary of World IPv6 Launch Day, we’re hosting the RIPE NCC::Educa IPv6-only on Monday, 8 June from 10:00 UTC+2 onwards. Expert presenters will talk about what it means to run IPv6-only data centres, ISPs and enterprises, among other topics. You can view the agenda at: https://www.ripe.net/support/training/ripe-ncc-educa/ripe-ncc-educa-ipv6-20… Register at: https://www.eventbrite.nl/e/ripe-ncceduca-ipv6-only-tickets-106761053184 We hope to see you online soon! Best regards, Ondřej Caletka RIPE NCC

16 43

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