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] re-evaluate route-object authorisation model

• Previous message (by thread): [db-wg] re-evaluate route-object authorisation model
• Next message (by thread): [db-wg] re-evaluate route-object authorisation model

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

Randy Bush randy at psg.com
Fri Jun 26 01:14:49 CEST 2015

> If the address space is assigned by a different RIR then Creating a 
> Route Object in RIPE should be disallowed.

sigh, let's try once more
  o there are operators at euro ixen which require peers' routes be
    registered in ripe irr.  we don't have to like it, it's just
    business; get over it.
  o there are folk who peer at those same ixen whose address space
    was not assigned by ripe ncc.

no one said that turning a sow's ear into a silk purse was easy.

randy

• Previous message (by thread): [db-wg] re-evaluate route-object authorisation model
• Next message (by thread): [db-wg] re-evaluate route-object authorisation model

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

[ db-wg Archives ]