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

Dave Crocker <> Mon, 09 July 2018 18:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 88601130E84 for <>; Mon, 9 Jul 2018 11:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.001
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9SGGATqLqj6k for <>; Mon, 9 Jul 2018 11:48:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 50838130E73 for <>; Mon, 9 Jul 2018 11:48:26 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) by (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 <>; Mon, 9 Jul 2018 11:50:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; 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=
References: <> <>
From: Dave Crocker <>
Organization: Brandenburg InternetWorking
Message-ID: <>
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: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-attrleaf
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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 <> 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.


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...


      <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>

      <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.



Dave Crocker
Brandenburg InternetWorking