[arin-announce] Changes to Out-of-Region Objects in the RIPE Database

[ARIN]

On 9 May 2018, the RIPE NCC announced that changes would be made to the 
way out-of-region routing objects are managed and represented in the 
RIPE Database. They state:

“A consensus has been drawn following discussions by the RIPE Database 
Working Group community that the Routing Registry will no longer support 
the creation of out-of-region route(6) and aut-num objects. …. Existing 
out-of-region objects will have their "source:" attribute changed to 
“RIPE-NONAUTH” and may be subject to further discussions by the community.”

We strongly encourage any ARIN community member with route, route6, or 
aut-num objects in the RIPE database to review the full text of the RIPE 
Labs article on this change, available at:

https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objects-in-the-ripe-database

We have also created a short FAQ:

https://teamarin.net/2018/07/10/changes-to-out-of-region-route-route6-and-aut-num-objects-in-the-ripe-database/

If you have additional questions, please submit a question to Ask ARIN 
in your ARIN Online account.

Regards,

Mark Kosters
Chief Technology Officer
American Registry for Internet Numbers (ARIN)