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> Thu, 13 September 2018 15:04 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 1CDEC1200D7 for <yot@ietfa.amsl.com>; Thu, 13 Sep 2018 08:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 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, URIBL_BLOCKED=0.001] 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 xD1EobufjXI2 for <yot@ietfa.amsl.com>; Thu, 13 Sep 2018 08:04:41 -0700 (PDT)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-co1nam04on070f.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe4d::70f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05BB9130DD1 for <yot@ietf.org>; Thu, 13 Sep 2018 08:04:40 -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=RT3c8P/DJlqL33a9ETRukckEB2WQeiUtzyIFD6l8KU4=; b=IOfkQq6vwlKuknrUcC3XNFQzxeuW6s91ljabJ/PQl4/dyrx0TLBYPzx7xUtbhsaKdf//rT0fC1uqH0TZxR6s1lRqtblRo+vNKg/1LoD4wO+3EyMxxSulrotac7kyaWfQiohamOBAkzPO8ORrXMyEI0LFcZZYqbbZxayUMBb8+no=
Received: from DM5PR06MB2777.namprd06.prod.outlook.com (10.175.107.139) by DM5PR06MB2731.namprd06.prod.outlook.com (10.168.199.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1143.14; Thu, 13 Sep 2018 15:04:38 +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; Thu, 13 Sep 2018 15:04:38 +0000
From: Michel Veillette <Michel.Veillette@trilliant.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "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/jggAEZyQCAAAksAIAAcxPw
Date: Thu, 13 Sep 2018 15:04:37 +0000
Message-ID: <DM5PR06MB27779684454F0E645DC45AE69A1A0@DM5PR06MB2777.namprd06.prod.outlook.com>
References: <29651.1536700610@localhost> <DM5PR06MB2777C6B37AE975F3DC189F599A1B0@DM5PR06MB2777.namprd06.prod.outlook.com> <20180913.092534.2221140746488750178.mbj@tail-f.com> <20180913075824.vd5ecwvd5wg5t4fv@anna.jacobs.jacobs-university.de>
In-Reply-To: <20180913075824.vd5ecwvd5wg5t4fv@anna.jacobs.jacobs-university.de>
Accept-Language: fr-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michel.Veillette@trilliant.com;
x-originating-ip: [207.96.192.122]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR06MB2731; 6:OmcddNMK8rPKZBWSlWV1RvvkrONIMehoZ62eM17W/D9+NbVSTXRuN/pI6Wo7wLEeKvD5sLZHtmyYYV22YmqNf9aQJZ17G1nlJrAbXtXUMKjqMt1ZNQjaOToeyYLPv1a+Y1RqlO/FC/7lvqixBb0jxTz5G2txw7WhmVmJKxxCaZQc+B4MVuBJFeCESqbwZ5c7ogyJTSkRsY+MxhssqS3/3LuzMzZ8azMUtl9yl/hQTo6gMGJH2MxVZ+djd01BgDM3Ie7o0PVsWYNI5RgRkuP/MVYR0ruedj/ERnESWMbHKj5MtnksBKV1oqhbBsbTZg1wYqv95mA1sjRqHFFIUKG9kuzDMc2TQLVvy9GFPXytKxTbzA0m4+wZ87MrxDm0KIcMWQlzzztnLUpVeyqtqcIs3XXqDaHISCRgDo7sSNYEULfZ94/nrsX15Bajb30Ts8P1Xc6Yhyh0KoGP9UeytXqt6g==; 5:+U4y1BRAG7PTXN7dWIcdw6RVx4BvpCAjnXYCmzdBxIWoTR22pz4DtZRLORi9DBS7FCDGnLyR22IaOskAVCtxbF1pX4mayCxfQWw+bQBkOUro7tIdLhooOE0j5GZoRnPhh3ae0jQHgdHwkVUHJvhnL5JneC/u7M27LRQbC5tiuyw=; 7:/hqekOFRXJU7l/oU5YzfzAOdvieHIZq2vTt/PBbJHUtuWz702DO3efO2rMZz7AJ15zhrTgwyhfVxPTMRER0jy6ys2jTKCbu/DQQttn0A75a2Q+F3sdmQ7TtZy34/wCXraPZGuL8tAsHazmsvprkEnU5ZSXtAZtnoMTdz3j9NQ8qaQ8RIAInzql2AW57cHG5ZAEiX0Pdkhaj6HlgIo7BIYMjm8aL+6E3bc/l9BV2p4STi+WJ/9Bq+5ZQWnGWgivFJ
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: ba2b094b-9991-45dd-1aae-08d6198a3989
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:DM5PR06MB2731;
x-ms-traffictypediagnostic: DM5PR06MB2731:
x-microsoft-antispam-prvs: <DM5PR06MB27316631C0976D891F4D75A29A1A0@DM5PR06MB2731.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)(93006095)(93001095)(3231311)(944501410)(52105095)(3002001)(10201501046)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201708071742011)(7699050); SRVR:DM5PR06MB2731; BCL:0; PCL:0; RULEID:; SRVR:DM5PR06MB2731;
x-forefront-prvs: 07943272E1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(136003)(346002)(396003)(39850400004)(366004)(199004)(189003)(13464003)(186003)(53546011)(305945005)(7736002)(110136005)(9686003)(74316002)(229853002)(68736007)(8676002)(8936002)(81156014)(81166006)(316002)(6306002)(6246003)(6436002)(55016002)(256004)(99286004)(53936002)(5250100002)(2501003)(105586002)(106356001)(66066001)(76176011)(5660300001)(478600001)(7696005)(3846002)(6116002)(33656002)(2906002)(14454004)(72206003)(966005)(476003)(2900100001)(11346002)(486006)(93886005)(446003)(97736004)(102836004)(6506007)(26005)(86362001)(25786009); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR06MB2731; H:DM5PR06MB2777.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: trilliant.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: Yy5y0h6cHlc6tFO+bPhgjfjY+7om5eivNb7v0ygKVINq6NyIAuQGOpbQenSDNf+ddfkGoVphpSPiwC3QF7EQRPRHhJza6Z2ect+45xwOtfnbgvr87kMhKyqF77QkRCGpS1cKi5im2mfW5xJpaPTslRLjVa8V/OhWEVHVKoXyWBRaXJa3YiH0wZWnqKAKv3CmhMOJD1QoP25AAysyXc0UhiEax6052B3tMVcwTkomIyOCLdBA+6RAfxOwZaWjrNoI+olhBXeHWYgYdkNrLGGf6SGclwI2yNJQ+5GNNglGkBPZWLwnx1NyfjHUoEZBScQDQmmAFLl1FsUFKikk2E5e1mB78L/Am4cFVZ77BPF4Y68=
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: ba2b094b-9991-45dd-1aae-08d6198a3989
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Sep 2018 15:04:37.9721 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB2731
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/nCoWmBoWIfC13HzzS0g8q3p2ojs>
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: Thu, 13 Sep 2018 15:04:44 -0000

=== About "Is the intention that this will done for *all* YANG modules"

Just some, this why say in my response, "optionally add them".
We should further qualify when SIDs are listed in an RFC.
For me, only when needed in the text of examples of this RFC.

=== About "why can't we make IANA maintain the sids"

The intent is to transfer the registry (i.e. https://comi.space/ or equivalent) under IANA control.
Having SIDs in a single location is less error prone.

As Juergen said " sids can be created for YANG modules as they are needed".
This is exactly the approach described in draft-ietf-core-sid  section 3 (".sid" file lifecycle)
https://tools.ietf.org/html/draft-ietf-core-sid-04#section-3

Regards,
Michel

-----Original Message-----
From: Yot <yot-bounces@ietf.org> On Behalf Of Juergen Schoenwaelder
Sent: Thursday, September 13, 2018 3:58 AM
To: yot@ietf.org
Subject: Re: [Yot] [Anima] documenting SID usage in IETF specification (fwd) Michael Richardson: [Anima] documenting SID usage in IETF specification

On Thu, Sep 13, 2018 at 09:25:34AM +0200, Martin Bjorklund wrote:
> > 
> > It will make sense to optionally add them in the IANA Considerations 
> > section of each RFC.
> 
> Is the intentation that this will done for *all* YANG modules 
> published in the IETF, or just for the YANG models from some WGs?
>

The sids are machine generated, no? If so, why can't we make IANA maintain the sids? This way, sids can be created for YANG modules as they are needed and we do not have to cast sids into RFCs just in case they could be needed.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

_______________________________________________
Yot mailing list
Yot@ietf.org
https://www.ietf.org/mailman/listinfo/yot

v2.23.0 | Report a Bug | By Email