AFRINIC has released a new version of its Routing Registry service <https://afrinic.net/en/services/afrinic-irr>.
This new version has removed the need for the ASN holder to authorise route or route6 objects.
Previously, route and route6 objects had to be authorised by both the holder of the IPv4 or IPv6 address space, and the holder of the ASN. In the case that the ASN and the address space were held by different organisations, then there was a process for semi-authorised objects to be held for seven days pending complete authorisation. In the case that the ASN was not issued by AFRINIC, then hostmaster staff had to authorise the route or route6 objects.
After discussion in AFRINIC's database working group <https://lists.afrinic.net/mailman/listinfo/dbwg>, and checking the practices of other Internet Routing Registry services, AFRINIC has decided to remove the need for the ASN holder to authorise any route or route6 objects in the AFRINIC IRR. The route or route6 objects still need to be authorised by the address space holder, using the password associated with the mnt-routes or mnt-lower fields in the associated inetnum or inet6num object. The address holder is responsible for maintaining the accuracy of the route(6) objects in the AFRINIC IRR.
These changes have been reflected in the updated version of the AFRINIC Internet Routing Registry Guide.
https://www.afrinic.net/images/AFRINIC_IRR_Public_Guide_09272018.pdf
