Early Registration Transfer [ERX] Project
Transfer of AS Number Registrations
Please note: the transfer of AS Number registrations
has been completed in 2002. The pages here are for your reference
only and are no longer updated.
Three groups of ASN registrations which are subject to the transfer
process have been identified:
Group 1: ASNs that have only records
in ARIN and no records in the RIPE Database. Check the complete
list of Group 1 AS Numbers.
A FAQ specific to this group is available at http://www.ripe.net/projects/erx/erx-asn/group1-faq.html
Group 2: ASNs that have records both
in ARIN and in the RIPE Database. The records in the RIPE Database
don't contain routing policy specifications (i.e. import/export attributes).
Check the complete list of Group 2 AS Numbers.
A FAQ specific to this group is available at http://www.ripe.net/projects/erx/erx-asn/group2-faq.html
Group 3: ASNs that have records both
in ARIN and in the RIPE Database. The records in the RIPE Database
contain routing policy specifications (i.e. import/export/default attributes).
Check the complete list of Group 3 AS Numbers
A FAQ specific to this group is available at http://www.ripe.net/projects/erx/erx-asn/group3-faq.html
These groups of ASN registrations are transferred
in two stages as follows:
1. Wednesday, 21 August 2002
- Group 1:
- Non-conflicting records are transferred,
- notification is sent to the holders of these ASNs.
- Corresponding objects are created in the Database.
- Group 2:
- Conflicting records without routing policy specification are merged,
- notification is sent to the holders of these ASNs.
- Corresponding objects are modified in the RIPE Database.
- Group 3:
- Announcement is sent to the holders of conflicting ASNs that contain
routing policy specification specifications. The deadline for resolving
the conflicts is 6 September.
2. Friday, 6 September 2002
- Corresponding objects for the Group3 ASNs are modified in the RIPE
Database.
|