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-07.txt> as Proposed Standard
This is a revision to a document that previously went through Last Call in 2019, but stalled in IESG Evaluation specifically with respect to the content of Section 4. This new revision modernizes significant portions of the text, and is now being returned to the community to verify continued consensus and then progress toward publication. 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 [email protected] mailing lists by 2024-10-21. Exceptionally, comments may be sent to [email protected] 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 -- [email protected] To unsubscribe send an email to [email protected]
