Re: [dnsext] [Editorial Errata Reported] RFC4343 (5112)

"Peter van Dijk" <peter.van.dijk@powerdns.com> Tue, 26 September 2017 20:20 UTC

Return-Path: <peter.van.dijk@powerdns.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 87CA6134457 for <dnsext@ietfa.amsl.com>; Tue, 26 Sep 2017 13:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 ezOjMCtyqnk9 for <dnsext@ietfa.amsl.com>; Tue, 26 Sep 2017 13:20:24 -0700 (PDT)
Received: from mx2.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB225134456 for <dnsext@ietf.org>; Tue, 26 Sep 2017 13:20:21 -0700 (PDT)
Received: by mx2.open-xchange.com (Postfix, from userid 1001) id 02FF16A433; Tue, 26 Sep 2017 22:20:20 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx2.open-xchange.com (Postfix) with ESMTP id EE7C46A3EA; Tue, 26 Sep 2017 22:20:15 +0200 (CEST)
Received: from [127.0.0.1] (helo=mx2.open-xchange.com) by localhost with ESMTP (eXpurgate 4.1.8) (envelope-from <peter.van.dijk@powerdns.com>) id 59cab67f-034f-7f000001272a-7f000001bb59-1 for <multiple-recipients>; Tue, 26 Sep 2017 22:20:15 +0200
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.open-xchange.com (Postfix) with ESMTPS id 7DD586A263; Tue, 26 Sep 2017 22:20:15 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by open-xchange.com (Postfix) with ESMTP id 71B6C3C10DB; Tue, 26 Sep 2017 22:20:15 +0200 (CEST)
Received: from open-xchange.com ([127.0.0.1]) by localhost (imap.open-xchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LC-DJOruTjH6; Tue, 26 Sep 2017 22:20:15 +0200 (CEST)
Received: from [192.168.0.20] (095-096-086-198.static.chello.nl [95.96.86.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 4915E3C1A2B; Tue, 26 Sep 2017 22:20:15 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: dnsext@ietf.org, rfc-editor@rfc-editor.org
Date: Tue, 26 Sep 2017 22:20:14 +0200
Message-ID: <247EEDCE-8F96-4E96-9DE3-2481FD95D339@powerdns.com>
In-Reply-To: <B68CA7B9-794B-475B-B8CC-F35E06372DF2@baylink.com>
References: <20170912221500.1622.qmail@ary.lan> <B68CA7B9-794B-475B-B8CC-F35E06372DF2@baylink.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_EE042EF7-4F2F-40D1-8F85-71F290435231_="
Embedded-HTML: [{"HTML":[1110, 4247], "plain":[623, 3650], "uuid":"EB42E533-53D4-4CC3-BEC5-495FC84688F8"}]
X-Mailer: MailMate (1.9.7r5419)
Content-Transfer-Encoding: 7bit
X-purgate-ID: 151428::1506457215-0000034F-8DE5D945/0/0
X-purgate-type: clean
X-purgate-size: 11186
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate: clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/3GGoRjFq88SxNe9CGfweJOnpx84>
Subject: Re: [dnsext] [Editorial Errata Reported] RFC4343 (5112)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 26 Sep 2017 20:20:26 -0000

Hello Jay,

neither the original text or the erratum suggest dropping queries with 
capital letters. The original text already says that queries MUST (2119 
capital) match uppercase letters to lowercase letters. The suggested 
erratum (in my eyes unnecessarily) suggests uppercasing a lowercase 
should to make this even more explicit.

As for devices dropping this, I don’t have any documentation handy but 
mixed case is certainly known to trigger bugs in various pieces of 
software now and then.

Kind regards,
-- 
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/

On 13 Sep 2017, at 4:38, Jay Ashworth wrote:

> Long time listener, first-time caller, but the problem I have with 
> this is that it suggests that queries containing capital letters are 
> dropped.
>
> I recommend to people with overly complicated and long domain names 
> that, as best practice, they spell them in camel case in advertising.
>
> www.MyBadDomain.com
>
> Partially, of course, this is to attempt to avoid the Pen Island/Who 
> Represents problem.  But I do it knowing that the DNS system will case 
> fold those queries and they will thus work properly.
>
> If there are devices dropping those...  I gotta say I'm a little 
> unhappy. Is there documentation of that?
>
> Cheers,
> -- jra
>
> On September 12, 2017 6:15:00 PM EDT, John Levine <johnl@taugh.com>; 
> wrote:
>> I would reject this or at most mark it as hold for update.  The word
>> "should" in lower case appears in two other places where it's not 
>> used
>> in the 2119 sense, and I think this one is not intended to be the 
>> 2119
>> sense either.  The sentence in question is describing the historical
>> situation, and the following capital MUSTs tell you what to do.
>>
>> Having said that, if we ever revisit this document, it would benefit
>> from rewording to make it clearer when it is telling you what to do
>> and when it's just giving background.
>>
>> R's,
>> John
>>
>>
>>
>> In article <20170912194513.752D0B8114C@rfc-editor.org>; you write:
>>> The following errata report has been submitted for RFC4343,
>>> "Domain Name System (DNS) Case Insensitivity Clarification".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata/eid5112
>>>
>>> --------------------------------------
>>> Type: Editorial
>>> Reported by: Change "should" to must in section 3.(no subsection)
>> <rich.tom@alticeusa.com>;
>>>
>>> Section: 3
>>>
>>> Original Text
>>> -------------
>>> comparisons on name lookup for DNS queries should be case 
>>> insensitive
>>>
>>> Corrected Text
>>> --------------
>>> comparisons on name lookup for DNS queries must be case insensitive
>>>
>>> Notes
>>> -----
>>> Some authoritative DNS servers and/or mitigation devices/software
>> silently drop queries that have
>>> uppercase letters in them.  Furthermore, the clarification of the 
>>> case
>> insensitive comparison in the
>>> following two sentences after that particular sentence use the term
>> MUST.  I suspect some readers of the
>>> RFC are reading the word "should" and aren't reading the rest of the
>> paragraph.
>>>
>>> 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
>>>
>>
>>
>> _______________________________________________
>> dnsext mailing list
>> dnsext@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsext
>
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.


> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext