This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
- Previous message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
- Next message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Shaw
daniel at afrinic.net
Wed Dec 13 05:39:35 CET 2017
On 05/12/2017, 11:11, Tim Bruijnzeels via db-wg typed: > > > We suggest the following solution as a basis for further discussion. > > 1) Remove the "origin:" authorization requirement > the "mnt-routes:" attribute on AUT-NUM objects will no longer be useful. We propose that the attribute is deprecated and removed from existing objects (of course with notification to the object holders). > Finally, there will be no more need for the existence of out-of-region AUT-NUM objects in the RIPE database. We propose that these objects will be deleted. > 2) Flag "route:" objects for non-RIPE-managed space with "source: RIPE-NONAUTH" to identify non-authoritative data. This all looks good to me. I'm in agreement as is. Thanks, Daniel
- Previous message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
- Next message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]