[routing-wg] Who uses the RIPE IRR and for what?

Hi,

On Wed, Nov 19, 2014 at 06:31:56PM -0800, Ronald F. Guilmette wrote:
> Of the remaining 235,061 route base IP addresses, fully 28,988 of
> those (12.3%) are being announced by some AS other than the one
> specified in the ripe.db.route file.

To state something that might be obvious or not - for the same prefix,
you can have multiple route: entries with different origin ASes, which
makes sense when a network moves (add new route: object, start new
announcement, eventually remove old route: object).  So, some of these
might be perfectly fine, some might be forgotten (= a route: object with
the proper origin AS exists as well), and some might just be legacy
garbage - indeed.

> Given the considerable number of routing anomalies revealed by my simple
> experiment, I am inclined to wonder who is actually using all of that
> route information in the RIPE DB, and what on earth they could be using
> it for.

We use it to build BGP filters for BGP customers.

For those, the filter is build using the origin AS as key, so if there are
additional route objects for the same prefix but with a different origin AS,
our script won't see them, so it's "garbage that does not disturb anything".

Of course, if the origin AS doesn't match at all, customers' BGP announcements
won't go out - and they usually notice that quickly and fix their stuff.

(Our upstream providers do the same thing for us, so it's used on a larger
scale - unfortunately, not all large transit providers do that, some just
take the money and look the other way)

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/20141121/fb335fa1/attachment.sig>