<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;}
span.gmail-hoenzb
{mso-style-name:gmail-hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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'>I still don’t see any value in specifying length. What you are looking for is contact info for someone with a clue about how a given network works and using length as a really poor proxy. I could live with a fourth line:<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'>Any end network emitting SMTP system SHOULD provide SWIP. <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'>I just don’t know how that gets enforced in any reasonable way. In general SMTP & independent routing are the big targets needing accurate contact info, and length has absolutely nothing to do with either. <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> Monday, July 24, 2017 2:53 PM<br><b><span style='font-weight:bold'>To:</span></b> Tony Hain<br><b><span style='font-weight:bold'>Cc:</span></b> 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 - updated 2017-07-21<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'>Actually, let me revise that; I'm willing to recognize at least the possibility there is a legitimate community interest in having records for assignments that are shorter than /40 for IPv6 and /24 for IPv4. Why, those numbers? They are the sizes at the bottom of ARIN's fee schedule, if anything smaller is the same fee, I'm not sure where there is a compelling community policy interest. <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'>On Mon, Jul 24, 2017 at 4:07 PM, David Farmer <<a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a>> wrote:<o:p></o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Honestly, I could live with it just those three lines. However, I'm willing to recognize at least the possibility there is a legitimate community interest in having records for assignments that are shorter than /48. <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'>As for IPv4, I'd also be just fine with those three lines. Again, recognizing at least the possibility there is a legitimate community interest in having records for assignments that are shorter than /24<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 Mon, Jul 24, 2017 at 2:51 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'>While I agree with the general direction David is heading, his text is still overly complex to deal with the goal. This whole thread only requires 3 lines:</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'>Reallocations MUST provide SWIP.</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'>Requests by the assignee MUST provide SWIP.<br>Anything appearing independently in the global routing table SHOULD provide SWIP.</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'>All the rest is noise that doesn’t add to solving any problem known to mankind, and is simply an artifact of the IPv4-think insane conservation mindset. Size is irrelevant in both protocol versions, and even if you think it is, the only time it comes up is in #3. In any case the length of #3 might change over time, and there is no reason the policy text needs to change to track it. If something is independent, no matter what it’s length is, the intent is to have accurate contact info. </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'>Saying anything more is trying to legislate ISP behavior, which is explicitly outside the scope of ARIN.</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></div></div></div><p class=MsoNormal><font size=2 color="#888888" face="Times New Roman"><span style='font-size:10.0pt;color:#888888'><br clear=all><span class=gmail-hoenzb><o:p></o:p></span></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><span class=gmail-hoenzb><font size=2 color="#888888" face="Times New Roman"><span style='font-size:10.0pt;color:#888888'>-- </span></font><o:p></o:p></span></p><div><p class=MsoNormal><font size=2 color="#888888" face="Times New Roman"><span style='font-size:10.0pt;color:#888888'>===============================================<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: <a href="tel:(612)%20626-0815" target="_blank">612-626-0815</a><br>Minneapolis, MN 55414-3029 Cell: <a href="tel:(612)%20812-9952" target="_blank">612-812-9952</a><br>=============================================== </span></font><o:p></o:p></p></div></div></div></div></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></div></body></html>