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

"Roy Arends" <roy@dnss.ec> Tue, 08 December 2015 15:33 UTC

Return-Path: <roy@dnss.ec>
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 EBFDC1B2F2F for <dnsop@ietfa.amsl.com>; Tue, 8 Dec 2015 07:33:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level:
X-Spam-Status: No, score=-4 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] 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 VT0Ua0CLGeZL for <dnsop@ietfa.amsl.com>; Tue, 8 Dec 2015 07:33:23 -0800 (PST)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E38FA1B2F2E for <dnsop@ietf.org>; Tue, 8 Dec 2015 07:33:22 -0800 (PST)
Received: by qgec40 with SMTP id c40so20930665qge.2 for <dnsop@ietf.org>; Tue, 08 Dec 2015 07:33:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dnss.ec; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-type; bh=TLPRhWyY2MYf+sfsk3EhPKqdDBJyS0ChKNPCk/9G2jQ=; b=WzI/PRdsJNXnLcMadHlG88TXln1IwRk26Q6M9O8FaKToKoSkalYz+71D1xSGxsJo7i ugF+e9TthgV+VVjNFE7KmXiMxiXKkWVG+asOmMWWFQVHCxt3OQG94uVKJ60gHz5SlAaX 63mRbEls85hoLY3+XP+K8+MVKA/2XD6NDMelE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-type; bh=TLPRhWyY2MYf+sfsk3EhPKqdDBJyS0ChKNPCk/9G2jQ=; b=GtcWWXYfWBhyWKL4H5yUM2YYZoakDQ+SGSQwXFoXz5pnLOKo/vG2tROvF6RN6i3z+3 DNvmgDzggaQb4ioaBrNW1VSUC51pZyTeTvGZOc4t8/3HX77JHAx0V7D42+f5BIYQP8DC BvugPUVZ9UkjHMPBnSSY7+ZWp7Bml9z0XMrkCdSxk2tvNHBXMliZnACy1s15i546LNvv FCLdgNBMrYl4dYqYKqTaWcLympI2IKNLc/ZxIy/xuKuefzT43qZPDsAMQm+p/mgAVtce 9VHiQtPh7yW/4kMuYieziTZ8lFQ/YdrZ1QrXhrOPo8bZNMvKJ3+1tLsrnl277+vvicrX yrbw==
X-Gm-Message-State: ALoCoQmOBRO+xNqyzH6NQiMSFMIr9LOx+L6H6q4ThsRdFmNyZqmLU4ScdZmik3Tdydd4bKRIXL3HpJYuqmibBDGY4TfYeOxWZw==
X-Received: by 10.140.19.36 with SMTP id 33mr161570qgg.65.1449588799477; Tue, 08 Dec 2015 07:33:19 -0800 (PST)
Received: from [10.47.60.46] (host217-42-117-142.range217-42.btcentralplus.com. [217.42.117.142]) by smtp.gmail.com with ESMTPSA id 63sm1706711qgl.31.2015.12.08.07.33.18 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 08 Dec 2015 07:33:18 -0800 (PST)
From: Roy Arends <roy@dnss.ec>
To: Paul Wouters <paul@nohats.ca>
Date: Tue, 08 Dec 2015 15:33:16 +0000
Message-ID: <9A97DA64-FDE5-4B35-A5F1-AC8624AAB2E2@dnss.ec>
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: text/plain; format="flowed"
X-Mailer: MailMate Trial (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/Y6pOEwWYuEr_qT5zyrKSlmDiDLE>
Cc: dnsop <dnsop@ietf.org>
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:33:25 -0000


On 8 Dec 2015, at 15:09, Paul Wouters 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")

These specific RR types contain a DNS name in the RDATA. Up until 
RFC3597 they might have been subject to name compression.

> b) What should be done with new RRtypes like OPENPGPKEY or SMIMA?

Nothing.

> c) Why the hell - hardcoded lists and not IANA registry?

Calm down. This is a complete set. Not to be expanded, ever. Exceptions 
to the RFC3597 rules (where the list originates) because they predate 
it.

> d) Does this need updating or an errata?

Not that I know.

Roy