[178807] in North American Network Operators' Group
Re: ASN to IP Mapping
daemon@ATHENA.MIT.EDU (Geoff Huston)
Sun Mar 8 05:32:18 2015
X-Original-To: nanog@nanog.org
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <5.1.1.6.2.20150308093452.01fba2e8@efes.iucc.ac.il>
Date: Sun, 8 Mar 2015 20:32:09 +1100
To: Hank Nussbacher <hank@efes.iucc.ac.il>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
> On 8 Mar 2015, at 6:35 pm, Hank Nussbacher <hank@efes.iucc.ac.il> =
wrote:
>=20
> At 14:37 08/03/2015 +1100, Geoff Huston wrote:
>=20
>> > On 8 Mar 2015, at 1:39 pm, Randy Bush <randy@psg.com> wrote:
>> >
>> >> If you want to know the registry assignments / allocations made to =
a
>> >> single entity and be able group together these assignments of =
address
>> >> prefixes and ASNs you should retrieve the combined extended stats =
file
>> >> from the RIRs
>> >> =
(https://www.nro.net/wp-content/uploads/apnic-uploads/delegated-extended)
>> >> and group together all those entries with a common value in column =
8
>> >> (except for the entries corresponding to assignments and =
allocations
>> >> made by the RIPE NCC, where this information is, unfortunately, =
not
>> >> published by them in such a convenient format.)
>> >
>> > care to give a decode for the fields in that file? :)
>>=20
>>=20
>> sure, I'll try.
>=20
> Or:
> https://www.nro.net/wp-content/uploads/nro-extended-stats-readme5.txt
Users of this report should be aware that there are some subtle =
deviations from this spec in the published data:
- the RIPE NCC uses the non-ISO 3166 2 letter code 'EU' for some =
allocations. I do not know exactly why;
- the date field is not quite as described in that file for ARIN =
entries. Again, I do not know why.
- the RIPE NCC does not provide the "opaque-id" in their records
