IETF Logo Mail Archive

Re: [core] [rfc-i] abbreviation SID

Andy Bierman <andy@yumaworks.com> Fri, 17 April 2020 18:50 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A35023A170A for <core@ietfa.amsl.com>; Fri, 17 Apr 2020 11:50:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 6ybtwsm8OvjT for <core@ietfa.amsl.com>; Fri, 17 Apr 2020 11:50:04 -0700 (PDT)
Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (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 1C3B53A1706 for <core@ietf.org>; Fri, 17 Apr 2020 11:50:03 -0700 (PDT)
Received: by mail-yb1-xb29.google.com with SMTP id i16so1550333ybq.9 for <core@ietf.org>; Fri, 17 Apr 2020 11:50:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HMqCMLXRcrfP0gW7R67uDcMcskNhOewcgXKOBqyu2Dc=; b=X9DLKdv6s3DUkGqcqJAvm1FdsLNcibs2rAxBdZUntCcgeego0B25MTE9nSGabIxyhy EyblQOqOCVmUOs1ZexJx3YtHzhnNze76isaGkgxujzQzGa7xD3/Gl3IybDbKob65RD9s yU4YU9W5QPvClOzKSctOFgQrGdfXddBwJTebQ++5w1U0o0DyvWOk7w/csiFlrsw6Jq7v bU034cOMsSGcqHIJ5prRE0I60Dd41urB72HkNQS2ZnwUwZOLfkLp/U3GyeK/wq0ujkjY 6ffhE4XccscVYZXQUvQ0l4xegACqkOqD7dAhaPpy5aN6BcbeZyQTM5tWp97uX6Sd3aJD R/ug==
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; bh=HMqCMLXRcrfP0gW7R67uDcMcskNhOewcgXKOBqyu2Dc=; b=QJD7gkYWqUL3bbly2rgfdwwF5xKIefgIctX8WopNSkIicPwk3dEzPQN0So+xUYE9Jg kJOb5JGOugRbWvjjc2FZw3axXl9jS6wYx7HWggnpDgoT8E9ShTUvY+n9gwHIRv98cMR8 rVdyM/32XvRJDOYnToYL8UEvtKvA3skZNoeJ8x31JA2rhGOkfdaKupiJCENpVq3Ddg1m 1LNN1iZ7MCWiodGL4xxSuCZetv9Zm+RPmmuQ0yeyQzuCvvwRvvcd3weGGwRoChUJwR7N UsM9TCdrktzmc6VXt0PJKDuaENo8YFfRpPy0kRRK3YYJdIj5z+Jok31unNbhcBD7IWPI Qf/A==
X-Gm-Message-State: AGi0PuZaLKu3rQOdJq/P33fSo/Gt9bNJrDS+smNBMzQWQ0o7y1kTTP6E KG0s83Qf684Z199EHwhk8GZvS+vzbPRImZp5vTnV5g==
X-Google-Smtp-Source: APiQypJ1m1ffY0LGg9HlIfINdhk3tuJACUJA0FkrqAfBBIloEur86WBI/1NCZOfXXSf8hppJyIgIsNaMZuU71hp3q2M=
X-Received: by 2002:a25:602:: with SMTP id 2mr323675ybg.359.1587149402458; Fri, 17 Apr 2020 11:50:02 -0700 (PDT)
MIME-Version: 1.0
References: <1UW7eW8VIi.1FNLrngyUqY@pc8xp> <11891.1587078130@localhost> <CABCOCHTu8NVmsENrzrVck+vFF1voeUrgJ7SG798z0Ve0OAwX1g@mail.gmail.com> <1UW7fdFd8A.12CdBil9GXf@pc8xp>
In-Reply-To: <1UW7fdFd8A.12CdBil9GXf@pc8xp>
From: Andy Bierman <andy@yumaworks.com>
Date: Fri, 17 Apr 2020 11:49:51 -0700
Message-ID: <CABCOCHSjk-f8dh14L-xfeRqY-o8OB+R1qscLOEvsfVxLFvVaaw@mail.gmail.com>
To: tom petch <daedulus@btconnect.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Core <core@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Content-Type: multipart/alternative; boundary="00000000000056ee5d05a38104cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/OHkeVWB-q1Hd-52JGvWg9EfG3J0>
Subject: Re: [core] [rfc-i] abbreviation SID
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2020 18:50:07 -0000

On Fri, Apr 17, 2020 at 4:43 AM tom petch <daedulus@btconnect.com> wrote:

> ----- Original Message -----
> From: Andy Bierman andy@yumaworks.com
> Sent: 17/04/2020 00:25:42
>
> Hi,
>
>
> I do not think three can be much expectation of uniqueness for an acronym
> like SID.
> Also doubt its use in YANG could be confused with Segment Routing. But...
> How about a full name "YANG SID" and OK to use a short name "SID" when the
> context is clear.
>
> <tp>
> Andy,
> The RFC Editor recently expanded POP, in a routing context, to Post Office
> Protocol (which is one of the three options listed) so my view of the scope
> for confusion may be greater than yours!  SID is currently listed as having
> six possibilities, none of which is Schema ID, so I think this needs
> expanding to seven, sooner rather than later (
>


In some of our code SID means Session ID.
I guess it is too generic.
I like YSID (short for YANG Schema Identifier) as a replacement.


Andy


>
> ---
> New Outlook Express and Windows Live Mail replacement - get it here:
> https://www.oeclassic.com/
>
> even if Segment routing has its tanks on the lawn),
> Tom Petch
>
>
> Andy
>
>
> On Thu, Apr 16, 2020 at 4:02 PM Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
>
>
> tom petch <daedulus@btconnect.com> wrote:
>     > SID already has many meanings of which Segment Routing Identifier is
>     > probably the most widely used.
>
> okay, but this is also a new meaning to our industry with SR.
>
>     > SID is now going to mean Schema IDentifier in the context of YANG and
>     > OAM in general as defined by draft-core-sid which will doubtless be
> on
>     > its way to the RFC Editor before too long.
>
> CORE/YANG/CBOR could change the abreviation used.
> It's in WGLC now, or maybe it's just passed.
>
> * SchemaID.
> * SchemaKey, or SK or SCK
> * CSID, CSI, CSiD
> * YSID, YSI
> * YangID, YID
>
>
> tom petch <daedulus@btconnect.com> wrote:
>     > I believe that an update is needed to the list of well known
> abbreviations,
>
>     > SID already has many meanings of which Segment Routing Identifier is
> probably the most widely used.
>
>     > SID is now going to mean Schema IDentifier in the context of YANG
> and OAM in general as defined by draft-core-sid which will doubtless be on
> its way to the RFC Editor before too long.
>
>     > So I think that the different possibilities for SID need updating
> sooner rather than later.
>
>     > Doubtless this will be a source of confusion for years to come but
> it might be possible to diminish that a little.
>
>     > ---
>     > New Outlook Express and Windows Live Mail replacement - get it here:
>     > https://www.oeclassic.com/
>
>
>     > Tom Petch
>     > _______________________________________________
>     > rfc-interest mailing list
>     > rfc-interest@rfc-editor.org
>     > https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>

v2.23.0 | Report a Bug | By Email