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 17:00 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 787103A0D47 for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 10:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 AgJenmmg9YAq for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 10:00:13 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 048D93A0D46 for <rfced-future@iab.org>; Tue, 22 Jun 2021 10:00:12 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 15MH09k0014501; Tue, 22 Jun 2021 18:00:09 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4DD3F4604F; Tue, 22 Jun 2021 18:00:09 +0100 (BST)
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 417CC4604E; Tue, 22 Jun 2021 18:00:09 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS; Tue, 22 Jun 2021 18:00:09 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.47.18]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 15MH08SN028370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 Jun 2021 18:00:08 +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>
In-Reply-To: <7ef10df2-cb21-a95b-b977-286b6d8a8405@lear.ch>
Date: Tue, 22 Jun 2021 18:00:06 +0100
Organization: Old Dog Consulting
Message-ID: <0a8101d76788$0e1af5a0$2a50e0e0$@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+yN4aSHniqmSlCBw
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.001
X-TM-AS-Result: No--5.046-10.0-31-10
X-imss-scan-details: No--5.046-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2034-8.6.1017-26236.001
X-TMASE-Result: 10--5.045700-10.000000
X-TMASE-MatchedRID: +f/wAVSGjui8rRvefcjeTb7u5vMMMVTtaMmm586o4gB/Z0SyQdcmEFEt MRGFGDWDb+7vqosU/TC7BxlnBatlVDdo3G+ad8Nf0XO+Yq6CqgIpA2ExuipmWiVuRe2PaRI7cfI ublHY1q0/yISm21cxkVv9ie1ACao8xBdQH2+4tBDwpAypldoLOb/I3arxTrviHzKz4AvJrgUhgV U1JTxZmMZG/XwAlayy3IsW8GtAmI+mWOD8X0TFhJr5ykm9NtIcIVpGz/U+S0ipjZQdHTnCmwKFZ 0L1cycYF2GG9DuV3YJGUJPwsrOuV9aSgJLPelTm+LORUvwlJdvjAcZeNJgY96Hr6eS9NQNKsOzO ncrmCoP3FLeZXNZS4JFOlJCK/1ftHwyRKA7hsdbGndwBzVZAKg6El4TvzUcw0+6OvTPS69kRRKY xqJyoQue/iaShuHdzftwZ3X11IV0=
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/ApOsr5xnDfcVNaplOsG3LHLDm6Q>
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 17:00:18 -0000

I don't have a problem with this idea, but I also think it is massively missing the point.

The RFC Series is not owned by the IAB. Formerly it was owned by the RSE and it will become owned by the RSWG&RSAB.

Thus, decisions about creating new streams (as many as are wanted) will be made by the RSWG&RSAB. So I don't think we need to document it, or if we do, let's do it in a more general way such as...

"The RSWG with approval of the RSAB may create additional streams as necessary."

Of course, a slightly tricky question is on which stream *this* document will get published.

Adrian

-----Original Message-----
From: Rfced-future <rfced-future-bounces@iab.org> On Behalf Of Eliot Lear
Sent: 22 June 2021 15:52
To: rfced-future@iab.org
Subject: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor

In yesterday's meeting there was general consensus that there should be 
a new stream, and that the RSE/A should manage it.  The general argument 
was that there should be no supervisory check performed by the IAB after 
the RSAB has approved a document.

Please send any concerns by 6 July.

Eliot

v2.23.0 | Report a Bug | By Email