<div dir="ltr">this needs to also include re-assign detail where a "01. Downstream Org ID:" is not included.<div><br></div><div>__Jason</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 14, 2017 at 2:54 PM, Jason Schiller <span dir="ltr"><<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I support this policy as written but...<div><br></div><div>It fails to address one concern that was clearly voiced by more than a few people </div><div>when discussing this policy in the past on list and at public policy consultations (PPCs)</div><div>held at recent public policy meetings (PPMs):</div><div><br></div><div>How do we prevent resources being randomly re-assigned simple to a random contact.</div><div>Today we catch these during the annual POC validation.</div><div><br></div><div>The proposal floated was that all re-assign simple need to be verified by the email listed</div><div>prior to the SWIP being processed.</div><div><br></div><div>Will that be addressed in this proposal or in a parallel proposal? </div><div><br></div><div>___Jason</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Tue, Nov 14, 2017 at 11:05 AM, Potter, Amy <span dir="ltr"><<a href="mailto:apotter@hilcoglobal.com" target="_blank">apotter@hilcoglobal.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div lang="EN-US" link="blue" vlink="purple">
<div class="m_-2646712641406349195m_6275348529661784484WordSection1">
<p class="MsoNormal">Updated text of 2017-3 is provided below. The problem statement has been simplified, and language has been cleaned up a bit. Feedback would be appreciated. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
UPDATE TO NPRM 3.6: Annual Whois POC Validation<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<b>Problem Statement:<u></u><u></u></b></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Many of the Point of Contacts listed in ARIN’s public Whois database contain out-of-date and inaccurate contact information.
<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<b>Policy Statement:<u></u><u></u></b></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<b><u></u> <u></u></b></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u>Current Text</u>: <u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
3.6 Annual Whois POC Validation<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
3.6.1 Method of Annual Verification<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
During ARIN's annual Whois POC validation, an email will be sent to every POC in the Whois database. Each POC will have a maximum of 60 days to respond with an affirmative that their Whois contact information is correct and complete. Unresponsive POC email
addresses shall be marked as such in the database. If ARIN staff deems a POC to be completely and permanently abandoned or otherwise illegitimate, the POC record shall be marked invalid. ARIN will maintain, and make readily available to the community, a current
list of number resources with no valid POC; this data will be subject to the current bulk Whois policy.<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u>Proposed Revised Text</u>:<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
3.6 Annual Validation of ARIN's Public Whois Point of Contact Data<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u> <u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
3.6.1 Annual POC Verification <u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
ARIN will perform an annual verification of specific Points of Contact registered in the public Whois using the criteria and procedures outlined in sections 3.6.2, 3.6.3, and 3.6.4.<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
3.6.2 Specified Public Whois Points of Contact for Verification<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Each of the following Points of Contact are to be verified annually, and will be referred to as Point of Contact or POC throughout this policy, and should be understood to be both organization and resource POCs:<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
- Admin<br>
- Tech<br>
- NOC<br>
- Abuse<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
3.6.3 Organizations Covered by this Policy<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
This policy applies to every Organization that has a direct assignment, direct allocation, or AS number from ARIN (or one of its predecessor registries) or a reallocation from an upstream ISP. This includes but is not limited to upstream ISPs and their downstream
ISP customers (as defined by NRPM 2.5 and 2.6), but not reassignments made to their downstream end user customers. <u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
3.6.4 Procedure for Verification<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
An annual email notification will be sent to each of the Points of Contact outlined in section 3.6.2 on an annual basis. Each Point of Contact will have up to sixty (60) days from the date of the notification in which to respond with an affirmative that their
Whois contact information is correct and complete or to submit new data to correct and complete it. If after careful analysis, ARIN staff deems a POC to be completely and permanently abandoned or otherwise illegitimate, the POC record shall be marked invalid
in Whois.<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
3.6.5 Non-Responsive Point of Contact Records <u></u><u></u></p>
<p class="MsoNormal" style="margin-right:.5in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Once a non-responsive POC has been marked invalid in the public Whois, any organization lacking a validated Admin or Tech POC will be unable to access the full suite of functionality within ARIN Online until the invalid POC(s) have either validated that their information
is accurate or modified their POC to contain up-to-date information.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br></div></div>______________________________<wbr>_________________<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" target="_blank">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" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div class="m_-2646712641406349195gmail_signature" data-smartmail="gmail_signature"><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">______________________________<wbr>_________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@<wbr>google.com</a>|<a href="tel:(571)%20266-0006" value="+15712660006" target="_blank">571-266-0006</a></font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">_______________________________________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|571-266-0006</font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</div>