Dear colleagues, As directed by the Database Working Group, we will soon be making changes to the way out-of-region objects are handled in the RIPE Database. It's important that database users are aware of these changes and what they mean: 1. The RIPE Routing Registry will no longer support the creation of out-of-region ROUTE(6) and AUT-NUM objects 2. The creation of ROUTE(6) objects will no longer need authorisation from the ASN holder 3. Existing out-of-region objects will have their "source:" attribute changed to "RIPE-NONAUTH" You can find a full list of planned actions here: https://www.ripe.net/ripe/mail/archives/db-wg/2018-February/005825.html <https://www.ripe.net/ripe/mail/archives/db-wg/2018-February/005825.html> We recently published an article on RIPE Labs with some background and additional context: https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-object... <https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objects-in-the-ripe-database> There is still some time before these changes come into effect, as we plan to deploy them in September. We will be sending regular updates to the RIPE Datbase WG mailing list at <db-wg@ripe.net <mailto:db-wg@ripe.net>>. Please join this mailing list if you would like to stay updated. Kind regards Nathalie Trenaman Product Manager RIPE NCC