IETF Logo Mail Archive

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

"Darcy Kevin (FCA)" <kevin.darcy@fcagroup.com> Mon, 28 August 2017 22:20 UTC

Return-Path: <kevin.darcy@fcagroup.com>
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 B57AB1326BB for <dnsop@ietfa.amsl.com>; Mon, 28 Aug 2017 15:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 OlKB9u9Mb-G6 for <dnsop@ietfa.amsl.com>; Mon, 28 Aug 2017 15:20:18 -0700 (PDT)
Received: from shbmap08.extra.chrysler.com (shbmap08.out.extra.chrysler.com [129.9.75.106]) (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 AFA8013208E for <dnsop@ietf.org>; Mon, 28 Aug 2017 15:20:18 -0700 (PDT)
Received: from odbmap09.oddc.chrysler.com (Unknown_Domain [151.171.137.34]) by (Symantec Messaging Gateway) with SMTP id 4C.FB.07972.D1794A95; Mon, 28 Aug 2017 18:20:13 -0400 (EDT)
X-AuditID: 81094b68-ebc6498000001f24-91-59a4971df7cf
Received: from mxph1chrw.fgremc.it (Unknown_Domain [151.171.20.45]) by (Symantec Messaging Gateway) with SMTP id B8.7C.17921.D1794A95; Mon, 28 Aug 2017 18:20:15 -0400 (EDT)
Received: from mxph4chrw.fgremc.it (151.171.20.48) by mxph1chrw.fgremc.it (151.171.20.45) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Mon, 28 Aug 2017 18:20:15 -0400
Received: from mxph4chrw.fgremc.it ([fe80::cc0c:cb4f:1b3f:2701]) by mxph4chrw.fgremc.it ([fe80::cc0c:cb4f:1b3f:2701%18]) with mapi id 15.00.1236.000; Mon, 28 Aug 2017 18:20:14 -0400
From: "Darcy Kevin (FCA)" <kevin.darcy@fcagroup.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
Thread-Index: AQHTHORnHuETSd4O0EiRIffADErT/qKT6iSAgAAsejiABfxBAP//5pnQ
Date: Mon, 28 Aug 2017 22:20:14 +0000
Message-ID: <06a96a6e59d14d378098013966f6641b@mxph4chrw.fgremc.it>
References: <149894524329.526.18431408698564464455@ietfa.amsl.com> <20170824142147.lshdlmjv62nojd32@nic.fr> <f3e75bd0-b398-1b6a-db3f-ecafd4f0c610@nic.cz> <20170824222734.C786E831AA5D@rock.dv.isc.org> <4DC2EF4E-8922-4531-958C-FC4BEF75EAFA@powerdns.com>
In-Reply-To: <4DC2EF4E-8922-4531-958C-FC4BEF75EAFA@powerdns.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [151.171.20.195]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFIsWRmVeSWpSXmKPExsUyfXWnkq7s9CWRBlOPmVvcfXOZxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGXsf72crOMJX8XSSfwPjA+4uRk4OCQETifV9k1m6GLk4hAS2 M0psX7CBHSaxddUNJhBbSGA9o8T7y7wQResYJS5++MEO4exklFh8bxVYBxtQx8Ird5lBbBEB VYkL/76DdQsLpEjs+7mRHSKeKjHp0BwWCNtN4t/3KawgNgtQ/fwz78HqeQWcJDa8XMoIsaCZ SWLqgSlgQzkFHCS2zH7PBmIzCohJfD+1BqyBWUBc4taT+UwQZwtILNlznhnCFpV4+fgfK4Rt ILF16T4WCFtJYuebDSwQvToSC3Z/YoOwtSWWLXzNDHGEoMTJmU+g6u+xS3TMYZ7AKDkLybpZ SNpnIWmfhaR9ASPLKkbp4oyk3MQCAwu91IqSokS95IyiyuKc1CK95PzcTYzAGGzk9M7YwThn q+UhRgEORiUeXt2pSyKFWBPLiitzDzFKcDArifD+nQwU4k1JrKxKLcqPLyrNSS0+xCjNwaIk zmtUBJQSSE8sSc1OTS1ILYLJMnFwSjUwmt12SBcIVtzYWzhHbUmM1rd3V2SY9mlvf+PG7+JR eynz2PclAuIeHz7Y/J4i8GHeWQ+95AsPFPyK7yveKf2ZnG99nbWucuu+nfbdHYaXZ8oVBnnP TV2rzrCg7ZGBeWCukV+Qqtk0fimZcEN2wf+fT6d8TXzp/+qLHWt2vQ3DNsnNbTbd9huUWIoz Eg21mIuKEwF93/hTvQIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNKsWRmVeSWpSXmKPExsUyfbWIrq789CWRBo9PSVrcfXOZxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGXsf72crOMJX8XSSfwPjA+4uRk4OCQETia2rbjCB2EIC6xkl 3l/m7WLkArLXMUpc/PCDHcLZySix+N4qdpAqNqCOhVfuMoPYIgKqEhf+fQfrFhZIkdj3cyM7 RDxVYtKhOSwQtpvEv+9TWEFsFqD6+Wfeg9XzCjhJbHi5lBFiQTOTxNQDU8CGcgo4SGyZ/Z4N xGYUEJP4fmoNWAOzgLjErSfzmSDOFpBYsuc8M4QtKvHy8T9WCNtAYuvSfSwQtpLEzjcbWCB6 dSQW7P7EBmFrSyxb+JoZ4ghBiZMzn7BMYBSbhWTFLCQts5C0zELSsoCRZRWjVH5KUm5igYGl Xn5KSrJeckZRZXFOapFecn7uJkZw3HQq7mBsXGR5iFGAg1GJh3fdlCWRQqyJZcWVuYcYJTmY lER5d1YsjhTiS8pPqcxILM6ILyrNSS0+xCjBwawkwvt3MlA5b0piZVVqUT5MSpqDRUmcV6XA IVBIID2xJDU7NbUgtQgmK8PBoSTB+3YqUKNgUWp6akVaZk4JQpqJgxNkOA/QcKlpIMOLCxJz izPTIfKnGCWlxHlZQRICIImM0jy43leM4kAvCPPuARnNA0yBcF2vgAYyAQ1UFFwIMrAkESEl 1cDovO9bw9xP+hKlu1WnHW7kb5zVcs7QXeBozkvVLYcaJfVurm5Rjvy3b24CU43ow82arQsU /s/yZl11pvyW88ebb87+e5iVwslrtLLeoTFMOoZXfLrZjsWyfae3nSz9+2D7V8WPqS/q1Jzi xCSMNUr9p1RvM53hNFc45Yv7t9jHf/YpmUbf/uCtxFKckWioxVxUnAgACkSqjT4DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/x3UGiNVgvO1iacG9b2ShBEAggQc>
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: Mon, 28 Aug 2017 22:20:21 -0000

Please understand that I don't have a strong opinion on the DNS terminology discussion, _per_se_, but I do have them with regard to semantics, logic and proper citation, which was kind of my prior life, before I even got into DNS, or even Information Technology (at various times an English major, Philosophy major, a professional proofreader, etc.)

The erratum-to-the-erratum is that RFC 1034 didn't *define* QNAME. But RFC 1035 did: Section 4.1.2, QNAME is one of the fields of the Query Section, which, it is stated, constitute " the parameters that define what is being asked". Thus, deductively, QNAME is defined in that document as "the name that was asked [by the client, assumed]".

RFC 2308 includes in its definition of "QNAME", end-of-CNAME-chain (where applicable). This was not covered by the RFC 1035 definition, since the client didn't ask for it.

We can talk about "references" all we want, but the erratum, despite an off-by-one error in RFC citation, is about *definitions*, and the one in RFC 2308 differs from the earlier one from the RFC 1034/1035 matched set.

											- Kevin



-----Original Message-----
From: DNSOP [mailto:dnsop-bounces@ietf.org] On Behalf Of Peter van Dijk
Sent: Monday, August 28, 2017 9:52 AM
To: dnsop@ietf.org
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt

On 25 Aug 2017, at 0:27, Mark Andrews 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.

+1

Kind regards,
-- 
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email