Re: ASN to IP Mapping
On 08/03/2015 09:32, Geoff Huston wrote: 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 Some of the EU allocations seem to be CDNs and other trans-national operators. Regards...jmcc
Re: ASN to IP Mapping
> 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; EU is, of course, an ISO-3166 2 letter code, it just happens to be "Exceptionally Reserved". I would naively have assumed EU was used for entities that span multiple European countries. > - 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 http://xkcd.com/927/ Regards, -drc signature.asc Description: Message signed with OpenPGP using GPGMail
Re: ASN to IP Mapping
On Sun, 8 Mar 2015, Geoff Huston wrote: 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; I believe ERX records transferred from ARIN to RIPE will have EU listed as country code until RIPE is contacted to correct it. -Hank
Re: ASN to IP Mapping
> On 8 Mar 2015, at 6:35 pm, Hank Nussbacher wrote: > > At 14:37 08/03/2015 +1100, Geoff Huston wrote: > >> > On 8 Mar 2015, at 1:39 pm, Randy Bush 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? :) >> >> >> sure, I'll try. > > 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
