IETF Logo Mail Archive

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

Adrian Farrel <adrian@olddog.co.uk> Wed, 23 June 2021 09:57 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 269B33A31C1 for <rfced-future@ietfa.amsl.com>; Wed, 23 Jun 2021 02:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 rTMsSL-Yhv3G for <rfced-future@ietfa.amsl.com>; Wed, 23 Jun 2021 02:57:20 -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 176403A31C0 for <rfced-future@iab.org>; Wed, 23 Jun 2021 02:57:19 -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 15N9vGYh022432 for <rfced-future@iab.org>; Wed, 23 Jun 2021 10:57:16 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4AA3C4604A for <rfced-future@iab.org>; Wed, 23 Jun 2021 10:57:16 +0100 (BST)
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3F0B24604B for <rfced-future@iab.org>; Wed, 23 Jun 2021 10:57:16 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs3.iomartmail.com (Postfix) with ESMTPS for <rfced-future@iab.org>; Wed, 23 Jun 2021 10:57:16 +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 15N9vFqY012077 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <rfced-future@iab.org>; Wed, 23 Jun 2021 10:57:15 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
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>
In-Reply-To: <cf2921d8-fd1f-d9c9-da72-ff760eda347c@lear.ch>
Date: Wed, 23 Jun 2021 10:57:14 +0100
Organization: Old Dog Consulting
Message-ID: <0b9a01d76816$25690dd0$703b2970$@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: AQFeB7wLGpfp4ou+LlCxukcXuovX/QFGv76aAvm9xwSr8hZ8oA==
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.006
X-TM-AS-Result: No--6.554-10.0-31-10
X-imss-scan-details: No--6.554-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2034-8.6.1017-26236.006
X-TMASE-Result: 10--6.554100-10.000000
X-TMASE-MatchedRID: scwq2vQP8OG8rRvefcjeTb7u5vMMMVTtaMmm586o4gBVjXcpQOPL2wSD CUdk18WiZWI/41dR8d9LTxZI1do3QY5S/4bo68Nb8irf7wNB3SgCC8zqHvcG2tRGf5c57+FFbYd a9H3QEXWrKaCIB8U9PexBC7yoarHzT5gVH5B/9XD5TWyhseEO1AEoHzC4m9uQvfScyRtKaR2sSI 0mH7EmmZAuc7XR18tKt+GvuYPoobwYB2fOueQzj91asM/801mntHIYYgLGbjZQSFbL1bvQAXnN0 DN7HnFmoBKX3XDeG+RZTROX7bSsh8jSWwFzbDVTgeprWlf1rRJ1iui33Anvi5RMZUCEHkRt
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/jweDRVUNyZUO6Smva-uuT9n8Kzs>
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: Wed, 23 Jun 2021 09:57:22 -0000

Oh, by the way, if we create a new stream, how shall we handle "interference" with other streams?

Today we have 5742 to allow the IESG to provide guidance on how IRTF and IS stream documents might adversely interfere with IETF work.
However, there is no such filter on the IAB stream (possibly because the IAB can go for community feedback, possibly because there is a liaison between IAB and IESG, and possibly because of history).

Suppose a new stream published something that impeded in some way IETF work? I'm sure it is not our intent to open up a channel for end runs or subversion.

A

v2.23.0 | Report a Bug | By Email