<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="FI" link="#0563C1" vlink="#954F72"> <div class="WordSection1"> Dear Working group,<o:p></o:p> <o:p> </o:p> Below are the draft minutes from ripe 81.<o:p></o:p> <o:p> </o:p> If you have any comments or remarks please let us know by replying to this email.<o:p></o:p> A big thanks to Nikolas for doing the scribe.<o:p></o:p> <o:p> </o:p> If we do not hear any comments these minutes will be published in about 2 weeks from now.<o:p></o:p> <o:p> </o:p> Rgds,<o:p></o:p> <o:p> </o:p> Ray, Jen, Benedikt.<o:p></o:p> <o:p> </o:p> <div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm"> <o:p> </o:p> </div> <o:p> </o:p> IPv6 Working Group Minutes - RIPE 81<o:p></o:p> Date: 29 October 2020, 13:00 - 13:45<o:p></o:p> WG Chairs: Benedikt Stockebrand, Jen Linkova, Raymond Jetten<o:p></o:p> Scribe: Nikolas Pediaditis<o:p></o:p> Status: Draft<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Welcome - Agenda Bashing <o:p></o:p> The Chairs <o:p></o:p> <o:p></o:p> The minutes of IPv6 Working Group session from RIPE 80 were accepted as final. There were no questions or comments.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> RIPE554-bis - Tim Chown <o:p></o:p> <o:p> </o:p> The presentation is available here: <o:p> </o:p> <a href="https://ripe81.ripe.net/presentations/58-ripe81-ipv6wg-ripe554bis-final.pdf">https://ripe81.ripe.net/presentations/58-ripe81-ipv6wg-ripe554bis-final.pdf</a><o:p></o:p> <o:p> </o:p> Dmitry Serbulov (Alpha Net Telecom LTD) asked if it would be possible to share material with attendees prior to the start of each session.<o:p></o:p> <o:p> </o:p> Raymond Jetten suggested that he should join the IPv6 WG mailing list.<o:p></o:p> <o:p> </o:p> Bringing IPv6 Everywhere - Nico Schottelius<o:p></o:p> <o:p> </o:p> The presentation is available here:<o:p></o:p> <a href="https://ripe81.ripe.net/presentations/73-ripe81-bringing-ipv6-everywhere.pdf">https://ripe81.ripe.net/presentations/73-ripe81-bringing-ipv6-everywhere.pdf</a><o:p></o:p> <o:p> </o:p> Ondrej Caletka (RIPE NCC) asked if connectivity will break if the host network becomes dual-stacked, or at worst, if the host network becomes IPv6-only.<o:p></o:p> <o:p> </o:p> Nico replied that it wouldn’t. IPv4 connectivity would still be available, and IPv6 would be added to it. <o:p></o:p> <o:p> </o:p> Kurt Kayser (BDBOS) asked if geo-IP will always show that the VIIRB-users are in Switzerland.<o:p></o:p> Nico Schottelius replied that at the moment, yes. And there is a bracket opening as soon as they are able to talk better to the RIPE API to change the registration of the /48 networks. It will be easy to actually assign the network to your location. <o:p></o:p> <o:p> </o:p> Christoph Berkemeier (DB Station&Service AG) asked if the IPv6 distribution is stateless only.<o:p></o:p> <o:p> </o:p> Nico confirmed that it is stateless at the moment but that could be changed if desired.<o:p></o:p> <o:p> </o:p> Veronica McKillop (UK IPv6 Council) asked where the device is being manufactured. <o:p></o:p> <o:p> </o:p> Nico replied that it's manufactured in China and shipped to and configured in Switzerland.<o:p></o:p> <o:p> </o:p> Dmitry Serbulov (Alpha Net Telecom LTD) asked if open source software is used between the device and the server it connects to.<o:p></o:p> <o:p> </o:p> Nico said that the software used, WireGuard and OpenWRT at the moment, are fully open source.<o:p></o:p> <o:p> </o:p> Vesna Manojlovic (RIPE NCC) mentioned that a hackathon about RIPE Atlas software probes is taking place in November. She asked if Nico would be interested in joining and seeing how they could combine his router with RIPE Atlas software probes if possible. <o:p></o:p> <o:p> </o:p> Nico replied that it would be a really cool project. <o:p></o:p> <o:p> </o:p> Christoph Berkemeier (DB Station&Service AG) asked if there is a virtual appliance to enable legacy hosters.<o:p></o:p> <o:p> </o:p> Nico replied that it builds on top of your existing IPv4 network so everything that's legacy continues to work. It's not a replacement. The nice thing about IPv6 is that although it is incompatible to IPv4 this also means that it runs in parallel to the existing infrastructure, allowing the legacy network to continue to work. <o:p></o:p> <o:p> </o:p> <o:p> </o:p> Recent Improvements in IPv6 Addressing - Fernando Gont<o:p></o:p> <o:p> </o:p> The presentation is available here:<o:p></o:p> <a href="https://ripe81.ripe.net/presentations/72-fgont-ripe81-ipv6-wg-ipv6-addressing.pdf">https://ripe81.ripe.net/presentations/72-fgont-ripe81-ipv6-wg-ipv6-addressing.pdf</a><o:p></o:p> <o:p> </o:p> Osamah Barakat (Siemens AG) asked if Windows 10 supports the latest IPv6 RFC or it is only Linux-based OS that support seen in the slide.<o:p></o:p> <o:p> </o:p> Fernando Gont replied that it’s surprising that they don’t support RFC 7217 as one the authors worked for Microsoft. They also haven’t implemented the update of 4941 either. However, he was less concerned about 4941, as compared to the support for 7217, as it has not been published as an RFC.<o:p></o:p> <o:p> </o:p> <div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm"> End of the session.<o:p></o:p> </div> <o:p> </o:p> <o:p></o:p> <o:p> </o:p> </div> </body> </html>