- ipv6-wg - mailman.ripe.net

A common problem with SLAAC in "renumbering" scenarios
by Fernando Gont 31 Jan '19

31 Jan '19

Folks, We have posted a new I-D discussing a problem that can arise in typical deployment scenarios where the CPE obtains a prefix via DHCPv6-PD and advertises a prefix on the LAN side. We also propose a solution to the aforementioned problem. Our draft is available at: https://tools.ietf.org/html/draft-gont-6man-slaac-renum The Abstract is: A very common IPv6 deployment scenario is that in which a CPE employs DHCPv6 Prefix Delegation to obtain an IPv6 prefix, and at least one prefix from within the leased prefix is advertised on a local network via SLAAC. In scenarios where e.g. the CPE crashes and reboots, nodes on the local network continue using outdated prefixes which result in connectivity problems. This document analyzes this problem scenario, and proposes workarounds. Any comments will be welcome. Thanks! Cheers, -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

1 0

IPv6 Working Group presentations for RIPE78
by Jetten Raymond 16 Jan '19

16 Jan '19

Hello All, The RIPE 78 meeting will take place will take place in Reykjavik Iceland from 20-24 May 2019. https://ripe78.ripe.net/ The IPv6 WG session will most likely be on Thursday after lunch. (still subject to change). Would you like to present at our WG session, and have a subject that would be of interest on IPv6? We, the IPv6 WG co-chairs, would like to invite you to submit your presentation proposals, including a brief description of the content and the time you would need. Please send them directly to us: ipv6-wg-chairs at ripe.net<https://lists.ripe.net/mailman/listinfo/ipv6-wg> . Once we start to make the final agenda, we will let you know if you are selected or not. Please be aware of the following: Due to potential technical issues, presenters/panelists should be physically present at the RIPE Meeting. RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. All sessions will be recorded and broadcasted, and will be publicly available afterwards, so make sure you own the copyrights of all content. See you in Reykjavik, Jen, Benedikt, Ray

1 0

New on RIPE Labs: Answering IPv6 Misconceptions
by Mirjam Kuehne 21 Dec '18

21 Dec '18

Dear colleagues, Please read these two new RIPE Labs articles by Jen Linkova where she responds to some common IPv6 misconceptions that are used as reasons for not deploying IPv6: https://labs.ripe.net/Members/jen_linkova/ipv6-misconceptions-it2019s-fake-… https://labs.ripe.net/Members/jen_linkova/ipv6-misconceptions-it2019s-fake-… Kind regards, Mirjam Kühne RIPE NCC

1 0

Report from ITU Study Group 20 meeting 3-13 December 2018 in Wuxi, China
by Marco Hogewoning 14 Dec '18

14 Dec '18

Dear colleagues, The meeting of ITU Study Group 20 in Wuxi, China, just finished and I’d like to give you a brief report on the discussions of the work on a draft Recommendation on IPv6 addressing. This meeting was the group's first face-to-face meeting since our discussion of the draft Recommendation at RIPE 77 in May 2018 and the July 2018 draft review deadline. The RIPE community's comments were brought to the meeting as a Liaison Statement. Several other parties also submitted their own Contributions, including the RIPE NCC in its role as an ITU Sector Member. The proposal in our Contribution, with reference to earlier discussions and your review, was to discontinue this particular Work Item. The United States Government and ARIN made Contributions along similar lines, seeking to stop the work developing this particular Recommendation. This position was also supported by the United Kingdom, Canada, Germany and several sector members. I’d like to highlight that both in their Contribution and interventions, the US expressed their gratitude to the RIPE community for their extensive review and feedback on the draft Recommendation. The main author of the draft submitted a Contribution with their account of our discussions at RIPE 77 and the review process, as well as a joint Contribution with the Beijing University for Post and Telecommunications providing a case study of an IPv6 address plan. Having taken all of these contributions and interventions into consideration, the focus of the meeting discussion was on whether or not the work should continue. Unfortunately, the RIPE community’s feedback was only taken into consideration as a high-level conclusion that the current text does not meet the technical standards expected, and the actual text of the draft was not reviewed or revised during this meeting. Unable to reach consensus, the question of whether the work should continue was deferred upwards to the meeting of the Working Party and finally to the closing plenary. During the closing plenary, the Chairman of Study Group 20 proposed continuing the work for at least one more meeting on the premise that the draft’s main author would come back with a Contribution addressing the concerns raised with the current draft. He emphasised that the work item would be dropped unless there were contributions and agreement to advance the text at the next meeting. The RIPE NCC accepted the Chairman’s proposal as a constructive way forward. We look forward to the contributions at the next meeting with the expectation that they will address the concerns raised during your review. We would like to thank you again for the constructive comments raised during the review process. We would also like thank the Question’s rapporteur, associate rapporteur and the Study Group’s management team for all their time and assistance, and of course all the member states and sector members that participated in this discussion. The next meeting of Study Group 20 is scheduled to take place in mid-April, in Geneva, Switzerland. Regards, Marco Hogewoning RIPE NCC

