IETF Logo Mail Archive

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

"Jay R. Ashworth" <jra@baylink.com> Tue, 26 September 2017 20:56 UTC

Return-Path: <jra@baylink.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 B45BE134463 for <dnsext@ietfa.amsl.com>; Tue, 26 Sep 2017 13:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7NZaiW08DzPO for <dnsext@ietfa.amsl.com>; Tue, 26 Sep 2017 13:56:00 -0700 (PDT)
Received: from franklin.baylink.com (li1308-44.members.linode.com [45.79.209.44]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78B12132153 for <dnsext@ietf.org>; Tue, 26 Sep 2017 13:56:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by franklin.baylink.com (Postfix) with ESMTP id DC5BE4A2002; Tue, 26 Sep 2017 20:55:59 +0000 (UTC)
Received: from franklin.baylink.com ([127.0.0.1]) by localhost (franklin.baylink.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id KVH7dA5OzBpe; Tue, 26 Sep 2017 20:55:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by franklin.baylink.com (Postfix) with ESMTP id 595F94A2003; Tue, 26 Sep 2017 20:55:59 +0000 (UTC)
X-Virus-Scanned: amavisd-new at franklin.baylink.com
Received: from franklin.baylink.com ([127.0.0.1]) by localhost (franklin.baylink.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id xaDO1rKr7sXW; Tue, 26 Sep 2017 20:55:59 +0000 (UTC)
Received: from franklin.baylink.com (franklin.baylink.com [45.79.209.44]) by franklin.baylink.com (Postfix) with ESMTP id 42E9C4A2002; Tue, 26 Sep 2017 20:55:59 +0000 (UTC)
Date: Tue, 26 Sep 2017 20:55:59 +0000
From: "Jay R. Ashworth" <jra@baylink.com>
To: Peter van Dijk <peter.van.dijk@powerdns.com>
Cc: dnsext@ietf.org, rfc-editor@rfc-editor.org
Message-ID: <352496552.13231.1506459359166.JavaMail.zimbra@baylink.com>
In-Reply-To: <247EEDCE-8F96-4E96-9DE3-2481FD95D339@powerdns.com>
References: <20170912221500.1622.qmail@ary.lan> <B68CA7B9-794B-475B-B8CC-F35E06372DF2@baylink.com> <247EEDCE-8F96-4E96-9DE3-2481FD95D339@powerdns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [45.79.209.44]
X-Mailer: Zimbra 8.6.0_GA_1153 (ZimbraWebClient - FF55 (Win)/8.6.0_GA_1153)
Thread-Topic: RFC4343 (5112)
Thread-Index: 3ItjHQ5VmTJIsgdtzYnorZZ/ZzWMsA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/45WMdg8B6sYDQWmXU2UNhcXBv_0>
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:56:01 -0000

> From: "Peter van Dijk" <peter.van.dijk@powerdns.com>

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

I was, in fact, being aghast at this:

>>> Some authoritative DNS servers and/or mitigation devices/software
>>> silently drop queries that have uppercase letters in them.

If there are authoritative zone servers that drop incoming queries with capital
letters in them, I wish someone would let me know where so that I can go set 
them on fire.  That's *terribly* antisocial, aside from violating the RFCs to a
fare-thee-well.

My apologies for being insufficiently clear about what I was responding to.

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra@baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates       http://www.bcp38.info          2000 Land Rover DII
St Petersburg FL USA      BCP38: Ask For It By Name!           +1 727 647 1274

v2.23.0 | Report a Bug | By Email