IETF Logo Mail Archive

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

Eliot Lear <lear@lear.ch> Tue, 22 June 2021 14:51 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 4AF8E3A27BC for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 07:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level:
X-Spam-Status: No, score=-2.09 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, 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 XGt_opfOGKWI for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 07:51:53 -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 CA42B3A27BA for <rfced-future@iab.org>; Tue, 22 Jun 2021 07:51:52 -0700 (PDT)
Received: from [IPv6:2001:420:c0c0:1011::4] ([IPv6:2001:420:c0c0:1011:0:0:0:4]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 15MEpo3c431625 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for <rfced-future@iab.org>; Tue, 22 Jun 2021 16:51:50 +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=1624373510; bh=nR2LfNb+644OXXtyRb1sSp9koC7XBDmSrV7xTv1SeTY=; h=To:From:Subject:Date:From; b=b3qeKglQDWDRWil3bdFkWmRI92yHyeo16s4laQlR+p9a+nlHWd4kYScYzyvI5wok+ aZ3bvhyduJrZ5HjuQ56dt/MBBN1uaY+Qq5Dm+KntBn1nROuXRtjIpjdITN69xxfJDP ZWYrUMtrFS0VhQi4S+U50QKlUf2G3dFmVKA5UKE0=
To: rfced-future@iab.org
From: Eliot Lear <lear@lear.ch>
Message-ID: <7ef10df2-cb21-a95b-b977-286b6d8a8405@lear.ch>
Date: Tue, 22 Jun 2021 16:51:49 +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
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="EPx0mLHYbOLVVmcSP31A86W4oDYuey91n"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/RKe72ohSFAsuICou-NxFYX5U5Q4>
Subject: [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 14:51:57 -0000

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