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/routing-wg@ripe.net/
[routing-wg] [db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
- Previous message (by thread): [routing-wg] [db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
- Next message (by thread): [routing-wg] [db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Wed Nov 11 15:44:18 CET 2015
Hi,
On Wed, Nov 11, 2015 at 02:52:36PM +0100, denis wrote:
[..]
> From what I understood from Gert and Randy's comments it is a user's
> choice where to put a ROUTE object and there seem to be some reasons why
> they sometimes choose to put it in the RIPE Database.
"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).
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: not available
URL: </ripe/mail/archives/routing-wg/attachments/20151111/428965b5/attachment.sig>
- Previous message (by thread): [routing-wg] [db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
- Next message (by thread): [routing-wg] [db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]