5 7

Re: [ipv6-wg] [cooperation-wg] Fwd: Report on ITU Study Group 20 meeting 3-13 December 2018
by Jim Reid 14 Dec '18

14 Dec '18

> On 14 Dec 2018, at 02:44, Marco Hogewoning <marcoh(a)ripe.net> wrote: > > Please find below a report on the meeting of ITU Study Group 20, that I have just shared with the IPv6 Working Group. Marco, as a fellow traveller on the SG20 bus, I thank you for this summary and all the hard work you did in Wuxi and in the preparations for that meeting. You did an excellent job and were a great ambassador for both RIPE and the NCC. You represented our interests very effectively. I appreciate that and hope everyone else here does too.

2 1

IPv6 transition mechanisms used around the world
by Yannis Nikolopoulos 30 Nov '18

30 Nov '18

Hello all, this probably hasn't been posted here so for everyone's info, there's a google spreadsheet created by IETF's Lee Howard, with information about transition mechanisms used by ISPs around the world. Obviously, anyone can edit and the more people add info, the more meaningful and useful it can become https://docs.google.com/spreadsheets/d/1ksOoWOaRdRyjZnjLSikHf4O5L1OUTNOO_7N… cheers, Yannis

1 0

New on RIPE Labs: IPv6 for Governments and Enterprises
by Mirjam Kuehne 23 Nov '18

23 Nov '18

Dear colleagues, Please find two new articles by Jordi Palet on RIPE Labs: IPv6 for Governments and Enterprises – a Case Study https://labs.ripe.net/Members/jordipaletm/ipv6-for-governments-and-enterpri… and Twelve Steps to Enable IPv6 in Government and Enterprise Networks https://labs.ripe.net/Members/jordipaletm/twelve-steps-to-enable-ipv6-in-go… Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: 10 Years of IPv6 Stakeout!
by Mirjam Kuehne 13 Nov '18

13 Nov '18

Dear colleagues, Please read on RIPE Labs how Torbjörn Eklöv is encouraging the municipalities in Sweden to deploy IPv6: https://labs.ripe.net/Members/teklov/10-years-of-ipv6-stakeout Kind regards, Mirjam Kühne RIPE NCC

1 0

IPv6 ipsec tunnel server on linux server
by Michael Hock 06 Nov '18

06 Nov '18

Hello, I'm trying to set up an ipsec server on a linux machine. The connection between clients and server should be IPv6 only but also needs to transport IPv4 packets. However, the linux kernel doesn't seem to support a feature which is required to transport IPv4 packets within an IPv6 ipsec connection, as shown here: https://wiki.strongswan.org/issues/939 Does maybe one of you know how to transport IPv4 packets in an IPv6 ipsec connection, or do we need to wait for the linux kernel to support this feature? Because this stops me from switching to IPv6 ipsec connections and I would like to reduce the usage of IPv4 as much as possible ... Sorry if this might be off-topic from the general IPv6 WG topics, but I thank you in advance for your time and answers! Best regards, Michael Hock

4 7

ipv6 francais: If you can read French...
by Jen Linkova 19 Oct '18

19 Oct '18

Very good document about IPv6 adoption in France (thanks Gordon for sharing!): https://www.arcep.fr/cartes-et-donnees/nos-publications-chiffrees/transitio… https://www.arcep.fr/fileadmin/reprise/observatoire/ipv6/Arcep_Barometre_20… -- SY, Jen Linkova aka Furry

2 1