IETF Logo Mail Archive

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

Christian Huitema <huitema@huitema.net> Fri, 25 June 2021 17:16 UTC

Return-Path: <huitema@huitema.net>
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 279343A0C1E for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 10:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level:
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.338, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] 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 EnFpN0bQrFKw for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 10:16:24 -0700 (PDT)
Received: from mx36-out20.antispamcloud.com (mx36-out20.antispamcloud.com [209.126.121.68]) (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 5FEA93A0C18 for <rfced-future@iab.org>; Fri, 25 Jun 2021 10:16:24 -0700 (PDT)
Received: from xse142.mail2web.com ([66.113.196.142] helo=xse.mail2web.com) by mx136.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1lwpRC-000eFR-RQ for rfced-future@iab.org; Fri, 25 Jun 2021 19:16:20 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4GBNvP4z4DzLBB for <rfced-future@iab.org>; Fri, 25 Jun 2021 10:16:17 -0700 (PDT)
Received: from [10.5.2.17] (helo=xmail07.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1lwpRB-00078Y-I6 for rfced-future@iab.org; Fri, 25 Jun 2021 10:16:17 -0700
Received: (qmail 6025 invoked from network); 25 Jun 2021 17:16:16 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.58.43.129]) (envelope-sender <huitema@huitema.net>) by xmail07.myhosting.com (qmail-ldap-1.03) with ESMTPA for <lear@lear.ch>; 25 Jun 2021 17:16:15 -0000
To: Lars Eggert <lars@eggert.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: rfced-future@iab.org, Joel Halpern Direct <jmh.direct@joelhalpern.com>, Jay Daley <jay@ietf.org>, Eliot Lear <lear@lear.ch>
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>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <ec86e68e-961a-2c1a-fb9a-0ba8be20c524@huitema.net>
Date: Fri, 25 Jun 2021 10:16:13 -0700
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: <D1D7247E-6F03-475A-88F4-50E45A8B6F0E@eggert.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Originating-IP: 66.113.196.142
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9WLQux0N3HQm8ltz8rnu+BPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5yXEnUqtuiszqcStXlDoE9S53HEEk0VSrq03gtFxbC/KnPw 1rr53sqPgnfHyWXoRWZwGYjbvhzWX8Co+5c+eruaSxIRXVMlFuiz/acFNeeXtxN2fFxZWB9eYgpR BRu3UlDHMLIJYRi1cXH9Dbm+IxLV0XgtlP1veEWDxFjeo42e2HGFd932lfz+R/06O3Iy4akhy/LP m2rFgOGYwKKX1POmkVWClPVvbW5lVyQanRxw5hTHswbbB/ha+ZWrSAi8SkwqWAikMcSxTAWn8RCv ieGEqjG/gXZAaRh1X6LVetRf2ZYIiHqfCgG4wrA3w4/kQTYKxDHA9JN9J4k4XZq11JQkMemT4rxn nByU11Ftkqf3f/PF3GUV+KdBBqrnCX8j0Gi8Ksk+aedMfNWSnJswrtlNtZo3HPHi5Q+jjsF5dcBx ehWYzrkgsp4/Fysgb2cPV4IH0+lPwKr4i5mAANUcVraZYOaeuiH/yEdZH8S1+TgcJBOjh0vPxcQO jKKOrYIQYpwamUdylUIKhf3z2GAHxH7Iiihnln5nLwsYugixy853dgjI4WE+pjPnfrWRF8b8VMfH sJwWmPl681iOth9SifSFb3UQT3xbkHqpqmyCe4PiKWIgJ2XxgK7Je5b0uU+cZFhDVPQ6fMev1BMP vQ9qu4cW0z6bhalFEM/pjPCQA+BAlgw/CRu/wrwygqWNLx1IwWi3h1ESmlc3/lS5x7qxkdlaU/Pp xAhc6nC0ugI5tOt5hN7v62g7tRPzfrFjvwTWA5ZRXxKF5tPxTxfD0dMN+t5ZGb7Hq3E5aV3VWpIu YPuVVpHzWMmvk0UHbhiG5Vg3xxiN9/YGRrhMRGhIOTxMW00yF8F1u0YDQf8cLP9taeSLFY0fPBnF 89BphpBNlUg+TzHwBTL1+6vDOMemz/4I88NDcmnEJ4r7C+SwLRamrhQTd3PrpJpP5ewAjeqkzRNl ucyd+NO2McmveAr4ch9F7rE89jihx+Za/cV70jOJzN2r4A==
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/KQtG5Hxr2Rmo6mynGEdxmcc5mpw>
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:16:26 -0000

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

v2.23.0 | Report a Bug | By Email