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

Michael StJohns <msj@nthpermutation.com> Fri, 25 June 2021 17:37 UTC

Return-Path: <msj@nthpermutation.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 C87CF3A0D01 for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 10:37:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.236
X-Spam-Level:
X-Spam-Status: No, score=-2.236 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.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 oW4lQ1mK8s79 for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 10:37:06 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 A8F1D3A0D00 for <rfced-future@iab.org>; Fri, 25 Jun 2021 10:37:06 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id o6so19981743qkh.4 for <rfced-future@iab.org>; Fri, 25 Jun 2021 10:37:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=X33P/0pFrFB/Fntj1vLSVbvFBMG0PfYZvnCThYqbnKA=; b=BFMlRml50MEnV13mw0yrO3WVShkPRVt2lyvPn2T+jdfBvA+4P+pSPdvyf5NqRk2srZ acN19N534T7cMJBmBhNgeCpfOPobwMU/nS7b3x5UrRS+0yA+Pbant9gBka9PLGXBczpq MtPSnJUrGsbj8BwVsjLtP/NKCGCMRZgVsfW1nsGewm/nXatPidzvaZmjICAAe92HHR7m pEc3ahuT42/MR0A1hEALzZ3P1OThAC7p0KbOZzILAKUYu/s2AS7kFEMJFMGL6eovsQU6 WGDUtbNNOZmQTuMUGwMRVLx48xAeE5URGs/4sXlA5REl5YcsDFGkFwo9EWEcTrormwIY xbaQ==
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-transfer-encoding :content-language; bh=X33P/0pFrFB/Fntj1vLSVbvFBMG0PfYZvnCThYqbnKA=; b=OF21NBxVPlX3OH7+ahyiDjbBNPE3xEFkjrwJ45qdAOSzwwza333XlCLFAp3kicTrqm Z0kRIPC8HptUO+Z/nAnFrmT7kE5U7n/yPolBylM8K8r7SifAIeYNsOjW037GuVcUc6vp G47QhWAR9QFepKeYiil//e5VywivzSvDzr54tD9/xFAjdRC+X1SHakzvEj9pw6o+K1q8 CXAtB+Sk9NZPnOhVDcFP1eem6kBgEB/eAWT5lS8c3Ja5VB2LD2JqOWg0SZmXbY3kSPH1 FB+xRHCxI564Gy5agyLvPbUj8zBHJd/B9DfPLLJkfTeYtl5WN/CG1cZyznfWSs3X5fgq b5gA==
X-Gm-Message-State: AOAM533qc101lg8HHKUaNbRYXYywPhE3Bic0NqDVc9IIfyRyVMO2IRld d6xKr2Gekk023GwxIZqkZUPQU2U2CPF8zTkImaw=
X-Google-Smtp-Source: ABdhPJyYoGBsDPdAp585ifD9bBj7xjk8BtUwcXM3CEadSkneaVYP4jqNqhfoBWAcFkEOBE17Di70Vg==
X-Received: by 2002:a37:bb82:: with SMTP id l124mr12487363qkf.119.1624642624934; Fri, 25 Jun 2021 10:37:04 -0700 (PDT)
Received: from [192.168.1.23] (pool-108-51-200-187.washdc.fios.verizon.net. [108.51.200.187]) by smtp.gmail.com with ESMTPSA id p14sm5267729qkh.128.2021.06.25.10.37.03 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Jun 2021 10:37:03 -0700 (PDT)
To: 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> <476493c2-e434-0451-beaf-29a59be15aa3@joelhalpern.com>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <cc246a9d-09b6-732b-a5dd-b36628fb5976@nthpermutation.com>
Date: Fri, 25 Jun 2021 13:37:01 -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: <476493c2-e434-0451-beaf-29a59be15aa3@joelhalpern.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/rfced-future/kJBzhV_zQumdcx-J3w_ZzoqhIRs>
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:37:11 -0000

On 6/25/2021 1:19 PM, Joel M. Halpern wrote:
> 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 ???

And to continue that thought, the IAB may change what it does with the 
IAB stream at any time for any reason. Effectively a veto.

-1 - do not run publications of this type through the IAB process.


Mike


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