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

"John Levine" <johnl@taugh.com> Tue, 12 September 2017 22:18 UTC

Return-Path: <johnl@taugh.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 95727132F64 for <dnsext@ietfa.amsl.com>; Tue, 12 Sep 2017 15:18:30 -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, 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 96Flj8mkAQQG for <dnsext@ietfa.amsl.com>; Tue, 12 Sep 2017 15:18:28 -0700 (PDT)
Received: from gal.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (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 80FC312421A for <dnsext@ietf.org>; Tue, 12 Sep 2017 15:18:28 -0700 (PDT)
Received: (qmail 48205 invoked by uid 125); 12 Sep 2017 22:18:27 -0000
Received: from unknown (64.57.183.53) by gal.iecc.com with QMQP; 12 Sep 2017 22:18:27 -0000
Date: 12 Sep 2017 22:15:00 -0000
Message-ID: <20170912221500.1622.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsext@ietf.org
Cc: rfc-editor@rfc-editor.org
In-Reply-To: <20170912194513.752D0B8114C@rfc-editor.org>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/CJrMDgHaTPFFNEkHM6mAW9EAau4>
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, 12 Sep 2017 22:18:30 -0000

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
>