IETF Logo Mail Archive

Re: [Yot] contents of SID registration authority

Andy Bierman <andy@yumaworks.com> Mon, 19 February 2018 17:52 UTC

Return-Path: <andy@yumaworks.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 4E18B12420B for <yot@ietfa.amsl.com>; Mon, 19 Feb 2018 09:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 O9qawTw6rMkL for <yot@ietfa.amsl.com>; Mon, 19 Feb 2018 09:52:24 -0800 (PST)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D70D01241F5 for <yot@ietf.org>; Mon, 19 Feb 2018 09:52:23 -0800 (PST)
Received: by mail-lf0-x236.google.com with SMTP id y19so612987lfd.4 for <yot@ietf.org>; Mon, 19 Feb 2018 09:52:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HSL56XFQxdocqeWW05K6RON78GsN4y7hyTS0fHNQaUA=; b=T0g5S/RuX6squBEk8RVr5VdZp04tLSio0HdKwrQIp4WIYFJThGdOUXSbs+3UHbxPRW Ck2byZ5WO9bin9+lBgip+lx3/aZZveE2qrRddT1HK/knzB5M7qATkqSimFkoQGdCt78m tywjU1BXRZXUbvJQv7R27PXPpeSEd5YflBHMHQsA0z3esVBxlYekAmFHo2FgGs9Ko7Iu ZSe+/F+ugNIvHYMBs+Fr6D/3QKXK88iOTVcDURSeqbbTEOadlC37ttInMo74ts6MzBup EqzXc+oV6nhbCnRV896VW7UeuRYtlSRMoblcv3XJe6dtLzTOLh27T0ytq9JEjz8gt9SB Rkkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HSL56XFQxdocqeWW05K6RON78GsN4y7hyTS0fHNQaUA=; b=QrxRwpEhYpbp/J4xYpuAx55rthNOABN16+AooL2kap0Lkm4QYXAvTAhyf9aCqN6VHi k07hc8w5GA3qH5AY39ee/AkRxRD2wBygK6FnhcX3p+RenBF01vb+8y887nl7n9HRA9BS VwoKqEPp+5Gz89+E8xJQpmv5DWPPU4EY94viTBcuiVpCSzhLIoGROaLce2MVCz0rUA6r b1og7z/52tIRBPO5WdQLuO69D6LreICdiPIuK9POvMfq8Rcg+ydDuZszBWg975UGEqtF K8aCCCyuQHzTcR/HGvaCeioGozB/UGgeCrX2ZvvSjCWAHVMG4WVvIG2U+1vlE8KvfBL8 Qhlg==
X-Gm-Message-State: APf1xPBS7ly/QKVWPsLAEu8VbNIvrtJMv/753NgmpwgFGrokAqEJ4L3b ay/0oGdONoDN6/rzdFI24fw1hdMiw3pid0wD/JhZqw==
X-Google-Smtp-Source: AH8x226RpdxeFQHFSQrYdovLVGaNxeRVumlD/6SLXsvZQaVpfd3dPopeQyKztZKdSa+gOfhBBFA91IfpPQI0sCiG7m4=
X-Received: by 10.46.32.11 with SMTP id g11mr1555812ljg.75.1519062742088; Mon, 19 Feb 2018 09:52:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.21.210 with HTTP; Mon, 19 Feb 2018 09:52:21 -0800 (PST)
In-Reply-To: <23288.1519061242@obiwan.sandelman.ca>
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>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 19 Feb 2018 09:52:21 -0800
Message-ID: <CABCOCHQ7HFLs4Q2mPxHbsh-0QY+JyWUeHQcKY+dk6ANwD3OdHQ@mail.gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: consultancy@vanderstok.org, yot@ietf.org, Michel Veillette <Michel.Veillette@trilliantinc.com>
Content-Type: multipart/alternative; boundary="001a1142c06622492d0565945ba4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/FtDerPdVDCeDMxoYlFhBa_lAo74>
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:52:26 -0000

On Mon, Feb 19, 2018 at 9:27 AM, Michael Richardson <mcr@sandelman.ca>
wrote:

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


There already is a set of registries managed by IANA for YANG module
information.
The SID range and/or official SID file need to be added to the YANG Module
Registry.
This takes care of assignments in RFCs.

For those that want to utilize the churn that is work-in-progress, there is
no stability.
Anything can happen and developers are on their own.  Opensource will have
to
provide a solution.


Andy



> --
> ]               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    [
>
>
> _______________________________________________
> Yot mailing list
> Yot@ietf.org
> https://www.ietf.org/mailman/listinfo/yot
>
>

v2.23.0 | Report a Bug | By Email