IETF Logo Mail Archive

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

Adrian Farrel <adrian@olddog.co.uk> Tue, 22 June 2021 20:29 UTC

Return-Path: <adrian@olddog.co.uk>
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 BA5743A16E2 for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 13:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 RJj3tsxpYbCz for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 13:29:01 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (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 BA21C3A16E4 for <rfced-future@iab.org>; Tue, 22 Jun 2021 13:28:59 -0700 (PDT)
Received: from vs4.iomartmail.com (vs4.iomartmail.com [10.12.10.122]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 15MKSuGr006113; Tue, 22 Jun 2021 21:28:56 +0100
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id ADEA14604A; Tue, 22 Jun 2021 21:28:56 +0100 (BST)
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A26CA46043; Tue, 22 Jun 2021 21:28:56 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs4.iomartmail.com (Postfix) with ESMTPS; Tue, 22 Jun 2021 21:28:56 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.47.18]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 15MKSts9009622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 Jun 2021 21:28:56 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Eliot Lear' <lear@lear.ch>, rfced-future@iab.org
References: <7ef10df2-cb21-a95b-b977-286b6d8a8405@lear.ch> <0a8101d76788$0e1af5a0$2a50e0e0$@olddog.co.uk> <fdb50b3a-a0e1-1421-4a4f-733002cfccda@lear.ch>
In-Reply-To: <fdb50b3a-a0e1-1421-4a4f-733002cfccda@lear.ch>
Date: Tue, 22 Jun 2021 21:28:53 +0100
Organization: Old Dog Consulting
Message-ID: <0ace01d767a5$39001350$ab0039f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQKeL0b/5i17ua5CtPab+yN4aSHnigK0KP5NAbezZw2pb4sBYA==
X-Originating-IP: 84.93.47.18
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2034-8.6.0.1017-26236.002
X-TM-AS-Result: No--2.135-10.0-31-10
X-imss-scan-details: No--2.135-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2034-8.6.1017-26236.002
X-TMASE-Result: 10--2.135100-10.000000
X-TMASE-MatchedRID: u7Yf2n7Ca/28rRvefcjeTb7u5vMMMVTtaMmm586o4gAZSz1vvG+0mneT 8UBawk/XyLw02+lay9yDcZNsbMgFcA8LKInWUps81a9nQumsfmopA2ExuipmWlAoBBK61BhcKMY zpi5TbqWaaBYwlL5lPpfucML7iAp6Eb0RuLqy8KGVUcz8XpiS9ARryDXHx6oXCDaSBZ23epqXid r9etFZ1v8nv9x3PStamKxXZqqGOgmwiGsT9HMfJhfqkKQlk1I5eFyzQYzPQ+Rhi+qQVejLGdG6R Yo2Y1dvRMR9kQkhA0GtqCg3ldkM2cfEYAf1qh/lngIgpj8eDcBTqzaeVVOfNfoLR4+zsDTt9xS3 mVzWUuB9IxzED4RL2TC2bm+IpRTvMvN/rHLA7NGQePyNBfl/1FcsN5Gz+oW7CjSsDX+d+Mb971q +mnxqjOyXtG142WwJIV6rstSLX5JTgxoB7fAIRk3+9BzFCkVzNAW83zYDw/v1OlCIPxKfizngMR AgrdeEPYigHtZ0QM5+3BndfXUhXQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/WCEY9oJpgLx2S7CXVhcjswOztBo>
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: Tue, 22 Jun 2021 20:29:06 -0000

I think a stream exists because an organisation has requested to publish within the RFC Series. 
The owner of the Series surely decides whether to allow publication and whether a new stream is appropriate.

I'm also interested in how a stream is shut down. Who makes that decision?

Cheers,
Adrian

-----Original Message-----
From: Eliot Lear <lear@lear.ch> 
Sent: 22 June 2021 19:27
To: adrian@olddog.co.uk; rfced-future@iab.org
Subject: Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor

Hi Adrian,

On 22.06.21 19:00, Adrian Farrel wrote:
> "The RSWG with approval of the RSAB may create additional streams as necessary."

I think this is actually an open question.  What is the process for 
creating a new stream?  Which body does that?  A stream usually itself 
represents an organization.  The RSAB wouldn't create orgs, tho perhaps 
they might recognize an org.

Now Issue 73.

Eliot

v2.23.0 | Report a Bug | By Email