Re: [Yot] contents of SID registration authority

Michael Richardson <mcr@sandelman.ca> Mon, 19 February 2018 17:27 UTC

Return-Path: <mcr@sandelman.ca>
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 A01AD1243F6 for <yot@ietfa.amsl.com>; Mon, 19 Feb 2018 09:27:25 -0800 (PST)
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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 H-xqcq0CR_aj for <yot@ietfa.amsl.com>; Mon, 19 Feb 2018 09:27:23 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1659A128959 for <yot@ietf.org>; Mon, 19 Feb 2018 09:27:23 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C3F3A20091; Mon, 19 Feb 2018 12:34:37 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1D19180C42; Mon, 19 Feb 2018 12:27:22 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: consultancy@vanderstok.org
cc: Michel Veillette <Michel.Veillette@trilliantinc.com>, yot@ietf.org
In-Reply-To: <232f180f1c728b1a614cca4ae3a6b3ac@xs4all.nl>
References: <792b282a276d738ddfaf519668a008a4@xs4all.nl> <BN6PR06MB2308A232AF7F2382F2344EDEFEF50@BN6PR06MB2308.namprd06.prod.outlook.com> <dababb77f3473da4817b8e85eefc8347@xs4all.nl> <BN6PR06MB2308EFDDD226631D7ED514B6FEF40@BN6PR06MB2308.namprd06.prod.outlook.com> <232f180f1c728b1a614cca4ae3a6b3ac@xs4all.nl>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 19 Feb 2018 12:27:22 -0500
Message-ID: <23288.1519061242@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/DVXFly9PUt0qg1ey-QNQ5ad7tcI>
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 17:27:25 -0000

peter van der Stok <stokcons@xs4all.nl> wrote:
    > 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:

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

I thought that IANA would allocate mega-ranges only.
One mega-range is to be allocated to comi-space for IETF WG use.
Other mega-ranges would be allocated to other SDOs (IEEE, Wifi alliance,
etc.) for use in their specifications.

Whether there are gaps in the mega-ranges is up to IANA.
Whether there are gaps in the IETF range is up to comi.space code.

I think it's reasonable if a specification outgrows the range before RFC that
it would just get reallocated into a new range and the old range recycled
after a period of time (6 months maybe).

It is my impression that the operation of comi.space would be turned over
either IANA or the IETF secretariat or some other contractor. All of this
under IAOC tools team oversight.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [