IETF Logo Mail Archive

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

tom petch <daedulus@btconnect.com> Fri, 17 April 2020 11:43 UTC

Return-Path: <daedulus@btconnect.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 5CB7C3A09EE for <core@ietfa.amsl.com>; Fri, 17 Apr 2020 04:43:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 uehV5ft-gjHc for <core@ietfa.amsl.com>; Fri, 17 Apr 2020 04:43:23 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130117.outbound.protection.outlook.com [40.107.13.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B03D03A09EA for <core@ietf.org>; Fri, 17 Apr 2020 04:43:22 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GRKacp1vrhQn2gAErZ9OczzXz5txzyd2vdQm+f5YFvvWjh7AXbTclGjP+nq907g9CHQPHxHiWTCMaj7a+Q1D4nIU5fU4xnf5gGo/p+jH2+9kJR++OmitWadBspBmV3wV3MdTCyqhGCQNWv8ruAM2B7XXhlDH+9myO4MgW2t+qMoG31wsbNEh6dD/BAaQz4UvHEWdP0KO2GWdSl3SnMV1VqUYH750stdD39WS0Zo6AuW9x205QKnzUJ5XB+hWz1qQDYmNZTEnY143MPMFW87kr8v7pEXZJlhgyqEEsudsBa4q+yHdY5G4LPZpNFauqh73bFBiB0izBPbtfkwyVuPSOA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SE/lmaw3RA4lgS5oiIRGjz3SCi97Csa9CyAvK37Ytbo=; b=QfvPitoJ9qMf1JhLFasU5nDvetw/Le+B4PH63L6W8cnm3ExvqXStX4F29pZkLX/JGp0XrJkPRxlmPhHNroDX5BPbEZY5DLg3/dNOwxBKzU+SzMUDxWZ6dD+TJKMLdYRUyzxl3RJ5TCKHI6vf3uQlPgqu4d65DlIg+S3rHLiElb32WCIgNS03GwKsTIUck3y7FJjQPQ1dckmpbLID2X8vaQSdMXfPuCNvMo/5qHT5oi1r1kSAbLWlFyBHnATGjh+wviSlgCJWKOiGWY6I2ut5A0HxsL2Y4hOyfhcPVGBXFj+wuPplHrjqQgmeQjVTrFg1dkqiq8NMPvhMAnqVMhnh7w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SE/lmaw3RA4lgS5oiIRGjz3SCi97Csa9CyAvK37Ytbo=; b=VaUi0F1pkn/Ok+WiUPjrqaMcOuajQeoGpqkGThBJx85/Z5+7mN1ly3GPAeqLw491OE0xbLfVLLPpR6oTVLUw9A3PvIeHMpAaNLlGoKcp/A84P6sVBf165rohw0pAizEGedbFboSwX1GlqIjQfXaO+RI9zhxPdLTRilh0lrXE4Dg=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com;
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16) by VI1PR0701MB2143.eurprd07.prod.outlook.com (2603:10a6:800:28::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.20; Fri, 17 Apr 2020 11:43:19 +0000
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::783c:2224:fe2c:848b]) by VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::783c:2224:fe2c:848b%11]) with mapi id 15.20.2921.027; Fri, 17 Apr 2020 11:43:19 +0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
References: <1UW7eW8VIi.1FNLrngyUqY@pc8xp> <11891.1587078130@localhost> <CABCOCHTu8NVmsENrzrVck+vFF1voeUrgJ7SG798z0Ve0OAwX1g@mail.gmail.com>
Date: Fri, 17 Apr 2020 12:43:06 +0100
Message-ID: <1UW7fdFd8A.12CdBil9GXf@pc8xp>
In-Reply-To: <CABCOCHTu8NVmsENrzrVck+vFF1voeUrgJ7SG798z0Ve0OAwX1g@mail.gmail.com>
From: tom petch <daedulus@btconnect.com>
To: Andy Bierman <andy@yumaworks.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Core <core@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
User-Agent: OEClassic/3.0 (WinXP.2600; F; 2019-11-28)
X-ClientProxiedBy: LO2P265CA0191.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a::35) To VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from pc8xp (81.131.229.19) by LO2P265CA0191.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a::35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.26 via Frontend Transport; Fri, 17 Apr 2020 11:43:17 +0000
X-Originating-IP: [81.131.229.19]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 42b2ed91-7481-4b3c-fdbe-08d7e2c485e0
X-MS-TrafficTypeDiagnostic: VI1PR0701MB2143:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB21432F32A47E5488A719305AC6D90@VI1PR0701MB2143.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-Forefront-PRVS: 0376ECF4DD
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR0701MB2480.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10019020)(39860400002)(396003)(366004)(346002)(376002)(136003)(186003)(316002)(16526019)(54906003)(86362001)(110136005)(4326008)(6496006)(478600001)(8936002)(8676002)(45080400002)(52116002)(81156014)(33716001)(966005)(52230400001)(9686003)(26005)(9576002)(5660300002)(2906002)(53546011)(66476007)(66946007)(55016002)(66556008)(956004)(6666004); DIR:OUT; SFP:1102;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: mlZ4xhS7Xk5YMSdIc2wgKjuvbg7nEJmnnM4nVmdrWuDCkQEDjVl0cTMCcLHcYwgckCBjI5KWzfGZOGAGCwnCbmQ18b9fXkXUjzSnJME+8RKDzYULuy8fMaXb1JpIGuXah71u1/hr4HMToSpkaYO2gFvHpUl7pG13ZAZy7ktT9fK6AOeQou/5rbrwVR+Z/iyQVYtqMQlJvimkBHCeeyL1T9LSLFbCujO4Hi7hJIiRgj3xuun9kHrhKKXWkKA/JQqdrYb4oumpR7q1do727+08c0IL+J7IFnuGrLuoXam2TRzSaRDohT7SrmVamgUratnn9o3bMLh1meVkA/5ZepuBpcZABuz14lY+x8sppopsHvywE/4XrMZFyOZqcMXuZcl/auY8Z2fKFtjWm2dZ89glQm5rn+Nz9I6vb5Woi38yCxHMydX7NlZc8nDlKCIUb0l786yVhB/Cc0/AnbINsA3VpLiUugl0oXCFVt/hgXHM3rkPHT1G5KsvMByZhMrfN2DcvDPY0pE3Lfv8KhmOO5M/Yw==
X-MS-Exchange-AntiSpam-MessageData: tbVAF2nAqqWROPrlVIzQ3qySCfOSmyEtxmTe0ppOkmeT1WO6VulORA4HlKN6PH1PJ4i5lnPGyKs2ErOXwFHemmwVjlGCiX2bP10jQ4WaEO0i1EBe+WAIVLuaET2NT4kkeGRb6m//h10Upg/ugxjjIA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 42b2ed91-7481-4b3c-fdbe-08d7e2c485e0
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 17 Apr 2020 11:43:19.1793 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: LpS+KDT1BWlpW51H7t1xa0Qz0fHguDOM6RH9u1e/hsmt5LNn9Gp233Mz4usrtQTr0WA52L91p7QCuyptXVo5Kw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2143
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/8ukXYZ9XHfTOxiIzQz4a-PlIgHE>
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 11:43:25 -0000

----- 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 (

---
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