<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div>On May 12, 2015, at 09:07, Jan Ingvoldstad <<a href="mailto:frettled@gmail.com">frettled@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, May 12, 2015 at 3:40 PM, Tim Chown <span dir="ltr"><<a href="mailto:tjc@ecs.soton.ac.uk" target="_blank">tjc@ecs.soton.ac.uk</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div>.....</div><div>On the /64 boundary, I’d point you at RFC7421.</div></div></blockquote></div><div class="gmail_extra"><br></div>Well, I guess that's a nice document to point people to, if they're unfamiliar with the history of IPv6 and the issues that have been raised. I'll be sure to mention it if I run into someone who needs it, thanks!</div></div></div></blockquote><div><br></div><div>I'd like to call you attention to the following paragraph from the end of section 2 of RFC7421;</div><div><br></div><div><pre class="newpage" style="margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><font face="UICTFontTextStyleBody"><span style="white-space: normal; background-color: rgba(255, 255, 255, 0);"> The remainder of this document describes arguments that have been </span></font></pre><pre class="newpage" style="margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><font face="UICTFontTextStyleBody"><span style="white-space: normal; background-color: rgba(255, 255, 255, 0);"> made against the </span></font><span style="white-space: normal; background-color: rgba(255, 255, 255, 0); font-family: UICTFontTextStyleBody;">current fixed IID length and analyzes the effects of </span></pre><pre class="newpage" style="margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><span style="white-space: normal; background-color: rgba(255, 255, 255, 0); font-family: UICTFontTextStyleBody;"> a possible change. However, the consensus of the IETF is that the </span></pre><pre class="newpage" style="margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><span style="white-space: normal; background-color: rgba(255, 255, 255, 0); font-family: UICTFontTextStyleBody;"> benefits of keeping the length fixed at 64 bits and the practical </span></pre><pre class="newpage" style="margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><span style="white-space: normal; background-color: rgba(255, 255, 255, 0); font-family: UICTFontTextStyleBody;"> difficulties of changing it outweigh the arguments for change.</span></pre></div><div><br></div><div>The point being that neither RIPE nor the other RIRs are the place to discuss changes to the IPv6 architecture. If you feel changes to the IPv6 <span style="background-color: rgba(255, 255, 255, 0);">architecture needed, you need to participate in discussions in the IETF v6ops and 6man working groups. It would have been helpful to have added your voice in the the discussion of the Why64 draft that became RFC 7421. There was a lively discussion, but the paragraph above accurately reflects the current consensus. Participation in the discussion at the IETF is really the only way to change that consensus.</span></div><div><br></div><div>Thanks</div><br><div><span style="background-color: rgba(255, 255, 255, 0);">-- </span><div><span style="background-color: rgba(255, 255, 255, 0);">===============================================</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">David Farmer Email: <a href="mailto:farmer@umn.edu">farmer@umn.edu</a></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Office of Information Technology</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">University of Minnesota </span></div><div><span style="background-color: rgba(255, 255, 255, 0);">2218 University Ave SE Phone: +1-612-626-0815</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Minneapolis, MN 55414-3029 Cell: +1-612-812-9952</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">===============================================</span></div></div><div><br></div></body></html>