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/[email protected]/
[db-wg] country codes in the RIPE Database (was: ORGANISATION country code)
- Previous message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)
- Next message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
George Michaelson
ggm at algebras.org
Tue Mar 7 23:29:22 CET 2023
I suggest that this is not just a localized decision of the db-wg, but has global implications. You are discussing a field whose value is interpreted both directly from WHOIS and RDAP, and less directly from delegated files in the registry system across all the RIR. Your consumers are my consumers, and ARINs and LACNIC and AfriNICs. It is a global market of consumption. I don't necessarily disagree with you about the risks here, but I suggest that the decision to deprecate or alter behavior with this field is not something which a single RIR should undertake without a wider conversation. Obviously my statement has no "normative force". We're not discussing address policy, we're not discussing "global address policy" and in any case, RIR secretariat staff aren't "in charge" here, its something discussed inside your own process. I just think that there's a global context which is very important: Cohesion of this data across the "ecology" is a really big deliverable. cheers -George
- Previous message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)
- Next message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]