IETF Logo Mail Archive

Re: [Rfced-future] Bike shedding?

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 14 January 2022 01:39 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 9DD3B3A1411 for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 17:39:45 -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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.714, SPF_HELO_NONE=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=gmail.com
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 d30iwWUi3rEu for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 17:39:41 -0800 (PST)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07D933A140E for <rfced-future@iab.org>; Thu, 13 Jan 2022 17:39:41 -0800 (PST)
Received: by mail-pj1-x1034.google.com with SMTP id l16-20020a17090a409000b001b2e9628c9cso12734135pjg.4 for <rfced-future@iab.org>; Thu, 13 Jan 2022 17:39:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=k46ibDAqk/KtFsLDK0ks/Q3UIm5IMzdk33HLSGMkfPE=; b=iq37ZJSNyFTnXRFJI7ahm8Mm+5AP4W3nHJ83835H5T3xoDGS7PvKdD8BRK6JGTc3uM Z2eP1xqCbjiVoLOZVQg+09JuhA4IXy7Gb8T3G5BGcvlnLX11QyHEarNxMAl93ZEzLej7 Ak8kqvJZdlD3W4poks9xpgWh59LEqhuQHCzGpC7Lc4Qa+jyFZiBxu3it7O4HGj5MdIMW HKMmimeew+eHv7J75A5vKX2QFHQ7JRyN7d01zRoo4FBAlLXtXPKPehyQNj1nzhALfVR3 gRx9VzoAA0jjWc9CLB93mg5oxYKOCCe55I2McGxYNGTdvw7v/n5mope5yezIC1/UfOHD vlwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=k46ibDAqk/KtFsLDK0ks/Q3UIm5IMzdk33HLSGMkfPE=; b=kNfSwLbjfFfX6bo6unSt87vnc3Ehe+w6PI40rxbWfR6eYAbp2Vjol5CiU6gxsH//cI IUWUh/mxEOycsT3SWtlbf811aLvbYnbAPqH/Ec356W1xp/p9rlsreoXWpChx7u7gLISd 1YycyE1U48Ne04mZU/tEh/vRzWL234Zn+vIGXRzgN3a7OHGt3FEG/Z13nUtOyj4bMnBm zVklBPQ07qJcVoZ5jRnNN+7NG+TQVtK1GCVvjuOnSqHWgpczn1QKaSnhxeCLXhyUY4V0 CBs3q0R8YVxjW9iaN78Qlz48XbJqF4TqFupGrXMwRZOnHxCmUKTeegRerOXj9epc6a4+ oD5w==
X-Gm-Message-State: AOAM5323duv3W6iffO9s7uCY482CLCKcpS/D31TG38B/f65T3XkBbnu6 nxCPlfATxVeGnpY2Q2nN7mF/WEuJdUNjvg==
X-Google-Smtp-Source: ABdhPJxARS0dHUh44E1Y11NtclNLanmg4u6FTScvSswt2+wNauaa2r9XDc7axs02ZytfSp9TU5b8Sw==
X-Received: by 2002:a17:90a:6b49:: with SMTP id x9mr17384769pjl.166.1642124378827; Thu, 13 Jan 2022 17:39:38 -0800 (PST)
Received: from ?IPv6:2406:e003:1071:1701:80b2:5c79:2266:e431? ([2406:e003:1071:1701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id i23sm3191377pgi.92.2022.01.13.17.39.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 13 Jan 2022 17:39:38 -0800 (PST)
To: John C Klensin <john-ietf@jck.com>, Mark Nottingham <mnot@mnot.net>
Cc: 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> <BF8B95AC-1A30-43DA-B71B-DE4E1A4F740B@mnot.net> <6BE0C6F244B127024770C350@PSB>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <389f6bef-1c06-a152-0b51-decd956961ba@gmail.com>
Date: Fri, 14 Jan 2022 14:39:33 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <6BE0C6F244B127024770C350@PSB>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/gbce4Ti0bHwi82wvoy5j_4e0QOk>
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 01:39:46 -0000

I can certainly accept "We've thought about it and we don't care"
if there's consensus for that.

(I would, however, hold one "I told you so" in credit for
later use :-)

Before anyone suggests RSPB, https://www.rspb.org.uk/

Regards
    Brian

On 14-Jan-22 14:13, John C Klensin wrote:
> 
> 
> --On Friday, January 14, 2022 11:30 +1100 Mark Nottingham
> <mnot@mnot.net> wrote:
> 
>> Well found.
>>
>> Friendly amendment: "Board for Approval of RFC Series Policy"
>> -- a.k.a. "BARSP".
> 
> <snark friendliness="probably not">
> Which, if we are already wandering around the Bike Shed, could
> also be an abbreviation indicating Silly Procedures carried out
> in the Bar, presumably accompanied by the sort of strong drink
> the procedures may require.  Anyone want to change "RPC" to
> either a four-letter abbreviation consistent with others (RSPC
> ?) or to something else entirely on the grounds that "RPC" could
> be interpreted as something having to do with Rendering Pig
> Cadavers?
> 
> Noting Peter's comment about RSWG and adding the possibility
> that it could actually stand for "RFC Series Writing Group" and
> remembering that "RFC" has not actually stood for "Request for
> Comment" for many years, may I propose we just stop, assume that
> no short abbreviation or acronym we pick will be confusion-proof
> for a sufficiently imaginative and clueless reader, and move on?
> </snark>
> 
> Sigh.
>      john
> 
>   
>>> On 14 Jan 2022, at 11:28 am, Brian E Carpenter
>>> <brian.e.carpenter@gmail.com> wrote:
>>>
>>> This may be bike shedding, 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.
>>>
>>> We know that this really means "RFC Series Policy Approval
>>> Board (RSPAB)".
>>>
>>> Regards
>>>    Brian Carpenter
>>>
>>> -- 
>>> Rfced-future mailing list
>>> Rfced-future@iab.org
>>> https://www.iab.org/mailman/listinfo/rfced-future
>>
>> --
>> Mark Nottingham   https://www.mnot.net/
> 
>

v2.23.0 | Report a Bug | By Email