<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=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@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: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:12.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.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Fair enough, but maybe it should be more explicit that it is aimed at keeping whois up to date. I agree that valid contact information is important. The major problem with v6 is going to be hijacking of address space simply because there is so much of it available. Nefarious operators are probably just going to grab a chunk of space and use it and the v6 “full bogons” list is so large that it probably can’t be used on most dual stack routers (along with the full v4 and v6 non-bogons tables).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>But as someone pointed out earlier, how big a problem is this? What percentage of the issued resources is currently assigned to “dead” contacts?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>“most of what you're objecting to is already policy” except the “we break your network” part about turning off reverse dns which on reflection, is probably ok. But you are right, it wasn’t exactly clear to me on a quick read how much of the proposed text is new. Thanks for sending that bolded version. In fact, I am in favor of producing that format in proposed changes with any deleted existing wording shown stuck through and new wording in bold. It sure makes it easier to see what exactly is being changed.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></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><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Scott Leibrand [mailto:scottleibrand@gmail.com] <br><b>Sent:</b> Tuesday, January 11, 2011 9:44 AM<br><b>To:</b> George Bonser<br><b>Cc:</b> arin-ppml@arin.net<br><b>Subject:</b> Re: [arin-ppml] ARIN-prop-126: Compliance Requirement<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>I don't think this policy proposal is about IPv4. There is already an effective enforcement mechanism there: you can't get more space unless you're following procedures. But for IPv6, there is no real enforcement mechanism to ensure that those who are allocated IPv6 addresses will keep whois up to date. The original intent of the author was to give ARIN a tool to encourage people to keep their IPv6 whois records up to date, even if they never go back for additional space.<br><br>And as I mentioned in another message, most of what you're objecting to is already policy. If you want to change that, we'd need a new policy proposal to do so...<br><br>-Scott<o:p></o:p></p><div><p class=MsoNormal>On Tue, Jan 11, 2011 at 9:10 AM, George Bonser <<a href="mailto:gbonser@seven.com">gbonser@seven.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal><br><br><br><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>