<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=iso-8859-2"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="FI" link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Dear list members, here are the draft minutes from RIPE 85 IPv6 wg.<o:p></o:p> <o:p> </o:p> Please share your comments or remarks to the list so they can be adjusted.<o:p></o:p> <o:p> </o:p> The minutes will otherwise be published in two weeks<o:p></o:p> <o:p> </o:p> <o:p> </o:p> IPv6 Working Group Minutes - RIPE 85<o:p></o:p> Wednesday, 26 Oct 2022, 12:00-13:00 (UTC+2)<o:p></o:p> <o:p> </o:p> WG co-Chairs: Benedikt Stockebrand, Raymond Jetten<o:p></o:p> Scribe: Oleg Muravskiy<o:p></o:p> Status: Draft <o:p></o:p> <o:p> </o:p> Welcome, Etiquette, Approving Minutes, Co-Chair Selection<o:p></o:p> IPv6 Working Group Co-Chairs<o:p></o:p> <o:p> </o:p> Raymond reminded participants about the Code of Conduct. The RIPE 84 minutes were approved. <o:p></o:p> <o:p> </o:p> Benedict announced that Raymond's term as co-chair had ended, but that he was happy to continue in that role. There were no further nominations or objections, so Raymond was re-appointed as co-chair.<o:p></o:p> <o:p> </o:p> Path Tracing<o:p></o:p> Pablo Camarillo, Cisco Systems<o:p></o:p> <o:p> </o:p> This presentation is available at: <a href="https://ripe85.ripe.net/wp-content/uploads/presentations/76-20221026-RIPE85-SR-PathTracing.pdf">https://ripe85.ripe.net/wp-content/uploads/presentations/76-20221026-RIPE85-SR-PathTracing.pdf</a><o:p></o:p> <o:p> </o:p> Pablo described the recent implementation of an addition to the IPv6 packet header extension that records the path of packets in ECMP networks and presented the use cases that were enabled by this feature.<o:p></o:p> <o:p> </o:p> Leandro Bertholdo, University of Twente, asked how this addition was different from the IPv4 registration option.<o:p></o:p> <o:p> </o:p> Pablo replied that the main difference in this approach was that they recorded the information at the line speed of the basic packet forwarding pipeline, and used only 3 bytes for each node.<o:p></o:p> <o:p> </o:p> Leandro asked the presenter if they recorded an ID of the router that the packet passed. <o:p></o:p> Pablo replied that they recorded a sequence of interface ID. <o:p></o:p> Leandro asked if it was for the input interface or the output. <o:p></o:p> Pablo replied that they recorded an ID of the output interface at each one of the routers<o:p></o:p> <o:p> </o:p> Alexander Azimov, Yandex, asked if this would work in the MPLS core. Pablo said that this was possible, but that for the moment it was only implemented for IPv6.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Open Source NAT64 Implementations<o:p></o:p> Nico Schottelius, ungleich<o:p></o:p> <o:p> </o:p> This presentation is available at: <a href="https://ripe85.ripe.net/wp-content/uploads/presentations/74-ripe85-open-source-nat64.pdf">https://ripe85.ripe.net/wp-content/uploads/presentations/74-ripe85-open-source-nat64.pdf</a><o:p></o:p> <o:p> </o:p> Nico showed a comparison of different open source implementations of NAT64, and asked the audience to provide more feedback and point out implementations they missed.<o:p></o:p> <o:p> </o:p> Jan �or�, 6connect, asked Nico if they had tried a VPP implementation as it was very fast.<o:p></o:p> <o:p> </o:p> Nico said that he hadn’t but that it was nice to know about it. <o:p></o:p> <o:p> </o:p> Urban Suhadolnik, University of Ljubljana, asked if the presenter knew of any CLAT implementation, possibly for Windows, as the user-space implementation of CLAT was missing.<o:p></o:p> <o:p> </o:p> Nico said that he couldn’t answer the question as he was not familiar with this the topic. <o:p></o:p> <o:p> </o:p> Deploying IPv6-Mostly Access Networks<o:p></o:p> Ond�ej Caletka, RIPE NCC<o:p></o:p> <o:p> </o:p> This presentation is available at: <a href="https://ripe85.ripe.net/wp-content/uploads/presentations/9-RIPE85-Deploying_IPv6_mostly.pdf">https://ripe85.ripe.net/wp-content/uploads/presentations/9-RIPE85-Deploying_IPv6_mostly.pdf</a><o:p></o:p> <o:p> </o:p> Ond�ej presented an "IPv6-mostly" network that was implemented at this RIPE Meeting, which combined IPv6 functionality only for devices that supported it, and traditional dual-stack for other devices, all in the same network.<o:p></o:p> <o:p> </o:p> Leonard Wagner, IN-Berlin e.V, asked since which Android PREF64, DHCP option 108 and CLAT were supported. <o:p></o:p> <o:p> </o:p> Ond�ej replied that version 11 and above were supported by the vendor, but that he was not sure about older versions.<o:p></o:p> <o:p> </o:p> Michael Richardson, one of the authors of the IPv4-only option, noted that when he developed this feature he never imagined that people would deploy it on DHCP servers and not change anything. He added that it was interesting to see how it worked because they assumed that DHCP servers would not allocate addresses and therefore would not run out of addresses in the pool. So it was cool to see that it just worked without doing that.<o:p></o:p> <o:p> </o:p> He further said that for any connect, if the client was v4-only, and was just creating a v4-only UDP encapsulated thing that the local end of course had no idea what to do with, it had to be encapsulated in a v6 packet to send it. He added that he thought CLAT would be of no help but that it might work on Mac OS but not on other systems. He mentioned that IOS would never work until it went to v6 and that the Cisco people should be embarrassed about this. <o:p></o:p> <o:p> </o:p> Veronika McKillop, UK IPv6 Council, asked which DHCP servers supported RFC8925.<o:p></o:p> <o:p> </o:p> Ond�ej replied that this was option 108 and that Kea, at least, did not support it. He added that there were two options. If you have enough addresses for the IPv4 pool, any server that allowed setting a custom option could be used. If there was any special support for this feature, the server would simply respond with option 108 and not allocate an address from the pool. He stated that he was not aware of such an implementation, as even Kea cannot be used in this way. He added that if the pool was empty, it would not even respond and that this was an interesting feature to implement for DHCP server producers. <o:p></o:p> <o:p> </o:p> Jordi Palet Mart�nez, The IPv6 Company, said that it was worth mentioning that most of the CLAT implementations just used a default NAT64 prefix (the WKP). He added that there was only a single translation when using the CLAT and that two translations were only needed if there were no DNS64 (<a href="https://datatracker.ietf.org/doc/rfc8683">https://datatracker.ietf.org/doc/rfc8683</a>). He said that even if your network was using NAT, NAT64 would also work well.<o:p></o:p> <o:p> </o:p> Radek Zajic via Meetecho shared that the CLAT on iOS 16 also worked in apps requiring unix/raw sockets too (e.g. Hurricane Electric Network Tools can ping IPv4-only targets via the CLAT). <o:p></o:p> <o:p> </o:p> Ond�ej thanked Radek for his comment. <o:p></o:p> <o:p> </o:p> <o:p> </o:p> Round Up and Thanks<o:p></o:p> IPv6 Working Group Co-Chairs<o:p></o:p> <o:p> </o:p> Raymond thanked all participants and the RIPE NCC and closed the session. <o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p></o:p> <o:p> </o:p> For Internal Use Only </div> </body> </html>