Re: [stir] Setting Direction for the STIR WG Last Call

Dave Crocker <dcrocker@bbiw.net> Fri, 19 August 2016 23:25 UTC

Return-Path: <dcrocker@bbiw.net>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7014B12D096 for <stir@ietfa.amsl.com>; Fri, 19 Aug 2016 16:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.198
X-Spam-Level:
X-Spam-Status: No, score=-1.198 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_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L5=0.001, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bbiw.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 nnjCCGZm710Y for <stir@ietfa.amsl.com>; Fri, 19 Aug 2016 16:25:57 -0700 (PDT)
Received: from simon.songbird.com (unknown [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 3447B12B016 for <stir@ietf.org>; Fri, 19 Aug 2016 16:25: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 u7JNQ4c2012205 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 19 Aug 2016 16:26:04 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1471649165; bh=lkh9XjuRjChA4wlKkAzkw0B/lrh/QTApD9MFdTulAL8=; h=Subject:To:References:From:Cc:Date:In-Reply-To:From; b=FdObRmEdUCofY4dA+FGdQRMtMoZcwpPt9xr2JOUd3f1ImXlMn+1hcBZ8IJVfYxXrp FkbCcA9TdZC91hQqJAmpbrn3Y7zSmsvkFbD4oCpnVBcdypBKLG0xPjBJR7kzAcVR7Q 6gJ8T1cMRBS+ZaVBefQ3Q2x5yNO7U/2fJ7rKnOmc=
To: Russ Housley <housley@vigilsec.com>
References: <07e0eb16-6758-cdf1-c571-1f1ed768e741@dcrocker.net> <D9E1B04E-EE62-44AD-B98E-05A264FD044C@vigilsec.com>
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
Message-ID: <366a7ee0-cce7-4bed-951c-05415676dd91@bbiw.net>
Date: Fri, 19 Aug 2016 16:25:42 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <D9E1B04E-EE62-44AD-B98E-05A264FD044C@vigilsec.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/HqdV1br7MW7sSlsURO7DSBvazg8>
Cc: IETF STIR Mail List <stir@ietf.org>
Subject: Re: [stir] Setting Direction for the STIR WG Last Call
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 23:25:58 -0000

Russ, et al,

On 8/17/2016 1:52 PM, Russ Housley wrote:
> However, WG Last Call is not the time to revisit each decision that
> brought the WG to this point.

That depends on the nature of the concerns being raised, and it always 
has.  The distinction that has always been made is between engineering 
aesthetics versus basic flaws.

We don't get to reopen an issue if it's really just a matter of 
preference -- I think semicolons are /so/ much better than forward 
slashes, we really do have to change the syntax.  Wrong.

But if someone happens to assess a serious technical flaw -- of the type 
that includes language like "it won't work" -- it doesn't (and 
shouldn't) matter when they notice it.

How the question of the flaw is resolved might matter, but that's a 
separate and later issue.


> If you are the author of a review that raises a large technical
> problem, I ask you to provide a concise description of the problem in
> a message of its own.  I am trying to separate the discussion of any
> such problems from the resolution of other document comments.

Speaking of basic flaws, there's a big one with that request.  I've put 
in an enormous amount of effort formulating comments carefully.

Twice.

You are now requiring me to do even more, for that work to /maybe/ get 
consideration.

That serves as an additional barrier to participation for me.  Even 
without the considerable pattern of abuses, that kind of barrier is 
artificial and exclusionary, in spite of how reasonable it seems.

And there is nothing preventing that extra effort to be done instead by 
the folk tasked with editing the documents. Or anyone else who is 
participating.

I've offered quite a bit of summary text, along with the detailed text. 
So anyone actually wishing to engage in serious discussion can easily 
initiate an email thread for it.

I'm going to post one or two, nonetheless, to test the waters.  But so 
far there appears to be little (no?) significant engagement from the 
general working group to consider the basic issues I've raised.

I'll respond to substantive comments -- and already have been -- but 
absent a change in participant engagement I won't be investing even more 
speculative energy on this.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net