Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt

P Vix <paul@redbarn.org> Thu, 24 August 2017 22:40 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A9EA132710 for <dnsop@ietfa.amsl.com>; Thu, 24 Aug 2017 15:40:27 -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, HTML_MESSAGE=0.001, SPF_PASS=-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 Hb9AX4bTcj3d for <dnsop@ietfa.amsl.com>; Thu, 24 Aug 2017 15:40:25 -0700 (PDT)
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 B209313219C for <dnsop@ietf.org>; Thu, 24 Aug 2017 15:40:25 -0700 (PDT)
Received: from [IPv6:2600:100f:b02b:7c6e:704:24f7:e921:11a2] (unknown [IPv6:2600:100f:b02b:7c6e:704:24f7:e921:11a2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id A037B61FF3; Thu, 24 Aug 2017 22:40:22 +0000 (UTC)
Date: Thu, 24 Aug 2017 22:40:12 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <20170824222734.C786E831AA5D@rock.dv.isc.org>
References: <149894524329.526.18431408698564464455@ietfa.amsl.com> <20170824142147.lshdlmjv62nojd32@nic.fr> <f3e75bd0-b398-1b6a-db3f-ecafd4f0c610@nic.cz> <20170824222734.C786E831AA5D@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----ZAKYQXRVUV6FHOEI3669ATCF9YL6ZX"
Content-Transfer-Encoding: 7bit
To: dnsop@ietf.org, Mark Andrews <marka@isc.org>, =?UTF-8?Q?Petr_=C5=A0pa=C4=8Dek?= <petr.spacek@nic.cz>
From: P Vix <paul@redbarn.org>
Message-ID: <47C8FA15-74BD-4C64-A962-226841BBC29A@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/srECmhWWXEZlFk4zOH6nTZqGpk4>
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 24 Aug 2017 22:40:27 -0000

We might want to invent a new term here like effective qname, but basically I agree with Mark. 2308 was written after bind itself learned the distinction.

On August 24, 2017 3:27:34 PM PDT, Mark Andrews <marka@isc.org> wrote:
>
>RFC 2308 is consistent with RFC 1034.
>
>Go read *all* of RFC 1034.  QNAME is used to refer to *both* the
>original
>*and* updated value after following a CNAME.
>
>Mark
>-- 
>Mark Andrews, ISC
>1 Seymour St., Dundas Valley, NSW 2117, Australia
>PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>
>_______________________________________________
>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.