Transfer of Networks in 198/8
As part of this ongoing project, the RIPE NCC will begin the transfer of networks in the 198/8 range on 29 July 2004.
Contacts for networks to be transferred to the RIPE Database will be notified by email on 29 July 2004. The contact will receive a single e-mail listing all the affected networks for which they are referenced as a contact.
In this message there will be a link to a web page through which the contact can provide us with the necessary information for these networks.
Mails will be tagged with a unique ticket number (one per contact). Please do not remove the ticket number from the subject header when replying to the email.
The transfer process is as below:
APPROACH
The plan is to perform the transfer by /8. For each /8 the following tasks have to be performed:
- Conflicts (contacts and description) to be resolved
- Records and associated documentation to be transferred
- Reverse delegation to be set up
CONFLICTS
The following types of conflicts have been identified:
C1. Record exists in ARIN Database only. There is no exact matching (range wise) record in the RIPE Database.
Proposal: to update internal documentation, create the record in the RIPE Database and protect with a unique generated maintainer. The inetnum will be created with a status attribute value of "EARLY-REGISTRATION"(*)
C2. Range matches records in both ARIN and RIPE Databases. This means that contact and description may be different. Most cases indicate out of date information in one of the Databases, not real conflicts or attempts to hijack address space. What happened in most cases is that people started maintaining their allocation or assignement in the RIPE Database, especially since the RIPE Database started to support the Routing Registry.
Proposal: Notify the contacts and give them time to reach consensus. After the deadline merge the records whose contacts have not responded. Database objects will not be locked by either ARIN or the RIPE NCC during the transfer process. The RIPE NCC will not change the maintainer on objects following the transfer process.
C3.0 Record exists in the RIPE Database only.
C3.1. One reason why such situation may exist is that this is a valid RIPE NCC allocation.
Proposal: To preserve information in the RIPE Database. The existing value of the status attribute will be preserved. If the existing inetnum object does not have a status attribute a status attribute with a value of "EARLY-REGISTRATION"(*) will be inserted.
C3.2 Another situation is that the registration data is simply garbage.
Proposal: Notify contacts and give them time to explain the situation. Where no explanation is forthcoming or the contacts explain that the registrations are 'garbage' the records will be deleted.
(*) The status of "EARLY-REGISTRATION"(*) is a special value proposed for the ERX networks. It has no policy implications and objects with this status can be created only by the Database Administration.
PROCEDURE for a /8
- Pre transfer
1.1 Initial dump is prepared for transfer by ARIN
1.2 Announcement is sent to ARIN's contacts
1.3 Reverse delegation domain space is cleaned up in the RIPE Database (reverse domain objects for which no delegation was provided are deleted) - Transfer
2.1. Final dump is prepared by ARIN
2.2. C1 group: database records are imported, documentation is updated, contacts are notified
2.3. C2 group: contacts (ARIN+RIPE) are asked to reach consensus.
2.4. C3.2 group: contacts are notified of possible deletion. - Conflict resolution
3.1 C2 group: non responding records are merged but not locked.
3.2 C3.2 group: records without good reasons are deleted.
TIMELINE
Pre-transfer: Happens on 29 July 2004
Transfer: Happens on 30 August 2004 and only takes 1 day.
Conflict resolution: May continue after 30 August 2004 if necessary.
