Re: [DNSOP] Question on RRtypes in RFC 4034 Section 6.2

P Vixie <paul@redbarn.org> Tue, 08 December 2015 15:17 UTC

Return-Path: <paul@redbarn.org>
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 977E11B2EE5 for <dnsop@ietfa.amsl.com>; Tue, 8 Dec 2015 07:17:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level:
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SPF_PASS=-0.001, 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 vHoNUS_TcS01 for <dnsop@ietfa.amsl.com>; Tue, 8 Dec 2015 07:17:37 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E8331B2ECD for <dnsop@ietf.org>; Tue, 8 Dec 2015 07:17:37 -0800 (PST)
Received: from [192.168.0.130] (unknown [96.231.223.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 1A45B13B62; Tue, 8 Dec 2015 15:17:35 +0000 (UTC)
In-Reply-To: <alpine.LFD.2.20.1512081004020.18633@bofh.nohats.ca>
References: <alpine.LFD.2.20.1512081004020.18633@bofh.nohats.ca>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----MR83MF16SCL43HNCDRBX0X3W9YP21I"
Content-Transfer-Encoding: 8bit
From: P Vixie <paul@redbarn.org>
Date: Tue, 08 Dec 2015 15:17:34 +0000
To: Paul Wouters <paul@nohats.ca>, dnsop <dnsop@ietf.org>
Message-ID: <03632261-161E-4274-BFE4-524596CD0302@redbarn.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/Yw8snu0XvRp16rFPLXZXUkJWWfY>
Subject: Re: [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:17:38 -0000

Existing signers and validators won't know the internal format of future rr types.

On December 8, 2015 10:09:06 AM EST, Paul Wouters <paul@nohats.ca> wrote:
>
>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
>
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.