Re: [core] Robert Wilton's Discuss on draft-ietf-core-sid-19: (with DISCUSS and COMMENT)

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 17 March 2023 18:26 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 DD4F4C1522D3; Fri, 17 Mar 2023 11:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DvvZsSAuQmzS; Fri, 17 Mar 2023 11:26:04 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60EDAC151535; Fri, 17 Mar 2023 11:25:56 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [5.148.108.163]) by relay.sandelman.ca (Postfix) with ESMTPS id A68431F47D; Fri, 17 Mar 2023 18:25:54 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 66770A10BB; Fri, 17 Mar 2023 14:25:54 -0400 (EDT)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 64069A1071; Fri, 17 Mar 2023 18:25:54 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
cc: Carsten Bormann <cabo@tzi.org>, The IESG <iesg@ietf.org>, "draft-ietf-core-sid@ietf.org" <draft-ietf-core-sid@ietf.org>, "core-chairs@ietf.org" <core-chairs@ietf.org>, "core@ietf.org WG (core@ietf.org)" <core@ietf.org>, "jaime@iki.fi" <jaime@iki.fi>
In-reply-to: <BY5PR11MB41968DD2DC778748CE9B73F5B5BD9@BY5PR11MB4196.namprd11.prod.outlook.com>
References: <167404882957.1138.7718323157797790477@ietfa.amsl.com> <788CA084-D4D5-44A5-BE88-5CD67AC809E7@tzi.org> <BY5PR11MB41968DD2DC778748CE9B73F5B5BD9@BY5PR11MB4196.namprd11.prod.outlook.com>
Comments: In-reply-to "Rob Wilton (rwilton)" <rwilton@cisco.com> message dated "Fri, 17 Mar 2023 14:09:22 +0000."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 17 Mar 2023 18:25:54 +0000
Message-ID: <2748748.1679077554@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Vuadaslk0InaGTY0xwXCN7RRTZE>
Subject: Re: [core] Robert Wilton's Discuss on draft-ietf-core-sid-19: (with DISCUSS and COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 17 Mar 2023 18:26:05 -0000

Rob Wilton (rwilton) <rwilton@cisco.com> wrote:
    > description
    > "The status field contains information about the stability
    > of the allocation.  For each specific SID value, over time
    > it can only transition from unstable to stable,
    > and possibly from stable to obsolete.";

    > What happens to an unstable SID that is allocated during a development
    > version, but ends up not being needed in the stable published version:

    > (i) Is it okay for this SID to just be deleted?
    > (ii) Is it okay for this SID to be assigned to a different stable path?

Yes, and Yes.
The WG can revise the unstable SIDs in anyway it likes until we get to
"publication".  (I think that WGLC is that point for the IETF)

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