Re: [Yot] questions concerning sid value assignments

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 20 February 2018 12:36 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 B01D7127333 for <yot@ietfa.amsl.com>; Tue, 20 Feb 2018 04:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] 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 6Pgg66GG65dt for <yot@ietfa.amsl.com>; Tue, 20 Feb 2018 04:36:09 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01DF3124D6C for <yot@ietf.org>; Tue, 20 Feb 2018 04:36:08 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5801020091; Tue, 20 Feb 2018 07:43:25 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CC16C80C60; Tue, 20 Feb 2018 07:36:06 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: consultancy@vanderstok.org
cc: Michel Veillette <Michel.Veillette@trilliant.com>, "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, Kent Watsen <kwatsen@juniper.net>, yot@ietf.org
In-Reply-To: <2860bc3620106db0d1ad1317582a7c27@xs4all.nl>
References: <faa44e95aa561876f119edc7358fd118@xs4all.nl> <26096.1518551413@obiwan.sandelman.ca> <9e0d297ad888a36e16921d10873cc947@xs4all.nl> <BN6PR06MB23082D66ED7486BDA002B1DBFEF50@BN6PR06MB2308.namprd06.prod.outlook.com> <eaccba06f07bc88eac32285fb8880f06@xs4all.nl> <22cc48128046319c662c116bcc39d761@xs4all.nl> <BN6PR06MB2308E44C22598B405243060F9AC80@BN6PR06MB2308.namprd06.prod.outlook.com> <2860bc3620106db0d1ad1317582a7c27@xs4all.nl>
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
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 20 Feb 2018 07:36:06 -0500
Message-ID: <31028.1519130166@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/zStRdLicVNZHjEu9ycM-c9qfKs0>
Subject: Re: [Yot] questions concerning sid value assignments
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: Tue, 20 Feb 2018 12:36:11 -0000

peter van der Stok <stokcons@xs4all.nl> wrote:
    > thanks for the rectifications; will work out the example better for the
    > draft.
    > But it served its purpose.

    >> Example:
    >> {
    >> 1001001: {
    >> +2 : "2016-10-07T19:31:42Z",  / SID = 1001003, created-on /
    >> +4 : "2016-10-21T19:31:42Z",  / SID = 1001005, expires-on /
    >> +1 : "verified",              / SID = 1001002, assertion /
    >> +10 : "JADA123456789",        / SID = 1001011, serial-number /
    >> +5 : h'0102030405060708090A0B0C0D0F',  / SID = 1001006, idevid-issuer /
    >> +8 : h'0102030405060708090A0B0C0D0F',  / SID = 1001009,
    >> pinned-domain-cert /
    >> +3 : true,                    / SID = 1001004,
    >> domain-cert-revocation-checks /
    >> +6 : "2017-10-07T19:31:42Z"   / SID = 1001007, last-renewal-date /
    >> }
    >> }
    >> 
    >> About "when using comi to return the value"
    >> 
    >> Currently, these YANG files don't define any data nodes which can be
    >> instantiated in a datastore.

    > This is an unexpected turn of events.
    > in ietf-voucher there is voucher container defined.
    > but the grouping makes sure that it is only a schema node and not a data
    > node.

Is there something we can/should change in ietf-voucher so that they do
define data nodes?  We aren't in AUTH48 yet.

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