[arin-ppml] Policy Proposal Idea: Reassignment records for IPv4 End-Users

Andrew Dul andrew.dul at quark.net
Mon Jul 13 11:31:09 EDT 2015

The AC has been discussing the following ideas on their list and I have 
drafted the following policy proposal as an outcome.  We are posting the 
ideas and proposal here to PPML for community discussion.  This draft 
has not been submitted formally to the PDP process at this point.  I 
believed having initial feedback from the community before submitting 
would be a valuable addition before going into the formal process.

You comments are welcome.




1.    Policy Proposal Name: Reassignment records for IPv4 End-Users

4.    Problem Statement:

End-User Organizations do not have the ability to create reassignment 
records in the number resource database.

Reassignment records can be used for a number of different functions 
which could benefit the overall desire to increase database accuracy by 
allowing organizations to add additional details in the database.

The following reasons have been noted as positive reasons to allow the 
creation of additional records.
-    Geolocation (allows an organization to specify a different location 
within the database which is used by organizations creating geo-location 
by IP address databases)
-    Subsidiary reassignment (allows an organization to note that a 
portion of their netblock is in use by a different subsidiary entity)
-    Assignment to contracted parties (some organizations have contracts 
with other organizations which are operating networks under agreements 
with the registrant, this allows the top-level organizations to 
accurately specify the organization operating the network in the number 
resource database)
-    More specific contact information (some organizations operate large 
networks which don’t necessarily have the same technical or abuse 
contact information)

5.    Policy statement:

Create new section 4.3.x

End-user organizations which have an active registration services 
agreement shall be permitted to create reassignment records in the 
number resource database.  Organizations shall use the guidelines 
outlined in section 4.2.3 when creating reassignment records.

     a.    Timetable for implementation: immediately
     b.    Anything else:

It is noted by the author of this policy proposal that one of the 
distinctions in the service between ISPs and End-Users has been the 
ability for an organization to create reassignment records.

This policy proposal stretches across responsibilities areas as it 
impacts number policy, ARIN operational practice, and fees.

Below we have noted the three areas and the different responsibilities:

A)    Providing reassignment support for end-user assignments, for those 
who wish to use it

This is an ARIN Service issue - could be an suggestion/consultation 
process, so long as any implied additional workload/cost can be 
accommodated in budget and the community supports

B) New requirement on end-users to provide reassignment information in 
certain circumstances so that ARIN will treat their usage assertion credibly

This is a policy issue.  These requirements should be vetted through the 
policy development process.

C)    Fee Implications of ISPs moving to end-user category

This is Board issue, but first requires a community discussion or 
consultation to be held to solicit community input on desired outcome.


More information about the ARIN-PPML mailing list