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/[email protected]/
[routing-wg] Who uses the RIPE IRR and for what?
- Previous message (by thread): [routing-wg] Who uses the RIPE IRR and for what?
- Next message (by thread): [routing-wg] Who uses the RIPE IRR and for what?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Hallgren
m.hallgren at free.fr
Fri Nov 21 10:28:51 CET 2014
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 21/11/2014 10:08, Gert Doering a écrit : > 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) Nice thing to do is to (script) analyze received versus expected, and send report to the customer. mh > > > Gert Doering > -- NetMaster -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRvBdMACgkQZNZ/rrgsqac7ZwCeL8MaYF3Ey8IGUSUtlUL9Fg4p bMIAnAuoS6Ks0Ut8kG/iiEhGr7jwOKsZ =ySs8 -----END PGP SIGNATURE-----
- Previous message (by thread): [routing-wg] Who uses the RIPE IRR and for what?
- Next message (by thread): [routing-wg] Who uses the RIPE IRR and for what?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]