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] 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 ]
Rene Wilhelm
wilhelm at ripe.net
Fri Nov 21 22:41:58 CET 2014
On 11/21/14, 10:07 PM, Ronald F. Guilmette wrote: > In message <20141121090850.GP28745 at Space.Net>, > Gert Doering <gert at space.net> wrote: > >> To state something that might be obvious or not - for the same prefix, >> you can have multiple route: entries with different origin ASes... > Yes. Thank you. So I have now been informed. > > I do confess, freely, that I had not considered or anticipated such a > possibility at all when I performed my simple minded analysis, and > also must admit that had the small script I write to perform this > analysis properly taken into account the meaning of such cases, the > number I reported would have been different, probably with a lower > number of "anomalies" (although, I suspect, not too much lower). another thing I noted is that the list of anomalies includes entries like 193.110.139.0/24 as24637 24637 In these cases the origin field in the RIPE IRR has "AS" in lower case. Although not large enough in number to change the order of magnitude of the anomalies, it does translate to 1750 additional route objects with a correct origin. -- Rene
- 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 ]