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

"Peter van Dijk" <peter.van.dijk@powerdns.com> Tue, 20 September 2016 20:08 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 4C6B212B4DA for <dnsop@ietfa.amsl.com>; Tue, 20 Sep 2016 13:08:57 -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 GKvhHyIxtJeU for <dnsop@ietfa.amsl.com>; Tue, 20 Sep 2016 13:08:54 -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 2278112B49B for <dnsop@ietf.org>; Tue, 20 Sep 2016 13:08:24 -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 B12D4C1B96; Tue, 20 Sep 2016 22:08:21 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: dnsop@ietf.org
Date: Tue, 20 Sep 2016 22:08:20 +0200
Message-ID: <C6863A2A-D3DD-438B-90C2-F7EC538C2788@powerdns.com>
In-Reply-To: <20160920161350.GA3288@laperouse.bortzmeyer.org>
References: <20160920161350.GA3288@laperouse.bortzmeyer.org>
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/u3grSwvGAYRIcxUL5rCF8nA6H7c>
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:08:57 -0000

Hello,

On 20 Sep 2016, at 18:13, Stephane Bortzmeyer wrote:

> Do you like long terminology discussions, backed by a dozen RFC, where
> people disagree on what's written in these RFC? If so, read on.

When I told you about this confusion in your draft I wasn’t even 
looking for a long terminology discussion. Be careful what you wish for, 
I suppose ;)

> RFC 7719 does not define QNAME (probably because it seemed obvious).

I checked 7719 today, was surprised QNAME was not in there. Probably a 
good idea to fix for 7719bis?

> Is the QNAME "www.afnic.fr" or "lb01-1.nic.fr" ("the data field of the
> last CNAME")???

In my mind, lb01-1.nic.fr, but I understand the other position - 
somewhat.

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