Re: [Rfcplusplus] IRTF stream considerations

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 July 2018 03:54 UTC

Return-Path: <brian.e.carpenter@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 7B9A5130EB7 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 20:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_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 69WyKOrQEk_E for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 20:54:21 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 D0D5A130DE8 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 20:54:21 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id k3-v6so3490959pgq.5 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 20:54:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=9LA5Zlgg6ujvL9rX6MUazMOSUAM0+8jqml0Vnq73oH0=; b=eiXpVE5Yp1QKNRmVSo5NFUw3nJVM9Yw7dEBWvot3c6P/4CvwCVWYnvnmrqYKBHQyfI VY+KhZdONi2VGX0jvi9YaPI2JO0972iuvnzi7qW4aWvNUz0Munw2WOt6R69Kg3Z7lmtg ZgTiCySHVP8PEdyabczi0q2Db3ynv9VFrEHBuBb8PN3sOSVVgLoP9C/rC+akTw9PGjKX forDJqGyiNRwT8ICUOKi5QrTHgepcIcj2xsXhSdmX1LOtjS75iWSwrd2/bRTlrdkudRm qaSqlsVp+G2feepW2Xnt4rqXCZZ4bfneCs58caaWqViS+vrLTV64ltBfSozPpX+fx4oH wR8w==
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:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9LA5Zlgg6ujvL9rX6MUazMOSUAM0+8jqml0Vnq73oH0=; b=OYEuQ9Y2CLr/LZL5TIE3UWMwOAGEDHZfN80mxiu3V2rACoCeXnF+0EO0i09S44Uw+N /yKgNT4NJC036avTgS3O0CXkoYdcVU8QjjaaB+QTX/5g/0CKUl1GAGqw54llrOdOHYrD yxTpvi13etuaI/U1OReA9gMh56D8c+ZCcmWWU9geqvyv0U8Hak52q+R+PMuBoV6UI2Yt jQI6CzRT+h9waOwUl5mBSlOiZZdIaYzhVjb9iHim7d6wjG7tTaYgJvZ1Nylvq5Tz5uj+ uq8MxA0dt44ahxNWjT3r0F32mRFkb3xsQs2ulqhzZMmXsuhzENe3S6qhWF5e6IsxikOU 2UCw==
X-Gm-Message-State: AOUpUlFu3dTUcRSFtWCpNQ5gIv5sqSbGQXLSXrseYKXZIjgbV4Juf2XX QemBhbkUR/ZWh/64HNEttPJmwA==
X-Google-Smtp-Source: AAOMgpfUE6AKDaYozp4LOHmjnTg48J5RCYEMpD3/my8DJU+nGChUCLK43xDsqfotOQmLq/SzbK7WqQ==
X-Received: by 2002:a65:6109:: with SMTP id z9-v6mr540109pgu.243.1531367661146; Wed, 11 Jul 2018 20:54:21 -0700 (PDT)
Received: from [192.168.178.40] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id r188-v6sm39256942pgr.78.2018.07.11.20.54.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 20:54:20 -0700 (PDT)
To: Adam Roach <adam@nostrum.com>, Allison Mankin <allison.mankin@gmail.com>, "Rfcplusplus@ietf.org" <Rfcplusplus@ietf.org>
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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <22b91a2a-82ff-af78-4b79-c58eb305cec6@gmail.com>
Date: Thu, 12 Jul 2018 15:54:24 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <c2c450a6-4f14-6325-8c54-6ecee4e0983f@nostrum.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/8BDNZ3u_D5I7YkR61NSs5ibbRQM>
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 03:54:25 -0000

On 12/07/2018 15:37, Adam Roach wrote:
> On 7/11/18 8:33 PM, Brian E Carpenter wrote:
>> On 12/07/2018 12:46, Adam Roach wrote:
>>> On 7/11/18 6:49 PM, Brian E Carpenter wrote:
>>>> Well, that's good to hear, but nevertheless it is an IETF BOF and that
>>>> limits its direct input to IESG decision making (certainly not its
>>>> range of topics).
>>>
>>> This assertion (which you've raised before) doesn't seem to serve what I
>>> suspect your goals are very well.
>>>
>>> Based on this statement and similar statements you've made elsewhere, it
>>> looks like you're trying to assert that there is no existing venue in
>>> which the topic of multi-stream RFC governance can be discussed with the
>>> community,
>> I'm saying that there's no clearly defined and announced venue for that,
>> except possibly rfc-interest@rfc-editor.org.
> 
> The BOF was announced on that list 
> (https://www.rfc-editor.org/pipermail/rfc-interest/2018-June/010237.html), 
> and the IETF itself is a non-member organization, so any such interested 
> parties are free to participate. You seem to be implying that some set 
> of interested parties is being excluded from the conversation in some 
> way, but I'm not sure evidence supports that position.
> 
> ...
>> It can happen if planned that way. IMHO it has happened, for example,
>> for the new RFC format...
> 
> The RFC format work was an IETF BOF too [1] (three, actually), and those 
> specific BOFs resulted in input that went well beyond impacts on the 
> IETF stream. I believe your original statement about the scope of 
> discussions that can take place in such a venue is more refuted than 
> supported by the precedent you cite.

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.
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.

   Brian