[dbwg] Converting Detailed Reassignments to Simple Reassignments

[Ginny Listman]

As discussed during the DBWG session of the ARIN Meeting in Chicago, ARIN 
would like to encourage upstream providers to convert existing detailed 
reassignments to simple reassignments as a means of database cleanup. The
advantage of doing this is the replacement of downstream POCs, many of 
which are outdated or invalid, with the more up-to-date default upstream 
POCs. The existing ORG records for the reassignments would be replaced 
with CUSTOMER records no longer requiring POCs.

The networks to be converted from detailed to simple must meet the 
following criteria:
    - The network cannot have distinct in-addr name servers that are 
      different than their upstream's
    - The network can no longer have its own POCs (only the upstream's 
      will be listed)
    - The existing POC linkage must no longer be desired
    - The network must be a reassignment (no reallocations)

If you wish to do this, you may send a detailed request to 
hostmaster at arin.net with one of the following options:
    - A list of all downstream network handles that should be converted to 
      simple reassignments
    - A list of upstream network handles, for which all downstream 
      reassignments should be converted
    - A list of org handles for which all upstream network handles that 
      have detailed reassignments should be converted

It should be noted that although the POC records will no longer be 
associated with the network, the POC record will remain in the ARIN 
database. If the POC is disassociated with all resources, it will be 
purged from the database after 180 days.

Ginny Listman
Director of Engineering
ARIN