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/db-wg@ripe.net/
[db-wg] FR: Publish list of RIPE NCC managed space
- Previous message (by thread): [db-wg] FR: Publish list of RIPE NCC managed space
- Next message (by thread): [db-wg] FR: Publish list of RIPE NCC managed space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Fri Dec 5 22:34:38 CET 2014
On Fri, Dec 05, 2014 at 08:42:30PM +0100, Alex Band wrote: >> On 5 Dec 2014, at 18:26, Job Snijders <job at ntt.net> wrote: >> 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. > > 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 Interesting approach, A++ for the novelty. Thanks Alex :) Is there a specification available on how to parse the 'sbgp-ipAddrBlock: critical' section? Looking at your pastebin I notice the following: <snip> 62.0.0.0/8 77.0.0.0-95.255.255.255 109.0.0.0/8 <snip> Why is a mixture of classic inetnum notiation & CIDR used? Kind regards, Job
- Previous message (by thread): [db-wg] FR: Publish list of RIPE NCC managed space
- Next message (by thread): [db-wg] FR: Publish list of RIPE NCC managed space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]