Sorry.. Had intended to remove that sentence before posting. -10 will be posted in a few minutes to correct this along with a typo that Russ identified. Thanks to both for the prompt and careful reading. john --On Thursday, February 6, 2025 16:51 -0500 Marc Blanchet <marc.blanchet@xxxxxxxxxxx> wrote: > Important missing info in the references: > > [LGR-forward-reference] > ?? TBD ??, "Overview and Summary of ICANN Label > Generation Rule Effort". > > Marc. > >> On Feb 6, 2025, at 16:32, The IESG <iesg-secretary@xxxxxxxx> wrote: >> >> >> The IESG has received a request from an individual submitter to >> consider the following document: - 'Internationalized Domain Names >> in Applications (IDNA): Registry >> Restrictions and Recommendations' >> <draft-klensin-idna-rfc5891bis-09.txt> as Proposed Standard >> >> The IESG plans to make a decision in the next few weeks, and >> solicits final comments on this action. Please send substantive >> comments to the last-call@xxxxxxxx mailing lists by 2025-03-03. >> Exceptionally, comments may be sent to iesg@xxxxxxxx instead. In >> either case, please retain the beginning of the Subject line to >> allow automated sorting. >> >> Abstract >> >> >> The IDNA specifications for internationalized domain names >> combine rules that determine the labels that are allowed in the >> DNS without violating the protocol itself and an assignment of >> responsibility, consistent with earlier specifications, for >> determining the labels that are allowed in particular zones. >> Conformance to IDNA by registries and other implementations >> requires both parts. Experience strongly suggests that the >> language describing those responsibilities was insufficiently >> clear to promote safe and interoperable use of the >> specifications and that more details and discussion of >> circumstances would have been helpful. Without making any >> substantive changes to IDNA, this specification updates two of >> the core IDNA documents (RFCs 5890 and 5891) and the IDNA >> explanatory document (RFC 5894) to provide that guidance and to >> correct some technical errors in the descriptions. >> >> >> >> >> The file can be obtained via >> https://datatracker.ietf.org/doc/draft-klensin-idna-rfc5891bis/ >> >> >> >> No IPR declarations have been submitted directly on this I-D. >> >> >> The document contains these normative downward references. >> See RFC 3967 for additional information: >> rfc1591: Domain Name System Structure and Delegation >> (Informational - Legacy stream) >> >> >> >> >> _______________________________________________ >> IETF-Announce mailing list -- ietf-announce@xxxxxxxx >> To unsubscribe send an email to ietf-announce-leave@xxxxxxxx > -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
