Re: [DNSOP] [Technical Errata Reported] RFC7719 (4611)

Ray Bellis <ray@bellis.me.uk> Tue, 02 February 2016 15:37 UTC

Return-Path: <ray@bellis.me.uk>
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 ECE161A9301 for <dnsop@ietfa.amsl.com>; Tue, 2 Feb 2016 07:37:16 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001] 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 4CuEdTKqPglR for <dnsop@ietfa.amsl.com>; Tue, 2 Feb 2016 07:37:15 -0800 (PST)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C8351B2C62 for <dnsop@ietf.org>; Tue, 2 Feb 2016 07:37:15 -0800 (PST)
Received: from [46.227.151.81] (port=63820 helo=rays-mbp.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1aQd0v-0003mn-8J (Exim 4.72) (return-path <ray@bellis.me.uk>); Tue, 02 Feb 2016 15:37:09 +0000
To: RFC Errata System <rfc-editor@rfc-editor.org>, paul.hoffman@icann.org, asullivan@dyn.com, fujiwara@jprs.co.jp, bclaise@cisco.com, joelja@bogus.com, suzworldwide@gmail.com, tjw.ietf@gmail.com
References: <20160202152153.D7F4A18000C@rfc-editor.org>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <56B0CD26.3070604@bellis.me.uk>
Date: Tue, 02 Feb 2016 15:37:10 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160202152153.D7F4A18000C@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/ARkPC4PUUuEYteyGutaoo1cc3vI>
Cc: dnsop@ietf.org, nmalykh@gmail.com
Subject: Re: [DNSOP] [Technical Errata Reported] RFC7719 (4611)
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, 02 Feb 2016 15:37:17 -0000


On 02/02/2016 15:21, RFC Errata System wrote:

> Type: Technical
> Reported by: Nikolai Malykh <nmalykh@gmail.com>
> 
> Section: 2
> 
> Original Text
> -------------
> CNAME:  "It is traditional to refer to the owner of a CNAME record as
>    'a CNAME'.  This is unfortunate, as 'CNAME' is an abbreviation of
>    'canonical name', and the owner of a CNAME record is most certainly
>    not a canonical name."  (Quoted from [RFC2181], Section 10.1.1)
> 
> 
> Corrected Text
> --------------
> CNAME:  "It is traditional to refer to the label of a CNAME record as
>    'a CNAME'.  This is unfortunate, as 'CNAME' is an abbreviation of
>    'canonical name', and the label of a CNAME record is an alias, not
>    a canonical name."  (Quoted from [RFC2181], Section 10.1.1)
> 
> Notes
> -----
> Incorrect quote from RFC 2181.

Arguably "owner" is more accurate - the owner name of a CNAME can
comprise multiple labels (and usually will once fully qualified.

That said, if the intent was to "correct" the quote from RFC 2181 then
RFC 7719 probably should have said so.

Ray