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] [anti-abuse-wg] AS43890
- Previous message (by thread): [routing-wg] [anti-abuse-wg] AS43890
- Next message (by thread): [routing-wg] Who uses the RIPE IRR and for what?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Mon Nov 17 12:14:04 CET 2014
On Sun, Nov 16, 2014 at 07:32:25PM -0800, Ronald F. Guilmette wrote: > 31.2.128.0/17 > 46.51.0.0/17 > 95.64.0.0/17 > 164.138.128.0/18 > 188.229.0.0/17 > > Prior to AS197207's decision to begin announcing the above routes (which > they did, starting on Oct. 25th), it appears that the proprietors of > AS43890, a Romanian ISP and RIPE LIR in good standing, apparently elected > to announce their own set of routes to some or all of the above Iranian > IP blocks, using lots and lots of little deaggregated /24 announcements > to do so. Try to compare: ftp://ftp.ripe.net:/ripe/stats/2014/delegated-ripencc-20141026.bz2 with ftp://ftp.ripe.net:/ripe/stats/2014/delegated-ripencc-20141027.bz2 looking for a change apply to 188.229.0.0/17 instead of drawing some (most probably) invalid conclusions. This page should also be very helpful: http://www.ripe.net/lir-services/resource-management/ipv4-transfers/table-of-transfers Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- Previous message (by thread): [routing-wg] [anti-abuse-wg] AS43890
- Next message (by thread): [routing-wg] Who uses the RIPE IRR and for what?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]