Re: RFC abbreviations list

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 26 July 2020 04:55 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D06933A0AE7 for <ietf@ietfa.amsl.com>; Sat, 25 Jul 2020 21:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 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.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 yAE56v7Up4Bt for <ietf@ietfa.amsl.com>; Sat, 25 Jul 2020 21:55:13 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 5F13F3A0AE2 for <ietf@ietf.org>; Sat, 25 Jul 2020 21:55:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4BDrGT1K7Cz1ntfD; Sat, 25 Jul 2020 21:55:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1595739313; bh=QUSQr/oKCWJti82HplcePLTj9WsULLOxDQMY7K3faaI=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Ba7w8+CG8dlbk5Dv1DqyyJu1slTGa2kqUpfqzlRltWgn/X/PzkJO5HuuVUb7Eu7M0 wfYgSff3pBx/hEvrC3KBRDEmYl9VB+nx6h5FK+rYgZgGniMVfefgJyBzsGVis6A9AQ Libr2lSAUw2L8yiPGoW+ot36sAkFCqRddAfP5owQ=
X-Quarantine-ID: <t8qoVcIc0P-2>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4BDrGS4dwZz1ntcR; Sat, 25 Jul 2020 21:55:12 -0700 (PDT)
Subject: Re: RFC abbreviations list
To: Carsten Bormann <cabo@tzi.org>
Cc: IETF list <ietf@ietf.org>
References: <35BE966B-63A2-438F-BD61-570E86ED2E1A@strayalpha.com> <297BF899-553D-44DB-AB56-04280F776F7A@employees.org> <6646575A-E6EA-4B4E-AC1B-F8B84B5A1203@strayalpha.com> <20200724225654.GB43465@faui48f.informatik.uni-erlangen.de> <8F6D2B44-1914-4B3B-9458-3F2BF2CFCA05@tzi.org> <20200725210457.GJ43465@faui48f.informatik.uni-erlangen.de> <9A6BE775-78B9-41C5-A3EE-A34C7D092CA0@tzi.org> <20200725221507.GL43465@faui48f.informatik.uni-erlangen.de> <b8163085-e988-ae6a-e93f-3702f33b0dd0@joelhalpern.com> <20200725225731.GP43465@faui48f.informatik.uni-erlangen.de> <CEA49C2751557DF4896FE6B2@PSB> <DD1FEBD3-4488-419E-A3E7-DC95FABB7F65@tzi.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <e6d6a42c-e085-e8a1-7c3e-5f7614e3d442@joelhalpern.com>
Date: Sun, 26 Jul 2020 00:55:11 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <DD1FEBD3-4488-419E-A3E7-DC95FABB7F65@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CtiHD_KB51sXdq_wINHKslGiWcY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jul 2020 04:55:15 -0000

It may be that we are discussing two different things.
I am not concerned with what abbreviations appear in the "these are 
abbreviations commonly used in the IETF" list.  I am concernwed with the 
subset of that list marked with a *, meaning that they usually do not 
require expansion.   Of the three examples you cite, two are marked with 
a *, the third (RSASSA-PSS) is not so marked.

If the question is how things get into the list at all, that is one 
question, and not something we have to be particularly limited about.
My reading of other notes was that the question was things marked with a 
"*".

Yours,
Joel

On 7/26/2020 12:26 AM, Carsten Bormann wrote:
> On 2020-07-26, at 04:32, John C Klensin <john-ietf@jck.com> wrote:
>>
>> that
>> the abbreviation be well-known and immediately obvious to anyone
>> with a significant Internet technical or operational background
>> and experience.
> 
> Hmm, I think the intersection between people knowing what RSVP-TE is, what JSON is, and what RSASSA-PSS is may be smaller than you think.  That bar is a bit high.  I would expect this to be limited to the target group for the specific RFC (which by the way in some cases isn’t “anyone with a significant Internet technical or operational background and experience”).
> 
> Grüße, Carsten
>