
From nobody Mon Jan  4 05:41:40 2021
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8437A3A0D29; Mon,  4 Jan 2021 05:41:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkO1ulrjz9Ud; Mon,  4 Jan 2021 05:41:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D89D63A0D28; Mon,  4 Jan 2021 05:41:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E9403F40721; Mon,  4 Jan 2021 05:41:29 -0800 (PST)
To: me@kasparetter.com, Donald.Eastlake@motorola.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: evyncke@cisco.com, iesg@ietf.org, dnsext@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210104134129.E9403F40721@rfc-editor.org>
Date: Mon,  4 Jan 2021 05:41:29 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/aRy5l4JC_p2hNJJVuVxZ_LFGDRU>
Subject: [dnsext] [Errata Held for Document Update] RFC4343 (6361)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 13:41:40 -0000

The following errata report has been held for document update 
for RFC4343, "Domain Name System (DNS) Case Insensitivity Clarification". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6361

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Kaspar Etter <me@kasparetter.com>
Date Reported: 2020-12-22
Held by: Eric Vyncke (IESG)

Section: 4.1

Original Text
-------------
No "case conversion" or "case folding" is done during such output operations, thus "preserving" case.

Corrected Text
--------------
?

Notes
-----
Whose case is preserved? The case of the label in the DNS query or the case of the label in the DNS database? In other words, if there is a DNS record for ietf.org and I query IETF.org, should the DNS response say ietf.org or IETF.org? I would expect it's the former so that the DNS administrator can inform the DNS requester about the preferred capitalization but I can't figure this out on the basis of the RFC. Does output case preservation refer to something else? All I observe is that tools like dig return the latter when I run 'dig IETF.org'. Maybe an errata is not the right place to ask for clarification but given the name of the RFC, I would expect to find a clear answer to this question in the RFC.

-- verifier note --
After discussion with the RFC author and the errata author, the conclusion is that the RFC isn't wrong but is arguably unclear for some readers.

--------------------------------------
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


