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

"Peter van Dijk" <peter.van.dijk@powerdns.com> Tue, 20 September 2016 20:09 UTC

Return-Path: <peter.van.dijk@powerdns.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 DA4AC12B785 for <dnsop@ietfa.amsl.com>; Tue, 20 Sep 2016 13:09:28 -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] 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 q8EMsJNl_YG3 for <dnsop@ietfa.amsl.com>; Tue, 20 Sep 2016 13:09:27 -0700 (PDT)
Received: from shannon.7bits.nl (shannon.7bits.nl [89.188.0.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE84212B506 for <dnsop@ietf.org>; Tue, 20 Sep 2016 13:09:27 -0700 (PDT)
Received: from [192.168.137.1] (unknown [IPv6:2001:610:666:0:2cfd:3de7:6332:9654]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: peter) by shannon.7bits.nl (Postfix) with ESMTPSA id 349DBC1B96; Tue, 20 Sep 2016 22:09:26 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: dnsop <dnsop@ietf.org>
Date: Tue, 20 Sep 2016 22:09:25 +0200
Message-ID: <1A867423-2299-497E-BFA2-064737BEF6A6@powerdns.com>
In-Reply-To: <CAHw9_iJApVDTn7P2mCyqzByGJXH2nwOaEWzmQCs0HXV82BW2Bw@mail.gmail.com>
References: <20160920161350.GA3288@laperouse.bortzmeyer.org> <20160920163753.5k4h4cvrtdkt4pjh@mycre.ws> <CAHw9_iJApVDTn7P2mCyqzByGJXH2nwOaEWzmQCs0HXV82BW2Bw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1PNUdOfKVFXVqZfq1OyUqxfl8uw>
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: Tue, 20 Sep 2016 20:09:29 -0000

Hello,

On 20 Sep 2016, at 19:09, Warren Kumari wrote:

> I think the RFC2308 definition is only true in the negative caching
> context... or something...

Which, of course, is the context in which draft-ietf-dnsop-nxdomain-cut 
uses QNAME.

I’m not here to argue which definition of QNAME is correct, but I do 
think the text could use some clarification to avoid this confusion. 
Easiest might be to point at 2308 as that definition is functionally 
identical to the longer texts the draft has now.

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