[core] sid-status changes
Michael Richardson <mcr+ietf@sandelman.ca> Sun, 22 January 2023 04:41 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 45D70C15154E; Sat, 21 Jan 2023 20:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 Nv4LuubnGnty; Sat, 21 Jan 2023 20:41:05 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 3A84CC14E514; Sat, 21 Jan 2023 20:41:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 1CB0C3898E; Sun, 22 Jan 2023 00:10:26 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5zOqrtOjLRtS; Sun, 22 Jan 2023 00:10:21 -0500 (EST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id AD93C3898D; Sun, 22 Jan 2023 00:10:21 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1674364221; bh=Of81jtSMNHTejrx9V5CXyuZbZ5T/m028FpTWKzAR5jI=; h=From:to:Subject:In-Reply-To:References:Date:From; b=Q+ppcegt9ZTSZHcuCvQlcK7U5wClssu0ffqIrIaW9z5BFbBcCHULPWYzK+rHJyy/B 2iVCFuvBOodc8xBEXTlyWMjnIX3xwRbKLR+/FNREagO89mVVHUvclrLTuNDA5ShW8N Bqw1aW6SKGjJp++Da4AjqZUxT0mz1tZFrrfBb41q/kTfCt5oZ8LyY576pP+hXDEJmd jGNDIlsOjdWmfDhAz7sCeEQ2ZIgg2HhmztzR9KdwXGmaRuyIGK3QY5wkEnsFbVv7Yt 5WvptBypy3zIsxVCNQneUZ+osrOSeEbpOGqv4vZYDiJuB/Vh1I0Y8M4X4aAENjNJJz kmK5s3BuEBr9g==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2DEB39A; Sat, 21 Jan 2023 23:40:59 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>, "core@ietf.org" <core@ietf.org>, "draft-ietf-core-sid@ietf.org" <draft-ietf-core-sid@ietf.org>
In-Reply-To: <1027.1674355108@localhost>
References: <BY5PR11MB41968473A66546388638767BB5C79@BY5PR11MB4196.namprd11.prod.outlook.com> <1027.1674355108@localhost>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.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-sha512"; protocol="application/pgp-signature"
Date: Sat, 21 Jan 2023 23:40:59 -0500
Message-ID: <21181.1674362459@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/FNOFOPBfrjDPICGS8MWyzNXsVPs>
Subject: [core] sid-status changes
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: Sun, 22 Jan 2023 04:41:10 -0000
Hi, in followup to my proposed text that adds "status" to the sid file, here are some patches to pyang's sid.py: https://github.com/mbj4668/pyang/pull/845 Again, the proposed text: https://github.com/core-wg/yang-cbor/pull/141/files > After writing up the descriptive text, I then wondered if instead of > "unstable", we should write "provisional". I'm more convinced of this now. here is a sid file where everything is "unstable": https://github.com/mcr/pyang/blob/sid-item-status/test/test_sid/test-2-expected-toaster%402009-11-20.sid here is a sid file where things have been "finalized": https://github.com/mcr/pyang/blob/sid-item-status/test/test_sid/test-21-expected-toaster%402009-12-28.sid I probably need a test case where some things were finalized, and then more things were added. That shouldn't be hard, but I'd like to resolve "unstable" vs "provisional" first. -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
- [core] Review comments on draft-ietf-core-sid-19 Rob Wilton (rwilton)
- Re: [core] Review comments on draft-ietf-core-sid… Michael Richardson
- [core] sid-status changes Michael Richardson