[db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

Hi,

On Thu, Nov 12, 2015 at 12:00:11PM +0900, Randy Bush wrote:
> > "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?

RADB?  Because anyone can put arbitrary stuff in there and the operators
seem more interested in selling maintainers (so you can protect your
own objects that you have put in there, which shouldn't be there in
the first place for RIPE region stuff).

Now, if the RADB would only serve as aggregator for properly authenticated
and sanitized objects from the 5 RIR IRRDBs, it would be useful.

Right now, it is dangerous, because people building filters from it believe
they are spending their efforts in a positive way.  They are deluded, as
anyone can circumvent these filters easily... (had this happen to a network
of ours - the /22 was not announced yet, route: object entered into the
RADB, announced for half an hour for spamming, merit refused to remove the
rogue object because "please contact the people who put it in" even though
it was perfectly clear from comparison with the mirrored RIPE objects that
it was bogus).

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/db-wg/attachments/20151112/e8150084/attachment.sig>