Re: [tsvwg] TSVWG: Quick drive-by note on well-known TSVWG TLAs

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Fri, 10 February 2023 16:47 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E68A1C139C24 for <tsvwg@ietfa.amsl.com>; Fri, 10 Feb 2023 08:47:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7hO6n6fPfUSv for <tsvwg@ietfa.amsl.com>; Fri, 10 Feb 2023 08:47:22 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 687D2C1595FE for <tsvwg@ietf.org>; Fri, 10 Feb 2023 08:47:21 -0800 (PST)
Received: from [192.168.1.64] (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 2528A1B001D6; Fri, 10 Feb 2023 16:47:18 +0000 (GMT)
Content-Type: multipart/alternative; boundary="------------fGMlzeytJAjFTMjGDZweLwED"
Message-ID: <ca74bb6a-e6ac-edc3-7205-a4bae9619d2d@erg.abdn.ac.uk>
Date: Fri, 10 Feb 2023 16:47:17 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
To: tsvwg@ietf.org
References: <Y+Wu+xmFsOhlRYtw@faui48e.informatik.uni-erlangen.de>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: UNIVERSITY OF ABERDEEN
In-Reply-To: <Y+Wu+xmFsOhlRYtw@faui48e.informatik.uni-erlangen.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/gkjrvXPOJVWNm7n_SSlYU06FEYM>
Subject: Re: [tsvwg] TSVWG: Quick drive-by note on well-known TSVWG TLAs
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2023 16:47:27 -0000

On 10/02/2023 02:42, Toerless Eckert wrote:
> I just wanted to leave a quick drive by note, maybe someone would like to take care of it.
>
> How can it be that an abbreviation as fundamental as DSCP is not listed
> as well-known inhttps://www.rfc-editor.org/materials/abbrev.expansion.txt  ?
>
> Of course, i am writing this complaint because i needed to check whether i had
> to expand DSCP on first use in some draft i am writing, and alas, i have to, and i think it
> sucks. Just check out on that URL what crazy historic and now irrelevant TLAs do have that
> well-known (*) gold status.
>
> So if anyone (WG chairs, Bueller) would like to talk to RFC editor about
> this,  o get core well-known TSVWG abbreviations be given that (*), i would highly appreciate.
>
> Of course, maybe there are more core TSVWG abbreviations that could be upgraded to gold status with RFC editor.
> I would recommend at least also EF and BE.
>
> (*) btw. does not mean that authors are prohibit to expand on first use, but they're free to do so.
> IMHO it primarily gives recognition to core teminology of the IETF (but thats of course my personal interpretation.
>
> Thanks a lot
>       Toerless

Thanks Toerless,


I'd suggest these are added

     DSCP - Differentiated Services Code Point

     EF - Expedited Forwarding (as in "Diffserv EF")

     CS - Class Selector (as in "Diffserv CS")

     LE - Lower Effort (as in "Diffserv LE")

Can we ask to mark this as depecated!

    TOS        - Type of Service (TOS)

---

I note that the following related items are already there:

     AF - Assured Forwarding (as in "Diffserv AF")
     BE         - best-effort (BE)
     PHB        - Per-Hop Behavior (PHB)

---

Let me know if anyone has comments, and I'll take the action to talk to RFC-Ed, we have a WG document with our
AD at the moment that is all about DSCPs :-), so now is a good time!

Gorry Fairhurst