<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"> Hello,<o:p></o:p> <o:p> </o:p> Here are the minutes from RIPE 83, if you have any comments or remarks, please let us know before 20.12 so we can have them published.<o:p></o:p> <o:p> </o:p> RIPE 83 RIPE IPv6 Working Group Minutes<o:p></o:p> <o:p> </o:p> Date: 25 November, 13:00-14:00 (UTC+1)<o:p></o:p> Chairs: Raymond Jetten, Benedikt Stockebrand <o:p></o:p> Scribe: Suzanne Taylor<o:p></o:p> Status: Draft<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Welcome, Administrative Matters<o:p></o:p> Raymond Jetten, Working Group Co-Chair<o:p></o:p> <o:p> </o:p> Raymond Jetten, Working Group Co-Chair, welcomed everyone to the session and went over some rules of engagement.<o:p></o:p> <o:p> </o:p> There were no questions or comments.<o:p></o:p> <o:p> </o:p> Building IPv4 Islands for Fun and Profit <o:p></o:p> Nico Schottelius, ungleich<o:p></o:p> <o:p> </o:p> This presentation is available at:<o:p></o:p> <a href="https://ripe83.ripe.net/wp-content/uploads/presentations/86-ripe83-ipv4-islands-for-fun-and-profit.pdf">https://ripe83.ripe.net/wp-content/uploads/presentations/86-ripe83-ipv4-islands-for-fun-and-profit.pdf</a> <o:p></o:p> <o:p> </o:p> Nico discussed the technical details of how to set up IPv6-only networks that need to incorporate IPv6-incompatible devices (such as x-ray or ultrasound scanners, LoraWAN gateways, printers, power plants) by setting up IPv4 “islands” for those devices. <o:p></o:p> <o:p> </o:p> Benedikt Stockebrand commented that there are many different approaches to this issue and that if this particular method doesn’t work, then attendees should be encouraged to reach out on the mailing list rather than simply give up on deploying IPv6. Nico said he fully agreed. <o:p></o:p> <o:p> </o:p> Michael Richardson, Sandelman Software Works, thanked Nico for his explanation and said he had also been doing something similar. He said he thought another name is needed, however, other than “islands”. Nico said he was open to other suggestions. Raymond suggested that ideas could be discussed on the mailing list. <o:p></o:p> <o:p> </o:p> There were no further questions or comments.<o:p></o:p> <o:p> </o:p> To ULA or not ULA<o:p></o:p> Nico Schottelius <o:p></o:p> <o:p> </o:p> This presentation is available at: <o:p></o:p> <a href="https://ripe83.ripe.net/wp-content/uploads/presentations/87-ripe83-to-ula-or-not-ula.pdf">https://ripe83.ripe.net/wp-content/uploads/presentations/87-ripe83-to-ula-or-not-ula.pdf</a><o:p></o:p> <o:p> </o:p> In his second presentation, Nico gave an overview of ULAs (unique local addresses), which are used in community networks and other use cases but aren’t generally visible on the Internet. He explained how his company has been asked to run a ULA registry and asked for opinions about how – and whether there was consensus – to support community projects by running a ULA registry. <o:p></o:p> <o:p> </o:p> Jordi Palet Mart�nez, Moremar - The IPv6 Company, said that the right way to have a registry is to revive the ULA-Central work, which he tried already in the IETF and with the RIRs. He said there is possibly a need for a global policy on running a central IANA registry or coordination for that among the RIRs, but that it didn’t work. He offered to continue working on that if there were community support. <o:p></o:p> <o:p> </o:p> Nico said that was an interesting approach and that there were also recent discussions around where to register IP space for aerospace technology and that this could be a way to go, or that the RIRs could have a subsection for ULA community space. He said he would reach out to Jordi after the meeting.<o:p></o:p> <o:p> </o:p> Niall O’Reilly, speaking as a “ULA user”, asked Nico whether he imported registrations from SixXS to the new registry. Nico responded that everything had been imported and that some have already been deleted because they saw old information in the registry. <o:p></o:p> <o:p> </o:p> Marco Hogewoning, RIPE NCC, said that the EU Cybersecurity Strategy suggests a possible sunset clause for IPv4 if insufficient progress is made with IPv6 and asked what the RIPE community thought could be done other than avoiding legislation to force a particular technical choice. He asked whether the community, for example, would advise forcing the use of IPv6 or discouraging the use (or forcing the disuse) of IPv4. He commented that this strategy is focuses on the market and not just the public sector. <o:p></o:p> <o:p> </o:p> Nico said that is a difficult question. He said the market is already at play, given the increasing price of IPv4 and that some governments are going IPv6-only. He said that an RIR like the RIPE NCC can encourage IPv6 deployment, and that he sees a role for open-source solutions to support this shift and enable bottom-up development and innovation. <o:p></o:p> <o:p> </o:p> R�diger Volk, my UNorganized self, said he remembered when Internet number resources were essentially available for free and the one registry was funded by the US federal government. He said that, in order to support communities that were outside of the very small Internet at the time that wanted to install TCP/IP locally or regionally with a limited view to interconnect globally, volunteers started to hand out things and get centrally registered space and create sub-registries. Essentially, he said, the RIPE NCC registry grew from there.<o:p></o:p> <o:p> </o:p> He said he felt that if the address space you’re using has enough free resources for everyone to be globally unique, then you should do that – but if the current ICANN anchored registry system doesn’t offer a way for all communities to adequately address their needs, that should be a trigger to question how to do that. He said that, in some ways, the precursor to ULA was the RFC 1918 space, but it was meant to just be local and was not meant to require a registry (unless your enterprise network isn’t connected to anything else and runs as a very closed system, in which case a local registry might be used). <o:p></o:p> <o:p> </o:p> Nico said he saw R�diger’s point and said that perhaps this work should be a community/volunteer effort. He said this topic already came up on the IETF mailing list, along with the usual question of who would pay for the project. He said the idea of handing out GUA (global unique addresses) was also discussed on the IETF mailing list, which he thought was good, as it would offer uniqueness along with global addressability. He added that sponsoring the address space is one thing, but sponsoring the work was another thing and being recognised, a third consideration. He encouraged anyone interested in contributing to the project to contact him. <o:p></o:p> <o:p> </o:p> Peter Hessler, speaking as an “open source enthusiast”, asked how much space the community should request from the RIPE NCC if it were to group together and form a LIR to request and manage IPv6 address space. <o:p></o:p> <o:p> </o:p> Nico said you can start with a /32 and simply request another as needed, because the addresses don’t need to be consecutive. Raymond added that you can get a /29 without any justification. <o:p></o:p> <o:p> </o:p> Michael Richardson said he had been a proponent of a non-connected IPv6 space for a long time and that he had first come across this before in using it in a data centre through VPNs as a management network. He said that in his experience, these inevitably leak and when they do, you don’t know who to tell. He said this was also why he doesn’t like ULA random. He said that the value of Whois is high and provides a feeling that no one will come and do something terrible to you because you’re using the address space. He also said the possibility of reverse DNS really matters in IPv6 space. For those reasons, he said he would like to have a registry but was agnostic as to whether it should be a /29 of carefully managed global address space that is unannounced in RPKI, or ULA central or fd/8 if that were ever to work. He said there should be a nominal, one-time fee to register the space. He said he oftens sees a need for this in equipment chassis and gave the example of a networked fishing boat. He said he would rather it wasn’t RFC1918 but IPv6, and if there were too much paperwork, you could use 1.1 or 11 network because 1918 is on the other interface and using NAT, so you don’t know what is there. He said engineers don’t use IPv6 because they think they can’t get it and don’t use ULA random because they need something different for every boat (in the example), which is correct, but he said it should be within the network you own. He said the community needs to enable this and that a small registration fee should make it your own in perpetuity. <o:p></o:p> <o:p> </o:p> Benedikt said that one use case that tends to be forgotten about, as most in the community are LIRs, is having a provider aggregated addresses and wanting to maintain some independence from your ISP, ULAs can be very helpful in renumbering. He said there’s a big difference between IPv4 and IPv6 in that IPv6 was designed to support multiple addresses per interface, and this can be very useful. He also cautioned against starting a separate address space that is sort of connected with people using ULAs across the Internet via tunnels where they really shouldn’t. <o:p></o:p> <o:p> </o:p> Raymond closed the queue to further questions in the interest of time.<o:p></o:p> <o:p> </o:p> RIPE-554bis<o:p></o:p> Jan �or�, 6connect<o:p></o:p> <o:p> </o:p> This presentation is available at:<o:p></o:p> <a href="https://ripe83.ripe.net/wp-content/uploads/presentations/73-RIPE554bis-RIPE83.pdf">https://ripe83.ripe.net/wp-content/uploads/presentations/73-RIPE554bis-RIPE83.pdf</a><o:p></o:p> <o:p> </o:p> Jan gave some background and history on updating RIPE-554 and RIPE-554bis, which provides guidance on how to procure IPv6-capable equipment and software for enterprises. He explained which updates were deemed necessary, such as adding fundamental RFCs like “IPv6 over Ethernet” and removing BOUNDv6, as it no longer exists. There are new requirements for hosts and enterprise/ISP switches, and some other changes for routers, CPEs, mobile devices, load balancers and software. He stressed the need to publish an update to RIPE-554 as soon as possible and asked the group whether there was consensus on RIPE-554bis. <o:p></o:p> <o:p> </o:p> Blake Willis, Zayo, asked whether RFC8950/RFC5549 BGP tunnel signalling was within the document’s scope. Jan replied that it included IPv6-specific things and he would need to look into it. Sander Steffann, 6connect and RIPE-554bis co-author, said he was also not certain. Jan said he did not think RFC8950 was included but that they could consider it for the next version, as they didn’t want to expand the scope of this version since it would take too long to update it. <o:p></o:p> <o:p> </o:p> �ric Vyncke, Cisco and IETF but speaking mainly as an “IPv6 evangelist”, said he couldn’t find in the draft RIPE-554bis document Jan’s reference during his presentation to not using a /64 and RFC8200 now including atomic/overlapping fragments. Jan said the RFC8200 was in the section on requirements for host equipment, and that it’s basically the same document, just updated. Sander said he thought he found the section that �ric was referring to, which was from RFC7608 (IPv6 prefix length recommendations for forwarding), which mentions that prefix lengths longer than /64 must be supported in forwarding. �ric said the other two RFCs mentioned were removed from the RIPE-554bis document and that the presentation had not been updated to reflect the most recent Google doc. <o:p></o:p> <o:p> </o:p> Christoph Berkemeier, DB Station & Service AG, asked whether Jan was aware of automated or semi-automated test scripts/environments for the recommendations. Jan responded that this was a mistake many people were making, and that the document was meant to be used as a template. He said that, for example, “if support for tunnelling and duo-stack is required, the device must support basic transition mechanisms for IPv6 hosts and routers” then it could be technically possible to build a script to test this, but you would need to include everything you want and need, which would be complicated. He said that you need to take the parts of the document that apply to your situation. But, he said, if someone wanted to build something like that, then he would be happy to include it. Sander said that Blake Willis was referring on the chat to the University of New Hampshire’s independent testing lab. Jan said there are asterisks on some of the requirements in the draft policy that indicate they are being tested. <o:p></o:p> <o:p> </o:p> Jan asked the collective whether there was consensus. <o:p></o:p> <o:p> </o:p> Benedikt said that no one would complain if they wanted to do the work. Raymond said he was happy to move forward but suggested leaving the mailing list open until the following Wednesday for any other potential objections to consensus, which Jan agreed to. <o:p></o:p> <o:p> </o:p> Jan and Raymond thanked everyone for their hard work.<o:p></o:p> <o:p> </o:p> Raymond thanked the scribe and said that there had been no comments on the minutes from RIPE 82, which had been online for some time, so declared them approved. He said that he hoped to see everyone at a meeting in person soon and closed the session. <o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Rgds,<o:p></o:p> <o:p> </o:p> Ray<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p> </o:p> </div> </body> </html>