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

"Paul Hoffman" <paul.hoffman@vpnc.org> Thu, 28 June 2018 19:02 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 EDD9E13107E for <dnsop@ietfa.amsl.com>; Thu, 28 Jun 2018 12:02:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 VnOdAH_s3nCU for <dnsop@ietfa.amsl.com>; Thu, 28 Jun 2018 12:02:26 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 6698413106D for <dnsop@ietf.org>; Thu, 28 Jun 2018 12:02:17 -0700 (PDT)
Received: from [10.32.60.119] (50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id w5SJ221q031256 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 28 Jun 2018 12:02:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141] claimed to be [10.32.60.119]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: dcrocker@bbiw.net
Cc: DNSOP WG <dnsop@ietf.org>
Date: Thu, 28 Jun 2018 12:02:07 -0700
X-Mailer: MailMate (1.11.2r5479)
Message-ID: <969A89A3-AFA5-4335-ADBE-1024CC09D6CA@vpnc.org>
In-Reply-To: <ac089db0-59c5-7083-b286-480ae99ae1eb@dcrocker.net>
References: <8bfea5a9-da8b-162f-8e81-45752821f9e1@NLnetLabs.nl> <7DA5ED9F-C2F0-4F72-9F38-909574C81C5C@vpnc.org> <ac089db0-59c5-7083-b286-480ae99ae1eb@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/petIm1KymZVqO83h_Bzh-vWAjnI>
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 19:02:44 -0000

On 28 Jun 2018, at 7:19, Dave Crocker wrote:

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

It feels like it loops into itself, where 3.1 and 3.2 sound like, but 
are different than, 2.2 and 2.3. I've stared it, and I don't see a way 
to make it better without making 2.2 and 2.3 more convoluted. It's not 
worth worrying about more unless someone else comes up with a 
simplification that is actually simpler.

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

s/audit/visual scan/  :-)

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

Fully agree.

--Paul Hoffman