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

Olafur Gudmundsson <ogud@ogud.com> Wed, 20 September 2017 17:03 UTC

Return-Path: <ogud@ogud.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 921B3134220 for <dnsext@ietfa.amsl.com>; Wed, 20 Sep 2017 10:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 qizwSIz1hfBG for <dnsext@ietfa.amsl.com>; Wed, 20 Sep 2017 10:03:49 -0700 (PDT)
Received: from smtp123.ord1d.emailsrvr.com (smtp123.ord1d.emailsrvr.com [184.106.54.123]) (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 CF87713420B for <dnsext@ietf.org>; Wed, 20 Sep 2017 10:03:49 -0700 (PDT)
Received: from smtp8.relay.ord1d.emailsrvr.com (localhost [127.0.0.1]) by smtp8.relay.ord1d.emailsrvr.com (SMTP Server) with ESMTP id EBB43C0060; Wed, 20 Sep 2017 13:03:48 -0400 (EDT)
X-Auth-ID: ogud@ogud.com
Received: by smtp8.relay.ord1d.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id BBC4AC0059; Wed, 20 Sep 2017 13:03:48 -0400 (EDT)
X-Sender-Id: ogud@ogud.com
Received: from [10.20.30.43] (pool-96-255-4-80.washdc.fios.verizon.net [96.255.4.80]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:25 (trex/5.7.12); Wed, 20 Sep 2017 13:03:48 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <20170912221500.1622.qmail@ary.lan>
Date: Wed, 20 Sep 2017 13:03:48 -0400
Cc: dnsext@ietf.org, rfc-editor@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D4627CA-550A-450C-BFBD-2E7BE51DC378@ogud.com>
References: <20170912221500.1622.qmail@ary.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/VCtxCxDdGbhi_7nZHCp0K69yfQI>
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: Wed, 20 Sep 2017 17:03:51 -0000

John and I agree 
please reject this errata 

Olafur

> On Sep 12, 2017, at 6:15 PM, 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