[arin-ppml] Draft Policy ARIN-2017-12: Require New POC Validation Upon Reassignment

Chris Woodfield chris at semihuman.com
Tue Nov 21 20:10:57 EST 2017

First off, I’m in favor of the goal of this proposal; I’m sure that a large percentage of unverified POCs are due to SWIPs being made with POCs that are invalid from the get-go. I expect the language will evolve through the PDP, so I’ll hold off on my “as written” judgement for the time being.

To your specific suggestion: I’d expect that such a mechanism would be a great enhancement to the current validation process, independent of this particular policy proposal. It would be great if it was possible to set up rules in the ARIN portal that, for example, funneled all POC creation attempts with @my.domain as the email address to a specific role account, for example. That said, your suggestion defines an implementation mechanism, not a policy, and as such, doesn’t belong in the NRPM.



> On Nov 21, 2017, at 4:36 PM, james machado <hvgeekwtrvl at gmail.com> wrote:
> Generally I support this idea but I would expand on 3.7.  
> In the event that an entity already has an ARIN POC they would have the option of accepting the new POC or utilizing an existing POC at the entities discretion for the reallocation or reassignment.
> I have been in the position of having multiple unknown POCs with ARIN for $dayjob and having them connected random employees depending on whom the salesman spoke too at the time they were filling out the documents.  I want the option to have all the reassignments/reallocations associated with the POCs I choose.
> James
> _______________________________________________
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.

More information about the ARIN-PPML mailing list