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] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

• Previous message (by thread): [db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
• Next message (by thread): [db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Randy Bush randy at psg.com
Thu Nov 12 04:00:11 CET 2015

> "Document everything one AS originates in a single database" is the
> primary motivation here (so upstreams/peers can go to a single source
> to build filters, and that single source must not be RADB).

and why not?

randy

• Previous message (by thread): [db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
• Next message (by thread): [db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]