IETF Logo Mail Archive

Re: [Yot] [Anima] documenting SID usage in IETF specification (fwd) Michael Richardson: [Anima] documenting SID usage in IETF specification

Michel Veillette <Michel.Veillette@trilliant.com> Wed, 12 September 2018 15:06 UTC

Return-Path: <Michel.Veillette@trilliant.com>
X-Original-To: yot@ietfa.amsl.com
Delivered-To: yot@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61AD3130E01 for <yot@ietfa.amsl.com>; Wed, 12 Sep 2018 08:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trilliant.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 skNEaTCsHIjG for <yot@ietfa.amsl.com>; Wed, 12 Sep 2018 08:06:06 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0127.outbound.protection.outlook.com [104.47.33.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B042130DC6 for <yot@ietf.org>; Wed, 12 Sep 2018 08:06:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-Trilliant-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4dFOxfSXN90dYu+aqjIrJzpfZCUYJQXmItgdez7As4A=; b=EcVAKZw/3Zid2hNT9zjhhy3eMp6QwamAQtzUSQgzJArkUvlwV0RhBuFUn6rqBAbiAGpNalOHNe/2h53O18AnNvhKEeCs7LgIDyLECIemA/bt7DL+DOq1R40PH6z61APJmYfvvV0C87gWdBnuuiFvmctvQZPF7qL5AZDpR1jY+oc=
Received: from DM5PR06MB2777.namprd06.prod.outlook.com (10.175.107.139) by DM5PR06MB2762.namprd06.prod.outlook.com (10.175.107.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1122.15; Wed, 12 Sep 2018 15:06:03 +0000
Received: from DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::85c4:bc9b:dc0e:19e8]) by DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::85c4:bc9b:dc0e:19e8%3]) with mapi id 15.20.1122.019; Wed, 12 Sep 2018 15:06:03 +0000
From: Michel Veillette <Michel.Veillette@trilliant.com>
To: Michael Richardson <mcr@sandelman.ca>, "yot@ietf.org" <yot@ietf.org>
Thread-Topic: [Yot] [Anima] documenting SID usage in IETF specification (fwd) Michael Richardson: [Anima] documenting SID usage in IETF specification
Thread-Index: AQHUShTI49tf+ze05UurFksSWsBc2qTst/jg
Date: Wed, 12 Sep 2018 15:06:03 +0000
Message-ID: <DM5PR06MB2777C6B37AE975F3DC189F599A1B0@DM5PR06MB2777.namprd06.prod.outlook.com>
References: <29651.1536700610@localhost>
In-Reply-To: <29651.1536700610@localhost>
Accept-Language: fr-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [207.96.192.122]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR06MB2762; 6:FfhRYQzBvn3wqPC3iyRYuVTr6oXZU6Fyaux3f6s91Ttc97xO5z2Q2lce2e6HjE/PXKuCc7nkS8Uja1h35fI3huda8na7nU65IzVcJNaT6gADAmbHTI13kYfBFzR+2Vce/JyWjMixhXbLKeBfnFXpHSHgSrbDR0Rn8U7dmd/h6CgYsg4fNvMipOaNSHz1Fh69AkByKkdQSO994PurMO5w6ySC2ze2GG5+UIdzkBbNb1FQnWB+Nf3yRPsLDHlh0Zxv5htJb/rc348jOIwseINizRnuS7q+XQJnLMbUWM3CPjOdOxWu06XJMPgsQKjlWCa9kQNCvVfQCwg1mzvgr8h9b2Rh1aKxUXA3fLsHeKvu2zpKIxTuTZT9d+EMuD+gC29yOaa1v3WO6qY5l9cPeVJDT2eGNJCUbo/uVhbM8p6hINjqENf/X4asd1KmyYDzgAV/rtuWA7UOlA3F/czufhRqkw==; 5:xQkh4qPVTm9AQdH5EGSf1mvbWIzP09J2PEHpZ0yJikJimr2QdC647ZrIEEPkAD2Y2fdU853njJQxsleVs7jc9yg2DaXVGqHBLyL9jWal0l9uSlg9uRQ4rmfufHwrX1QMziwT2oNv3VYYOJa0KL5zW94W+2Vdm2OPUJBqg4WEK0k=; 7:vjUnabOp+SA1+I+tVU94DY8ymZkWt/xoxynUrkig6Z1CYHxwlxogwOH3pZbuRE5fDrJJD1+lhByvKfFuMMbblkBxZsdlMguXYBnMiGYmkTqaEaqV0HSftRaYbFowqeswAlEbYrum2XSBafaV9r8wScKMWQkwVgj0dIofwoDnEYHCuCrk8SZw8Y+dx+WJ4+8he4CXeGni7CJLnoJQUgllkMB8kenC77aIqRN1JyhvBfFUP1J7R3AyEBymm+d4YRJR
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 1320b14b-0fd4-4294-74b1-08d618c1421a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:DM5PR06MB2762;
x-ms-traffictypediagnostic: DM5PR06MB2762:
x-microsoft-antispam-prvs: <DM5PR06MB2762CD465032C0A0FBAAB8979A1B0@DM5PR06MB2762.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3002001)(3231344)(944501410)(52105095)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201708071742011)(7699050)(76991041); SRVR:DM5PR06MB2762; BCL:0; PCL:0; RULEID:; SRVR:DM5PR06MB2762;
x-forefront-prvs: 07935ACF08
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39840400004)(366004)(136003)(346002)(396003)(13464003)(69234005)(189003)(199004)(97736004)(316002)(5250100002)(2900100001)(5660300001)(2501003)(110136005)(3846002)(6116002)(7696005)(53936002)(6306002)(9686003)(55016002)(99286004)(6246003)(74316002)(76176011)(25786009)(305945005)(7736002)(256004)(8676002)(66066001)(33656002)(6346003)(6436002)(14454004)(53546011)(102836004)(86362001)(68736007)(229853002)(186003)(476003)(26005)(81156014)(81166006)(6506007)(446003)(966005)(2906002)(72206003)(478600001)(486006)(106356001)(8936002)(11346002)(105586002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR06MB2762; H:DM5PR06MB2777.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: trilliant.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michel.Veillette@trilliant.com;
x-microsoft-antispam-message-info: JlNTKUOhN0y8s0Oi7cJIdGU+5RSXpIa8XagSEeUyQBcXLtoMThBUoWONvVY698AfCR6ls8ZaRYLtQrbEVKtS9Rcg9b/QWJUX1hdH7MzqQvsaj9+Azf6F2vdDmnKDC/CBEbUKOW2xxG1pXV2H0tJ7FB/QmnexDIMheaKD1m66r/NAlaDWKqQArttlt4JkwHrGJzdKPMk2oSWFKWx6oFSuESaQsBRLpH7ZHVG+j2GFM2jASzVcnXPb3G4YVXQ6I7DUZQR6ZlnTTgkiCxpwNmRrmY+4P3konHPWnTgMRWrLWlFyohL/neRAFPPZde7yhYVDXw3t2WYx1Pnctw95AI4IeLJDKwexcF/um24T34XJKl4=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Trilliant.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1320b14b-0fd4-4294-74b1-08d618c1421a
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Sep 2018 15:06:03.4726 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB2762
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/EWoO5Aq5x4VDWy5v9iQx1ok2MMw>
Subject: Re: [Yot] [Anima] documenting SID usage in IETF specification (fwd) Michael Richardson: [Anima] documenting SID usage in IETF specification
X-BeenThere: yot@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Yang of Things <yot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yot>, <mailto:yot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yot/>
List-Post: <mailto:yot@ietf.org>
List-Help: <mailto:yot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yot>, <mailto:yot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2018 15:06:13 -0000

Hi Michael

=== About " It appears that there might be a typo in ietf-core-sid-04, section 6.1.1:"

Error fixed in http://core-wg.github.io/yang-cbor/draft-ietf-core-sid-latest.txt

=== About your general question "HOW SHOULD SID VALUES BE DOCUMENTED IN RFCs"

It will make sense to optionally add them in the IANA Considerations section of each RFC.
The allocated range should be added  to the "RFC SID range assignment" sub-registry.
The allocated SIDs should be added  to the a new sub-registry to be added to "draft-ietf-core-sid".

I will add this second sub-registry to the next revision of "draft-ietf-core-sid" in case we want to proceed this way.

Regards,
Michel

-----Original Message-----
From: Yot <yot-bounces@ietf.org> On Behalf Of Michael Richardson
Sent: Tuesday, September 11, 2018 5:17 PM
To: yot@ietf.org
Subject: [Yot] [Anima] documenting SID usage in IETF specification (fwd) Michael Richardson: [Anima] documenting SID usage in IETF specification


FYI.

v2.23.0 | Report a Bug | By Email