[db-wg] FR: Publish list of RIPE NCC managed space

> On 5 Dec 2014, at 18:26, Job Snijders <job at ntt.net> wrote:
> 
> On Fri, Dec 05, 2014 at 04:55:35PM +0100, Job Snijders wrote:
>> It would make my life easier if I could fetch a list of prefixes from
>> either ftp.ripe.net or an API endpoint that contains all address space
>> for which RIPE NCC is authoritive. (E.g. not NON-RIPE-NCC-MANAGED-ADDRESS-BLOCK etc).
>> 
>> I'd use this list to create a patricia tree to do lookups in and assess
>> the validity of route objects. It is important that this list does not
>> cover space which RIPE does not administrate. Please don't fill it with
>> /8s unless RIPE NCC truely manages that entire /8. The list should
>> solely create prefixes for which route objects can only be created
>> following  RIPE's solid authentication mechanism.
>> 
>> I'd expect the dump on ftp.ripe.net to be updated on a daily basis.
>> 
>> I don't care if the prefixes in the list match prefix-lengths of
>> inetnums, I only care about the totally of the chunk of space out of 0/0
>> which RIPE manaages.
> 
> Robert Kisteleki was kind enough to point me at
> ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-extended-latest.
> The file does contain the data I am interested in, but not in a super
> easy format to parse.
> 
> I'd like a list of prefixes in CIDR format. Even if that means that
> some lines contain just a /32 or /128 because the allocation isnt on
> boundries.


Hi Job,

In a creative Friday evening mood, I thought of the RPKI Root certificate:

$ rsync rsync://rpki.ripe.net/ta/ripe-ncc-ta.cer
$ openssl x509 -in ripe-ncc-ta.cer -inform der -text

resulting in http://pastebin.com/4ZAvmT05

-Alex