This section details the technical side of how to use the Routing Registry and how to actually create and maintain objects on the DB in practice
- Each RIR database is independent from the other RIRs databases.
- Creation of the route objects is based on the planned routing policy, other objects may be needed based on the specific case.
- Creation of routing objects doesn't mean that your routes will be advertised. You still need to configure BGP on your routers and complete the network setup with your transit/upstream providers.
- Existence of routing objects prevent your routes from being filtered in the Internet routing table - in cases where automated checks happen
Before an AFRINIC Resource Member can use the routing registry, there are some prerequisite information that the member needs to be aware of. Such information are shared with the registered contacts of the organisation in the AFRINIC Registry/Databases and therefore it’s critical that the person attempting to create, update route-related objects are aware of these.
- Member is COC compliant
- The minimum required objects, to create route(6) objects are:
- The maintainer on the IP Number Resources?
- The maintainer authentication (password, PGP key, X.509)
- The autonomous system number(ASN) that shall originate the IPv4 or IPv6 prefix
- In case you are trying to create the route object for your IPv4 prefix issued by AFRINIC
- or inet6num
- In case you are trying to create the route6 object for your IPv6 prefix issued by AFRINIC
If you are a legacy resource Holder and need help with your route objects, please contact us on email@example.com
AFRINIC recommends that:
- You ensure your membership account has no outstanding balance
- Contact details are updated after staff joins in or leave your company
- Maintainer passwords are kept up to date
- Avoid proxy registration to ensure full control of your routing policies and route objects. Proxy registration relate to cases where your upstream or another third party creates and maintains your route objects.
- If you hold resources from AFRINIC, have your route object registered in the AFRINIC IRR
- Migrate route objects from third-party IRRs to AFRINIC to avoid being filtered after housecleaning by the third-party IRR
- Encourage resource members to clean up the various registries to avoid inconsistencies using tools such as https://irrexplorer.nlnog.net
- Inform AFRINIC(via firstname.lastname@example.org) in case your upstream provider still insist to have the route objects created on other IRRs such as RIPE NCC
- Regarding changes in RIPE NCC’s IRR DB, Operators are encouraged to perform whois queries, specifying the source IRR with the source flag (-s or --sources). For example, if they only specify "RIPE", then no out of region objects will be returned. If no source flag is specified, then matches from both RIPE and RIPE-NONAUTH are returned.