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

Dave Crocker <dhc@dcrocker.net> Tue, 10 July 2018 14:32 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 D553A130FCE for <dnsop@ietfa.amsl.com>; Tue, 10 Jul 2018 07:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, URIBL_BLOCKED=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 yKMS8JfTK2js for <dnsop@ietfa.amsl.com>; Tue, 10 Jul 2018 07:32:49 -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 EEF91130FBF for <dnsop@ietf.org>; Tue, 10 Jul 2018 07:32:48 -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 w6AEZ7Yh019482 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 10 Jul 2018 07:35:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1531233308; bh=rUX8tAKKFR2QvIUnSRovt+y3qMkvi6A2D8il67E0TCM=; h=Subject:To:Cc:References:Reply-To:From:Date:In-Reply-To:From; b=Xc2whLmmNQEANf9GH1WSwQ+M/W0KxF5dDkcs0q7NLlKabSI5GyWhb5ms39vO6lDdW Oo9QJGsmKvgLb06iTFKf9km0kNKFSfERXEaTbWIAN8EZsQ1oAKf9azB76NFGiZQ1pO JX/xgfDuBbJdZY4lUH3pJ86tgWBrgqJrxg7y6PCw=
To: Dick Franks <rwfranks@acm.org>
Cc: DNSOP WG <dnsop@ietf.org>
References: <60eb1c1a-5a3a-5908-27c1-7b3cf587eb14@NLnetLabs.nl> <20180706152250.n7242t2holox6bgq@nic.fr> <9ab5e7e3-2959-2e3c-135d-d749e0aa66fd@dcrocker.net> <CAKW6Ri6FSvzLE5NQYgLWXFOypmz8onih7DqAMFLn=B0XsNZOLw@mail.gmail.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <a3c2141b-1b15-aa06-b01d-7421493066f0@dcrocker.net>
Date: Tue, 10 Jul 2018 07:32:33 -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: <CAKW6Ri6FSvzLE5NQYgLWXFOypmz8onih7DqAMFLn=B0XsNZOLw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kQVEpNy0EBuwnARD2W3w_68OUkQ>
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: Tue, 10 Jul 2018 14:32:59 -0000

On 7/9/2018 2:35 PM, Dick Franks wrote:
> 
> On 9 July 2018 at 19:48, Dave Crocker <dhc@dcrocker.net 
> <mailto:dhc@dcrocker.net>> wrote:
>  >8
> 
>     Does this cause anyone intolerable heart-burn?  If it does, please
>     at least explain but preferably offer something better.
> 
> 
> I do not suffer from intolerable heart-burn but happy to offer:
> 
>   <t>If a public specification calls for the use of an 
> underscore-prefixed domain name,
> the underscored name closest to the root MUST be entered into this registry.
> 

Thanks.  I've added some tweakage to your text:

  <t>If a public specification calls for use of an _underscore-prefixed
    domain node name, the 'global' underscored name -- the name that is
    closest to the DNS root -- MUST be entered into this registry.
    Historically, this is the right-most name that is begins with an
    underscore.</t>


 > (Editorial:  The word underscore does not itself need to be
 > underscore_prefixed)

   It's there as clarification/reminder, in case the reader isn't sure 
what character is meant.  But I'll re-calibrate its use and take out 
extra ones...

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net