<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear colleagues,<br class=""><br class="">On Tuesday, 4 September, we will make changes to the way out-of-region<br class="">objects are handled in the RIPE Database, as directed by the RIPE<br class="">Database Working Group.<br class=""><br class="">We will implement the following changes in this order between 09:00 and 15:00 UTC+2.<br class=""><br class="">1. The RIPE Routing Registry will no longer support the creation of<br class="">out-of-region ROUTE(6) and AUT-NUM objects<br class="">2. The creation of ROUTE(6) objects will no longer need authorisation<br class="">from the ASN holder<br class="">3. Existing out-of-region objects will have their "source:" attribute<br class="">changed to "RIPE-NONAUTHâ<div class=""><br class=""></div><div class="">For users of NRTM, these changes will be reflected on the FTP website after 00:00 UTC+2 on Wednesday, 5 September.<div class=""><br class="">You can find our implementation plan at:<br class=""><a href="https://www.ripe.net/manage-ips-and-asns/db/impact-analysis-for-nwi-5-implementation" class="">https://www.ripe.net/manage-ips-and-asns/db/impact-analysis-for-nwi-5-implementation</a><br class=""><br class="">We also published an article on RIPE Labs with some background and<br class="">additional context:<br class=""><a href="https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objects-in-the-ripe-database" class="">https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objects-in-the-ripe-database</a><div class=""><br class=""></div><div class="">We will inform the Database Working Group once all changes have been implemented. <br class=""><br class="">Kind regards<br class=""><br class="">Nathalie Trenaman<br class="">Product Manager<br class="">RIPE NCC</div></div></div></body></html>