Guide to the maintenance of historical Internet resources
Table of contents
1. Introduction
2. Sources of historical resources
2.1 Early Registration Transfer (ERX)
2.2 AUNIC to APNIC migration
2.3 Historical APNIC resources
3. How to update resource registrations
1. Introduction
These guidelines complement the policy document [APNIC-127] APNIC Internet Number Resource Policies, and are intended to guide LIRs wishing to update information about historical Internet resources registered in the APNIC Whois Database.
2. Sources of historical resources
2.1 Early Registration Transfer (ERX)
Most historical registrations were initially made by the global registries that predated ARIN, such as DDN-NIC, SRI-NIC, and InterNIC. ARIN inherited these registrations automatically when it was established. Historical registrations made to organisations in the APNIC region are being transferred to APNIC during 2003 and 2004 as part of the RIRs’ Early Registration Transfer (ERX) project.
A list of resources transferred to APNIC as part of the ERX project is available at: Early registration transfer project
2.2 AUNIC to APNIC migration
Some historical resource registrations have been inherited by APNIC from the former AUNIC address registry.
A list of resources transferred to APNIC as part of the migration is available at: Transfer of AUNIC network records
2.3 Historical APNIC resources
Historical APNIC resources were delegated to organisations by APNIC prior to the introduction of a membership structure. These resources have always been registered in the APNIC Whois Database, but if the resource holder did not become an APNIC member at any time after the introduction of the membership structure, the resources were not made subject to current APNIC policies.
3. How to update resource registrations
To update registrations, the following steps must take place:
Step 1 |
The resource holder contacts APNICIf the organization is an existing APNIC member, the organization can contact APNIC hostmasters directly by email or phone. If the organisation as an APNIC non-member account or has no previous relationship with APNIC, the resource holder should complete the Historical maintain form |
Step 2 |
APNIC verifies the organization is the legitimate holder of the resourcesIf the resource holder is an existing APNIC member and the historical resource registration shows the same organisation details, APNIC Hostmasters will accept that the member is the legitimate holder of the resources. If the registration details are substantially different from the member’s details, the member may need to complete a declaration form or claim responsibility for the resources. If the resource holder does not have an existing APNIC member or non-member account:
|
Step 3 |
APNIC updates the historical resource registration in the APNIC Whois DatabaseThe resource holder’s own maintainer can then be added to the “mnt-lower” attribute of inetnum objects to allow the holder to create sub-allocation assignment objects within the address range. The resource holder’s own maintain can also be added to the “mnt-routes” attribute of inetnum or aut-num objects to allow the creation of route objects associate with the resources. Please note that the maintainer will be removed from the “mnt-lower” field if the organisation ceases to pay the fees associated with their APNIC member or non-member account. In addition, historical resource holders with a current APNIC account have access to MyAPNIC, which allows organisations to manage their resources and account information via a secure website. |