IETF Logo Mail Archive

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

Eliot Lear <lear@lear.ch> Tue, 22 June 2021 18:26 UTC

Return-Path: <lear@lear.ch>
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 AE1D33A118D for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 11:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level:
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
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 yslCIv-L8QKF for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 11:26:43 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (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 E06A73A1188 for <rfced-future@iab.org>; Tue, 22 Jun 2021 11:26:41 -0700 (PDT)
Received: from Lear-Air.local ([IPv6:2a02:aa15:4101:2a80:30b7:e5f4:91df:5ed5]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 15MIQYQo433854 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 22 Jun 2021 20:26:34 +0200
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1624386394; bh=bMNsk7Oj/DyXyJoYQXJpkA3rLiE67yJfHg1MBXQ8Hwk=; h=To:References:From:Subject:Date:In-Reply-To:From; b=CR/7rOhl/lFEYBXpGpLoOEXbcAAgq2UgmY+KtWBmDHyvJV4hqezLAAwz7wL+NeOOT 4yvb/1CGa6hkl1rv0even3u6D3R5All1UbfKoctTqkQgxtqQcDAgKmw6Dk3UJFlZX0 Zs0KMskB6MO9zCOf72pJAxdhAHy3oAZP07y5Zb3o=
To: adrian@olddog.co.uk, rfced-future@iab.org
References: <7ef10df2-cb21-a95b-b977-286b6d8a8405@lear.ch> <0a8101d76788$0e1af5a0$2a50e0e0$@olddog.co.uk>
From: Eliot Lear <lear@lear.ch>
Message-ID: <fdb50b3a-a0e1-1421-4a4f-733002cfccda@lear.ch>
Date: Tue, 22 Jun 2021 20:26:31 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <0a8101d76788$0e1af5a0$2a50e0e0$@olddog.co.uk>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="qwcePI2rwmqVafMInYkObwKpcmwC7h3hB"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/wO6SELI5XVcFNlfL7qUyoleeRkA>
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 18:26:48 -0000

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