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

[ARIN]

On 15 March 2018 the ARIN Advisory Council (AC) advanced the following 
Draft Policy to Recommended Draft Policy status:

ARIN-2017-12: Require New POC Validation Upon Reassignment

The text of the Recommended Draft Policy is below, and may also be found at:
https://www.arin.net/policy/proposals/2017_12.html

You are encouraged to discuss all Recommended Draft Policies on PPML 
prior to their presentation at the next ARIN Public Policy Consultation 
(PPC). PPML and PPC discussions are invaluable to the AC when 
determining community consensus.

The PDP can be found at:
https://www.arin.net/policy/pdp.html

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html

Regards,

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)



Recommended Draft Policy ARIN-2017-12: Require New POC Validation Upon 
Reassignment

AC assessment of conformance with the Principles of Internet Number 
Resource Policy:

Recommended Draft Policy ARIN 2017-12 contributes to fair and impartial 
number resources administration by making it easier for ARIN to contact 
the correct individuals who perform the POC functions for reassigned 
resources, in conjunction with ARIN’s administration of those resources. 
It is technically sound in that it ensures that the correct POCs for 
reassigned numbering resources are associated with those resources. 
There is significant community support for this recommended draft policy 
as written.

Problem Statement:

Some large ISPs assign individuals to be POCs for reassigned blocks 
without consultation of the individual they are inserting into Whois. 
For example, during the reassignment/reallocation process, some large 
ISPs automatically create POCs from their customer's order form. This 
process is automated for many ISPs and therefore the resulting POCs are 
not validated prior to being created in the ARIN Whois database. This 
creates unknowing POCs that have no idea what Whois is or even who ARIN 
is at the time they receive the annual POC validation email. It can also 
create multiple POCs per email address causing that same person to 
receive a multitude of POC Validation emails each year.

This policy proposal seeks to improve the situation where a POC is 
unwittingly and unintentionally inserted into Whois.

It also seeks to mitigate the significant amount of time that ARIN staff 
reports that they spend fielding phone calls from POCs who have no idea 
they are in Whois.

Finally, it is hopeful that this proposal will improve the overall POC 
validation situation, by forcing ISPs and customers to work together to 
insert proper information into Whois at the time of sub-delegation.

Policy statement:

Insert one new section into NRPM 3:

3.7 New POC Validation Upon Reassignment

When an ISP submits a valid reallocation or detailed reassignment 
request to ARIN which would result in a new POC object being created, 
ARIN must (before otherwise approving the request) contact the new POC 
by email for validation. ARIN's notification will, at a minimum, notify 
the POC of:

- the information about the organization submitting the record; and
- the resource(s) to which the POC is being attached; and
- the organization(s) to which the POC is being attached.

If the POC validates the request, the request shall be accepted by ARIN 
and the new objects inserted into Whois.  If the POC does not validate 
the request within 10 days, ARIN must reject the request.

Timetable for implementation: Immediate