Re: [Yot] questions concerning sid value assignments
peter van der Stok <stokcons@xs4all.nl> Wed, 21 February 2018 08:23 UTC
Return-Path: <stokcons@xs4all.nl>
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 D5AAE12E882 for <yot@ietfa.amsl.com>; Wed, 21 Feb 2018 00:23:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 omv5VHISpXsu for <yot@ietfa.amsl.com>; Wed, 21 Feb 2018 00:23:31 -0800 (PST)
Received: from lb2-smtp-cloud7.xs4all.net (lb2-smtp-cloud7.xs4all.net [194.109.24.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34BF012D7EA for <yot@ietf.org>; Wed, 21 Feb 2018 00:23:30 -0800 (PST)
Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:195]) by smtp-cloud7.xs4all.net with ESMTPA id oPgUeCQXS3A62oPgUeagyc; Wed, 21 Feb 2018 09:23:29 +0100
Received: from AMontpellier-654-1-186-134.w92-145.abo.wanadoo.fr ([92.145.165.134]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Wed, 21 Feb 2018 09:23:26 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Wed, 21 Feb 2018 09:23:26 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: Michel Veillette <Michel.Veillette@trilliant.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, consultancy@vanderstok.org, "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, Kent Watsen <kwatsen@juniper.net>, yot@ietf.org
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <BN6PR06MB2308D4824A16F3C1D0A59A349ACF0@BN6PR06MB2308.namprd06.prod.outlook.com>
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> <31028.1519130166@obiwan.sandelman.ca> <BN6PR06MB2308D4824A16F3C1D0A59A349ACF0@BN6PR06MB2308.namprd06.prod.outlook.com>
Message-ID: <6afbd40d69fb2b9f8d6f241d3b7fb656@xs4all.nl>
X-Sender: stokcons@xs4all.nl
User-Agent: XS4ALL Webmail
X-CMAE-Envelope: MS4wfHpCuUlbfHTTZFq6/7HADInRj5FDsikl/ZLuH5rMbAQdP/75fmEd74sJGfB6JKNeln585z4usva7Gvf/rXRohmvxq66bL97zZE1gTYIUgfrKClARO444 DeXMimVYsi6Q+rauYKKoQEBLLvaDGTqLTsrR+obGSFOX7FdkWnZxZbuaRZjjHaX7ljrDMEEivG++1qIuqbLOK0SIqxcbPeQa6Rprq1Dpdpa3g9Nu+xlr27vj HW73myUAF2gS1AkBhRWY+iqCRGRN7gxqJxPrlKta7wNsh07SAZhQMKYC4qvvDwpyqoPenreoPR2xR4E4y49ttA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/jfu6J_EGWYUtV6tW6Y-iPh2u200>
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: Wed, 21 Feb 2018 08:23:34 -0000
Hi Michel, Sorry, some problems interpreting your answer Michel Veillette schreef op 2018-02-20 16:59: > Hi Michael > > " Is there something we can/should change in ietf-voucher so that they > do define data nodes?" > > You first need to determine which voucher you want to make available > in the datastore. What do you mean? a cwt-voucher or a voucher; OR how to derive cwt-voucher from voucher; OR having a mailbox of vouchers? > Last received, last sent, a list of the last x received. May be, that is not a voucher problem but application specific?? > You also need to determine if meta information need to be added (e.g. > 'timestamp', 'accepted/rejected'). That information is in the voucher. (@Michael?) > Once done, you just need to add a container or list based on the > grouping already defined. This I understand if you want to use, NETCOF, RESTCONF or CoMI, but is not necessary if we only talk serialization of the voucher. > This new definition(s) should be included in an optional feature. Here I am lost again > > Regards, > Michel Thanks for your efforts, but probably I don't understand their purpose. Peter > > -----Original Message----- > From: Michael Richardson [mailto:mcr+ietf@sandelman.ca] > Sent: Tuesday, February 20, 2018 7:36 AM > 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 > Subject: Re: questions concerning sid value assignments > > > 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 =-
- Re: [Yot] questions concerning sid value assignme… Michel Veillette
- Re: [Yot] questions concerning sid value assignme… peter van der Stok
- Re: [Yot] questions concerning sid value assignme… peter van der Stok
- Re: [Yot] questions concerning sid value assignme… Michael Richardson
- Re: [Yot] questions concerning sid value assignme… peter van der Stok
- Re: [Yot] questions concerning sid value assignme… peter van der Stok
- Re: [Yot] questions concerning sid value assignme… Michael Richardson
- Re: [Yot] questions concerning sid value assignme… peter van der Stok
- Re: [Yot] questions concerning sid value assignme… Michel Veillette
- Re: [Yot] questions concerning sid value assignme… Michel Veillette
- Re: [Yot] questions concerning sid value assignme… Michael Richardson
- Re: [Yot] questions concerning sid value assignme… peter van der Stok
- Re: [Yot] questions concerning sid value assignme… peter van der Stok
- Re: [Yot] questions concerning sid value assignme… Michel Veillette
- Re: [Yot] questions concerning sid value assignme… Michael Richardson