[arin-ppml] Policy idea: POC Validation
mysidia at gmail.com
Sat Apr 18 20:27:57 EDT 2015
On Sat, Apr 18, 2015 at 7:01 PM, Bill Woodcock <woody at pch.net> wrote:
> I certainly HOPE it doesn't require a policy proposal. It shouldn't. Nate, what's the quickest process to get this feature added?
The exact procedures ARIN takes to manage POCs and POC e-mail
addresses are out of the scope of policy... therefore: a policy
proposal cannot change them, since these are decisions that have to
be made by ARIN staff in regards to how to implement policy.
However, it seems they ought to take reasonable steps such as
confirming an e-mail address is valid, before it can be used, and not
wait too long for POC validation.... confirming e-mail addresses by
sending an initial message is common practice for most online
My expectation would be that ARIN staff should see this discussion
thread about POC validation; and consider the suggestions about
changes to Annual POC verification e-mail content, the inclusion of a
"Not Acknowledged" Option, that there be an immediate Annual POC
verification required when a new POC is created, and POC information
is not fully visible in Whois, until properly confirmed, And
reallocations that require a POC will be considered invalid for
justifying further resource assignments, if there are no confirmed
POCs on that subdelegation.
And that there be optionally batched e-mail notification to POCs on
additions to new roles or records. With options to object or specify
a different POC with the same e-mail address / consolidate POCs.
More information about the ARIN-PPML