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] A test on AFRINIC range announcing without RIPE route object
- Previous message (by thread): [db-wg] A test on AFRINIC range announcing without RIPE route object
- Next message (by thread): [db-wg] A test on AFRINIC range announcing without RIPE route object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Suchy
danny at danysek.cz
Wed Jun 13 14:24:05 CEST 2018
Hello, On 06/13/2018 01:39 PM, Sascha Luck [ml] via db-wg wrote: > There was a time when it would have been seen as the obligation > of any RIR to keep the internet running as smoothly as possible. sometimes things needs to be really breaked to get fixed them. People are lazy, they're ignoring all notifications to fix "legacy" things, refusing changes, when things "currently" somewhat works for them. > IMO such actions should be delayed until there is a mechanism for > every resource holder to register their advertisements properly, > no matter where they are. Presumably this is something the RIRs > themselves could be pushing as they are coordinating among > themselves and with ICANN anyway. There's no reason for again delaying things from my perspective. It's problem on advertising (and relevant RIR) side, and there is easy option to fix root cause of their problem. Solution exists. With regards, Daniel
- Previous message (by thread): [db-wg] A test on AFRINIC range announcing without RIPE route object
- Next message (by thread): [db-wg] A test on AFRINIC range announcing without RIPE route object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]