[dnsext] [Errata Held for Document Update] RFC4343 (5112)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 13 September 2017 14:42 UTC

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 29D0D133017; Wed, 13 Sep 2017 07:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 TNd_A--zeREk; Wed, 13 Sep 2017 07:42:27 -0700 (PDT)
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 BF8D6132949; Wed, 13 Sep 2017 07:42:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3D81CB82150; Wed, 13 Sep 2017 07:42:15 -0700 (PDT)
To: rich.tom@alticeusa.com, Donald.Eastlake@motorola.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: warren@kumari.net, iesg@ietf.org, dnsext@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20170913144215.3D81CB82150@rfc-editor.org>
Date: Wed, 13 Sep 2017 07:42:15 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/Fp-ouTRqOwaPS1rE_YitCbcwL9w>
Subject: [dnsext] [Errata Held for Document Update] 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, 13 Sep 2017 14:42:29 -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:
http://www.rfc-editor.org/errata/eid5112

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

Reported by: Change "should" to must in section 3.(no subsection) <rich.tom@alticeusa.com>
Date Reported: 2017-09-12
Held by: Warren Kumari (IESG)

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
-----
--- Original report ---
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.

---- WK Update ----
The full quote is: "According to the original DNS design decision, comparisons on name
   lookup for DNS queries should be case insensitive [STD13]. ", and the title of this (RFC4343) is "Domain Name System (DNS) Case Insensitivity Clarification" -- seeing as the whole point of this document is to clarify the original spec, I think that readers will read the RFC2119 bits.

However, I do agree that this could be better worded, and future updates of this document should probably reword this to make it clearer. 

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