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] Non-RIPE INRs in an Example returned by RIPE Whois DB Query Service

• Previous message (by thread): [db-wg] Non-RIPE INRs in an Example returned by RIPE Whois DB Query Service
• Next message (by thread): [db-wg] Non-RIPE INRs in an Example returned by RIPE Whois DB Query Service

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Edward Shryane eshryane at ripe.net
Mon Jul 11 23:09:12 CEST 2022

Hi Sylvain,

> On 11 Jul 2022, at 19:48, Sylvain Baya <abscoco at gmail.com> wrote:
> 
> Dear RIPE DB-WG,
> 
> Please find my comments below, inline...
> Thanks!
> 
...
> btw, now, have you considered the issue raised by Cynthia?
>  

Can you clarify please? Do you mean Cynthia's comment, "there is no /16 for documentation purposes afaik" ?

I'm using the documentation /24's as examples of valid and invalid prefixes, not as examples of holes.

Regards
Ed Shryane
RIPE NCC

• Previous message (by thread): [db-wg] Non-RIPE INRs in an Example returned by RIPE Whois DB Query Service
• Next message (by thread): [db-wg] Non-RIPE INRs in an Example returned by RIPE Whois DB Query Service

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]