From nobody Mon Jan  4 11:16:10 2021
Return-Path: <tale@dd.org>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A9123A0FDE; Mon,  4 Jan 2021 11:16:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v6dEwWP2oMKp; Mon,  4 Jan 2021 11:16:02 -0800 (PST)
Received: from gro.dd.org (host2.dlawren-3-gw.cust.sover.net [207.136.201.30]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA4213A0FD5; Mon,  4 Jan 2021 11:16:01 -0800 (PST)
Received: by gro.dd.org (Postfix, from userid 102) id 51A3B12EEBE; Mon,  4 Jan 2021 14:15:59 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <24563.26991.309998.571334@gro.dd.org>
Date: Mon, 4 Jan 2021 14:15:59 -0500
From: Dave Lawrence <tale@dd.org>
To: me@kasparetter.com, Donald.Eastlake@motorola.com, evyncke@cisco.com, iesg@ietf.org, dnsext@ietf.org
In-Reply-To: <20210104134129.E9403F40721@rfc-editor.org>
References: <20210104134129.E9403F40721@rfc-editor.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/-yuOC5lj8WeHQUrXZHbmg4nYFYY>
Subject: Re: [dnsext] [Errata Held for Document Update] RFC4343 (6361)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 19:16:05 -0000

RFC Errata System writes:
> After discussion with the RFC author and the errata author, the
> conclusion is that the RFC isn't wrong but is arguably unclear for
> some readers. 

Agreed that it could be a little confusing when focusing on that one
sentence, despite the surrounding paragraphs trying to fill the
context.  Was there new proposed text?  Is this sufficient, given the
surrounding text?

Old:  No "case conversion" or "case folding" is done
      during such output operations, thus "preserving" case.  

New:  No "case conversion" or "case folding" is done on input octets
      during such output operations, thus "preserving" case.  


From nobody Mon Jan  4 13:26:21 2021
Return-Path: <me@kasparetter.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A60CB3A1106; Mon,  4 Jan 2021 13:26:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.019
X-Spam-Level: 
X-Spam-Status: No, score=-0.019 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id poTxxiSkoQya; Mon,  4 Jan 2021 13:26:18 -0800 (PST)
Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DC123A1104; Mon,  4 Jan 2021 13:26:17 -0800 (PST)
X-Originating-IP: 51.154.104.215
Received: from [192.168.1.4] (unknown [51.154.104.215]) (Authenticated sender: me@kasparetter.com) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 30A8660005; Mon,  4 Jan 2021 21:26:12 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Kaspar Etter <me@kasparetter.com>
In-Reply-To: <24563.26991.309998.571334@gro.dd.org>
Date: Mon, 4 Jan 2021 22:26:10 +0100
Cc: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, iesg@ietf.org, dnsext@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEBC7569-CC6C-48FA-AD71-4C47C1F8F87E@kasparetter.com>
References: <20210104134129.E9403F40721@rfc-editor.org> <24563.26991.309998.571334@gro.dd.org>
To: Dave Lawrence <tale@dd.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/GmhtHzMVL2ZKyMeDYb8v1WfaSsA>
Subject: Re: [dnsext] [Errata Held for Document Update] RFC4343 (6361)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 21:26:20 -0000

Thank you for proposing an improved wording. As the author of the =
errata, I have to say that the addition of =E2=80=9Con input octets=E2=80=9D=
 would not have helped me. The statement in the errata system is =
correct: My =E2=80=9Cerrata=E2=80=9D was simply a =E2=80=9Crequest for =
clarification=E2=80=9D and not a =E2=80=9Crequest for correction=E2=80=9D.=


The following response from Evan Hunt was really helpful for me:

> This has been ambiguous for a long time.  If you check the =
authoritative
> servers for ietf.org, the answer section is capitalized as specified =
in
> the zone database, not matching the question:
>=20
>   $ dig +noall +answer @ns1.ams1.afilias-nst.info. IETF.org
>   ietf.org.		1800	IN	A	4.31.198.44
>=20
> However, some servers use case-insensitive name compression in their
> responses. Differently-capitalized versions of the same name are =
treated as
> duplicates, so if IETF.org appears in the question section, the answer
> section will refer back to that.  In my view, this behavior is =
incorrect,
> but it's commonplace.

I agree that the single sentence likely doesn=E2=80=99t give enough =
context for the person who will update this RFC in the future. If I have =
to propose a concrete change, I would go for the following:

Old:
No "case conversion" or "case folding" is done during such output =
operations, thus "preserving" case.
However, to optimize output, indirect labels may be used to point to =
names elsewhere in the DNS answer.

New:
No "case conversion" or "case folding" is done during such output =
operations, thus "preserving=E2=80=9D the case of the domain name as it =
is stored in the database of the authoritative name server.
However, to optimize output, indirect labels may be used to point to =
names elsewhere in the DNS answer, typically from the answer section to =
the question section.

I think my confusion comes from the fact that the current situation is =
not really satisfying in my opinion. What=E2=80=99s the point of output =
(and thus also input) case preservation in theory if you rarely get case =
preservation in practice? I see the following options to improve the =
situation:
1. Just say that an authoritative name server can store and return =
domain names in any capitalization it likes instead of indicating that =
the case should be preserved.
2. Discourage name servers (with a =E2=80=9CSHOULD NOT=E2=80=9D?) from =
pointing from the answer section to the question section of the DNS =
response so that the capitalization of the DNS answer can actually be =
used to display the domain name to the user as the owner of the domain =
name intended it.
3. Preserve =E2=80=9Cname compression=E2=80=9D and case by encouraging =
name servers to point from the question section to the answer section =
instead of the other way around. If this is not possible, simply use the =
capitalization of the answer section in the question section so that =
name compression remains the same. As far as I can tell, the RFC =
doesn=E2=80=99t say anything about whether the question section has to =
preserve the case of the DNS query, which is probably also something =
that should be addressed in a future iteration of this RFC.
4. Encourage domain names to be stored, queried, and returned in =
lowercase to make the behavior of ASCII domain names more similar to the =
behavior of IDNA2008 domain names. (Assuming that IDNs increase in =
importance over time, I see little reason to treat the subset of ASCII =
domain names differently in the long term.) Encouraging that domain =
names are displayed in lowercase might also be desirable in the context =
of mitigating homograph attacks.

I understand that this debate is beyond the scope of this errata but =
given the comment by Evan Hunt I have the impression that other people =
share my dissatisfaction with the current situation. Therefore, it might =
make sense to have (or revisit?) this debate in the future and then =
supersede RFC 4343 accordingly (instead of just changing the wording in =
Section 4.1.).

Best regards,
Kaspar


> On 4 Jan 2021, at 20:15, Dave Lawrence <tale@dd.org> wrote:
>=20
> RFC Errata System writes:
>> After discussion with the RFC author and the errata author, the
>> conclusion is that the RFC isn't wrong but is arguably unclear for
>> some readers.=20
>=20
> Agreed that it could be a little confusing when focusing on that one
> sentence, despite the surrounding paragraphs trying to fill the
> context.  Was there new proposed text?  Is this sufficient, given the
> surrounding text?
>=20
> Old:  No "case conversion" or "case folding" is done
>      during such output operations, thus "preserving" case. =20
>=20
> New:  No "case conversion" or "case folding" is done on input octets
>      during such output operations, thus "preserving" case. =20


From nobody Wed Jan  6 08:29:35 2021
Return-Path: <d3e3e3@gmail.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2E7A3A0FCF; Wed,  6 Jan 2021 08:29:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nqA8Jcvcwcp2; Wed,  6 Jan 2021 08:29:26 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 558943A0FC3; Wed,  6 Jan 2021 08:29:20 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id w18so3302648iot.0; Wed, 06 Jan 2021 08:29:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Q1FOyQ5F505sXxDF9rGXkxjrGdzWnhB829wpUThxsMg=; b=YDi+gmfrY9EC8HPYjMmXaPjBLaYLWEcGLq6uI/pVFe6rdOiSVdDEcazD5f059w2z/9 C75dJ8HS6CbljPSp2IVdlb1C7+HDypPJ5APF9NmC4APBDuA8QBYXsSZxUfpH/dVl8BYe plkVsmFeuP/uLcMbp9enl11B8TmDjmg+8tWetscowItAURlTfrFMWYp6C0IyCmZbJps1 w1fe2i6TwTtuFQcSJlbBvFdjX6dceDLonKmseVK4wW+2t7s5cEU8ecTIGaWr5ckCLc3A 6suTri8HefnmEsJvI0w3k0VBLisEI/piOve4nB5tnN3LJVfKyI+ZCaepW1jfPxfl9R6/ pR2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Q1FOyQ5F505sXxDF9rGXkxjrGdzWnhB829wpUThxsMg=; b=jqtuj7iPwkIwyueqF9hQlJLuyEzpvsaoUIuVoKD0ssU755naToCBvjz2o1H9TIsvkt o7k907wF/JmxkH9Ay7SpgSY1xxqc2IlmGrxU6Oe27Cmt9sXYpy9tAu0QoBF8WJIgBoNy /YoV96Qz2gE7f9NhfsGXZgImy5ZbTCheu3fSl38M1LWJrvLKjTi/7P87FgUK2AGqD2lE 7nI2pD0Xdj2c3JP7HXDcKV0c0UAG1uwaCpyqk72WNBnupTEWSJmUxsR3EZ5vYLe6xlVS SXWIFGhOBPqf0xSsoLVN8PuWUGgyZ8HrRfWivC/HZYs5rIy7iSW1Xdcg1CdycIxncP1l B0Ow==
X-Gm-Message-State: AOAM530GFNVTwMsS3mVPtzemrAAN8LBZFuRtbISvVH/MW8IhrYe+I27e Faxc5FmmEpX+jYMz6IwkPSt272aKplcnh7mIPc8=
X-Google-Smtp-Source: ABdhPJyeDUdNKWU1uSyEf0nBcJDX6trhXyGp7BaHKeRN/CZvE0XIIxlI78hvWqIcUmqSEt5GkiD6XiAblBIAykzGViA=
X-Received: by 2002:a6b:1457:: with SMTP id 84mr3417974iou.185.1609950559503;  Wed, 06 Jan 2021 08:29:19 -0800 (PST)
MIME-Version: 1.0
References: <20210104134129.E9403F40721@rfc-editor.org> <24563.26991.309998.571334@gro.dd.org> <EEBC7569-CC6C-48FA-AD71-4C47C1F8F87E@kasparetter.com>
In-Reply-To: <EEBC7569-CC6C-48FA-AD71-4C47C1F8F87E@kasparetter.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 6 Jan 2021 11:29:08 -0500
Message-ID: <CAF4+nEFPOtMtrRWWhm0k2VaE53LrtTPKW8Ft3Ax62MfAje=7AQ@mail.gmail.com>
To: Kaspar Etter <me@kasparetter.com>
Cc: Dave Lawrence <tale@dd.org>, IETF DNSEXT WG <dnsext@ietf.org>,  "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "iesg@ietf.org" <iesg@ietf.org>,  Donald Eastlake <d3e3e3@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/ZZovRkxaAen-1ofZCxJ3Tk0gmQs>
Subject: Re: [dnsext] [Errata Held for Document Update] RFC4343 (6361)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 16:29:30 -0000

Hi,

See below.

On Mon, Jan 4, 2021 at 4:26 PM Kaspar Etter <me@kasparetter.com> wrote:
>
> Thank you for proposing an improved wording. As the author of the errata,=
 I have to say that the addition of =E2=80=9Con input octets=E2=80=9D would=
 not have helped me. The statement in the errata system is correct: My =E2=
=80=9Cerrata=E2=80=9D was simply a =E2=80=9Crequest for clarification=E2=80=
=9D and not a =E2=80=9Crequest for correction=E2=80=9D.
>
> The following response from Evan Hunt was really helpful for me:
>
> > This has been ambiguous for a long time.  If you check the authoritativ=
e
> > servers for ietf.org, the answer section is capitalized as specified in
> > the zone database, not matching the question:
> >
> >   $ dig +noall +answer @ns1.ams1.afilias-nst.info. IETF.org
> >   ietf.org.           1800    IN      A       4.31.198.44
> >
> > However, some servers use case-insensitive name compression in their
> > responses. Differently-capitalized versions of the same name are treate=
d as
> > duplicates, so if IETF.org appears in the question section, the answer
> > section will refer back to that.  In my view, this behavior is incorrec=
t,
> > but it's commonplace.
>
> I agree that the single sentence likely doesn=E2=80=99t give enough conte=
xt for the person who will update this RFC in the future. If I have to prop=
ose a concrete change, I would go for the following:
>
> Old:
> No "case conversion" or "case folding" is done during such output operati=
ons, thus "preserving" case.
> However, to optimize output, indirect labels may be used to point to name=
s elsewhere in the DNS answer.
>
> New:
> No "case conversion" or "case folding" is done during such output operati=
ons, thus "preserving=E2=80=9D the case of the domain name as it is stored =
in the database of the authoritative name server.
> However, to optimize output, indirect labels may be used to point to name=
s elsewhere in the DNS answer, typically from the answer section to the que=
stion section.

I would be fine with the suggested wording change above.

> I think my confusion comes from the fact that the current situation is no=
t really satisfying in my opinion. What=E2=80=99s the point of output (and =
thus also input) case preservation in theory if you rarely get case preserv=
ation in practice? I see the following options to improve the situation:
> 1. Just say that an authoritative name server can store and return domain=
 names in any capitalization it likes instead of indicating that the case s=
hould be preserved.
> 2. Discourage name servers (with a =E2=80=9CSHOULD NOT=E2=80=9D?) from po=
inting from the answer section to the question section of the DNS response =
so that the capitalization of the DNS answer can actually be used to displa=
y the domain name to the user as the owner of the domain name intended it.

This RFC was not intended to push for or require any particular change
in case handling.

> 3. Preserve =E2=80=9Cname compression=E2=80=9D and case by encouraging na=
me servers to point from the question section to the answer section instead=
 of the other way around. If this is not possible, simply use the capitaliz=
ation of the answer section in the question section so that name compressio=
n remains the same. As far as I can tell, the RFC doesn=E2=80=99t say anyth=
ing about whether the question section has to preserve the case of the DNS =
query, which is probably also something that should be addressed in a futur=
e iteration of this RFC.

Maybe. I think question case in responses in the same as in the query.

> 4. Encourage domain names to be stored, queried, and returned in lowercas=
e to make the behavior of ASCII domain names more similar to the behavior o=
f IDNA2008 domain names. (Assuming that IDNs increase in importance over ti=
me, I see little reason to treat the subset of ASCII domain names different=
ly in the long term.) Encouraging that domain names are displayed in lowerc=
ase might also be desirable in the context of mitigating homograph attacks.

This RFC was not intended to push for or require any particular change
in case handling.

> I understand that this debate is beyond the scope of this errata but give=
n the comment by Evan Hunt I have the impression that other people share my=
 dissatisfaction with the current situation. Therefore, it might make sense=
 to have (or revisit?) this debate in the future and then supersede RFC 434=
3 accordingly (instead of just changing the wording in Section 4.1.).

While I might agree that the current situation is inelegant, things
work fine so I'm not sure it would be worth trying to mandate
different behavior. Such a mandate would, in any case, take many many
years, quite possibly decades, before it even approached being
universally applied.

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

> Best regards,
> Kaspar
>
>
> > On 4 Jan 2021, at 20:15, Dave Lawrence <tale@dd.org> wrote:
> >
> > RFC Errata System writes:
> >> After discussion with the RFC author and the errata author, the
> >> conclusion is that the RFC isn't wrong but is arguably unclear for
> >> some readers.
> >
> > Agreed that it could be a little confusing when focusing on that one
> > sentence, despite the surrounding paragraphs trying to fill the
> > context.  Was there new proposed text?  Is this sufficient, given the
> > surrounding text?
> >
> > Old:  No "case conversion" or "case folding" is done
> >      during such output operations, thus "preserving" case.
> >
> > New:  No "case conversion" or "case folding" is done on input octets
> >      during such output operations, thus "preserving" case.
>
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext


From nobody Wed Jan  6 21:34:14 2021
Return-Path: <marka@isc.org>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0758A3A083E; Wed,  6 Jan 2021 21:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cLnKb_W4-Qjr; Wed,  6 Jan 2021 21:34:05 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AD5C3A07F7; Wed,  6 Jan 2021 21:34:05 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 330593BD553; Thu,  7 Jan 2021 05:34:05 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 1E076160081; Thu,  7 Jan 2021 05:34:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0D804160080; Thu,  7 Jan 2021 05:34:05 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id fcnOeCx2C1Jt; Thu,  7 Jan 2021 05:34:04 +0000 (UTC)
Received: from [172.30.42.68] (n114-75-149-106.bla4.nsw.optusnet.com.au [114.75.149.106]) by zmx1.isc.org (Postfix) with ESMTPSA id 88C9E160054; Thu,  7 Jan 2021 05:34:03 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <EEBC7569-CC6C-48FA-AD71-4C47C1F8F87E@kasparetter.com>
Date: Thu, 7 Jan 2021 16:34:01 +1100
Cc: Dave Lawrence <tale@dd.org>, Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>, dnsext@ietf.org, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, iesg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA576190-824A-4A8B-979A-54E0F8802278@isc.org>
References: <20210104134129.E9403F40721@rfc-editor.org> <24563.26991.309998.571334@gro.dd.org> <EEBC7569-CC6C-48FA-AD71-4C47C1F8F87E@kasparetter.com>
To: Kaspar Etter <me@kasparetter.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/fAcuExhkOAQ_ZiO7JkjWj2ycT7M>
Subject: Re: [dnsext] [Errata Held for Document Update] RFC4343 (6361)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 05:34:08 -0000

> On 5 Jan 2021, at 08:26, Kaspar Etter <me@kasparetter.com> wrote:
>=20
> Thank you for proposing an improved wording. As the author of the =
errata, I have to say that the addition of =E2=80=9Con input octets=E2=80=9D=
 would not have helped me. The statement in the errata system is =
correct: My =E2=80=9Cerrata=E2=80=9D was simply a =E2=80=9Crequest for =
clarification=E2=80=9D and not a =E2=80=9Crequest for correction=E2=80=9D.=

>=20
> The following response from Evan Hunt was really helpful for me:
>=20
>> This has been ambiguous for a long time.  If you check the =
authoritative
>> servers for ietf.org, the answer section is capitalized as specified =
in
>> the zone database, not matching the question:
>>=20
>>  $ dig +noall +answer @ns1.ams1.afilias-nst.info. IETF.org
>>  ietf.org.		1800	IN	A	4.31.198.44
>>=20
>> However, some servers use case-insensitive name compression in their
>> responses. Differently-capitalized versions of the same name are =
treated as
>> duplicates, so if IETF.org appears in the question section, the =
answer
>> section will refer back to that.  In my view, this behavior is =
incorrect,
>> but it's commonplace.
>=20
> I agree that the single sentence likely doesn=E2=80=99t give enough =
context for the person who will update this RFC in the future. If I have =
to propose a concrete change, I would go for the following:
>=20
> Old:
> No "case conversion" or "case folding" is done during such output =
operations, thus "preserving" case.
> However, to optimize output, indirect labels may be used to point to =
names elsewhere in the DNS answer.
>=20
> New:
> No "case conversion" or "case folding" is done during such output =
operations, thus "preserving=E2=80=9D the case of the domain name as it =
is stored in the database of the authoritative name server.
> However, to optimize output, indirect labels may be used to point to =
names elsewhere in the DNS answer, typically from the answer section to =
the question section.
>=20
> I think my confusion comes from the fact that the current situation is =
not really satisfying in my opinion. What=E2=80=99s the point of output =
(and thus also input) case preservation in theory if you rarely get case =
preservation in practice?

Firstly while fixes to implementations in the DNS take a long time to =
filter through, they do filter through.  There is a misconception that =
change in the DNS is hard to do.  It isn=E2=80=99t.  What hard to do is =
getting rid of the myth that change in the DNS is hard to do.

See the difference between talking to a case preserving server to one =
which doesn=E2=80=99t.  Note every server should already be case =
preserving as that is a STD-13 requirement.

[beetle:~/git/bind9] marka% dig A.RooT-SerVers.Net @c.root-servers.net =
+noadd +nocookie

; <<>> DiG 9.15.4 <<>> A.RooT-SerVers.Net @c.root-servers.net +noadd =
+nocookie
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60341
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 26
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;A.RooT-SerVers.Net.		IN	A

;; ANSWER SECTION:
a.root-servers.net.	3600000	IN	A	198.41.0.4

;; AUTHORITY SECTION:
root-servers.net.	3600000	IN	NS	d.root-servers.net.
root-servers.net.	3600000	IN	NS	h.root-servers.net.
root-servers.net.	3600000	IN	NS	f.root-servers.net.
root-servers.net.	3600000	IN	NS	k.root-servers.net.
root-servers.net.	3600000	IN	NS	g.root-servers.net.
root-servers.net.	3600000	IN	NS	m.root-servers.net.
root-servers.net.	3600000	IN	NS	b.root-servers.net.
root-servers.net.	3600000	IN	NS	i.root-servers.net.
root-servers.net.	3600000	IN	NS	l.root-servers.net.
root-servers.net.	3600000	IN	NS	e.root-servers.net.
root-servers.net.	3600000	IN	NS	j.root-servers.net.
root-servers.net.	3600000	IN	NS	c.root-servers.net.
root-servers.net.	3600000	IN	NS	a.root-servers.net.

;; Query time: 184 msec
;; SERVER: 192.33.4.12#53(192.33.4.12)
;; WHEN: Thu Jan 07 16:10:17 AEDT 2021
;; MSG SIZE  rcvd: 843

[beetle:~/git/bind9] marka%=20


[beetle:~/git/bind9] marka% dig A.RooT-SerVers.Net @a.root-servers.net =
+noadd +nocookie

; <<>> DiG 9.15.4 <<>> A.RooT-SerVers.Net @a.root-servers.net +noadd =
+nocookie
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55706
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 26
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;A.RooT-SerVers.Net.		IN	A

;; ANSWER SECTION:
A.RooT-SerVers.Net.	3600000	IN	A	198.41.0.4

;; AUTHORITY SECTION:
RooT-SerVers.Net.	3600000	IN	NS	A.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	b.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	c.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	d.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	e.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	f.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	g.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	h.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	i.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	j.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	k.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	l.RooT-SerVers.Net.
RooT-SerVers.Net.	3600000	IN	NS	m.RooT-SerVers.Net.

;; Query time: 126 msec
;; SERVER: 198.41.0.4#53(198.41.0.4)
;; WHEN: Thu Jan 07 16:01:24 AEDT 2021
;; MSG SIZE  rcvd: 825

[beetle:~/git/bind9] marka%=20


> I see the following options to improve the situation:
> 1. Just say that an authoritative name server can store and return =
domain names in any capitalization it likes instead of indicating that =
the case should be preserved.
> 2. Discourage name servers (with a =E2=80=9CSHOULD NOT=E2=80=9D?) from =
pointing from the answer section to the question section of the DNS =
response so that the capitalization of the DNS answer can actually be =
used to display the domain name to the user as the owner of the domain =
name intended it.

It's not a question point to particular sections or not.  It=E2=80=99s a =
question of looking at the case of the domain name that is to =
(potentially) converted to a compression point and the case of the =
domain name at that target.  If they are the same you replace the domain =
name with the compression pointer.  If they are not you add the first =
label and repeat the test.

When adding the answer section in the case sensitive response the =
following domains exist as targets:

A.RooT-SerVers.Net.
RooT-SerVers.Net.
Net.

When you get to adding the authority section the following domains exist =
as targets:

A.RooT-SerVers.Net.
RooT-SerVers.Net.
Net.
a.root-servers.net.
root-servers.net.
net.

> 3. Preserve =E2=80=9Cname compression=E2=80=9D and case by encouraging =
name servers to point from the question section to the answer section =
instead of the other way around.

This is not permitted.  Legal compression pointers only point towards =
the start of the message.  This is actually enforced by clients.

> If this is not possible, simply use the capitalization of the answer =
section in the question section so that name compression remains the =
same. As far as I can tell, the RFC doesn=E2=80=99t say anything about =
whether the question section has to preserve the case of the DNS query, =
which is probably also something that should be addressed in a future =
iteration of this RFC.

Why? Are we really worried about a couple of bytes of difference due to =
having two different representations of the QNAME in the response.  The =
difference above is 18 bytes.

> 4. Encourage domain names to be stored, queried, and returned in =
lowercase to make the behavior of ASCII domain names more similar to the =
behavior of IDNA2008 domain names. (Assuming that IDNs increase in =
importance over time, I see little reason to treat the subset of ASCII =
domain names differently in the long term.) Encouraging that domain =
names are displayed in lowercase might also be desirable in the context =
of mitigating homograph attacks.
>=20
> I understand that this debate is beyond the scope of this errata but =
given the comment by Evan Hunt I have the impression that other people =
share my dissatisfaction with the current situation. Therefore, it might =
make sense to have (or revisit?) this debate in the future and then =
supersede RFC 4343 accordingly (instead of just changing the wording in =
Section 4.1.).
>=20
> Best regards,
> Kaspar
>=20
>=20
>> On 4 Jan 2021, at 20:15, Dave Lawrence <tale@dd.org> wrote:
>>=20
>> RFC Errata System writes:
>>> After discussion with the RFC author and the errata author, the
>>> conclusion is that the RFC isn't wrong but is arguably unclear for
>>> some readers.=20
>>=20
>> Agreed that it could be a little confusing when focusing on that one
>> sentence, despite the surrounding paragraphs trying to fill the
>> context.  Was there new proposed text?  Is this sufficient, given the
>> surrounding text?
>>=20
>> Old:  No "case conversion" or "case folding" is done
>>     during such output operations, thus "preserving" case. =20
>>=20
>> New:  No "case conversion" or "case folding" is done on input octets
>>     during such output operations, thus "preserving" case. =20
>=20
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org

