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

Dave Crocker <dhc@dcrocker.net> Mon, 09 July 2018 18:48 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 88601130E84 for <dnsop@ietfa.amsl.com>; Mon, 9 Jul 2018 11:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 9SGGATqLqj6k for <dnsop@ietfa.amsl.com>; Mon, 9 Jul 2018 11:48:26 -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 50838130E73 for <dnsop@ietf.org>; Mon, 9 Jul 2018 11:48:26 -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 w69IosrY020806 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for <dnsop@ietf.org>; Mon, 9 Jul 2018 11:50:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1531162254; bh=e8zXmpIqnpYpV7UeVX/UhSqaM97SHUU9fbnx31+ttxQ=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=hnnbaAD7GQ9Gwv8cOiYFbsvVQVr+Y8hBox6N3YdlqcbqRQABkdLELRHhV4Zh7cyPJ ZNp4cGohfEvimUtVfjBM7LV8BOTuVfgt4Lis241oWOCCBJtmUSi3NjLnjwsIsQT7aG e1MXBkx0ccJEqDCXjZExMtEv709o9m6j+epepwe4=
To: 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: <9ab5e7e3-2959-2e3c-135d-d749e0aa66fd@dcrocker.net>
Date: Mon, 9 Jul 2018 11:48:19 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0
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/msjY5HFAogIcCtXCp-MRSa_G-nE>
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: Mon, 09 Jul 2018 18:48:29 -0000

On 7/6/2018 8:22 AM, Stephane Bortzmeyer wrote:
> On Mon, Jun 25, 2018 at 12:27:17PM +0200,
>   Benno Overeinder <benno@NLnetLabs.nl> wrote
>   a message of 27 lines which said:
> 
>> This starts a Working Group Last Call for draft-ietf-dnsop-attrleaf
> 
> I've read -10 and it seems OK. It solves a real issue, and does it
> properly.
> 
> 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.


G'day.

Given the reality of arguably-legitimate left-to-right domain name 
hierarchy presentation in some contexts, and given a desire to have 
specification text that is both correct and robust, I'm going to suggest 
a bit more verbosity in the attrleaf document, along the lines of...


from:

      <t>If a public specification calls for use of an
         _underscore-prefixed domain node name, the 'global'
         (right-most) _underscored name MUST be entered into this
          registry. </t>

to:
      <t>If a public specification calls for use of an
         _underscore-prefixed domain node name, the 'global'
         (highest level, and typically right-most) _underscored name MUST
         be entered into this registry. </t>


Does this cause anyone intolerable heart-burn?  If it does, please at 
least explain but preferably offer something better.

Thanks.


d/

-- 
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net