Speaking as a participant: Thanks Jim. I agree with you that broader work on IDNs would be a good thing for this working group. The extension analysis work is a good place to start.
I wanted to note that a prior version of the variants draft had examples and XML included. We dropped them in this version when we revised the document to present the work as “related groups” not variants. We’ll certainly bring that back. I’m also interested in whether or not you think IDN variants should be addressed directly in any of the other extensions? I don’t think so but you’ve done a deeper dive so perhaps you’ve got a question to consider. Thanks, Jim On 25 Nov 2025, at 12:35, Gould, James wrote: > Antoin, > > I'm supportive of work on IDNs by the working group. Based on the EPP > extensibility and extensions analysis, the work is broader than an individual > draft that includes how to validate the code points during an IDN > registration and how to manage variants. I find > draft-galvin-regext-epp-variants to be more of a template or concept than a > candidate EPP extension in its current form. The draft doesn't include an > XML schema or a set of examples that I view as being a minimum bar for > adoption consideration of an EPP extension. The working group could look to > address IDN domain names in EPP from a high-level first (e.g., informational > draft) and then target one or more standards track EPP extensions based on > the high-level work. Below is the set of IDN extensions reviewed in the EPP > extensibility and extensions analysis and presented at IETF-124: > > 1. IDN Language Tag > 2. Related Domain > 3. Strict Bundling > 3. IDN Mapping and IDN Mapping – Identity Digital > 4. IDN Table Mapping > 5. IDN - TANGO > 6. Domain Variants (draft-galvin-regext-epp-variants) > > Thanks, > > -- > > JG > > > > James Gould > Fellow Engineer > [email protected] > <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> > > 703-948-3271 > 12061 Bluemont Way > Reston, VA 20190 > > Verisign.com <http://verisigninc.com/> > > > > > On 11/24/25, 11:04 AM, "Antoin Verschuren" <[email protected] > <mailto:[email protected]>> wrote: > > > Caution: This email originated from outside the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > > > > Hi folks, > > > This is a reminder this call for adoption is open for another week. We didn’t > see any reactions yet. > > > Your REGEXT co-chairs Jorge and Antoin. > > > > >> Op 17 nov. 2025, om 16:13 heeft Antoin Verschuren >> <[email protected] <mailto:[email protected]>> het >> volgende geschreven: >> >> Hi all, >> >> This is a formal adoption request for “Domain Related Group Support for EPP”: >> >> https://secure-web.cisco.com/1n-5Ba_BhzzZOtOV9lXhXAz5xXfd-WwW6p6lsUmPP4qI_7OGvgb5Ti-6EWfRoOHUSm0ye59Yb8g6tPrQ-r-hzDM93U-mcbeOnTcIs0JgSnqcBJ6qS5rMvqG_CJTYFn60Fk3JCOs7wYMNqvQ8HrnNZu_JczmtpMrdHypew2CBkIsG95xywl_opYl9v92w0y3nAr_YBWEBQt8YNP66u_Ff841WSmdY9gfsQ_q7Awf_ZMl9tQEatk66humWqzBM9JjI9ckFAR3Cc8NfFH0Q5HPUYahUWeWn37MtDErAZw8QUNcQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-galvin-regext-epp-variants%2F >> >> <https://secure-web.cisco.com/1n-5Ba_BhzzZOtOV9lXhXAz5xXfd-WwW6p6lsUmPP4qI_7OGvgb5Ti-6EWfRoOHUSm0ye59Yb8g6tPrQ-r-hzDM93U-mcbeOnTcIs0JgSnqcBJ6qS5rMvqG_CJTYFn60Fk3JCOs7wYMNqvQ8HrnNZu_JczmtpMrdHypew2CBkIsG95xywl_opYl9v92w0y3nAr_YBWEBQt8YNP66u_Ff841WSmdY9gfsQ_q7Awf_ZMl9tQEatk66humWqzBM9JjI9ckFAR3Cc8NfFH0Q5HPUYahUWeWn37MtDErAZw8QUNcQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-galvin-regext-epp-variants%2F> >> >> Please review this draft to see if you think it is suitable for adoption by >> REGEXT and comment on this message on the list, clearly stating your view. >> Responding with “+1” will be counted as agreeing with adoption. >> >> Optionally indicate if you are willing to contribute text or review text. >> Note that Jody Kolker has agreed to be the Document Shepherd for this >> document. >> >> This Call For Adoption will close on Monday, 1 December 2025. >> >> If there are no objections, the chairs will consider this document adopted. >> >> Thanks, >> >> Your REGEXT co-chairs Jorge and Antoin >> _______________________________________________ >> regext mailing list -- [email protected] <mailto:[email protected]> >> To unsubscribe send an email to [email protected] >> <mailto:[email protected]> > > > _______________________________________________ > regext mailing list -- [email protected] <mailto:[email protected]> > To unsubscribe send an email to [email protected] > <mailto:[email protected]> > > > > _______________________________________________ > regext mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
