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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 07 March 2017 04:20 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 ED9B9129AF2 for <ietf@ietfa.amsl.com>; Mon, 6 Mar 2017 20:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.com
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 7rdEHDD4mSkk for <ietf@ietfa.amsl.com>; Mon, 6 Mar 2017 20:20:18 -0800 (PST)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 C340A129AF0 for <ietf@ietf.org>; Mon, 6 Mar 2017 20:20:18 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id o126so22041960pfb.3 for <ietf@ietf.org>; Mon, 06 Mar 2017 20:20:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=vgyCm5KO0iTEanfUzl1cz/2jLZFpJGXkQz5/+XwLxTA=; b=eHdeZHONN3PXtIaCvfCQ9t2PbxiAaHDNU9La8jcdhtcgYfHsbS+m4YL6GjNgw7k1Nz haesFBqPxIDfwbS9oRalMx6jBjBG/LN7/Dow5SwzV854ZFsFsGB1awxS2wXHVEbWR6Cb 3qu9wRyDzuzISiRSlNEOyub1nVIna5PfzmPCI5rLT3cjv2NwQdQVGLQfRrLkIcRlto9S 7ZOyzEIZrx4LDwpYX6wjMs4eXbdWXfDrKnr/K/hrigl0fDrX0ztd6kaM4srJ39jaR1w1 DPQE/iuTnyf6YRRNrNjYAlnzsiS/BDfoBJw8alHDH3qnI9kxjogNxJ2w3Geqr27uf7Ln RThQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=vgyCm5KO0iTEanfUzl1cz/2jLZFpJGXkQz5/+XwLxTA=; b=tG2um1GRZa6RkBXSaq2BjAvLSCSAY3ze0LGR1dpDrtoJRO4Zsb2RlNounFmBMa5sbC jRLNQtrkuTBM2/4bQ6NGoSpPu8NsQqJYlzKkMCMYG6JiyVNdn7KaTl72vLORcZP7DSn+ V3sCJbhQUmGRAOUw9poqwWBDkYZN+8G8Uf4Jl53A+8pRyJpAIF+MZoqknl+hnRub3KM1 sQuvjjhCT6CBJSwzx+MhUTD0+eOguzgjOFCO0UK9xofdzmsWIFUsXjJUDPYGeh12Z3zS B9LnGkuEZ3i9M6ZuMP7RYrjZDS2neoBC0pBD6N+00Ukz09l0kzvE/7x2graEOhVBdpEL 5OoQ==
X-Gm-Message-State: AMke39lhP3aVeVZo8zlqRzlrcfsFLusaZYanhhOpJhpMBB/wwM1eV8JOWbq12ZrFejwm7A==
X-Received: by 10.84.141.129 with SMTP id 1mr31619614plv.166.1488860418380; Mon, 06 Mar 2017 20:20:18 -0800 (PST)
Received: from [192.168.178.23] ([118.148.79.158]) by smtp.gmail.com with ESMTPSA id p4sm42533327pgd.50.2017.03.06.20.20.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Mar 2017 20:20:17 -0800 (PST)
Subject: Re: RANT: posting IDs more often -- more is better -- why are we so shy?
To: Eric Rescorla <ekr@rtfm.com>
References: <14476.1488384266@obiwan.sandelman.ca> <CAOdDvNo0x9mVeqc9a5yGbB6yKDnrQVgoKfq_Q8HSfpFv1BmJ=A@mail.gmail.com> <f2203a9d-595e-19cd-a7b9-2ccaa814f8f9@gmail.com> <CABcZeBPH6Y+EdbSfPMH-Rs_k5ZDwKb=13ZOGcWbi_TYJpdpsBQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <480b22e4-bf25-01fa-87fe-f91bc68940f8@gmail.com>
Date: Tue, 07 Mar 2017 17:20:15 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBPH6Y+EdbSfPMH-Rs_k5ZDwKb=13ZOGcWbi_TYJpdpsBQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EVFn0n-gCwIRySk_KrFK5DYHljM>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <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: Tue, 07 Mar 2017 04:20:20 -0000

On 07/03/2017 17:06, Eric Rescorla wrote:
> On Wed, Mar 1, 2017 at 11:24 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>>
>>> I'm not arguing against updating data tracker more often - just saying
>> this
>>> 'editor's draft' convention can work very well between official revisions
>>> no matter the cadence a WG chooses.
>>
>> The details of that discussion probably belong on ietf-and-github@ietf.org
>> ,
>> but I must point out that this way of working *excludes* from the
>> discussion WG participants who don't grok github. Substantial issues
>> need to be discussed on the mailing list and substantial (non-typo)
>> revisions need to be posted as I-Ds.
>>
> 
> Well, it's hard to know what to make of this without knowing what you
> mean by "substantial" but an active draft takes literally hundreds of PRs
> in its lifetime with perhaps half of those being non-typos. We could of
> course gateway every PR merge to an IETF draft push. Is that what you're
> looking for?

No. In fact (countering Michael's point slightly) I get quite annoyed
by draft versions that turn out only to fix few typos or grammatical errors;
those can wait. As for what constitutes "substantial", that's very subjective.
Anything that causes an on-the-wire protocol change would certainly be
substantial. Clarifying ambiguous text might be substantial. But YMMV.

> It seems to me that some of the benefit of having discrete draft revisions
> is that they represent coherent checkpoints, but you totally lose that if
> you treat each commit or merged PR as a co-equal revision.

Yes, I agree.

    Brian