Re: [Rfced-future] Bike shedding?
John C Klensin <john-ietf@jck.com> Fri, 14 January 2022 02:48 UTC
Return-Path: <john-ietf@jck.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 7881A3A1713 for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 18:48:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 7sWBVMB1Gpf7 for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 18:47:59 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 858EE3A1712 for <rfced-future@iab.org>; Thu, 13 Jan 2022 18:47:57 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1n8Cd7-00064C-Hd; Thu, 13 Jan 2022 21:47:53 -0500
Date: Thu, 13 Jan 2022 21:47:46 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Peter Saint-Andre <stpeter@stpeter.im>, rfced-future@iab.org
Message-ID: <E022A0DB8B0147F58140A99E@PSB>
In-Reply-To: <85ea06d1-428c-875a-b692-0024ac4b9e67@gmail.com>
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> <e422b5e3-4c0b-e7da-4a9d-c80230af68f9@stpeter.im> <85ea06d1-428c-875a-b692-0024ac4b9e67@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/JXbslTAMpz9hMRFuc9xq8JaSN5w>
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 02:48:04 -0000
(slightly less snarky) --On Friday, January 14, 2022 14:11 +1300 Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > On 14-Jan-22 13:38, Peter Saint-Andre wrote: >> 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? > > I debated that with myself and decided that it really wouldn't > matter - it's the word "Board" that tends to suggest authority. But maybe the "B" stands for "Body" or even "Bakery". Or, more likely, the "A" is interpreted, not as "Approval" but as "Advisory". If we had used "RFCAB", then it would be rational to assume that it was a group advising on or approving RFCs. But we picked "RS" to convey the idea that this was about the Series (not individual documents) and "Approval Board" would then refer to approving things about the Series and not individual documents, which, I think, is exactly what we wanted. FWIW, I also note the IETF's history of choosing atrocious and, in some cases, so cute as to be deliberately misleading, abbreviations and acronyms for WGs. We have also had real world problems with the Internet Advertising Board and the Intergalactic Astronomy Bureau probably lies in our near-time future.. Anyone with any experience reading our documents has learned to be careful about understanding our acronyms. FWIW, the RFC Editor has had longstanding policies about this sort of thing. Sorry, but I suspect we have better and more productive ways to spend our time. But, because it just came in as I was writing... --On Friday, January 14, 2022 14:39 +1300 Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > 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/ But, as sort of suggested above, we've had RSVP (see either www.rsvp.com or www.rsvp.org). If one picked a random sample of people with more than a modicum of training in computer scientist and ask them what LISP was, how many of them do you think would guess an IETF WG rather than, for example, something that would lead them to an obit for John McCarthy (www.lisp.org)? Or how about rum? Nope, Captain Morgan has been there. And those don't even get to trying to treat the terms as acronyms or abbreviations. If you want to go down that path, try asap.org. Going to the birds suddenly feels more attractive. john
- [Rfced-future] Fwd: New Version Notification for … Peter Saint-Andre
- Re: [Rfced-future] Fwd: New Version Notification … Brian E Carpenter
- Re: [Rfced-future] Fwd: New Version Notification … Eric Rescorla
- Re: [Rfced-future] Fwd: New Version Notification … Peter Saint-Andre
- Re: [Rfced-future] Fwd: New Version Notification … Brian E Carpenter
- Re: [Rfced-future] Fwd: New Version Notification … Eric Rescorla
- Re: [Rfced-future] Fwd: New Version Notification … Joel M. Halpern
- [Rfced-future] CONSENSUS CHECK: Issues 134, 143, … Eliot Lear
- Re: [Rfced-future] New Version Notification for d… Mark Nottingham
- Re: [Rfced-future] New Version Notification for d… Eliot Lear
- Re: [Rfced-future] New Version Notification for d… Mark Nottingham
- Re: [Rfced-future] New Version Notification for d… Stephen Farrell
- Re: [Rfced-future] New Version Notification for d… Peter Saint-Andre
- Re: [Rfced-future] New Version Notification for d… Mark Nottingham
- Re: [Rfced-future] New Version Notification for d… Martin J. Dürst
- Re: [Rfced-future] New Version Notification for d… Peter Saint-Andre
- Re: [Rfced-future] New Version Notification for d… Eliot Lear
- Re: [Rfced-future] New Version Notification for d… Peter Saint-Andre
- Re: [Rfced-future] New Version Notification for d… Mark Nottingham
- Re: [Rfced-future] New Version Notification for d… Peter Saint-Andre
- Re: [Rfced-future] New Version Notification for d… Mark Nottingham
- Re: [Rfced-future] New Version Notification for d… Peter Saint-Andre
- [Rfced-future] Bike shedding? Brian E Carpenter
- Re: [Rfced-future] Bike shedding? Mark Nottingham
- Re: [Rfced-future] Bike shedding? Peter Saint-Andre
- Re: [Rfced-future] Bike shedding? Brian E Carpenter
- Re: [Rfced-future] Bike shedding? John C Klensin
- Re: [Rfced-future] Bike shedding? Brian E Carpenter
- Re: [Rfced-future] Bike shedding? John C Klensin
- Re: [Rfced-future] Bike shedding? Eliot Lear