Re: [Rfcplusplus] IRTF stream considerations

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 July 2018 01:33 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 00051130DE3 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 18:33:03 -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 9ZaVXQ9VPDhW for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 18:33:02 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::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 2EB06130DD4 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 18:33:00 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id j3-v6so19527636pfh.11 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 18:33:00 -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=9Pgt19YtiWfrr+9c+6dtZjf9KVP1tL9wC6E7+AloVhM=; b=YxlVNPKzarMrFShHKiFHHW7YDdvRrNXa9AasatwSfzProLdqKVhV/9JtkthUQ010IJ pzX4Ai681YtFtup4GWwsw9DH1WLSnhFVE4uY8Ll5zS5841LWz2T3oo9+qLgC90ltcxTI /3BvkttlqJMIQjeA8YWoafm/gxl40AC/Ab+HcL2X5QFFQ2CkWeVa7mQ4rEDqR2feEXfF WCMLkZ1R/v28XjyxndZn80KNsbtzKsbAs/ZYF0YeCpxBnz2wbVHosjkhttZIb+IitB/A w4VeVcNX+MexREHbwlzZY1fx8Cphxt292tklX+oNCY5pB2R9d7tfRmuUP8wIQefKe7FK EUuQ==
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=9Pgt19YtiWfrr+9c+6dtZjf9KVP1tL9wC6E7+AloVhM=; b=sdaG/tFa3zZj9dYYtELXViKZhSe4Q0e+8pFkGwxIeQi8nEF9SNSPrErW1N9TqXLCuQ 7L1PZMcplcbpErwy3JIeAIDVwKbpo2rBBC3SqKzcmchONwzVFl06aZ4ILbtwdw3rcJol ByLd33O/DMmq46De97xW1I7Mi/nSQeBeXQ2CoUtaMBNp6GNdpL2mKPHX8Ivmu3dJJpwH u+9TodyC3FRQsv4R+Qvi8tHtnBMFmE3om2fdgaThcXiLEznrjfZj6Vqia5cE3jIzURjB qY84ll/WJ6jn6dpBM7Vok00j6L9JeHBFu7P1DYsq68o7CnZWZ4wSCRrl+zMVkMqN+2Rb +VBA==
X-Gm-Message-State: AOUpUlFIeXeBLi011/875roWMHOtFbRbuZA2Yp061K0SpXuDSgRVfDOu C1vZP8VdpMyKxXPcz38EK+mBXA==
X-Google-Smtp-Source: AAOMgpc3+9gIyEzb87c+0jbpsEldGfZ2dCMWpZGEA/Tyw4Lw51a8UT1SfxiL/7j4HDZOETn3eWgdzw==
X-Received: by 2002:a63:2043:: with SMTP id r3-v6mr211257pgm.105.1531359179375; Wed, 11 Jul 2018 18:32:59 -0700 (PDT)
Received: from [192.168.178.38] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id q28-v6sm41879142pfg.144.2018.07.11.18.32.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 18:32:58 -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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <08e8650b-2f33-943e-ddcb-a6bf6c45b2ce@gmail.com>
Date: Thu, 12 Jul 2018 13:33:02 +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: <8f98deb9-7ed3-3303-356a-e6d3dc5a80c0@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/1JcEG8RWXRy08A-RhXKNKAtc5y0>
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 01:33:05 -0000

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. So if there are proposals
that affect multiple streams or the series as a whole, there is some
work to be done to ensure that all interested parties are involved.
I'm not saying that's impossible, but it's more than convening an IETF
BOF.

> and so the conversation simply cannot happen. 

It can happen if planned that way. IMHO it has happened, for example,
for the new RFC format, and clearly all the RFC streams were involved
in formally setting up the streams some years ago.

> Given that the 
> alternative would appear to be for the IAB to act without community 
> input (or perhaps with the limited input provided by an IAB workshop), 
> I'm not sure why you're pressing this point so hard. Not only would that 
> kind of action set what I think would be bad precedent, but it would 
> probably not have the outcome you desire.

It wouldn't, because if a number of people felt that the IAB had exceeded
its authority, the outcome would indeed be painful for everybody.

> Or perhaps I've misunderstood: do you think that there is a venue in 
> which multi-stream RFC governance topics can be discussed with the 
> various stakeholders, and that this simply isn't it?

That, yes. (Also, I don't understand why the RFC Series Oversight
Committee isn't heavily involved in this discussion.)

   Brian