[DNSOP] Question on RRtypes in RFC 4034 Section 6.2

Paul Wouters <paul@nohats.ca> Tue, 08 December 2015 15:09 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3802E1B2EE8 for <dnsop@ietfa.amsl.com>; Tue, 8 Dec 2015 07:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.01
X-Spam-Level:
X-Spam-Status: No, score=-4.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 xwbLl-NcnmDI for <dnsop@ietfa.amsl.com>; Tue, 8 Dec 2015 07:09:17 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 471931B2EE6 for <dnsop@ietf.org>; Tue, 8 Dec 2015 07:09:11 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3pFPzn1ND6z3K8 for <dnsop@ietf.org>; Tue, 8 Dec 2015 16:09:09 +0100 (CET)
Authentication-Results: mx.nohats.ca; dkim=pass (1024-bit key) header.d=nohats.ca header.i=@nohats.ca header.b=H+iDo4Bz
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id hJpGtomvtAu5 for <dnsop@ietf.org>; Tue, 8 Dec 2015 16:09:08 +0100 (CET)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <dnsop@ietf.org>; Tue, 8 Dec 2015 16:09:08 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPS id 588648009F for <dnsop@ietf.org>; Tue, 8 Dec 2015 10:09:06 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1449587346; bh=iuxzCwATTZ4OY9ShOu8C3LuRBiBHuS4D1mYlXvrwRwg=; h=Date:From:To:Subject; b=H+iDo4Bz6EB3wNQoQ/xqcogIokKjlVeZHmbPMPiesXme6GLwEef11pmP1t48WA+Ub nDsHOT2nWDY7rLK+eDqUiqI0f6PaLGtol/vR5NVeW7lIaZY4kyMeZfREgufi+TexV9 j0MpDVHCUXTz+eEMloeFF70g57vMZQ36fE3xt5kY=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.15.2/8.15.2/Submit) with ESMTP id tB8F963a019863 for <dnsop@ietf.org>; Tue, 8 Dec 2015 10:09:06 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Tue, 08 Dec 2015 10:09:06 -0500
From: Paul Wouters <paul@nohats.ca>
To: dnsop <dnsop@ietf.org>
Message-ID: <alpine.LFD.2.20.1512081004020.18633@bofh.nohats.ca>
User-Agent: Alpine 2.20 (LFD 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/BayP1lNwLnbObZZ6ZX2_9bcuQN8>
Subject: [DNSOP] Question on RRtypes in RFC 4034 Section 6.2
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2015 15:09:18 -0000

Hi,

Section 6.2 of 4034 talks about canonicalization of the RR Form

Item 3 states:

3.  if the type of the RR is NS, MD, MF, CNAME, SOA, MB, MG, MR, PTR,
        HINFO, MINFO, MX, HINFO, RP, AFSDB, RT, SIG, PX, NXT, NAPTR, KX,
        SRV, DNAME, A6, RRSIG, or NSEC, all uppercase US-ASCII letters in
        the DNS names contained within the RDATA are replaced by the
        corresponding lowercase US-ASCII letters;

My questions:

a) What was the purpose of listening these and not all RRtypes?
    (It seems perhaps it wanted to say "All except A/AAAA")
b) What should be done with new RRtypes like OPENPGPKEY or SMIMA?
c) Why the hell - hardcoded lists and not IANA registry?
d) Does this need updating or an errata?

Paul