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/[email protected]/
[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 ]
Randy Bush
randy at psg.com
Wed Feb 14 04:59:22 CET 2018
>> This can be a separate effort. However, what I did not mention >> earlier is that we probably should disallow the creation of new >> out-of-region AUT-NUM objects if they are no longer required to >> authorise ROUTE(6) objects. how long do you think it will be before there are no inter-region barriers to AS transfers? add a year or so to that to give people time to clean up the mess caused by this policy hole. > Yes, I support disallowing the creation of NEW out-of-region AUT-NUM > and ROUTE objects. not exact;ly what tim was suggesting, see above. > I keep seeing route objects covering non-RIPE IP space popping up in > the RIPE IRR for nefarious purposes. that may be the wrong question. are some appearing for legitimate and useful purposes? if so, how will those needs be addressed going forward? randy
- 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 ]