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

The policy "Lame delegations in AFRINIC reverse DNS" has been ratified on 21 March 2018.

The policy ensures that lame delegations appearing in the reverse DNS are acted upon by equipping the WHOIS with automatic checks, notifications to admin-c, tech-c and zone-c contacts of domain objects and removal of lame delegations after 30 days.

On day 1 of every month, a fresh scan of WHOIS domain objects is performed and checks made for lame delegations. During the next 30 days, multiple lameness checks are performed. Up to 4 notifications are sent to admin-c, tech-c and zone-c contacts of domain objects with lame delegations as long as the lame delegations are detected, allowing them to act upon them.

AFRINIC has published a manual <https://www.afrinic.net/services/lame-delegation> for members to act on the lame delegations. At the end of the 30-day period, remaining lame delegations are automatically removed from the WHOIS.

These features have been deployed in the WHOIS.

We are pleased to announce the publication of a guide on AFRINIC’s Internet Routing Registry. AFRINIC Members who use the RIPE NCC database and who are impacted by the upcoming changes in the out-of-region objects in the RIPE NCC database will be able to use the information from the guide to proceed with the migration of their route objects to the AFRINIC IRR.

Continue

The AFRINIC Board has made the following appointments to fill vacant seats in the Board, in terms of Article 13.14 of the AFRINIC Bylaws

Continue

4 July 2018 - This is to inform you that the RIPE NCC will be making some changes to their Internet Routing Registry (IRR) which may affect AFRINIC resource holders effective September 2018. Exact timelines are yet to be determined and announced.

Prior to 2012, when the AFRINIC IRR was established, a large section of AFRINIC resource holders was using the RIPE NCC IRR to maintain their route objects. Even today, many AFRINIC members continue to use the RIPE NCC IRR.

Continue

2 July 2018 - Following the ASO review consultation and the presentation by the CEO at the AIS 2018 meeting in Dakar, AFRINIC’s representatives on the ASO AC/NRO NC have been asked to lead a community process to develop AFRINIC’s response to the ASO review.

The feedback on the ASO Review report outlined 18 recommendations which the NRO has resolved to accept. The first 17 recommendations are expected to be non-controversial and straightforward to implement by the NRO Secretariat, or the ASO Address Council (ASO AC).

The 18th recommendation and the reason for this process, is that “The NRO should initiate a public consultation, involving the five RIR communities, to determine the future structure of the ASO.”

We invite you all to discuss and comment in the community-discuss mailing list.  We hope to provide a report by the end of July 2018 or mid-August at the latest.

Thank you.

Fiona Asonga, Noah Maina and Omo Oaiya

Background:

Various announcements, presentations, calls for comments, etc.:https://www.nro.net/about-the-nro/aso-independent-review-2017/

The ASO Review report: https://www.icann.org/en/system/files/files/aso-review-final-03aug17.pdf

Questions posed by the NRO EC: https://www.nro.net/aso-review-consultation-2018/

CEO presentation at the AIS 2018 meeting:  https://www.internetsummit.africa/components/com_afmeeting/speakers/4/20180511_AIS18_ASO_Review_Consultation.pdf