+1 on this as well
Albert Erdmann
Network Administrator
Paradise On Line Inc.
On Tue, 26 Feb 2019, ARIN wrote:
The following has been revised:
* Draft Policy ARIN-2017-12: POC Notification and Validation Upon
Reassignment or Reallocation
Revised text is below and can be found at:
https://www.arin.net/policy/proposals/2017_12.html
You are encouraged to discuss all Draft Policies on PPML. The AC will
evaluate the discussion in order to assess the conformance of this draft
policy with ARIN's Principles of Internet number resource policy as stated in
the Policy Development Process (PDP). Specifically, these principles are:
* Enabling Fair and Impartial Number Resource Administration
* Technically Sound
* Supported by the Community
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)
Draft Policy ARIN-2017-12: POC Notification and Validation Upon Reassignment
or Reallocation
Problem Statement:
Some 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 prevent the situation where a POC is
unwittingly and unintentionally inserted into Whois. Doing so will reduce the
significant amount of time that ARIN staff spend fielding phone calls from
POCs who have no idea they are in Whois.
The proposal will improve the overall POC validation situation, by ensuring
that all reallocation or detailed reassignment requests are related to a
pre-existing receiving organization with at least one valid POC object, and
by requesting that any other existing invalid POC objects are validated.
Policy statement:
Insert one new section into NRPM 3:
3.7 POC Notification and Validation Upon Reassignment or Reallocation
When a request for reallocation or detailed reassignment is made to ARIN, the
receiving organization must already be in the ARIN database and linked to at
least one valid POC object. If there is no valid POC object associated with
the receiving organization, ARIN shall reject the request.
In addition to notifying the requester, ARIN will also notify, via email, all
POCs associated with the receiving organization, whether the request was
successful or not, and will request validation of any invalid POC objects
associated with the receiving organization.
Note: Simple reassignments are made without any linkage to an organization or
POC objects in the ARIN database.
Comments:
Timetable for implementation: Immediate
_______________________________________________
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:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
_______________________________________________
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:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
