<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:24.0pt;
font-family:"Calibri",sans-serif;
font-weight:bold;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:13.5pt;
font-family:"Calibri",sans-serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Calibri",sans-serif;
mso-fareast-language:FI;
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Calibri",sans-serif;
mso-fareast-language:FI;
font-weight:bold;}
span.ripe-glossary-popover
{mso-style-name:ripe-glossary-popover;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FI" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hello All,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Here are the minutes form the previous meeting in Amsterdam, if you have any comments on the content of them, please contact us (
<a href="mailto:ipv6-wg-chairs@ripe.net">ipv6-wg-chairs@ripe.net</a> )<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In a little over 2 weeks we will approve the minutes including the comments at the RIPE78 meeting in Reykjavik.<o:p></o:p></span></p>
<h1><span lang="EN-US">IPv6 Working Group Minutes - RIPE 77<o:p></o:p></span></h1>
<p><span lang="EN-US">Date: 18 October 2018, 11:00 - 12:30<br>
WG Co-Chairs: Jen Linkova, Benedikt Stockebrand, Raymond Jetten</span><span style="font-family:"MS Gothic"">
</span><span lang="EN-US">
<br>
Scribe: Massimiliano Stucchi </span><span style="font-family:"MS Gothic"">
</span><span lang="EN-US"><br>
Status: Draft<o:p></o:p></span></p>
<h3><span lang="EN-US">1. </span><span lang="EN-GB">Welcome/Agenda Bashing/Meeting Minutes</span><span lang="EN-US"><o:p></o:p></span></h3>
<p><span lang="EN-US">The presentation is available at<br>
</span><a href="https://ripe77.ripe.net/archives/video/2278/"><span lang="EN-US">https://ripe77.ripe.net/archives/video/2278/</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">There were no questions or comments.<o:p></o:p></span></p>
<h3><span lang="EN-US">2. </span><span lang="EN-GB">IPv6 Work at IETF (v6ops/6man WGs updated) Jen Linkova, WG Co-Chair </span><span lang="EN-US"><o:p></o:p></span></h3>
<p><span lang="EN-US">The presentation is available at: <br>
</span><a href="https://ripe77.ripe.net/archives/video/2279/"><span lang="EN-US">https://ripe77.ripe.net/archives/video/2279/</span></a><span lang="EN-US"><br>
<br>
Pawel Lunin from Scaleway mentioned that RFC8475 was recently published, and<br>
asked for a more detailed explanation from Jen Linkova, one of the authors.<br>
<br>
Marco Hogewoning from RIPE NCC thanked the presenters and asked to<br>
point those interested towards smaller Internet drafts that haven't been adopted by Working Groups. He suggested taking a look at a specific draft on
<span class="ripe-glossary-popover">ENUM</span> numbers and said that participants in the room should comment on that.<br>
<br>
Cyril Malevanov from Selectel spoke against <span class="ripe-glossary-popover">IPv6</span> on behalf of the operators from St. Petersburg. He said he wanted his voice to be heard, and to state his opinion.<br>
<br>
Alissa Cooper, IETF Chair, thanked the presenters on behalf of the IETF.<br>
She also stated that if there were ideas, people could approach her and other IETF<br>
participants to get help.<br>
<br>
There were no more questions or comments.<o:p></o:p></span></p>
<h3><span lang="EN-US">3. </span><span lang="EN-GB">Clusters in the Expanse: Understanding and Unbiasing IPv6 Hitlists
<br>
Oliver Gasser, RACI </span><span lang="EN-US"><o:p></o:p></span></h3>
<p><span lang="EN-US"> The presentation is available at: <br>
</span><a href="https://ripe77.ripe.net/archives/video/2283/"><span lang="EN-US">https://ripe77.ripe.net/archives/video/2283/</span></a><span lang="EN-US"><br>
<br>
Jen Linkova, Google, said she liked the conclusions because she finds it hard to understand the issue of security by obscurity.<br>
<br>
The presenter answered that there was a previous paper that compared the reachability of
<span class="ripe-glossary-popover">IPv4</span> against <span class="ripe-glossary-popover">
IPv6</span> and the outcome was that <span class="ripe-glossary-popover">IPv6</span> addresses are more likely to respond because firewall rules were not set.<br>
<br>
Randy Bush, IIJ and Archis asked about the <span class="ripe-glossary-popover">IPv6</span> responsiveness graph in the slides and how it compares to
<span class="ripe-glossary-popover">IPv4</span>.<br>
<br>
The presenter answered that the numbers are in the paper, but couldn't provide any more data as he couldn't remember it in detail.<br>
<br>
There were no more questions or comments.<o:p></o:p></span></p>
<h3><span lang="EN-US">4. </span><span lang="EN-GB">We Don't Need IPv6 - Update <br>
Jens Link</span><span lang="EN-US"><o:p></o:p></span></h3>
<p><span lang="EN-US">The presentation is available at: <br>
</span><a href="https://ripe77.ripe.net/archives/video/2285/"><span lang="EN-US">https://ripe77.ripe.net/archives/video/2285/</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">Jen Linkova, Google, commented during the presentation that she wouldlike to do the"<span class="ripe-glossary-popover">IPv6</span> bullshit bingo" if any more references to a paper mentioned during thepresentation will be highlighted.<o:p></o:p></span></p>
<p><span lang="EN-US">Randy Bush, IIJ, mentioned that they tried turning off <span class="ripe-glossary-popover">
IPv4</span> at the lastIETF,specifically for the <span class="ripe-glossary-popover">
IPv6</span>-related Working Groups (6man, v6ops) and it didn'twork out the way they would have liked. They tried NAT64. Hesaid unfortunately there is still work to be done.<o:p></o:p></span></p>
<p><span lang="EN-US">Jen Linkova said there were bugs in the network, and 75% of the peoplereported they had no problems getting work done in a survey sent later.<o:p></o:p></span></p>
<p><span lang="EN-US">There were no more questions nor comments.<o:p></o:p></span></p>
<h3><span lang="EN-US">5. The Art of Running Out of IPv6 Addresses </span><span lang="EN-GB">Benedikt Stockebrand</span><span lang="EN-US"><o:p></o:p></span></h3>
<p><span lang="EN-US">The presentation is available at: <br>
</span><a href="https://ripe77.ripe.net/archives/video/2287/"><span lang="EN-US">https://ripe77.ripe.net/archives/video/2287/</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">Jan Zorz thanked the presenter and seconded the fact that history<br>
repeats itself over and over again, and errors keep being repeated.<br>
<br>
There were no more questions nor comments.<o:p></o:p></span></p>
<p><span lang="EN-US">---<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The minutes are also available online:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://www.ripe.net/participate/ripe/wg/ipv6/minutes/ipv6-working-group-minutes-ripe-77">https://www.ripe.net/participate/ripe/wg/ipv6/minutes/ipv6-working-group-minutes-ripe-77</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Rgds,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">IPv6-WG-Chairs: Jen, Benedikt, Ray<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>