[DBWG] Routing registry - remove out-of-region autnum authentication

Ben Maddison benm at workonline.africa
Fri Sep 21 11:50:20 UTC 2018


That is excellent news. Thanks Yogesh.

Cheers,

Ben Maddison

Director
Workonline Communications (Pty) Ltd

Office:      +27 (0) 21 200 9000
Mobile:      +27 (0) 82 415 5545
Email:       benm at workonline.africa

________________________________________
From: Yogesh Chadee <yogesh at afrinic.net>
Sent: 21 September 2018 13:12:39
To: dbwg at afrinic.net
Subject: [DBWG] Routing registry - remove out-of-region autnum authentication

[https://tr.cloudmagic.com/h/v6/emailtag/tag/2.0/1537528359/51bf3281b356b58b13ff396fe8512afa/6/63af1217fc13a95cdef1b135550be1a0/c6721e3f73eb911c3f5a7b1a5ccfa89d/f745025024a0f24def6a91eb0dabd3f6/newton.gif]
Dear all,

AFRINIC will release a new version of its Routing Registry service on 27 September 2018. This will remove 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 7 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,  mnt-lower, or mnt-by fields in the associated inetnum or inet6num object.

Best regards,
AFRINIC Applications Unit



More information about the DBWG mailing list