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
Sun Dec 7 00:37:09 CET 2014
On Sun, Dec 07, 2014 at 07:24:44AM +0900, Randy Bush wrote: > > Why is a mixture of classic inetnum notiation & CIDR used? > > rfc 3779 Thanks. > > 77.0.0.0-95.255.255.255 > > that might be hard to represent in classic cidr notation. and you want > the allocation as a single object as it was a single allocation (i > presume) No, aligning allocations with the actual space for which RIPE NCC is responsible is not important for this application. I'm okay with a list in which (for example) a bunch of IPv4 /32s is present, just to make it a CIDR list covering all. 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 ]