[regext] using subdomains in RDAP bootstrap
Hello everyone, As a long-time lurker on regext@ and an infrequent participant in IETF meetings, I apologize if I missed something. We have a practical issue with RDAP. My registry, Hostmaster.UA have implemented RDAP for UA (URL: https://rdap.hostmaster.ua/, as included into IANA bootstrap.) Similarly to say UK we have multiple public suffixes where domains are registered, such as com.ua net.ua odesa.ua etc. The trouble is, some of these domains are not managed by us; let’s say that alice.ua would have rdap.alice.ua, and bob.ua, rdap.bob.ua whereas com.ua would use IANA bootstrap element. Now, I want RDAP service to be as seamless as possible. How can we implement this? IANA JSON registry only has TLDs. I can of course create my own bootstrap file but I cannot imagine practical way of informing RDAP clients of it’s existence. I can use HTTP codes “moved permanently” when answering RDAP queries on our server. (I can query the other server myself and serve the response; bad idea.) Is there a most effective way to do it? Thanks! ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
Re: [regext] RDAP Search Using Regular Expressions
On 20 лип. 2017 р., at 09:45, Hollenbeck, Scott wrote: > > As mentioned at the mic on Tuesday, I'd like to ask one more time if anyone > has any interest in extending RDAP search functionality to use regular > expressions. The draft proposal can be found here: > > https://datatracker.ietf.org/doc/draft-fregly-regext-rdap-search-regex/ As I (silently) said by raising my hand on Tuesday I am interested in this (.UA ccTLD). This being said, the good thing about regexps is that there are so many varieties to choose from, so we have to be careful. > If there's no interest we'll just let this expire (until people realize that > core search functionality is incomplete and something better really is needed > :(). If anyone wants to see it continue, and possibly be brought into this > group for adoption, please say so. > What is needed for this to happen? ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
[regext] Re: RDAP country - how to do it right
On 3 Jun 2025, at 14:32, Marco Davids (IETF IMAP) 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 -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
