Re: RFC abbreviations list

Toerless Eckert <tte@cs.fau.de> Sat, 25 July 2020 22:57 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 A66883A0B55 for <ietf@ietfa.amsl.com>; Sat, 25 Jul 2020 15:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 i2sq7QvRffeh for <ietf@ietfa.amsl.com>; Sat, 25 Jul 2020 15:57:36 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 756743A0B4F for <ietf@ietf.org>; Sat, 25 Jul 2020 15:57:36 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id E4384548011; Sun, 26 Jul 2020 00:57:31 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id D8C20440043; Sun, 26 Jul 2020 00:57:31 +0200 (CEST)
Date: Sun, 26 Jul 2020 00:57:31 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: IETF list <ietf@ietf.org>
Subject: Re: RFC abbreviations list
Message-ID: <20200725225731.GP43465@faui48f.informatik.uni-erlangen.de>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <b8163085-e988-ae6a-e93f-3702f33b0dd0@joelhalpern.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LtvcSB3Q-hzQ6hE3MQCnelrX74c>
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: Sat, 25 Jul 2020 22:57:39 -0000

Well, i will invite you to the next discuss where an AD wants to educate
a WG as to the appropriate use of some abbreeviation for a new expansion
by referring to the RFC abbreviation list.

I for once don't think it is difficult to get things added. Indeed, i
have simply added to my drafts an RFC-editor note stating which new
abbreviations i would like to have added, something i think that
should bhave been done for other now ubiquouts abbreviations as
well.

Just as a reminder, why this thread came into place: I think we're
not doing a well structured job on the RFC abbreviations list and
i was just pointing that out as a bad example for how to not do things
for someting like a "recommended new replacement acronyms" list
that probably would ahve to evolve from that other folks thred we're
just having here on the list.

Cheers
    Toerless

On Sat, Jul 25, 2020 at 06:30:08PM -0400, Joel M. Halpern wrote:
> The ADs do not own the RFC Editor list of abbreviations which do not need
> expansion.
> As a first approximation, as long as an abbreviation is considered new, it
> is extremely unlikely to be added by the RSE (or equivalent person). The
> point of that list is to list things that are so well known even outside the
> narrow field of use that it is reasonable to expect people to know the
> abbreviation.
> 
> Personally, I wouldn't care if that list were reduced to zero.  Out goal is
> to write clear documents.  expanding abbreviations / acornyms on first use
> is a good idea.  I do understand that we do not bother with things like IP,
> TCP, HTTP.  So having a list is useful.  But if people complain about how
> hard it is to get anything on the list, I will push to remove it entirely.
> 
> Yours,
> Joel
> 
> On 7/25/2020 6:15 PM, Toerless Eckert wrote:
> > If we can put the most important new standards into RFC abbreviation list
> > even after i tell an AD twice, then i don't think we can deal with
> > new technical terms in the organization any better.
> > 
> > On Sat, Jul 25, 2020 at 11:34:43PM +0200, Carsten Bormann wrote:
> > > On 2020-07-25, at 23:04, Toerless Eckert <tte@cs.fau.de> wrote:
> > > > 
> > > > For exmple i have to observe a real bad execution on evolving the
> > > > RFC abbreviations list, and every time i pointed to problems,
> > > > they where not fixed, and ADs did not bother to pick up the problem.
> > > 
> > > True.  One of these ???medium importance??? issues???  Hard to get attention for them.
> > > 
> > > I think we need a calendar to attend to them once a year or so.
> > > 
> > > Grüße, Carsten
> > 

-- 
---
tte@cs.fau.de