Administrative and Policy-Related Questions
- What does “legacy” mean?
"Legacy" is the term given to those Internet number resources that were distributed before (or outside of) the current system of hierarchical distribution by the Regional Internet Registries (RIRs).
- What is a top-level legacy INETNUM object?
Legacy address space is hierarchical. For every legacy hierarchy in the RIPE Database there is one inetnum that sits at the top of the hierarchy. The RIPE NCC considers the holder of this inetnum as the top-level legacy resource holder. All more specifics to this object are considered to have some business or contractual or historical relationship with the top-level legacy resource holder.
- Why are all these changes to legacy resources being made now?
The RIPE community has accepted the policy proposal 2012-07, "RIPE NCC Services to Legacy Internet Resource Holders". The RIPE NCC has started implementing this policy according to this plan.
- Why has the “status:” attribute of my INETNUM object(s) been changed to ‘LEGACY’.?
For inetnum objects in the RIPE Database, all legacy Internet resources originally had the "status:" attribute value ‘EARLY-REGISTRATION’. Users were able to change this attribute value and many objects have been updated. This status value was no longer considered reliable.
In order to achieve a transparent, complete and accurate overview of legacy resources in the RIPE Database, a new ‘LEGACY’ value for the “status:” attribute of inetnum objects has been introduced. The RIPE NCC has set the “status:” in inetnum objects to ‘LEGACY’ for all top-level legacy Internet resources and more specifics in the RIPE Database.
- Why does my AUT-NUM object(s) now have a “status:” attribute?
There are three different categories of aut-num objects in the RIPE Database. Until recently, there was no indication of which category an aut-num object in the RIPE Database belonged to. The RIPE NCC introduced a new generated “status:” attribute to clearly show which category an aut-num object belongs to.
- What values can an AUT-NUM “status:” attribute have?
There are three values that can be set:
- ‘ASSIGNED’, - all AS Number resources assigned by the RIPE NCC
- ‘LEGACY’ - all legacy AS Numbers used within the RIPE region but not assigned by the RIPE NCC
- ‘OTHER’ – any aut-num that is not one of the above, typically a non-authoritative copy of an aut-num from another RIR region used for routing authentication in the RIPE Database
- Does this changed status of my INETNUM or AUT-NUM object affect the holding or responsibility of my resource?
No. This change is only administrative. Holding and responsibility for the legacy resources is not affected by the status changes.
- Will the RIPE NCC contact all legacy resource holders individually about these changes?
The RIPE NCC has contacted all aut-num resource holders, including legacy resource holders. In the case of legacy address space, the RIPE NCC will only contact and have discussions with the top-level legacy resource holder.
- Should I contact the RIPE NCC about these changes?
No. If you are a legacy aut-num resource holder or a top-level legacy inetnum resource holder, the RIPE NCC will contact you to discuss the situation. This process will start in Q3 2014.
- Who should provide details about these changes to the more specific legacy resource holders?
This is the responsibility of the top-level legacy resource holders.
- My legacy address space is shown as part of another hierarchy. How can I be recognised as a top-level legacy resource holder?
You need to discuss this with the current top-level legacy resource holder and provide the RIPE NCC with documentation showing that this resource was transferred to you in the past. If satisfactory documentation is provided, the RIPE NCC will split the current top-level inetnum object to make your inetnum a separate top-level object.
- I received an email about a legacy resource object that should not be registered to me. What should I do?
You have received this email because your contact details are registered in the corresponding object in the RIPE Database. If this is an aut-num or top-level legacy inetnum object, first contact the maintainer or other people referenced in the object. If there are no other contacts, or you receive no response, please contact the RIPE NCC: firstname.lastname@example.org. If the inetnum object is more specific to a top-level legacy resource object, please contact the top-level legacy resource object holder. If you get no response and you want your personal details removed from the RIPE Database, please contact email@example.com.
- The “status:” of my INETNUM object changed to ‘LEGACY’. Why was I not notified?
When the RIPE NCC updated all the more specific inetnum objects to the top-level legacy objects we suppressed notifications. There are about 35,000 more specific inetnum objects. Each could have multiple notification email addresses. It is not practical to send what could be 100,000 emails at once, any of which could trigger a question to the RIPE NCC. Along with the status change, we added a link to this FAQ that should answer all your questions.
- I don’t understand this issue about legacy resources, who can I talk to?
If you have a legacy aut-num or a top-level legacy inetnum object, you will have been notified in an email sent by the RIPE NCC. If you have a more specific inetnum to the top-level legacy resource, you need to talk to that top-level legacy resource holder.
- I used to have PI space with “status:” ‘ASSIGNED PI’. Can I change my resource status back?
If it is a top-level legacy resource with no more specifics, it can be converted to ‘ASSIGNED PI’ address space. The RIPE NCC will contact you about this sometime after the start of Q3 2014.
If it is a top-level legacy resource with more specific inetnum objects, it may be possible to convert it to ‘ALLOCATED PA’. It cannot be converted to ‘ASSIGNED PI’, even if it was PI space before. The RIPE NCC will contact you about this sometime after the start of Q3 2014.
If it is a more specific inetnum to a top-level legacy resource, it cannot be converted to ‘ASSIGNED PI’, even if it was PI space before. You need to contact the top-level legacy resource holder to discuss your options.
- I used to have address space with “status:” ‘ALLOCATED PA/PI/UNSPECIFIED’. Can I change my resource status back?
If it is a top-level legacy resource object, it can be converted to ‘ALLOCATED PA’. The RIPE NCC will contact you about this sometime after the start of Q3 2014.
If it is a more specific inetnum to a top-level legacy resource, it cannot be converted to ‘ALLOCATED PA’, even if it had the status of an allocation before. You need to contact the top-level legacy resource holder to discuss the options available to you.
- Can I convert my top-level legacy INETNUM resources to ‘ALLOCATED PA’ or ‘ASSIGNED PI’?
Yes. If you have (or plan to have in the future) a hierarchy of address space, it can only be converted to ‘ALLOCATED PA’. If there is no hierarchy, it could be converted to either ‘ALLOCATED PA’ or ‘ASSIGNED PI’. In Q3 2014, the RIPE NCC will begin to contact the holders of top-level legacy inetnum and legacy aut-num resources to determine whether they would like a direct or indirect contractual relationship with the RIPE NCC. All legacy Internet resource holders who choose to enter into a direct or indirect contractual relationship with the RIPE NCC can choose to keep their resources registered as ‘LEGACY’ or register them as though they had originally been distributed by the RIPE NCC.
- Can I register my legacy Internet resources with an LIR?
Yes- if it is a top-level legacy inetnum resource or a legacy aut-num. In Q3 2014, the RIPE NCC will begin to contact the holders of top-level legacy inetnum and legacy aut-num resources to determine whether they'd like a direct or indirect contractual relationship with the RIPE NCC. Legacy Internet resource holders will have several options available to them, including engaging with the RIPE NCC through a sponsoring LIR (see section 2.0 of ripe-605, “RIPE NCC Services to Legacy Internet Resource Holders”).
- Who is responsible for keeping legacy resource information up-to-date in the RIPE Database?
The legacy aut-num holder and the top-level legacy resource holder is responsible for the accuracy of their data in the RIPE Database. Where there are more specific objects to the legacy resource, the top-level legacy resource holder is also responsible for making sure all the data relating to all the more specifics is accurate in the RIPE Database.
- The RIPE Database shows me as a top-level legacy resource holder but I am not responsible for some of the more specifics. How do I fix this?
If you have transferred one or more of the more specific resources to other organisations/individuals, this needs to be shown in the RIPE Database. Please contact firstname.lastname@example.org and provide appropriate documents to show that this transfer has taken place. The RIPE NCC will then split your top-level legacy resource to reflect the new situation.
- The RIPE Database shows me as a top-level legacy resource holder but I am not responsible for any of these resources. How do I remove my details from the RIPE Database?
Some organisations were tasked many years ago to ‘hand out’ address space to other organisations to help develop Internet usage. It may be that the RIPE Database still shows you as the top-level legacy resource holder and responsible for all the more specifics. If you no longer hold that responsibility, please contact email@example.com and explain the situation. It may be that you have no documentation and no longer have any business or contractual relationship with the more specifics. The RIPE NCC may still be able to remove your top-level legacy resource object from the RIPE Database and raise all the one-level more specific objects to top-level legacy resources.
- I have a question about status values that is not answered by this FAQ. What should I do?
If your question is related to the introduction of the “status:” attribute in aut-num objects and/or the change in the value of the “status:” attribute of inetnum objects to ‘LEGACY’, please contact firstname.lastname@example.org. You will receive an auto-response acknowledging your question. The RIPE NCC will collect these questions and may update this FAQ by adding questions, along with the appropriate, corresponding answers.