Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-attrleaf

Dave Crocker <dhc@dcrocker.net> Thu, 12 July 2018 01:59 UTC

Return-Path: <dhc@dcrocker.net>
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 98548130FD4 for <dnsop@ietfa.amsl.com>; Wed, 11 Jul 2018 18:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
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 GJU1bP-JXEoZ for <dnsop@ietfa.amsl.com>; Wed, 11 Jul 2018 18:59:01 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 50101130FCF for <dnsop@ietf.org>; Wed, 11 Jul 2018 18:59:01 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w6C21UJq011862 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 11 Jul 2018 19:01:30 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1531360891; bh=pfNaD99EJ0Iz/XlCwYO/Arewp/Ft8MidYdhxoBYkhzM=; h=Subject:To:Cc:References:Reply-To:From:Date:In-Reply-To:From; b=BBZgSek0DN7JZCmZyvR+lr6T7dsrAass9PkMoLo3CFBoWywiNCrcFoLR7bemgzR1r AtDeln7ZwSPt+f7CsT4bnjgA6lyHPjbULCLJEdHmLYmID5nqmJEgLh05LrSHOvrz5O b93dFV+WKFrCLGsezLIMOvzs4ajCntcZd6vKv/f8=
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Benno Overeinder <benno@NLnetLabs.nl>
Cc: DNSOP WG <dnsop@ietf.org>
References: <60eb1c1a-5a3a-5908-27c1-7b3cf587eb14@NLnetLabs.nl> <20180706152250.n7242t2holox6bgq@nic.fr>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <d29c02f6-f092-0092-9ac2-ee5d0f1e2e14@dcrocker.net>
Date: Wed, 11 Jul 2018 18:58:54 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20180706152250.n7242t2holox6bgq@nic.fr>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4-8xhh3Yl9j16hfywZuqf14zDQI>
Subject: Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-attrleaf
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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, 12 Jul 2018 01:59:04 -0000

On 7/6/2018 8:22 AM, Stephane Bortzmeyer wrote:
> Editorial: I would prefer all occurrences of "right-most" to be
> replaced by "most general", to emphasize that it is not the position
> which matters, it is the closeness to the root.
> 
> Editorial: 'that is they are the "top" of a DNS branch, under a
> "parent" domain name.' I assume that "top" is used instead of "apex"
> because the sentence does not always refer to the top of a zone?


So, this turned into a niggling 'thing' for me and produced a collection 
of small changes.

The basic model now is to introduce the issue early in the document and 
dispatch it once, and then use a single term for the rest of the 
document, without all the distractingly redundant clarifications.

So there's now text in attrleaf that explains about hierarchy, top, 
highest, and the original presentation convention of right, but noting 
that other presentations are possible.

It then declares the term 'global' as referring to the node name of 
interest and only uses that term in the rest of the document.  (Well, 
there are a couple of places where 'highest' was needed as clarification.)

The -fix document doesn't stand alone, so it merely continues the 
convention and does not re-explain it.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net