IETF Logo Mail Archive

Re: [Yot] questions concerning sid value assignments

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 21 February 2018 22:41 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 B63A112AAB6 for <yot@ietfa.amsl.com>; Wed, 21 Feb 2018 14:41:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 n19PZNL31NQl for <yot@ietfa.amsl.com>; Wed, 21 Feb 2018 14:41:43 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2619B12D9FE for <yot@ietf.org>; Wed, 21 Feb 2018 14:41:43 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 42E4F20091; Wed, 21 Feb 2018 17:49:05 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D24AA806C2; Wed, 21 Feb 2018 17:41:41 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: consultancy@vanderstok.org, yot@ietf.org
cc: Michel Veillette <Michel.Veillette@trilliant.com>, "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, Kent Watsen <kwatsen@juniper.net>
In-Reply-To: <6afbd40d69fb2b9f8d6f241d3b7fb656@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> <31028.1519130166@obiwan.sandelman.ca> <BN6PR06MB2308D4824A16F3C1D0A59A349ACF0@BN6PR06MB2308.namprd06.prod.outlook.com> <6afbd40d69fb2b9f8d6f241d3b7fb656@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: Wed, 21 Feb 2018 17:41:41 -0500
Message-ID: <6537.1519252901@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/zerCTvJa6nU27pLCAjKEN9Shaqs>
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 22:41:45 -0000

peter van der Stok <stokcons@xs4all.nl> wrote:
    > Sorry, some problems interpreting your answer

I think that some of the concerns are irrelevant to data-at-reset.

    >> 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?

My discussion with Kent on Tuesday suggests that he doesn't think that there
is anything that needs adjusting. I just want to be sure.

    >> You also need to determine if meta information need to be added (e.g.
    >> 'timestamp', 'accepted/rejected').

    > That information is in the voucher. (@Michael?)

Yeah, that's all in the augment.

    >> 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.

Exactly: it's all data at rest at this point.
as in:  https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-data-ext/

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

v2.23.0 | Report a Bug | By Email