Re: [Rfcplusplus] IRTF stream considerations

Adam Roach <adam@nostrum.com> Thu, 12 July 2018 03:37 UTC

Return-Path: <adam@nostrum.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 C97CB130EB2 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 20:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 ZydVdGx8Wqqv for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 20:37:26 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 AAEE6130EB1 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 20:37:26 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w6C3bN0q049178 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 11 Jul 2018 22:37:24 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Brian E Carpenter <brian.e.carpenter@gmail.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>
From: Adam Roach <adam@nostrum.com>
Message-ID: <c2c450a6-4f14-6325-8c54-6ecee4e0983f@nostrum.com>
Date: Wed, 11 Jul 2018 22:37:18 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <08e8650b-2f33-943e-ddcb-a6bf6c45b2ce@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/FdlFVak-zTNsCzBNRj7rXkI4fZ8>
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:37:29 -0000

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.

/a

____
[1] https://trac.tools.ietf.org/bof/trac/wiki/BofIETF83