Re: [Rfcplusplus] IRTF stream considerations

Ted Hardie <ted.ietf@gmail.com> Thu, 12 July 2018 15:58 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: rfcplusplus@ietfa.amsl.com
Delivered-To: rfcplusplus@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2305130EA7 for <rfcplusplus@ietfa.amsl.com>; Thu, 12 Jul 2018 08:58:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 Or1fDUWeG1jj for <rfcplusplus@ietfa.amsl.com>; Thu, 12 Jul 2018 08:58:19 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 C98FF130DED for <Rfcplusplus@ietf.org>; Thu, 12 Jul 2018 08:58:19 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id 13-v6so56729388ois.1 for <Rfcplusplus@ietf.org>; Thu, 12 Jul 2018 08:58:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eGDQ1wzDxex2YnPbXwQq01ie6usqK3ArQsXn997ozEo=; b=qEP+owuOcw4+gbNq0Oc5K2d87tBS+IennKI5jBdz4SNk8OLOvWwhHQwp/IgZJtGDvW lNalDU8GHUs9MDlHGDzZtVv+pZ6LAe+B0t4Kts1rXH7s+2NWQhuTCLff0L+dOgGgKY2a TAeCXkbIb67kniw1mRxNMvG5ajf95Jt9aKikY5F0rC65otAeNk7A1QWDFVoCfczW/kcB Sr0sWlBmkWAKAo7earv0HyAMGdFlK9Bl2DLqKP4AM5YlosSL5pCrTvEL7TnIvVe3N5UW zCYuEe2j9ywmj1KQGAgd5Itvi2VzDo7+O05yGSO9KDJWC+iFpyc2OsoYXeB84eG7S8BI NURA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eGDQ1wzDxex2YnPbXwQq01ie6usqK3ArQsXn997ozEo=; b=IoPqnfNtLtMTkRsNTKsPCUlWSwlJiyedoJzJ8h5nzAORFu42+2oUUi9syaxa0X0iwj m5/lWsT8bvecZzJAvRAbtu5zj9XDHDODLFF5Bc3wAvLj8YLjoAily6/WyiqcGbYX9cFs bNVTkIk6Hjq3QxWIPEEhJl+K8+HptL4M0Pp2C0JXCi+6rV5ckn+8WyVdMi7CEnl+YoRn 2HJLatX9SIAkAo2pgFXisRo3AJ9fy5xZnqhci3zV0bmSzf31eoZJ+cnEhUQmiU60FN2x W445oS8KK+rS+iKeJ2FUwC3P7XO1cbYwaQUk0Rh5NfiIP1pLmf5tQW8YqA212C+FOYZA uI6A==
X-Gm-Message-State: AOUpUlGy2hPTmKvJseh4tv9DOJCEMBOHK7syFBtiCvOevsKTFj0ZOo+/ 57Mt05iY8/gOxjqpwx/lWkoiji+HtsESYtdmIEQ=
X-Google-Smtp-Source: AAOMgpdOnxqFiH7S+fgbpyyymhKdr8lXcBTg8SSiFQumXiYItfgXAZUgAci7sly8qwSouVtXIhzE0sC5BU3qGPzOiMI=
X-Received: by 2002:aca:603:: with SMTP id 3-v6mr3108460oig.103.1531411098952; Thu, 12 Jul 2018 08:58:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:66d9:0:0:0:0:0 with HTTP; Thu, 12 Jul 2018 08:57:47 -0700 (PDT)
In-Reply-To: <22b91a2a-82ff-af78-4b79-c58eb305cec6@gmail.com>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com> <b69b370c-317b-284f-85d1-1353c67a3043@gmail.com> <8f98deb9-7ed3-3303-356a-e6d3dc5a80c0@nostrum.com> <08e8650b-2f33-943e-ddcb-a6bf6c45b2ce@gmail.com> <c2c450a6-4f14-6325-8c54-6ecee4e0983f@nostrum.com> <22b91a2a-82ff-af78-4b79-c58eb305cec6@gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 12 Jul 2018 08:57:47 -0700
Message-ID: <CA+9kkMCP+66+dxcukbG4BN24heH5oVHP6fJB0tZ3xA+Gsc2-QQ@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Adam Roach <adam@nostrum.com>, Allison Mankin <allison.mankin@gmail.com>, "Rfcplusplus@ietf.org" <Rfcplusplus@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008eeb330570cf6ee1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/_qzebAd-3lR09zBgNMnB_tLmfQQ>
Subject: Re: [Rfcplusplus] IRTF stream considerations
X-BeenThere: rfcplusplus@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: For discussion of the RFC++ BoF proposal and related ideas <rfcplusplus.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfcplusplus/>
List-Post: <mailto:rfcplusplus@ietf.org>
List-Help: <mailto:rfcplusplus-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 15:58:23 -0000

Slightly off-topic, but perhaps important
On Wed, Jul 11, 2018 at 8:54 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> There's a real difference, in my opinion, in that the definition of
> the streams was a codification of existing practice, and the format
> update was something people have been requesting for many years.
> Neither of them showed any signs of being fundamentally contentious.
>

I'm not sure what you mean by "fundamentally contentious", but both
proposals had many months of discussions and, in some parts, quite serious
opposition.  Contentious would have been a word I would personally have
used to describe the format update, for example, and I'm not sure why you
would disagree.

This time, we've seen a much more radical proposal which, if carried
> forward, would fundamentally change the series. In that case you can't
> duck the question of authority and who calls consensus.
>
>
I'll note that the proposed experiment borrows many elements of the format
discussion's process.  While there is no question that the final format
documents were published by the IAB, the face-to-face discussions were all
hosted at IETF plenary meetings, for the same reason:  it's the place where
the largest number of stream contributors are together at the same place
and the same time.  It also borrows the rollback method inherent in the
format proposal (double RFC publication, first with trial format, then with
final format).  If you have other methods in mind that would produce more
transparent discussion or more opportunity to test the results as we go,
I'd personally be interested in hearing them.  But this BoF follows the
pattern we have used recently, at least to my eyes.

regards,

Ted




>    Brian
>
> _______________________________________________
> Rfcplusplus mailing list
> Rfcplusplus@ietf.org
> https://www.ietf.org/mailman/listinfo/rfcplusplus
>