Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 25 June 2021 17:19 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA1CA3A0C52 for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 10:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.338, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 himTwVQj-4pi for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 10:19:51 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CAD43A0C40 for <rfced-future@iab.org>; Fri, 25 Jun 2021 10:19:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4GBNzV6mWSz6GKM1; Fri, 25 Jun 2021 10:19:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1624641590; bh=oAkN9Ibl3zY+M13MX73V6D3Pkd9Qxk9VX4PtwolxhrM=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=pEPxLJS+KMzUFiZNH40KxrWBdS3vaptQkxJY+JPkDjDIGgKmKAE5uG1pa6kLBXQvl hjWvDfFdb4ArOChAyBDYnTr/Ex/UgUCAQzHfj/QZpYEn6lV4QoDnfnlBuInXTkKS5H 94TpMwJXRtohy7PR0bNdKR30Jf7P7KbZwJTuEYtI=
X-Quarantine-ID: <b-MOMreBD82G>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.23.64] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4GBNzV2mfCz6G98X; Fri, 25 Jun 2021 10:19:50 -0700 (PDT)
To: Christian Huitema <huitema@huitema.net>
Cc: rfced-future@iab.org
References: <3f4c264e-4639-4d6b-cf22-0a2be503decc@joelhalpern.com> <3D3EC062-7B1A-43C4-99D5-A204A4565ECE@ietf.org> <cf2921d8-fd1f-d9c9-da72-ff760eda347c@lear.ch> <3b4b6d91-64e3-d0d7-bcbc-284f29a46fb7@joelhalpern.com> <9fdeb823-9470-00a8-b1b1-91630b996c8c@gmail.com> <351774DB-C6DC-439F-9B5C-FB427EC9F6FE@ietf.org> <ac1aea74-da8e-405d-2a73-fbc6fc97ce24@gmail.com> <D1D7247E-6F03-475A-88F4-50E45A8B6F0E@eggert.org> <ec86e68e-961a-2c1a-fb9a-0ba8be20c524@huitema.net>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <476493c2-e434-0451-beaf-29a59be15aa3@joelhalpern.com>
Date: Fri, 25 Jun 2021 13:19:48 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <ec86e68e-961a-2c1a-fb9a-0ba8be20c524@huitema.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/cY3cZ0yTRzdKd4SytVZ8W1banMw>
Subject: Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2021 17:19:56 -0000

If the IAB retains the right to rewrite or refuse the documents from 
this process, then I do not see what we have accomplished with this 
entire circus ???

Yours,
Joel

On 6/25/2021 1:16 PM, Christian Huitema wrote:
> 
> On 6/24/2021 1:46 AM, Lars Eggert wrote:
>> Hi,
>>
>> On 2021-6-24, at 7:57, Brian E Carpenter <brian.e.carpenter@gmail.com> 
>> wrote:
>>> As somebody else said, this stream by its very nature is going to be 
>>> special and even self-referential. The notion we have of a stream 
>>> being a client of the RFC Series just doesn't apply, so the normal 
>>> notion of a stream manager doesn't apply**. But surely we need 
>>> someone to act as progress chaser and nit resolver when a document 
>>> has left the RSAB and is inside the RPC? And who will that be if it's 
>>> not the RSEA?
>> I still remain unconvinced that we even need a new stream. I may be in 
>> the rough, but I would be OK with using the IAB stream and leaving the 
>> IAB a role here.
> 
> +1. That seems a much simpler solution than creating yet another rarely 
> used structure.
> 
> -- Christian Huitema
>