this needs to also include re-assign detail where a "01. Downstream Org ID:" is not included.
__Jason On Tue, Nov 14, 2017 at 2:54 PM, Jason Schiller <[email protected]> wrote: > I support this policy as written but... > > It fails to address one concern that was clearly voiced by more than a few > people > when discussing this policy in the past on list and at public policy > consultations (PPCs) > held at recent public policy meetings (PPMs): > > How do we prevent resources being randomly re-assigned simple to a random > contact. > Today we catch these during the annual POC validation. > > The proposal floated was that all re-assign simple need to be verified by > the email listed > prior to the SWIP being processed. > > Will that be addressed in this proposal or in a parallel proposal? > > ___Jason > > On Tue, Nov 14, 2017 at 11:05 AM, Potter, Amy <[email protected]> > wrote: > >> 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. >> >> >> >> UPDATE TO NPRM 3.6: Annual Whois POC Validation >> >> >> >> *Problem Statement:* >> >> >> >> Many of the Point of Contacts listed in ARIN’s public Whois database >> contain out-of-date and inaccurate contact information. >> >> >> >> *Policy Statement:* >> >> >> >> *Current Text*: >> >> >> >> 3.6 Annual Whois POC Validation >> >> >> >> 3.6.1 Method of Annual Verification >> >> >> >> 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. >> >> >> >> *Proposed Revised Text*: >> >> >> >> 3.6 Annual Validation of ARIN's Public Whois Point of Contact Data >> >> >> >> 3.6.1 Annual POC Verification >> >> 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. >> >> >> >> 3.6.2 Specified Public Whois Points of Contact for Verification >> >> 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: >> >> - Admin >> - Tech >> - NOC >> - Abuse >> >> >> >> 3.6.3 Organizations Covered by this Policy >> >> 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. >> >> >> >> >> >> 3.6.4 Procedure for Verification >> >> 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. >> >> >> >> >> >> 3.6.5 Non-Responsive Point of Contact Records >> >> 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. >> >> >> >> _______________________________________________ >> PPML >> You are receiving this message because you are subscribed to >> the ARIN Public Policy Mailing List ([email protected]). >> Unsubscribe or manage your mailing list subscription at: >> http://lists.arin.net/mailman/listinfo/arin-ppml >> Please contact [email protected] if you experience any issues. >> > > > > -- > _______________________________________________________ > Jason Schiller|NetOps|[email protected]|571-266-0006 <(571)%20266-0006> > > -- _______________________________________________________ Jason Schiller|NetOps|[email protected]|571-266-0006
_______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
