IETF Logo Mail Archive

Re: [Yot] contents of SID registration authority

Michel Veillette <Michel.Veillette@trilliantinc.com> Wed, 14 February 2018 20:07 UTC

Return-Path: <Michel.Veillette@trilliantinc.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 8A68F129516 for <yot@ietfa.amsl.com>; Wed, 14 Feb 2018 12:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 fiaYRIYk6N6l for <yot@ietfa.amsl.com>; Wed, 14 Feb 2018 12:07:19 -0800 (PST)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0096.outbound.protection.outlook.com [104.47.34.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95D93127867 for <yot@ietf.org>; Wed, 14 Feb 2018 12:07:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-trilliantinc-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=si929I0JLJC5oviFDO/aW72HSFUF0mwMBP3zmLdpEYg=; b=tLxemTwjKzUZZJPuuEhsWmiCDeN+f83uxxeziopcdnYB2tb9b127eCKFEBnukmkw0MwPAW/IZR4a7/xbsv48Aln6xLxl4J4yHlG3Vh8Qcx5GE3iJ4FD6y9fyMq1beFLU27DVsycuWp9cSeF0dv9knwaRit/Y2+f2UU9Sz+QkK84=
Received: from BN6PR06MB2308.namprd06.prod.outlook.com (10.173.19.139) by BN6PR06MB3170.namprd06.prod.outlook.com (10.174.232.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.506.18; Wed, 14 Feb 2018 20:07:18 +0000
Received: from BN6PR06MB2308.namprd06.prod.outlook.com ([10.173.19.139]) by BN6PR06MB2308.namprd06.prod.outlook.com ([10.173.19.139]) with mapi id 15.20.0485.017; Wed, 14 Feb 2018 20:07:18 +0000
From: Michel Veillette <Michel.Veillette@trilliantinc.com>
To: "yot@ietf.org" <yot@ietf.org>
CC: "consultancy@vanderstok.org" <consultancy@vanderstok.org>, Michael Richardson <mcr@sandelman.ca>
Thread-Topic: contents of SID registration authority
Thread-Index: AQHTpX1dvKbZ5/a2pUqp4epfBudwSaOkPjzQ
Date: Wed, 14 Feb 2018 20:07:18 +0000
Message-ID: <BN6PR06MB2308A232AF7F2382F2344EDEFEF50@BN6PR06MB2308.namprd06.prod.outlook.com>
References: <792b282a276d738ddfaf519668a008a4@xs4all.nl>
In-Reply-To: <792b282a276d738ddfaf519668a008a4@xs4all.nl>
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@trilliantinc.com;
x-originating-ip: [207.96.192.122]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR06MB3170; 7:vs9sw0f80PZfsR/12xxoRV/bDj7GgbRjjAxuClAhv7Llx0laVzqCF5qH+DCqEgETyEVhUCZMqy/Da8yDSsf8Z4XGBvD9l5QzDURat04s6p7T7ryYZTPNITbMK2OurW1EG9nGZ9eKU4HjleZ+doffnPZ+rcUCQg5rX26+bthno8stv0LT/OwGRQcmKY+QuFEzsAbfa4mFlynluCmrwtO8oEoCPnC4NIas+1yBz26ASmd10X60xD4YhxanqBvfSOZY
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 84b06e26-9cc7-441b-0721-08d573e68cc2
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:BN6PR06MB3170;
x-ms-traffictypediagnostic: BN6PR06MB3170:
x-microsoft-antispam-prvs: <BN6PR06MB31707B0791665188A48B96ABFEF50@BN6PR06MB3170.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(788757137089);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231101)(944501161)(10201501046)(3002001)(93006095)(93001095)(6041288)(20161123564045)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BN6PR06MB3170; BCL:0; PCL:0; RULEID:; SRVR:BN6PR06MB3170;
x-forefront-prvs: 0583A86C08
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(366004)(39850400004)(376002)(39380400002)(396003)(199004)(377424004)(13464003)(189003)(86362001)(186003)(2351001)(4001150100001)(99286004)(15974865002)(77096007)(68736007)(7736002)(6436002)(7696005)(102836004)(72206003)(8936002)(2501003)(81166006)(106356001)(966005)(81156014)(3660700001)(5660300001)(97736004)(478600001)(26005)(53546011)(6506007)(305945005)(74316002)(4326008)(2950100002)(316002)(25786009)(105586002)(14454004)(76176011)(53936002)(1730700003)(229853002)(8676002)(2900100001)(55016002)(33656002)(6916009)(2906002)(6116002)(6306002)(6246003)(66066001)(54906003)(9686003)(5640700003)(3846002)(3280700002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR06MB3170; H:BN6PR06MB2308.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: trilliantinc.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: HZzHmAhWWjeGlCmB8smAcrKeJQgZ/lhR9cxad248OXt6lFWHGpzLdTlbFxcW6OXX/dFYXlDM1Kd1YwQSolYb5A==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: trilliantinc.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 84b06e26-9cc7-441b-0721-08d573e68cc2
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2018 20:07:18.3522 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR06MB3170
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/67lLxkpNBVCqQIakszB8q_dFSMQ>
Subject: Re: [Yot] contents of SID registration authority
X-BeenThere: yot@ietf.org
X-Mailman-Version: 2.1.22
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, 14 Feb 2018 20:07:22 -0000

Hi Peter

=== About "remove ietf-restconf@2016-08-15 because there is already an ietf-restconf@2017-01-26 owned by ietf"

ietf-restconf is imported by other YANG modules.
To automatically resolve these imports, it is more convenient to keep this module in the SID registry.
Furthermore, the SID assigned to the ietf-restconf module can be used in the yang library (https://datatracker.ietf.org/doc/draft-veillette-core-yang-library/)
The new version of ietf-restconf should be added however.

=== About " What is the policy for drafts that become rfcs? will they be entered automatically?
The latter will mean that the originally attributed SIDs are replaced with the values from the ietf range?"

The second bullet in https://tools.ietf.org/html/draft-ietf-core-sid-03#section-6.1.1 address this topic.
In summary, we allows final SIDs allocation after working group adoption.
In this case, the transition to RFC have no impacts.

   o  The range of 1000 to 59,999 is reserved for YANG modules defined
      in RFCs.  The IANA policy for future additions to this sub-
      registry is "RFC required" [RFC5226].  Allocation within this
      range requires publishing of the associated ".yang" and ".sid"
      files in the YANG module registry.  The allocation within this
      range is done prior to the RFC publication but should not be done
      prior to the working group adoption.

Regards,
Michel

-----Original Message-----
From: peter van der Stok [mailto:stokcons@xs4all.nl] 
Sent: Wednesday, February 14, 2018 5:20 AM
To: Michel Veillette <Michel.Veillette@trilliantinc.com>; Michael Richardson <mcr@sandelman.ca>
Subject: contents of SID registration authority

Hi Michel and Michael,

I looked at the contents of SID registration authority.

I have the following suggestions for mcr314 entries:
- Replace ietf-voucher@2017-10-25 by ietf-voucher@2018-01-24; better would be to have an ietf version which is updated with the latest version.
- remove ietf-restconf@2016-08-15 because there is already an
ietf-restconf@2017-01-26 owned by ietf

What is the policy for drafts that become rfcs?; will they be entered automatically?
The latter will mean that the originally attributed SIDs are replaced with the values from the ietf range?

Greetings,

Peter

--
Peter van der Stok
vanderstok consultancy
mailto: consultancy@vanderstok.org
www: www.vanderstok.org
tel NL: +31(0)492474673     F: +33(0)966015248

v2.23.0 | Report a Bug | By Email