Yes, Jim, I agree. In this document, initially we’ll be focused on the relationship between domain names. We expect to review and discuss the strict bundling and related domain work within the working group and, of course, we’ll incorporate any feedback into this draft as the work progresses, assuming the working group adopts the work.
Regarding the mapping and language tag issues you mention, at least currently we don’t believe that these issues need to be addressed in this document, but of course any discussion in the working group that changes this will be incorporated in the work, assuming the working group adopts the work. Thanks for the reminder, Jim On 8 Sep 2025, at 10:31, Gould, James wrote: > Jim, > > There are two aspects to consider when it comes to the IDN extensions, which > is support for IDN registrations that would be handled via the IDN mapping / > IDN language tag with support of the IDN table draft and IDN relationships > that could be supported via the Strict Bundling, the Related Domain, and the > new Variants draft. > > -- > > 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 9/8/25, 10:24 AM, "James Galvin" <[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. > > > Speaking as a participant, I’d like to ask for time on the agenda to discuss > the following document: > > > https://secure-web.cisco.com/18rEXrAnQ1ju50q6MzGLNF7emv0h3WV3VknEs_rsHimRfkKnEFuxS8Ky103ZsgK1Fg2i9_kucLiMXRHnOQfIz5gERIJ_W0Clt11FZUsNV3_K1nFDpFQ7JHCa1fwJsmVpmbupixOXMeRGtMTMCEpXrbFP0HgTwlJVX913GDAeF7EAhPdrYt87ixIdacS745SpFS7cM1keQVzt6VfXX-0P6z5X2iVSx-ynchX3h5Extwx-2pH8cAB3A8QT1KDP5b8NsKLC8ZWdLyAHZBEbkPTgplm2fzkjRPCd7k93eG8AVqLznCocf7sKsYNlpBxDhK-5a/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-galvin-regext-epp-variants%2F > > <https://secure-web.cisco.com/18rEXrAnQ1ju50q6MzGLNF7emv0h3WV3VknEs_rsHimRfkKnEFuxS8Ky103ZsgK1Fg2i9_kucLiMXRHnOQfIz5gERIJ_W0Clt11FZUsNV3_K1nFDpFQ7JHCa1fwJsmVpmbupixOXMeRGtMTMCEpXrbFP0HgTwlJVX913GDAeF7EAhPdrYt87ixIdacS745SpFS7cM1keQVzt6VfXX-0P6z5X2iVSx-ynchX3h5Extwx-2pH8cAB3A8QT1KDP5b8NsKLC8ZWdLyAHZBEbkPTgplm2fzkjRPCd7k93eG8AVqLznCocf7sKsYNlpBxDhK-5a/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-galvin-regext-epp-variants%2F> > > > Recall from IETF123 the authors did indicate that they will be asking the > working group to consider adopting this work, which we will do before > IETF124. The authors are working through one material update to the document, > which is to move from presenting the proposal in the context of IDN Variants > to presenting the proposal in the context of related groups. Recall that this > is being done so that the proposal will also support at least Latin > diacritics and not just IDN variants. As soon as this work is done we will > put the document forward the working group and then we will use time at > IETF124 to continue discussions to advance the work. > > > Probably at least 20 minutes is appropriate. > > > Thanks, > > > Jim > > > > > On 25 Aug 2025, at 6:18, Antoin Verschuren wrote: > > >> Dear Working Group, >> >> It is time to start thinking about IETF 124 in Montreal. >> Working Group scheduling is due in 3 weeks. >> Since last IETF 123 we were short in time due to last minute requests, and >> we had to cancel a meeting for IETF 122, we want to make sure we will >> request enough time to accommodate all this time. >> So if you are planning to present anything in Montreal, both on-site or >> remote, or request any other time on our agenda, please let us know before >> September 14th so we can schedule accordingly. >> No need for abstracts or presentations yet, just reply to this message to >> indicate plans. >> >> Regards, >> >> Your REGEXT co-chairs Jim, 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]
