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] Notification/authorisation of references to aut-num from other RPSL objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Sat Nov 22 00:34:12 CET 2014
In message <546FB1A6.1020609 at ripe.net>, Rene Wilhelm <wilhelm at ripe.net> wrote: >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. Yes, another programatic faux pas on my part. Sorry.
- Previous message (by thread): [routing-wg] Who uses the RIPE IRR and for what?
- Next message (by thread): [routing-wg] Notification/authorisation of references to aut-num from other RPSL objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]