Re: RANT: posting IDs more often -- more is better -- why are we so shy?

Joe Touch <touch@isi.edu> Thu, 02 March 2017 16:02 UTC

Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29B031294DA for <ietf@ietfa.amsl.com>; Thu, 2 Mar 2017 08:02:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 y_7N5G8y373c for <ietf@ietfa.amsl.com>; Thu, 2 Mar 2017 08:02:57 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D06F129505 for <ietf@ietf.org>; Thu, 2 Mar 2017 08:02:57 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v22G2FaL017407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 2 Mar 2017 08:02:17 -0800 (PST)
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <14476.1488384266@obiwan.sandelman.ca> <13e5803d-c2f3-7bc8-63c8-2a8311c22fae@isi.edu> <17514.1488420343@obiwan.sandelman.ca>
From: Joe Touch <touch@isi.edu>
Message-ID: <489dfee3-66d9-03be-2614-4ba0483d0b82@isi.edu>
Date: Thu, 02 Mar 2017 08:02:15 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <17514.1488420343@obiwan.sandelman.ca>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9sjmRs0y6izfXA8-OZRREzdj-ew>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Mar 2017 16:02:58 -0000

Hi, Michael,

On 3/1/2017 6:05 PM, Michael Richardson wrote:
> Joe Touch <touch@isi.edu> wrote:
>     > FWIW, industry often doesn't let out ideas until filing preliminary
>     > patents, which has a similar effect.
>
>     > AFAICT, the speed of an -00 is more tightly correlated to the
>     > motivation for the document.
>
> Good point, but tell me why -01 and -09 and -17 don't come out faster?
> If it's because the authors are busy, and aren't working on that document,
> that's fine.  But I'm seeing some kind of shyness to putting new versions out.

I'm not sure it's easy to determine except on a case-by-case basis.

Other reasons: the community wasn't ready for the doc yet, other docs
took priority (for the author or WG), there might be lots of email list
activity to resolve an issue, etc.

> Is there a distrust of documents which have "too many" revisions?
I'm not sure I'd call it "distrust". But it is hard to keep up with a
constant stream of revisions, esp. for very large docs.

> Should the beautiful history bar in the datatracker, have some measure of
> changes?  Would graph of lines changed (in the XML!) per revision be
> interesting?   Would that help know how close a document is to being ready?
Not necessarily. First, moving sections around can give a false sense of
a major change. And a doc that is only wordsmithed could either be close
to being ready or be an indication of apathy.

There's no substitute for actually tracking what's going on with a
document, and no replacement for a person investing time to figure that out.

Joe