IETF Logo Mail Archive

Re: [Rfced-future] Bike shedding?

Peter Saint-Andre <stpeter@stpeter.im> Fri, 14 January 2022 00:38 UTC

Return-Path: <stpeter@stpeter.im>
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 B72483A113B for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 16:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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.714, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=QLCJKXtq; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=KhR1mveb
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 tXhF7YjXn4lO for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 16:38:10 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 182763A113C for <rfced-future@iab.org>; Thu, 13 Jan 2022 16:38:10 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 465695C00ED; Thu, 13 Jan 2022 19:38:09 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 13 Jan 2022 19:38:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= message-id:date:mime-version:subject:to:references:from :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=f HWBZY/rKXoBMzEwzXwXHpK0BT5kDGkkS+vxt8AO9DE=; b=QLCJKXtqW+ugmWbI3 KGRDgkJMSXMAyoqHuk0FNw1SfYF1UdlMv4FPul2LY21LDzrvTzoy6izDdGoUvjMq HMfswWhXX60oSXequ2Vfjm8bYqsn4jKZ8asL+fhPBT/+GCWRevZyck791ZI/AG4u CJA5r/o2UIQHID+9AdmKCmxiBbznoGNlTWRtr0EN9sMRyhq5ZPSH65BUV3ztbk62 r2LPgNJCSykfx3CSjGyZ1eqc+eCuKKCS/DzX+aEmUMKP2IGVjfKW3hkg3X/ESe3L QCWeZXeF2jBQuaFOwnTnEAHYWrkF9XDrOuMbtzb6dvqFJ4Bmbf5UPeKkJR9+UicV Z5WgQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=fHWBZY/rKXoBMzEwzXwXHpK0BT5kDGkkS+vxt8AO9 DE=; b=KhR1mvebQDrPZZzWoSgtgpLdnd4x1fsPe7sWVyv7VjbHadaxGA0fyoqPb azBvjPdQcs5500dvjQtV85Cq5e4XnR4QNUXxEToaKRRiujQthIk803DRHvZww/K4 oLBudBKs1+QB1F3EBGZ3TDiYuAD52TcyZovx51Q/Gcb5+orh9cQW1fYzlai1462J 8pafinUijWbV8+hbuDnKU1HZ1m119sj6Pj2eLQR8oxZ1qnTFde8oNYEahJ+a5Kha lu6dzOcyOfPE7m9rNW4aiHbrEBk/l1R3E7bYdiVDuXn/uW+gT7rU5jTAvpOJoTIR J09g3JnukEoHS5GGepUQDNtLJiXvA==
X-ME-Sender: <xms:8cXgYXBWuAijmg5z9G_2ff2hRyT0NCLrehp3o7539NtkUsfwbV5jeQ> <xme:8cXgYdiJW2t-Y7eJxWOY5V5Jail84kGxr4xM78RqkMZAwhseE37HoB9Y7ERgi86VZ 6yhGpmEgfmrveI7kg>
X-ME-Received: <xmr:8cXgYSkZUk6PRkNPXSM8BeNpd80e8R8vQ3ProlybXMY1iNVHo9TK-Bb743MJrji64r5CflvDmh7b6vW3Szn0t8gGU0vLZsyvni8VLTI>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrtdeggddvgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqeenuc ggtffrrghtthgvrhhnpeehtefhvdejvdfhgeetgefhfeeuudefkeetvdfhkeelleeuheef leekkeekieffudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:8cXgYZz4PiCA6N2Cn4PC8X1W0SRWkSj8ioqoFZIH5TLiMYIqO_jngQ> <xmx:8cXgYcTGPwJwxAzrGLUZNrWUTWAHcZ6Gtb95GZl98hfCRrGnW0zlLw> <xmx:8cXgYcZVUvcxxcDQtdihXobd-5m1a0KxE90Hyh0-sOTwcbu8rVsZXw> <xmx:8cXgYXL7aTKn32fdd6vrP4tkA8IJ76MvWCh12utI_mX0Te6esNvb7A>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 13 Jan 2022 19:38:08 -0500 (EST)
Message-ID: <e422b5e3-4c0b-e7da-4a9d-c80230af68f9@stpeter.im>
Date: Thu, 13 Jan 2022 17:38:04 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, rfced-future@iab.org
References: <164159953944.5205.10517887235280838552@ietfa.amsl.com> <1e6664f9-f19d-a226-e709-d03fe6968497@stpeter.im> <116833C8-6D7C-43B3-A91A-E63FCCE7C448@mnot.net> <14bde881-ae07-a3a6-b458-39ed69c05c36@stpeter.im> <e9a8e7ae-c11c-4ab3-d6f5-5ab2b2bcde09@lear.ch> <5dc3d1ec-9fc5-d708-89cd-6e1b659b73ae@gmail.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <5dc3d1ec-9fc5-d708-89cd-6e1b659b73ae@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/wskmjgPJGbpLxuqHis6QiVU3Mlk>
Subject: Re: [Rfced-future] Bike shedding?
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: Fri, 14 Jan 2022 00:38:15 -0000

On 1/13/22 5:28 PM, Brian E Carpenter wrote:
> This may be bike shedding, 

It gladdens me that we've reached the bikeshedding phase.

> but I had a horrible thought last night. 
> Sorry to arrive with this at such a late stage.
> 
> "RFC Series Approval Board (RSAB)"
> 
> Suppose an outsider sees this out of context? They might imagine that 
> the RSAB is there to approve RFCs.

Might they also imagine that the RSWG is the place where all RFCs are 
developed?

> We know that this really means "RFC Series Policy Approval Board (RSPAB)".

It doesn't exactly roll off the tongue, but I don't particularly care 
about that as long as we've defined roles and responsibilities properly.

Peter

v2.23.0 | Report a Bug | By Email