On 3 Jun 2025, at 14:32, Marco Davids (IETF IMAP) <[email protected]> wrote: (oh the email address transformation magic) > > Dear RDAP gurus, > > I am struggling a bit with understanding how to represent the country in RDAP. > > So far I found: > > https://datatracker.ietf.org/doc/html/rfc6350#section-6.3.1 > (vCard Format Specification)
…which recommends structured text field and uses country name (not 2-letter ISO code.) > > 'overruled'/extended by: > > https://datatracker.ietf.org/doc/html/rfc8605#section-3 > (ICANN Extensions for RDAP) which asks for CC=country-code but still uses full country name (USA) in examples. my own opinion is that ISO code is better: less ambiguous (United States / USA / US etc). the problem with that is some countries do not habe these codes (example: Kosovo.) we also have some ISO 3166 codes which are not a country, for example EU, or *were* (like SU.) > Then there is: > https://datatracker.ietf.org/doc/html/rfc9083#name-common-data-types (JSON > Responses for RDAP) referring to > https://datatracker.ietf.org/doc/html/rfc8259 (The JSON Data Interchange > Format). > > All suggesting to use the alpha-2 ISO-3166 country code abbreviation. This is > also what I see in the wild; no full country names. For reference, our UA ccTLD service (https://ap.hostmaster.ua) returns country names, not codes, so at least one exception exists. > But it's not clear to me if the alpha-2 country code needs to be in the CC > parameter [RFC8605], or if it also allowed in the country name [RFC6350, > section 3] or perhaps it doesn't matter ? > > I see both in the wild: (…) another thing’s to consider: using country code instead of country name, in some rare cases, may be considered better by its residents if their country code refers to colonial name (touchy.) — dk@ _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
