John, The policy proposal in the archive initially stated that it should be brought to the attention of the community and didn't imply roadblocks. I forget how the whois requirement was inserted and I don't really care since the issue is policy, but if I recall correctly that whois document wasn't a legal agreement "back then". Transparency != 6 pages of legalese.
Would have been nice to for the system to generate a warning to an associated admin POC that ARIN was going to cripple a networks ability to maintain its resource legitimately. IMHO, ARIN is over stepping its boundaries. YMMV, Marty > On Aug 18, 2014, at 17:38, John Curran <[email protected]> wrote: > >> On Aug 18, 2014, at 5:14 PM, Martin Hannigan <[email protected]> wrote: >> >> The policy doesn't state users should be locked out, rather it states a list >> will be provided publicly and the POC marked "invalid". POC invalidation >> works. Wheres the list? > > Martin - > > Per NRPM 3.6.1) - "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." > > Note that available to the community and subject to the current bulk Whois > policy > is not quite the same as "publicly"; for more details on the Bulk Whois AUP, > you > should check here: > > https://www.arin.net/resources/request/bulkwhois.html > > Once you have signed the Bulk Whois AUP, you may download the list > of "Number Resources without valid POCs" via ARIN Online under the > "Downloads & Services" menu item - > > <https://www.arin.net/public/secure/downloads/index.xhtml> > > FYI, > /John > > John Curran > President and CEO > ARIN > > _______________________________________________ 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.
