Importing route objects from another IRR

APNIC operates an Internet Routing Registry (IRR), which at this time, is embedded in the normal APNIC Whois Database as ‘source APNIC’. This IRR permits the full set of RPSL objects to be created and maintained under normal whois methods or via MyAPNIC.

Some Internet number resource (INR) holders maintain their RPSL data in other IRRs such as RADB, the RIPE NCC Routing Registry or the JPIRR. There are sometimes circumstances where an INR holder wishes or needs to import these objects into the APNIC registry.

The primary purpose of the APNIC Whois Database service is an allocation and assignment registry view, and APNIC reserves the right to move IRR information to another service. Noting that, this is our understanding of the possible classes of need you may encounter.

1. Only APNIC maintained INR assets

At this time, only route objects that relate directly to resources maintained by APNIC or the NIR community under APNIC can be imported directly. RPSL references can be made to INRs that lie outside of APNIC, but not as primary objects. For example, ‘route:’ and ‘route6:’ objects can refer to an external ‘origin-as:’ value but can only reference ‘inetnum:’ and ‘inet6num’ objects that lie in the APNIC managed ranges.

2. Types of object being imported

  • Any valid RPSL object can be imported, as long as it refers to primary resources (IPv4 or IPv6) maintained in APNIC.
  • Associated policy objects that conform to RPSL specification as implemented by the RIPE whois code.

APNIC expects the majority of imports to be ‘route:’ and ‘route6:’ objects maintained in RADB or the RIPE whois.

3. Your addresses, your ASN

If the entity controlling the INR is an APNIC Member, then objects can be created in the APNIC Whois Database using normal mechanisms (MyAPNIC or the email) with no other consequences. Please follow the normal whois object management process.

4. Your addresses, somebody else’s ASN

If, for IPv4 and IPv6 addresses managed through APNIC, a route object refers to an ASN (‘origin:’) for which you do not have the appropriate IRR authorization, the system will still permit the object to be created. However, in this case, a notification email will be sent to the ASN holder automatically to inform them of the new objects. APNIC reserves the right to alter objects in light of any feedback from the ASN holder.

5. Your addresses, under an NIR

If the IPv4 and IPv6 resources lie under one of the APNIC NIRs and are not directly managed at APNIC but are in the APNIC regional management set, the NIR is able to apply the objects on your behalf. In some cases, the NIR operates their own IRR services (JPNIC JPIRR) and will elect which is the best location to represent the objects. In complex situations, APNIC Hostmasters/Helpdesk can help with the object creation along with the NIR. Normal obligations (as above) will apply to out of region ASNs in ‘origin-as:’ references.

6. Your addresses but some unallocated ASNs

In some cases, people seek to declare routing against undefined or unallocated resources. APNIC Hostmasters will engage with Members in these situations to discuss the object creation.

7. Addresses managed outside of the APNIC region

APNIC does not permit the creation of routing objects that relate to resources outside the APNIC region. It is possible that future service models will be deployed that can use external authorization hooks to present a more encompassing service, but at this time, only resources that are under direct APNIC management can be maintained in the APNIC IRR.