IETF Logo Mail Archive

Re: [Yot] contents of SID registration authority

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 19 February 2018 19:08 UTC

Return-Path: <mcr+ietf@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 05CFF1204DA for <yot@ietfa.amsl.com>; Mon, 19 Feb 2018 11:08:23 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 6ooHUpCBoRdf for <yot@ietfa.amsl.com>; Mon, 19 Feb 2018 11:08:21 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10BB31243F6 for <yot@ietf.org>; Mon, 19 Feb 2018 11:08:21 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id ED7BE20091; Mon, 19 Feb 2018 14:15:34 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 08DF080766; Mon, 19 Feb 2018 14:08:19 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Andy Bierman <andy@yumaworks.com>, yot@ietf.org
cc: consultancy@vanderstok.org, Michel Veillette <Michel.Veillette@trilliantinc.com>
In-Reply-To: <CABCOCHQ7HFLs4Q2mPxHbsh-0QY+JyWUeHQcKY+dk6ANwD3OdHQ@mail.gmail.com>
References: <792b282a276d738ddfaf519668a008a4@xs4all.nl> <BN6PR06MB2308A232AF7F2382F2344EDEFEF50@BN6PR06MB2308.namprd06.prod.outlook.com> <dababb77f3473da4817b8e85eefc8347@xs4all.nl> <BN6PR06MB2308EFDDD226631D7ED514B6FEF40@BN6PR06MB2308.namprd06.prod.outlook.com> <232f180f1c728b1a614cca4ae3a6b3ac@xs4all.nl> <23288.1519061242@obiwan.sandelman.ca> <CABCOCHQ7HFLs4Q2mPxHbsh-0QY+JyWUeHQcKY+dk6ANwD3OdHQ@mail.gmail.com>
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
X-Attribution: mcr
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 19 Feb 2018 14:08:19 -0500
Message-ID: <19100.1519067299@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/NvQrfwUq8M-rNWSBeaNLTtp7L2U>
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 19:08:23 -0000


Andy Bierman <andy@yumaworks.com> wrote:
    mcr> It is my impression that the operation of comi.space would be
    mcr> turned over
    mcr> either IANA or the IETF secretariat or some other contractor. All
    mcr> of this
    mcr> under IAOC tools team oversight.

    > There already is a set of registries managed by IANA for YANG module
    > information.

Yes, but this is something additional.

    > The SID range and/or official SID file need to be added to the YANG
    > Module Registry.
    > This takes care of assignments in RFCs.

Section 6.1.1
https://tools.ietf.org/html/draft-ietf-core-sid-03#section-6.1.1
says:

   The range of 100,000 to 999,999 is reserved for standardized YANG
   modules.  The IANA policy for future additions to this sub-
   registry is "Specification Required" [RFC5226].  Allocation within
   this range requires publishing of the associated ".yang" and
   ".sid" files in the YANG module registry.

It is my impression that Internet-Drafts authors can come to comi.space
and ask for an allocation based upon a SID/YANG file.  And since publication
of the RFC satisfies "Specification Required", that they can keep that
allocation.  That they don't need to move/wait for RFC to move to the 
<60,000 range.

There was a thread about where/when a document should ask: upon personal -00,
upon WG adoption -00, WGLC, ?    The intention is, I understand, to be as
light weight as possible.


-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email