Re: [DNSOP] Where in a CNAME chain is the QNAME?

Shumon Huque <shuque@gmail.com> Thu, 29 September 2016 14:44 UTC

Return-Path: <shuque@gmail.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 A8F1812B151 for <dnsop@ietfa.amsl.com>; Thu, 29 Sep 2016 07:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 3ZQ2NRXaN-Fq for <dnsop@ietfa.amsl.com>; Thu, 29 Sep 2016 07:44:22 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 306B312B0E6 for <dnsop@ietf.org>; Thu, 29 Sep 2016 07:44:21 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id w72so31559661wmf.1 for <dnsop@ietf.org>; Thu, 29 Sep 2016 07:44:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ijW3B2NhBWMnwiwEjs/53EdRBfIL9j2hQu+i5Xd2S/k=; b=UuSlosZOXog6dfVLAMqLfg7AKn4GI57alb7yclDDikIsFvgfCiLV6XOK1rBz5caU53 F58OSc3u5urlNioAZQhanOxZ3GL/hborccX7llJ4CdjijiB3RLMU+WFrlxnb1noVzE1r qbuRHxYdgXDYRlbkNAD+8R6iVk/zHVQJ4BEr+Iu5rcHsIZLRE1r0cMK805hG26+F7Qtl xSGW8ZEbZkooKKh6bjdbUbTh+tJcSMfwgDuC+ybmZmiYK4GJTqOoopjcSdccOYSTGA6+ BnxdhsWDivjVufCjFjHHRPtwEVVIi3AG97KKT8eIykfSTi09KvLidujZgUzCmfxsRT7o Z8NA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ijW3B2NhBWMnwiwEjs/53EdRBfIL9j2hQu+i5Xd2S/k=; b=DeBXZyBTc9UJHjQ8VRQ9tQXtwsTXPyS+U9nbrDhI1e+GZ6zEzGjx3GJfx2NrZiMj6K fnGtg/XTaETAQq0+yuY9NvN5+HMiQMVZ4nuk90SneNABPYuNP6Xnzl/iiymNLf8dg+pv uz5RybnsdvIYIu5UXdU+cT0LFgo7SH8Rz0jV6OfFOvijsUZ9tFNRzRu+A0KE+kKGOxK2 ZhFKEx53GXunQrPRKMV1bozLWc1lnWDNytLWclFU7ZPKGzcabYRqhJHHdl1C9xhy2qSS F8y021gVwm1GeCu+NVwTSHQLrph86MwAQ8ds5WLkpgjHB/7oBWAAh1onHUkO+yMqEmx5 FyDA==
X-Gm-Message-State: AA6/9RkPvYoa56OYIenGc2GkYuZipGfxNIhtZuZqc1HuzupsykeIk/yyPoyEFeSC/0m5hCqEzrU7X3Isw08NZg==
X-Received: by 10.28.56.196 with SMTP id f187mr3032739wma.120.1475160259676; Thu, 29 Sep 2016 07:44:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.165.168 with HTTP; Thu, 29 Sep 2016 07:44:18 -0700 (PDT)
In-Reply-To: <5ECA97D4-2753-4078-880A-17AE11AC97BA@vpnc.org>
References: <20160920161350.GA3288@laperouse.bortzmeyer.org> <20160923082232.6j2jlr4wqp2fxs56@nic.fr> <2C1851F8-E4D4-402D-9F0A-2C37D40167B0@kahlerlarson.org> <20160928213259.GE4192@laperouse.bortzmeyer.org> <20160929055005.ritosc5cxnds6iyx@mycre.ws> <5ECA97D4-2753-4078-880A-17AE11AC97BA@vpnc.org>
From: Shumon Huque <shuque@gmail.com>
Date: Thu, 29 Sep 2016 10:44:18 -0400
Message-ID: <CAHPuVdW13Tk63ny5VJ2kRvQCwOWuafp9GNc0LDDDadoDG=R4Xw@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=001a114cca4e43d0ce053da6834b
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/TUj3KLyIZZ11T_NuaO7kn_NGwgU>
Cc: Robert Edmonds <edmonds@mycre.ws>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] Where in a CNAME chain is the QNAME?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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, 29 Sep 2016 14:44:24 -0000

On Thu, Sep 29, 2016 at 10:36 AM, Paul Hoffman <paul.hoffman@vpnc.org>
wrote:

> On 28 Sep 2016, at 22:50, Robert Edmonds wrote:
>
> Stephane Bortzmeyer wrote:
>>
>>> On Mon, Sep 26, 2016 at 09:04:54AM -0400,
>>>  Matt Larson <matt@kahlerlarson.org> wrote
>>>  a message of 41 lines which said:
>>>
>>> I'd venture that more people familiar with the subject matter would
>>>> define QNAME as the name in the question section of a DNS message.
>>>> (That's my sense of the definition, FWIW.)
>>>>
>>>
>>> What about adding this text to the Terminology section of the draft?
>>>
>>>    <t>"QNAME": it is defined in <xref target="RFC1034"/> and
>>>    in <xref target="RFC1035"/>, section 4.1.2, but, because <xref
>>>    target="RFC2308"/> provides a different definition, we repeat the
>>>    original one here: the QNAME is the owner name of the record in the
>>>    Question section.</t>
>>>
>>
>> The QNAME is a domain name, but is it an owner name? There is no owned
>> record data in the question section (and the entries in the question
>> section are not RRs).
>>
>
> Oddly, "owner name" is correct here. From RFC 1035, Section 3.2.1 which
> describes the format of resource records:
>
> All RRs have the same top level format shown below:
>
>                                     1  1  1  1  1  1
>       0  1  2  3  4  5  6  7  8  9  0  1  2  3  4  5
>     +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>     |                                               |
>     /                                               /
>     /                      NAME                     /
>     |                                               |
>     +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>     |                      TYPE                     |
>     +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
> . . .
>
> where:
>
> NAME            an owner name, i.e., the name of the node to which this
>                 resource record pertains.
>

Yes, Owner name is defined in terms of a resource record, i.e. the domain
name that owns a resource record.

But the question section has no resource record. It has 3 components of a
potential resource record.

-- 
Shumon Huque