[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] RIPE Database Service Criticality Questionnaire
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Mon Jul 11 23:50:05 CEST 2022
I don't think I really made any big comment so I am guessing it was that but if a /16 wasn't needed for demonstration purposes, I prefer using the documentation specific prefixes (as you mentioned) of course. -Cynthia On Mon, Jul 11, 2022 at 11:09 PM Edward Shryane via db-wg <db-wg at ripe.net> wrote: > > 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 > > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
- 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] RIPE Database Service Criticality Questionnaire
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]