Re: [Pals] Barry Leiba's No Objection on draft-ietf-pals-ms-pw-protection-03: (with COMMENT)

Donald Eastlake <d3e3e3@gmail.com> Tue, 20 October 2015 15:06 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE4191A9081; Tue, 20 Oct 2015 08:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 BloCAoKUW3Ua; Tue, 20 Oct 2015 08:06:17 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 D0BF41B344E; Tue, 20 Oct 2015 07:59:12 -0700 (PDT)
Received: by oiev17 with SMTP id v17so11343241oie.2; Tue, 20 Oct 2015 07:59:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=biHodQnKXqo0SscL0fQVrsH2vcl/GJcGsE6An8Ljg7s=; b=BtdwQgF70StbLq4GQtUo8bNH3KPHSqWbrgX207nj2Z2LT8pkTj9WmzWAGwmqaPqsOp FrlBsO2fTuQIzuFYdKvCSMwnkQY/2DJIPz6fTLa6Skly/WA5/WCroR2sXawfwIOFaCau +2dNmJXDopz8CAnDRDgektC1bRf/5KKp7cGT1f5v7V5YjtgI36BDfe/FseKY1ry5oaH/ aQKnxCdRRQPS4HKjf9lgewIF2GA25TtWFng/X95ExAlCXPzq6Jyps0uBZTkaO/hnxRWD CEkrQFYdZhmg/+bZ/k1mRXcm+IejQ3Brrj9Hlba2KUqigx5GlM7txnd/VVMAAHquumOC IF4Q==
X-Received: by 10.202.62.139 with SMTP id l133mr2195108oia.0.1445353152242; Tue, 20 Oct 2015 07:59:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.101.209 with HTTP; Tue, 20 Oct 2015 07:58:57 -0700 (PDT)
In-Reply-To: <CALaySJJxNwa+s-rJcihA0j3azzTHyPxgouJdZy1PhT=m2ZhJiQ@mail.gmail.com>
References: <20151019182200.4130.21008.idtracker@ietfa.amsl.com> <CAA=duU2iOdCzf9Ce1dAvZvX8YKEOpXHR_Mk2dPezFs4-vwEv2g@mail.gmail.com> <CALaySJJxNwa+s-rJcihA0j3azzTHyPxgouJdZy1PhT=m2ZhJiQ@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 20 Oct 2015 10:58:57 -0400
Message-ID: <CAF4+nEEd8JPmEbJv7myHXsQbTrrLGgF1+sjUeWExuaRH3H6otQ@mail.gmail.com>
To: The IESG <iesg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/pals/ydKpI_KVU6GGfDkpLLGIlfA68V4>
Cc: Stewart Bryant <stbryant@cisco.com>, pals-chairs@ietf.org, draft-ietf-pals-ms-pw-protection.all@ietf.org, draft-ietf-pals-ms-pw-protection@ietf.org, "pals@ietf.org" <pals@ietf.org>
Subject: Re: [Pals] Barry Leiba's No Objection on draft-ietf-pals-ms-pw-protection-03: (with COMMENT)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 15:06:18 -0000

I endorse a policy of spelling out acronyms on the first occurrence in
the body text a document if there is any doubt as to whether or not
that should be done. Even if someone went to the faintly ridiculous
length of spelling out IETF and IP and TCP once, when they first
occurred in the body text of a document, what harm would it do?

It seems to me that, although the RFC Editor has a list which informs
their RFC editing, the effective rule is approximately that the
authors of a draft make an initial determination but they later have
to spell out the first occurrence of any acronym when asked to do so
by any of the WG Chair, Shepherd, Directorates, ADs, or other
reviewers. I think that works out fine.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Tue, Oct 20, 2015 at 4:05 AM, Barry Leiba <barryleiba@computer.org> wrote:
>> Thanks for your comments, and that leads to a question. All of the
>> abbreviations that you cite are included in
>> https://www.rfc-editor.org/materials/abbrev.expansion.txt
>
> Right; that's where I checked whether they were approved as not
> needing expansions.
>
>> when do you need to expand commonly used acronyms, and when not?
>
> As the above URL says:
> "Some abbreviations are so well known that expansion is probably
> unnecessary.  The RFC Editor exercises editorial judgment about whether
> a particular use of one of the "well-known" abbreviations requires
> expansion.  (For example, strict adherence to the expansion requirement
> can lead to impossibly ugly titles.)  In the following list of
> abbreviations, those that are usually (but not necessarily) treated as
> "well known" are marked with asterisks.  However, since there are so
> many different abbreviations and there is a range of knowledge among
> RFC readers, we tend to expand abbreviations in case of doubt."
>
> In my review, I only called out ones that do not have asterisks.
> "MPLS", "LDP", and some others *do* have asterisks, and don't need to
> be expanded.
>
> Barry
>
> _______________________________________________
> Pals mailing list
> Pals@ietf.org
> https://www.ietf.org/mailman/listinfo/pals