Re: [Iotops] Use of abbreviations

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 02 November 2020 19:45 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 997533A1014 for <iotops@ietfa.amsl.com>; Mon, 2 Nov 2020 11:45:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level:
X-Spam-Status: No, score=-2.345 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_FROM=0.001, NICE_REPLY_A=-0.247, 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 A5wQxM7ABwTs for <iotops@ietfa.amsl.com>; Mon, 2 Nov 2020 11:45:38 -0800 (PST)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 16AB73A0FB3 for <Iotops@ietf.org>; Mon, 2 Nov 2020 11:45:19 -0800 (PST)
Received: by mail-pg1-x530.google.com with SMTP id o3so11663845pgr.11 for <Iotops@ietf.org>; Mon, 02 Nov 2020 11:45:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=6+W/aWBJauEcTm/aER8zJLF4F//xWQynibpw+qUI7ME=; b=PEv2oh1LJtQqPST2ebUprq+VZw8MNEeu6/VpX33jO+A+4f0iwhXwTVG+1HkY8iupDq EtFzi3YVOb6vuzaNjmzMia53AAMfJPGX3zxOWEhDJ4WzGiJO4on0rZBzN+/LW6IZDKOF gz19J5Mc0ixImhahS/R1vM9SP9MxIw7/b3UzYGebAtn672dDDUJggaACiHpBYq/vSU9y FeZbx9EqqMU1hSDNvFI+DPEjI1CfOaFGJflQaQqi1UNqNIKqN0XV+viy0JQ8fKyIU7A4 yRhxs9cAjkCc18r3H6u77g7IojCdGr/4qYVV7eLtpo+fzy938ZX8VmWBbW1ZM9+7KzbB 0Png==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6+W/aWBJauEcTm/aER8zJLF4F//xWQynibpw+qUI7ME=; b=m9ISU7kV2LLu+R2kSn5v/45JGmtZoXfLhejEQB9S+Gq/uGkkqEtqfgi68Z7WRbNUSf EeH/RXMmnwDZ07Sitnmp4ek4M+dp9Z8whg2rU06A+offM1jn7z41lum7NqO8zAIkSOcm kPD0/WN7prl7ZA7xeD6I0+Ub5BuqK1oJ8xo4SWxXNvhuq6LuESS9tjuMECcu7xPZC77u djJCVvBTzg+RreDntR3vVbGjrnSwjSbJeo+V2YAj7wxqUHStEOv2sExW56DSBDrHD/2D dYqYJNq1C2KIHFBJhLbbyV41DI5g5RRZKezgCVvv7zJW4Pix/u9J6olCxRBRsLCS/CSR Jw+g==
X-Gm-Message-State: AOAM533IFs1pBzTm3PqQ+lLmsKB14Vyb+Jhq+eB6mwQdq0evgz5nE5wV 9B+QcKjsLyIhNzSg6zihyWF4wiHpcRsGgA==
X-Google-Smtp-Source: ABdhPJzwOnBGs68OhYR1C7nK6I+fs3ld7+F5KznX92jhT/PbQhmrqOWxi7ZYCBecwv/WYwuVeokOmA==
X-Received: by 2002:a17:90a:c48:: with SMTP id u8mr19050415pje.121.1604346318111; Mon, 02 Nov 2020 11:45:18 -0800 (PST)
Received: from [192.168.178.20] ([151.210.130.0]) by smtp.gmail.com with ESMTPSA id b17sm13277624pgb.94.2020.11.02.11.45.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Nov 2020 11:45:17 -0800 (PST)
To: William_J_G Overington <wjgo_10009@btinternet.com>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, Iotops@ietf.org
References: <6e7fc2c3.ccb.1757e4c3e9e.Webtop.227@btinternet.com> <4838.1604246428@localhost> <20201101165125.GQ48111@faui48f.informatik.uni-erlangen.de> <51ef63e2.18a.17587fb6b8f.Webtop.229@btinternet.com> <4eeec81c-67e8-dd7b-19dc-0a84722d32ce@sit.fraunhofer.de> <6236ffbd.676.17588f7729d.Webtop.217@btinternet.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <f5760e80-c9ac-411d-cb69-bb4d8e55607f@gmail.com>
Date: Tue, 03 Nov 2020 08:45:14 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <6236ffbd.676.17588f7729d.Webtop.217@btinternet.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/ks9jI7AySUy9WIvhpXT_Tv_EfQc>
Subject: Re: [Iotops] Use of abbreviations
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2020 19:45:40 -0000

FYI, the RFC Editor maintains a list of abbreviations. A few of them are marked as "well known" and can be used in RFCs (and by implication in drafts) without expansion. Otherwise, the policy is that abbreviations should be expanded when first used or in a Terminology section.

The list is at https://www.rfc-editor.org/materials/abbrev.expansion.txt

TA and OTP are both listed, but without an asterisk, so they should be expanded in drafts. However, it's a big ask for people to expand them in emails, IMHO.

Regards
   Brian Carpenter

On 03-Nov-20 01:38, William_J_G Overington wrote:
> Hello Henk
> 
> 
> Thank you.
> 
> 
> Best regards,
> 
> 
> William
> 
> 
> 
> 
> 
>     ------ Original Message ------
>     From: "Henk Birkholz" <henk.birkholz@sit.fraunhofer.de>
>     To: "William_J_G Overington" <wjgo_10009=40btinternet.com@dmarc.ietf.org>; Iotops@ietf.org
>     Sent: Monday, 2020 Nov 2 At 10:45
>     Subject: Re: [Iotops] Use of abbreviations
> 
>     Hello William,
> 
> 
> 
>     thank you for chiming in and speaking out. Sometimes conversations migrate to a place - hitting the road running - and that can make it more difficult to join such conversations.
> 
> 
> 
>     TA typically refers to a Trust Anchor in this context. That word is given a well-scoped meaning in RFC4949.
> 
> 
> 
> 
> 
>     Viele Grüße,
> 
> 
> 
>     Henk
> 
> 
> 
>     On 02.11.20 09:03, William_J_G Overington wrote:
> 
>     			Could it be the custom and practice of this mailing list that upon first use of an abbreviation in a post that the meaning is stated in full please?
> 
> 
> 
>     Recently I had to look up OTP, I think I found the correct meaning but I am not congruently sure.
> 
> 
> 
>     I am still trying to find out what TA means.
> 
> 
> 
>     When, in another venue, I included mention of a
> 
> 
> 
>     PDF (Portable Document Format) document
> 
> 
> 
>     I was informed that readers would know what PDF meant.
> 
> 
> 
>     So it is a balance. My training was to always explain an acronym the first time one uses it, because some readers might not know the meaning of the acronym.
> 
> 
> 
>     So, I am retired, at home, just trying to take an interest and participate, I am not "at" an organization and I am "not representing an organization", but hopefully that is fine with the people who are "at" or are "representing an organization".
> 
> 
> 
>     William Overington
> 
> 
> 
>     Monday 2 November 2020
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>     -- 
> 
>     Iotops mailing list
> 
>     Iotops@ietf.org
> 
>     https://www.ietf.org/mailman/listinfo/iotops
> 
>