Re: [dnsext] [Technical Errata Reported] RFC4343 (7290)

This seems like a reasonable proposed update to DNS case considerations to
be included in a future RFC.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

On Mon, Dec 26, 2022 at 12:02 PM RFC Errata System <
rfc-editor@rfc-editor.org> wrote:

> The following errata report has been submitted for RFC4343,
> "Domain Name System (DNS) Case Insensitivity Clarification".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7290
>
> --------------------------------------
> Type: Technical
> Reported by: John Klensin <john-ietf@jck.com>
>
> Section: 5
>
> Original Text
> -------------
> A scheme has been adopted for "internationalized domain names" and
> "internationalized labels" as described in [RFC3490, RFC3454, RFC3491, and
> RFC3492]. It makes most of [UNICODE] available through a separate
> application level transformation from internationalized domain name to DNS
> domain name and from DNS domain name to internationalized domain name. Any
> case insensitivity that internationalized domain names and labels have
> varies depending on the script and is handled entirely as part of the
> transformation described in [RFC3454] and [RFC3491], which should be seen
> for further details.
>
> Corrected Text
> --------------
> A scheme has been adopted for "internationalized domain name labels" (and
> "internationalized domain names" (IDNs) more generally) as described in
> [RFC5890, RFC5891, RFC5893, RFC5894], and documents that update and clarify
> them. It makes selected [UNICODE] characters and code point sequences
> available through a separate application level transformation from
> internationalized domain name to DNS domain name and from DNS domain name
> to internationalized domain name. Because of ambiguities among possible
> definitions of case and case relationships once one moves beyond ASCII, the
> IDNA specifications prohibit characters that could be interpreted as "upper
> case", making discussions of case insensitivity irrelevant. See the
> documents cited for further details.
>
> Notes
> -----
> In trying to research something else, I reread RFC 4343.  It still
> references IDNA2003 (RFC 3490ff) as the authority for IDNs and says a few
> things that are misleading, or worse, under IDNA2008.   In retrospect, RFC
> 5890 should have updated 4343 and adjusted the language of its Section 5.
> The author of 5890 clearly screwed up (i.e., mea culpa) and the WG and
> broader IETF review, especially by DNS-related groups, did not catch the
> problem.
>
> The "corrected" text above is merely an example of how this might be
> remedied.  The issue is clearly (at least to me) one to be "held for
> document update" of either RFC 4343 or 5890 but it seems worth inserting a
> pointer into the errata list to warn those who might want to look for it.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC4343 (draft-ietf-dnsext-insensitive-06)
> --------------------------------------
> Title               : Domain Name System (DNS) Case Insensitivity
> Clarification
> Publication Date    : January 2006
> Author(s)           : D. Eastlake 3rd
> Category            : PROPOSED STANDARD
> Source              : DNS Extensions
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG
>
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext
>