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

Dave Crocker <dhc@dcrocker.net> Thu, 28 June 2018 14:19 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 C7C85130DC5 for <dnsop@ietfa.amsl.com>; Thu, 28 Jun 2018 07:19:58 -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 E3lsudfhlJ1g for <dnsop@ietfa.amsl.com>; Thu, 28 Jun 2018 07:19:57 -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 7F30C130DC3 for <dnsop@ietf.org>; Thu, 28 Jun 2018 07:19:57 -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 w5SEMI5W007196 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 28 Jun 2018 07:22:19 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1530195739; bh=tRTfwJaj0pcjjTav4SGTFN9b/GCIMASax+E2oDlKEEY=; h=Subject:To:References:From:Cc:Reply-To:Date:In-Reply-To:From; b=cemaGP37l8J9Cjh4c6twaO6A/iJCVppQQ5m6yfwHPRFMZ6ZM84Zcg7Z0cUnr2dARc nvaDDKNiOjXgThJtNOPwebqH5EwyujoU7c1PlhJyDqRocObkBVgMnjnrYwbR2ExBDU QOu9vfi4b/UIbKZKdgwgNrtyi+NUaGgTfDUxUd4Q=
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <8bfea5a9-da8b-162f-8e81-45752821f9e1@NLnetLabs.nl> <7DA5ED9F-C2F0-4F72-9F38-909574C81C5C@vpnc.org>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Cc: DNSOP WG <dnsop@ietf.org>
Reply-To: dcrocker@bbiw.net
Message-ID: <ac089db0-59c5-7083-b286-480ae99ae1eb@dcrocker.net>
Date: Thu, 28 Jun 2018 07:19:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <7DA5ED9F-C2F0-4F72-9F38-909574C81C5C@vpnc.org>
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/B2w4gD9z2NTgEJdsON5FgGxEnxI>
Subject: Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-attrleaf-fix
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
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, 28 Jun 2018 14:19:59 -0000

On 6/27/2018 3:01 PM, Paul Hoffman wrote:
> Due to its nature, the document is a bit difficult to read, but I don't 
> have any suggestion about how to make it better. 

Could you at least provide some description of what it is that you find 
difficult?


> The only problem I have 
> with the document is that there are lots of informational references 
> that are not referred to in the body of the text; they are not even 
> listed in the Updates list at the top of the document. This should 
> either be explained clearly in the body of the document or removed.

Assuming my xml processor produces the same list of not-used references 
as yours:  most indeed needed to be added to the Updates list and have 
been.  A few were carry-overs from the base document and indeed are 
unused here; they've been drops.  Thanks for the audit.

FWIW, I'd considered replicating the Updates list in the body of the 
document, solely to get rid of the 'unused' list during processing, but 
decided that merely invites divergent copies...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net