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] 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
Wed Jun 13 16:49:33 CEST 2018

> On Jun 13, 2018, at 9:23 AM, Lu Heng via db-wg <db-wg at ripe.net> wrote:
> 
> I do not mean in the very least sense to delay an implementation unless the risk shown by it is far too serious. So if it is just because no one notices the problem in the very beginning (which I am trying to address now)

Not true that no one noticed the problem.

Lots of discussion of the problem on the working group list, which included why people want to register route objects in the RIPE db for non-RIPE resources.

—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 ]