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

Jay Ashworth <> Sat, 23 September 2017 03:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D67491332DF for <>; Fri, 22 Sep 2017 20:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.505
X-Spam-Level: *
X-Spam-Status: No, score=1.505 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_96_XX=3.405, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MHBVtJDU9FXg for <>; Fri, 22 Sep 2017 20:09:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3A3CA1332D7 for <>; Fri, 22 Sep 2017 20:09:26 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7886C4A2002; Sat, 23 Sep 2017 03:09:25 +0000 (UTC)
Received: from ([]) by localhost ( []) (amavisd-new, port 10032) with ESMTP id Tciv9A57ae1E; Sat, 23 Sep 2017 03:09:24 +0000 (UTC)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8E9074A2003; Sat, 23 Sep 2017 03:09:24 +0000 (UTC)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10026) with ESMTP id 7x-RWOMlgJUr; Sat, 23 Sep 2017 03:09:24 +0000 (UTC)
Received: from [IPv6:2607:fb90:5246:ffd8:aa:6bf:d08a:cb94] (unknown []) by (Postfix) with ESMTPSA id 01CCB4A2002; Sat, 23 Sep 2017 03:09:23 +0000 (UTC)
Date: Tue, 12 Sep 2017 22:38:22 -0400
User-Agent: K-9 Mail for Android
In-Reply-To: <20170912221500.1622.qmail@ary.lan>
References: <20170912221500.1622.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----4A11JDH0DN06B9QTQ19VWRB36MIYZI"
Content-Transfer-Encoding: 7bit
To:,John Levine <>
From: Jay Ashworth <>
Message-ID: <>
Archived-At: <>
Subject: Re: [dnsext] [Editorial Errata Reported] RFC4343 (5112)
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Extensions working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 23 Sep 2017 03:09:28 -0000

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.

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?

-- jra

On September 12, 2017 6:15:00 PM EDT, John Levine <> 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.
>In article <> 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:
>>Type: Editorial
>>Reported by: Change "should" to must in section 3.(no subsection)
>>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
>>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
>>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
>>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 mailing list

Sent from my Android device with K-9 Mail. Please excuse my brevity.