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] Route Object Cleanup (Was: Re: RIPE 66 Draft minutes)
- Previous message (by thread): [db-wg] RIPE 66 Draft minutes
- Next message (by thread): [db-wg] Route Object Cleanup (Was: Re: RIPE 66 Draft minutes)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
rhe at nosc.ja.net
Wed May 15 12:28:48 CEST 2013
Hi, I notice this item in the minutes: > Route object cleanup: proposal to change auth requirements for route object from IP address holder and ASN holder to only IP address holder. Concern was expressed that this effectively gives permission for the address holder to write to the AS owners routers. It was felt that this was a dangerous precedent. > [AP66.2] RIPE NCC Raise this proposal on the DB-WG mailing list for discussion Unfortunately I was in the Address Policy WG this morning, not in DB, and wasn't aware this was going to be discussed. This is a topic that comes up periodically, as whilst the authentication rules for route object creation have a reason, they are at times arcane and at time the inability to find the right contact in another ASN can lead to delays in being able to route a prefix. On Thursday's Routing WG session, George Michaelson of APNIC will make a very strongly related suggestion: <https://ripe66.ripe.net/presentations/218-RIPE66-Dublin-Route-Object-Process-Improvement.pdf> I'm happy to see discussion of this on the DB WG, but you're also more than welcome to join in the routing WG session and discuss this on the routing list too. All the best, Rob
- Previous message (by thread): [db-wg] RIPE 66 Draft minutes
- Next message (by thread): [db-wg] Route Object Cleanup (Was: Re: RIPE 66 Draft minutes)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]