Re: [DNSOP] Please review in terminology-bis: QNAME

Robert Edmonds <edmonds@mycre.ws> Tue, 02 January 2018 16:29 UTC

Return-Path: <edmonds@mycre.ws>
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 777BC12706D for <dnsop@ietfa.amsl.com>; Tue, 2 Jan 2018 08:29:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 tf47seUKGepq for <dnsop@ietfa.amsl.com>; Tue, 2 Jan 2018 08:29:02 -0800 (PST)
Received: from mycre.ws (mycre.ws [45.33.102.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96F50124319 for <dnsop@ietf.org>; Tue, 2 Jan 2018 08:29:02 -0800 (PST)
Received: by chase.mycre.ws (Postfix, from userid 1000) id B697E12C104F; Tue, 2 Jan 2018 11:29:01 -0500 (EST)
Date: Tue, 02 Jan 2018 11:29:01 -0500
From: Robert Edmonds <edmonds@mycre.ws>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, dnsop WG <dnsop@ietf.org>
Message-ID: <20180102162901.wxq4d4libbwgvs43@mycre.ws>
References: <F8509291-AAA0-49FC-BF84-21C3ECAF9813@vpnc.org> <20171218131223.yfu5ntzdyjivlnzi@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20171218131223.yfu5ntzdyjivlnzi@nic.fr>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mQVhgxpO8TgqMEzIaneluf2bVSs>
Subject: Re: [DNSOP] Please review in terminology-bis: QNAME
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: Tue, 02 Jan 2018 16:29:04 -0000

Stephane Bortzmeyer wrote:
> On Mon, Dec 11, 2017 at 07:30:27AM -0800,
>  Paul Hoffman <paul.hoffman@vpnc.org> wrote 
>  a message of 16 lines which said:
> 
> > Some of the new terms added to the terminology-bis draft
> > (https://datatracker.ietf.org/doc/draft-ietf-dnsop-terminology-bis/)since
> > RFC 7719 can expose what some (but not all) people perceive as lack
> > of clarity in RFC 1034/1035. This week, we hope you will look at the
> > definition in the draft for "QNAME".
> 
> As I mentioned in this errata
> <https://www.rfc-editor.org/errata/eid4983>, I think RFC 2308 was
> wrong in redefining QNAME. My personal preference would be to change
> the second paragraph to "RFC 2308 proposed another definition,
> different from the original one. Since it is actually a different
> concept, it would be better to find another name for it. Here, QNAME
> retains the original definition of RFC 1034."
> 
> Otherwise, if the WG prefers, I can live with the current text :-(

I agree with Stephane. The STD 13 definition of QNAME is extremely clear
while the RFC 2308 re-definition seems rare enough that it tends to
occur mainly in discussions about how to define QNAME :-\

-- 
Robert Edmonds