Re: [DNSOP] A quick update on draft-ietf-dnsop-attrleaf / draft-ietf-dnsop-attrleaf-fix

Dave Crocker <dhc@dcrocker.net> Fri, 19 October 2018 15:52 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 09639130F5F for <dnsop@ietfa.amsl.com>; Fri, 19 Oct 2018 08:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, 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 H9X9gk3SG6HV for <dnsop@ietfa.amsl.com>; Fri, 19 Oct 2018 08:52:18 -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 97414130EF6 for <dnsop@ietf.org>; Fri, 19 Oct 2018 08:52:18 -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 w9JFqhCc027781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 19 Oct 2018 08:52:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1539964363; bh=DLfYQu0uhuHzVhVjBwbY6wStSpRo1NlYlyY84TqW3y0=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=df7A9Y1rTQnAcWLuY9aNJ9zAtRf4B4LB8h/rQhelONiwvSeME+NogfNQu17oJzx1Q PLzvDEyfXIXQjAxmBv+ITaMHOcWrf9hZI9QVNa9giWBDwKGCFR+qJ52exFD0RpotaL RcyBUrubx7vxCflHqV+YVoBfO0nKFFb0SIcG+9Ms=
To: Alissa Cooper <alissa@cooperw.in>
Cc: dnsop <dnsop@ietf.org>
References: <CAHw9_i+Hi_y2W+5sSLuZvtM0nLHVR=y5R--3D-UB2_W3TYJ8JA@mail.gmail.com> <27c9d56e-abd6-1ab1-029d-514036151517@dcrocker.net> <C43FBD7D-FA2A-4C47-8B61-B40A62FFA5F1@cooperw.in>
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: dcrocker@bbiw.net
Organization: Brandenburg InternetWorking
Message-ID: <7ceb4930-ce09-9757-eaa1-ee34fc3c3539@dcrocker.net>
Date: Fri, 19 Oct 2018 08:52:08 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <C43FBD7D-FA2A-4C47-8B61-B40A62FFA5F1@cooperw.in>
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/9yqj36ZNXlaAeleJfn-PZU2ZzcQ>
Subject: Re: [DNSOP] A quick update on draft-ietf-dnsop-attrleaf / draft-ietf-dnsop-attrleaf-fix
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 19 Oct 2018 15:52:21 -0000

On 10/19/2018 3:05 AM, Alissa Cooper wrote:
>> I'll also note that I gave this feedback to Alissa directly,
>> earlier and she did not respond to it.  That failure to engage is
>> just one more problem with this Discuss.  (And it hearkens back to
>> years ago when ADs would do this sort of thing regularly.  Not me,
>> of course, but some...)

> Could you point out which message I did not respond to? After your
> last message in the thread about my DISCUSS we had the telechat and
> from my discussion there with Warren it seemed we had agreed on a way
> forward, which seemed more appropriate for him to communicate back
> than for me to.


Alissa,

Thanks for asking.

My wording was too facile, because I was frankly trying to avoid getting 
into the detail.

More accurate wording would have that you responded once, superficially 
and inaccurately, and then failed to respond.


The exchange was:

   1) On 10/10/2018 7:52 AM, Alissa Cooper wrote:
> DISCUSS:
> I think this document needs to state explicitly which updates apply to which
> existing RFCs. That is, I would expect to see in sections 2.1,  2.2, and 2.3
> the list of which documents are updated by each section. I realize this can be
> intuited, but typically for avoidance of doubt authors specify precisely which
> updates apply to which documents. This will also clear up the unused references
> that idnits is pointing out

   2) On 10/10/2018 11:32 AM, Dave Crocker wrote:
> What is the downside of using the existing text, as compared against
> the effort (and delay -- quite possibly infinite) caused by
> requiring development of the considerable detail that you are calling
> for?
> 
> My question is not about the difference in cleanliness but about 
> serious, practical risk.


   3) On 10/10/2018 11:48 AM, Alissa Cooper wrote:
> I think the downsides are (1) people reading the documents updated by
> this document are confused about which parts of the update apply,
> and (2) it sets a precedent that one RFC can update another without 
 > being specific about what is being updated.
> 
> I’m not asking for considerable detail, I’m asking for each of 2.1,
 > 2.2, and 2.3 to specify which documents out of the list in the Updates
 > header they update.


   4) On 10/10/2018 12:16 PM, Dave Crocker wrote:
 > So by my count, that requires going over roughly 35 documents (again)
 > to audit and document this additional detail.
 >
 > My guess is that the burden on someone updating one of those
 > documents, seeing the reference to -fix, and being able to properly
 > determine whether their document revision needs to attend to the
 > section on TXT RRset usage and/or SRV RRset usage and/or URI RRset
 > usage is minimal, and the risk of their getting it wrong is zero.

and THEN you stopped responding.


Above, I say 'superficially' because the two reasons you gave are 
intuitively appealing but lack the effort needed to balance against 
cost. That is, they are easy, pro forma tags, appealing in the abstract. 
  Casually deciding to add a task that is likely to take hours -- for 
someone you aren't paying to do the work -- is problematic, absent 
serious benefit.  This task doesn't come close.

I say 'inaccurately' on several counts.

First, consider the format and content of the -fix subsections of 
concern here.  Any editor who is revising one of the cited documents and 
can't figure out which of the 3 sub-sections applies to their document 
has bigger problems.  (Alternatively if folk really believe this is a 
decision moment that has any serious likelihood of the editor's making 
an error, we need to word those subsections better.)

Second, the assertion of 'precedent' presumes a policy that doesn't 
exist, as I had noted.  Worse, I fear you haven't reviewed all prior 
RFCs that did updating, to establish that it is at least a de facto policy.

But while ad hoc assertion of a non-existent policy is serious in the 
abstract, it is a minor point compared to the reality of this particular 
draft:  I am pretty sure we have never had an RFC that updated 35+ other 
documents.  Even better is that you are not calling for these 
subsections to match the precise and complete string-editing style 
typical for updating RFCs, since that would require 35+ subsectons and 
dramatically more work.

In other words, pragmatics require that this draft already be distinct, 
so citing 'precedent' fails on the facts.

That is why your not responding further was problematic.

The latter part of your latest note (quoted at the beginning of this 
message) points to a larger issue that I'm sure no one wants to pursue, 
namely the idea that an IESG discussion away from the working group and 
the author can make absolute decisions with no further discussion or 
recourse.  No matter how excellent the AD, they aren't a principal actor 
for the work being discussed.

Late-stage review and suggestions often produce significant benefit, but 
they also often lack context and encourage a failure to balance cost 
against benefits.  And in particular when the call for change comes from 
the IESG stage, there are two problematic forces: overworked folk 
lacking the time and inclination to engage in serous discussion and 
eager folk just wanting to finally get the darn thing published.  That 
encourages appeasement rather than careful consideration.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net