Re: [core] [Anima] documenting SID usage in IETF specification

Andy Bierman <andy@yumaworks.com> Thu, 13 September 2018 22:32 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B189130E79 for <core@ietfa.amsl.com>; Thu, 13 Sep 2018 15:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 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_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=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 XVL8t2ZCAH-1 for <core@ietfa.amsl.com>; Thu, 13 Sep 2018 15:32:28 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 91D1C130E78 for <core@ietf.org>; Thu, 13 Sep 2018 15:32:27 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id u83-v6so5923538lje.12 for <core@ietf.org>; Thu, 13 Sep 2018 15:32:27 -0700 (PDT)
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=IJ1us6GpLsDiUmInnKzAhZa+19fVo2ToG47rDb096Ho=; b=B/z5ohP6Z/4Svjm3cxeNr4z5rkCiD/ef39a0R1UCLYXLFtk+p5dVLSf0tE05//upPM hFIzY+up+QqXCfQlGEBtawWzmweQZme9njTUO5F3jNLFjhoL33Y9Fs5xpsdDaNT1x0z/ vp1ubwq7/FwghVcWd8JCL911/HNyGmcxC9VEWvuEgj4qrgfuP0Hm2FmBYBox4AqPRQAy WoJdpi7X2gt1Tu5lM3X0XNrCvj9drmVupzapP+4c0aPadv+TsIQFAGfwaYu9PggHoYC+ Gku3+vketuS8SbUXIsVVjjy1zhMPPhX7ILcgHsUhbX7ss/lHI+D/RU8NUx+vtmRTmlcJ 4Pvw==
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=IJ1us6GpLsDiUmInnKzAhZa+19fVo2ToG47rDb096Ho=; b=pYiR2wsB/+vs0TrQ6xted8bD8pBoQ1r4GkF7KY/3Y7p/pWdJb8JETjR+4q1tcT6Ewo 6FC0oEZ1ttTyOSLp2LHsU9KnYvOGHGcqSt2DMnjyFvp+FzYX0840aw+5vQKPF2Wd+d7e YymQwxxRwPeyk2/l6iYPmyiyQIAcEA6/tzP69YmJx2mwdR3BLlM1ukkGQBRZos/a+xoO ijJbRz2S2jQUk3lHqqjUXyBtbjKRASV8i5Llh6frkKFxixvuy6PYN5EPIjFe5PvT/jxH qQo30wcbxUCPbqvIZegiROZfAVmbzmkM3bDMuQujSZts0zSCFsPdIHtXfwA3jUy6VZWi 0+6A==
X-Gm-Message-State: APzg51DwFi0XKsSZsqqI07svRHY441KAmkVX+wbtkwqmA5AmjqanY8Rg jWK12RtWQdjttk3/RiaVpPKHiveODoYWBmpp+kIqNAYE
X-Google-Smtp-Source: ANB0VdZVwlQtXu3twLh7eJ2RqoUOq/NN7ERQjK9/bUCA4hxvWkD3e2UfL05otaqhU9CM6w3YjRt9xdfal/UpxGpMu8k=
X-Received: by 2002:a2e:97c8:: with SMTP id m8-v6mr3522548ljj.52.1536877945485; Thu, 13 Sep 2018 15:32:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:48c9:0:0:0:0:0 with HTTP; Thu, 13 Sep 2018 15:32:24 -0700 (PDT)
In-Reply-To: <25103.1536871813@localhost>
References: <17342.1536697549@localhost> <622CDA79-7BE4-4A71-BFF7-0C80F63A1556@tzi.org> <CABCOCHTrjYZmK4e+L7pj=V=sWxg97jw2AFGen2PFe7ceBrB7bg@mail.gmail.com> <50f58c78b6825ce1cdbc33ea852c3145@bbhmail.nl> <84F58F84-4637-4D65-8F86-8E86B346528F@tzi.org> <7766.1536851909@localhost> <CABCOCHStd-_VPcf6TGXkc5gF5RwaiGM0Gf9T-LwX1ujYo+BkjA@mail.gmail.com> <25103.1536871813@localhost>
From: Andy Bierman <andy@yumaworks.com>
Date: Thu, 13 Sep 2018 15:32:24 -0700
Message-ID: <CABCOCHQoeKFRnF2fWjFbersiAS4PUuT018kwNBN=_37p52Yz3Q@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Core <core@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000010cee0575c84828"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/DHcgYy6Ny8hCbE7uf1w4LBnWUDk>
Subject: Re: [core] [Anima] documenting SID usage in IETF specification
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2018 22:32:29 -0000

On Thu, Sep 13, 2018 at 1:50 PM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Andy Bierman <andy@yumaworks.com> wrote:
>     > I think that we used to call these "Proposed standards" :-)
>     > I'm not sure we need to have this designation. I think that SID
>     > numbers are
>     > cheap enough that it's okay if some drafts consume some and then
>     > get
>     > abandonned. The numbers could be recycled 6 months after the draft
>     > expires.
>
>     > IMO you had it right up to the last sentence.
>     > There are not port numbers. There are 2^^64 of them.
>
> Agreed.  So when recycled, they go to the end of the 2^^64 list :-)
>
>     > The "experimental" SID space is especially problematic in this
> regard.
>     > Within a deployment there will be server code from all different
>     > dates,
>     > so being able to declare the SID space clean at 1 single point in
> time
>     > is not good enough.
>
> Stuff in the experimental SID space is a problem.
>
>
Yes -- it is the wrong way of looking at it.
There is really only "global" and "local" SIDs.

IMO it is better to reserve a range where it is clear there are no
expectations
that the SID assignments are real. (Imagine if we told everybody to name
their YANG module my-module.yang -- these experimental SIDs are like that)

There will be modules that do not get registered (for various reasons),
or that simply get used/tested before they are registered.


Andy



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