Re: RFC abbreviations list

Donald Eastlake <d3e3e3@gmail.com> Mon, 27 July 2020 00:07 UTC

Return-Path: <d3e3e3@gmail.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 838F73A157A for <ietf@ietfa.amsl.com>; Sun, 26 Jul 2020 17:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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 qrpfK4Jx1esi for <ietf@ietfa.amsl.com>; Sun, 26 Jul 2020 17:07:27 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 D92B83A1536 for <ietf@ietf.org>; Sun, 26 Jul 2020 17:07:26 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id k23so15152478iom.10 for <ietf@ietf.org>; Sun, 26 Jul 2020 17:07:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=57WkAry6hONJXsSNM1MuRBk1tMnXNOKFW8e7FtYpMIM=; b=PXaG6OQpBtKRdzAsEDQKTugBRuFK7Fn5FY21wFaezlM+y8Y85adgP4yannbW4PvlnD 5AvuOhq/aVZ4JwHWnk9XLEjh8aRecyDzkDYTSyiBByhoCDIQWZC27Ey7qKzxdA+IRCJe kIVSrCioWTvUcVbFR4gOf/e8jxZYd+QxCCKdEoFCrcBuiGt2NAZzP/G6KvaawEKQtYjF Yx8z+ncy5qWGnb39zEl8gYbyQX89QEXe0hozsI6WIwF2xtzKi9Ze4/2ibLEqP81hc0M9 uP9pt0LceikJHREI6DNxC0Cf8BXXQt5NzomHnA+mehLA9n+TviUO+wxrqtWjf6kwkKCC oiBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=57WkAry6hONJXsSNM1MuRBk1tMnXNOKFW8e7FtYpMIM=; b=c/RUBeBvkiIc6Flz2XFo6g3wCPpr33AeC5TKW+2JzCnIuVrLzYBLQFiSmSsDaYeRQV yzI43iZ++xPmze3m7QUPrRB1kBgYPsTzLMm1IfDr35Kuyj4x8gO6q66wZeo0PSu5dy3I KQP7DUTM5Dj30VT1TB+hbx2/8MgmFXt9l3EPwwp9qLf2PhPrJiR+SNFxH6rkFsYS88ze zO6fgE8kzV14gt1AdxKCikcOX8SR8wiVvwqOEgviziIa+EUU0eKgNY2yWu+4mWkL/u94 khA8nwJAlyqmraxzCZoUewbddO9cgEznLNO+aCro4BUzhU3yJ6AW48XoddjyaeZwfezz wmlw==
X-Gm-Message-State: AOAM53391nP90kkGg/wrUMZzocMR27RaRenJG96l1oCvDbKmbY323ycr uyMucf7nK8/f822Moa+TaFD74nyPacfM4G8EIhoGfcpE
X-Google-Smtp-Source: ABdhPJwlktQV2WdX2LrbUR/zdhr+Dup1QGIy42oFjEVzBqze+NcVggS1KsLRwhzzEcFr29ed39Vf3kRSu6sqaSJYpfk=
X-Received: by 2002:a05:6638:771:: with SMTP id y17mr23241976jad.96.1595808445419; Sun, 26 Jul 2020 17:07:25 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <b8163085-e988-ae6a-e93f-3702f33b0dd0@joelhalpern.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 26 Jul 2020 20:07:14 -0400
Message-ID: <CAF4+nEH9VZCcoPvn6w3SsqhKG9syhDLu_+yXRBNGn16C4PfH4w@mail.gmail.com>
Subject: Re: RFC abbreviations list
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: Toerless Eckert <tte@cs.fau.de>, IETF list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pTbXv2cBbHW_4BxOBXKBn2QOsYs>
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: Mon, 27 Jul 2020 00:07:29 -0000

I agree with Joel. Standards document in all SDOs with which I am
familiar vastly overuse acronyms.

I never consult the RFC Editor abbreviations list. I just try to apply
common sense. I don't spell out things like IP, IETF, UDP, TCP, etc.
but quite frequently spell out things that turn out to be on the RFC
Editor abbreviations list. Occasionally the office of the RFC Editor
or an AD points this out to me and I just push back and say that I
think it is better to be clearer and more explicit. I have never been
forced to use an acronym in the IETF.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

On Sat, Jul 25, 2020 at 6:30 PM Joel M. Halpern <jmh@joelhalpern.com> 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
> >
>