IETF Logo Mail Archive

Re: [Yot] contents of SID registration authority

Michel Veillette <Michel.Veillette@trilliant.com> Mon, 19 February 2018 21:20 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 6C2F5126579 for <yot@ietfa.amsl.com>; Mon, 19 Feb 2018 13:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 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_H2=-0.001, 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 9ZHip8rH_-Xz for <yot@ietfa.amsl.com>; Mon, 19 Feb 2018 13:20:49 -0800 (PST)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0114.outbound.protection.outlook.com [104.47.38.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC872124E15 for <yot@ietf.org>; Mon, 19 Feb 2018 13:20:48 -0800 (PST)
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; bh=AMYQicon4ChfvyHlc8R9tsWFkfd2VwvnPoL53DbEb7c=; b=weFz6B+Q7RMr+wxA5NqOUU/UzZZYlacbeYRo8iJrFdVxVgAMjw5RPdTRZ3tdEF2NyIsMbY4qcPYKFcKdkty4Dny8GtlCZczxMmWZKEeQnk2Vn5fRtpK7Ge3rgOFiGhSbFlEO1VYLuzKA24EMIW2hLccti/GaE+R2WnwmoqgafJU=
Received: from BN6PR06MB2308.namprd06.prod.outlook.com (10.173.19.139) by BN6PR06MB2497.namprd06.prod.outlook.com (10.173.22.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.506.18; Mon, 19 Feb 2018 21:20:45 +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.0506.023; Mon, 19 Feb 2018 21:20:45 +0000
From: Michel Veillette <Michel.Veillette@trilliant.com>
To: "consultancy@vanderstok.org" <consultancy@vanderstok.org>
CC: "yot@ietf.org" <yot@ietf.org>, Michael Richardson <mcr@sandelman.ca>
Thread-Topic: contents of SID registration authority
Thread-Index: AQHTpX1dvKbZ5/a2pUqp4epfBudwSaOkPjzQgADkzgCAAG2J0IAF/QoAgACzi9A=
Date: Mon, 19 Feb 2018 21:20:45 +0000
Message-ID: <BN6PR06MB23087FF6C2A7A67AA57523B19AC80@BN6PR06MB2308.namprd06.prod.outlook.com>
References: <792b282a276d738ddfaf519668a008a4@xs4all.nl> <BN6PR06MB2308A232AF7F2382F2344EDEFEF50@BN6PR06MB2308.namprd06.prod.outlook.com> <dababb77f3473da4817b8e85eefc8347@xs4all.nl> <BN6PR06MB2308EFDDD226631D7ED514B6FEF40@BN6PR06MB2308.namprd06.prod.outlook.com> <232f180f1c728b1a614cca4ae3a6b3ac@xs4all.nl>
In-Reply-To: <232f180f1c728b1a614cca4ae3a6b3ac@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@trilliant.com;
x-originating-ip: [207.96.192.122]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR06MB2497; 7:q0GddC4PuboJHvujencVU5ec5LjjRIX5spUsKJxpEBEaDOqndMCB8gD6X4T1TYxsOkYkx5xFY32noa9HODM/Roe7gGZxIuLGVLR0Qj/votP6Zm3PcffOAs2R8TqrnzmrCGnaJ+GVmoBfOTkMf7kpaAEOS+8j940dPhvgNn1xuIikVAaDOLoKAgzEX7ZJZoPC6aG3qunb0ErNoL6Flv8Kl51sEuXjvAqS2KSnKTCEzmlC3mGu+X9BRlPQv/bIAg7c
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 5998237f-2f93-4ed4-27b0-08d577dea38c
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:BN6PR06MB2497;
x-ms-traffictypediagnostic: BN6PR06MB2497:
x-microsoft-antispam-prvs: <BN6PR06MB249755AF299069858201E1A39AC80@BN6PR06MB2497.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231101)(944501161)(3002001)(6041288)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(6072148)(201708071742011); SRVR:BN6PR06MB2497; BCL:0; PCL:0; RULEID:; SRVR:BN6PR06MB2497;
x-forefront-prvs: 0588B2BD96
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39850400004)(396003)(376002)(346002)(366004)(39380400002)(199004)(189003)(13464003)(478600001)(25786009)(3280700002)(229853002)(6916009)(2950100002)(4326008)(3660700001)(105586002)(5660300001)(7696005)(72206003)(86362001)(53936002)(6246003)(2906002)(76176011)(97736004)(2900100001)(99286004)(9686003)(55016002)(53546011)(14454004)(6116002)(3846002)(6436002)(54906003)(316002)(102836004)(66066001)(6506007)(5640700003)(2501003)(2351001)(7736002)(106356001)(305945005)(26005)(77096007)(93886005)(186003)(33656002)(1730700003)(74316002)(8676002)(81166006)(8936002)(81156014)(68736007); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR06MB2497; H:BN6PR06MB2308.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: trilliant.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 930+FcO107u66+sTWg1D0guQiLynWxYlYSi3T6NP9762gIbSxpW5vH3LNSuUT2DJ06CTlBcokkF6Lea/8zL0h8ZzESS6IyaQ3jqIUMbYFzKJDQbyhFfZJ4VyJ13qPUFGsw4bAacdxIGPCeclD8b6xTm9RiZGlmLhpSiUnE+l+Zw=
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: 5998237f-2f93-4ed4-27b0-08d577dea38c
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2018 21:20:45.1078 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR06MB2497
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/X5WR4Ilh_844CKhyA9eraaLHXU8>
X-Mailman-Approved-At: Mon, 19 Feb 2018 13:44:26 -0800
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: Mon, 19 Feb 2018 21:35:58 -0000

About "During the draft development the number of required SIDS changes radically and a new allocation is required."

During the development, the authors have two options.

1) Stay backward compatible by updating the previous .sid file.
   In this case, previously assigned SIDs are preserved.
   Data nodes can be deprecated but not deleted as mandated by RFC7950 section 11.
   "Obsolete definitions MUST NOT be removed from published modules"

2) Restarting from scratch by generating a brand new .sid file.
    In this case, a completely new set of SIDs is generated.

Regards,
Michel

-----Original Message-----
From: peter van der Stok [mailto:stokcons@xs4all.nl] 
Sent: Monday, February 19, 2018 5:28 AM
To: Michel Veillette <Michel.Veillette@trilliant.com>
Cc: consultancy@vanderstok.org; yot@ietf.org; Michael Richardson <mcr@sandelman.ca>
Subject: Re: contents of SID registration authority

Hi Michel,

I read the core-sid draft, and saw that indeed there is a IANA registry called "SID mega-range" and another called "YANG module assignment".
That simplifies things. Good.
some text enhancements below:

>> 
>>    o  The range of 1000 to 59,999 is reserved for YANG modules defined
>>       in RFCs.  The IANA policy for future additions to the "SID 
>> mega-range" sub-
>>       registry is "RFC required" [RFC5226].
All RFC-based YANG modules SHOULD allocate SID values and register them in "SID mega-range" registry.
          It is required to register the associated ".yang" and ".sid"
>>       files in the "YANG module assignment" registry.  The allocation 
>> within this
>>       range is done prior to the RFC publication but should not be 
>> done
>>       prior to the working group adoption.
>> 

Question:
Suppose after WG adoption SID are allocated in the IETF range. During the draft development the number of required SIDS changes radically and a new allocation is required.

How is that going to be handled? Will there be holes in the allocated SID value range?

Greetings,

Peter

v2.23.0 | Report a Bug | By Email