<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>David,<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>While I totally agree with your reasoning, doesn’t that fly in the face of the policy that Arin says “nothing about routing”? It is one thing to have a BCP stating expectations for being able to find a contact for a routing entry, it is another to have a “policy” that a routing entry requires swiped contact info. <o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Tony<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><a name="_MailEndCompose"><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></a></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";font-weight:bold'>From:</span></font></b><font face=Tahoma><span style='font-family:"Tahoma","sans-serif"'> David Farmer [mailto:farmer@umn.edu] <br><b><span style='font-weight:bold'>Sent:</span></b> Friday, July 14, 2017 2:58 PM<br><b><span style='font-weight:bold'>To:</span></b> Tony Hain<br><b><span style='font-weight:bold'>Cc:</span></b> William Herrin; Owen DeLong; arin-ppml@arin.net<br><b><span style='font-weight:bold'>Subject:</span></b> Re: [arin-ppml] Draft Policy ARIN-2017-5: Equalization of Assignment Registration requirements between IPv4 and IPv6<o:p></o:p></span></font></p></div></div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Rather than base it on the criteria of business vs. residential customer, how about simply basing it on the criteria, is the assignment intended to be or is used within the global routing system or not, or if the customer requests their assignment be SWIPed. Most residential assignments be they /56 or /48 won't be in the global routing system, neither will many business assignments either, after that then an assignment is only SWIPed if the customer requests it.<o:p></o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>My reasoning for wanting to have /48s SWIPed isn't based on business vs residential customer type, which has a fuzzy definition sometimes anyway. Its that /48s might appear in the routing table. So just make that the criteria in the first place, if we are not going to based it on a specific size like we did in IPv4. Also, then any policy violations become easily apparent. If an ISP doesn't SWIP some of there business customers, how are you going to know anyway? However, if a route is in the route table and there is no SWIP that is fairly self apparent.<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Thanks.<o:p></o:p></span></font></p></div></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>On Fri, Jul 14, 2017 at 3:07 PM, Tony Hain <<a href="mailto:alh-ietf@tndh.net" target="_blank">alh-ietf@tndh.net</a>> wrote:<o:p></o:p></span></font></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill,</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>To avoid the situation of Owen being a lone voice, I have to echo his point that it is insane that people persist with IPv4-think and extreme conservation. Allocations longer than a /48 to a residence ensure that automated topology configuration can’t happen, because /52’s won’t happen and /56’s are too long for random consumer plug-n-play. Therefore a policy that /48’s must be swiped ensures that we maintain single subnet consumer networks. A policy that says /48’s might be swiped (will in a business and not in a non-residential case) does not reinforce the braindead notion that longer than /48 has some special meaning beyond the need to kill off a generation of those with the ‘addresses are a scarce resource’ mindset. </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Tony</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a name="m_2289219881633447079__MailEndCompose"><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span></font></a><o:p></o:p></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";font-weight:bold'>From:</span></font></b><font face=Tahoma><span style='font-family:"Tahoma","sans-serif"'> ARIN-PPML [mailto:<a href="mailto:arin-ppml-bounces@arin.net" target="_blank">arin-ppml-bounces@arin.net</a>] <b><span style='font-weight:bold'>On Behalf Of </span></b>William Herrin<br><b><span style='font-weight:bold'>Sent:</span></b> Thursday, July 13, 2017 3:12 PM<br><b><span style='font-weight:bold'>To:</span></b> Owen DeLong<br><b><span style='font-weight:bold'>Cc:</span></b> <a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br><b><span style='font-weight:bold'>Subject:</span></b> Re: [arin-ppml] Draft Policy ARIN-2017-5: Equalization of Assignment Registration requirements between IPv4 and IPv6</span></font><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'> <o:p></o:p></span></font></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>On Thu, Jul 13, 2017 at 4:49 PM, Owen DeLong <<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>> wrote:<o:p></o:p></span></font></p><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Consensus hasn’t yet been reached. I agree that there is significant support for “shorter than /56” actually (not /56 itself). Nonetheless, I don’t believe that shorter than /56 is the ideal place to put the boundary.<o:p></o:p></span></font></p></blockquote><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'> <o:p></o:p></span></font></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Hi Owen,<o:p></o:p></span></font></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'> <o:p></o:p></span></font></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>I think you're an outlier here. I see consensus that /48 should be swiped and /56 should not. If there's debate that /52 or /49 should also not be swiped or that a some more subtle criteria should determine what's swiped, it's not exactly chewing up bandwidth on the mailing list.<o:p></o:p></span></font></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'> <o:p></o:p></span></font></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Regards,<o:p></o:p></span></font></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Bill Herrin<o:p></o:p></span></font></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'> <o:p></o:p></span></font></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'> <o:p></o:p></span></font></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>-- <o:p></o:p></span></font></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>William Herrin ................ <a href="mailto:herrin@dirtside.com" target="_blank">herrin@dirtside.com</a> <a href="mailto:bill@herrin.us" target="_blank">bill@herrin.us</a><br>Dirtside Systems ......... Web: <<a href="http://www.dirtside.com/" target="_blank">http://www.dirtside.com/</a>><o:p></o:p></span></font></p></div></div></div></div></div></div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><br>_______________________________________________<br>PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<o:p></o:p></span></font></p></div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><br><br clear=all><o:p></o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>-- <o:p></o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== <o:p></o:p></span></font></p></div></div></div></div></body></html>