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 ]
Sandra Murphy
sandy at tislabs.com
Fri Jun 15 16:54:51 CEST 2018
> On Jun 15, 2018, at 9:12 AM, Sascha Luck [ml] via db-wg <db-wg at ripe.net> wrote: > > There is nothing stupid or unreasonable about asking to delay an > action that *will* cause operational issues even if their root > cause lies elsewhere. “Our operation relies on insecurity in the IRR database, so we want you to maintain your insecurity so that we can maintain our operational design” Relaboring the point: It is not “*will* cause”. Using some other IRR database would avoid the operational issue. This operational issue could also be avoided if someone with a maintainer somewhere just proxy-registered a route object on their behalf. (Anyone but me see irony in that?) —Sandy
- 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 ]