IETF Logo Mail Archive

Re: [Yot] questions concerning sid value assignments

peter van der Stok <stokcons@xs4all.nl> Tue, 20 February 2018 12:50 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 DD157127522 for <yot@ietfa.amsl.com>; Tue, 20 Feb 2018 04:50:50 -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 kE4j5yw1biqM for <yot@ietfa.amsl.com>; Tue, 20 Feb 2018 04:50:48 -0800 (PST)
Received: from lb1-smtp-cloud9.xs4all.net (lb1-smtp-cloud9.xs4all.net [194.109.24.22]) (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 A47F0127342 for <yot@ietf.org>; Tue, 20 Feb 2018 04:50:48 -0800 (PST)
Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:216]) by smtp-cloud9.xs4all.net with ESMTPA id o7NeeJKDooWCOo7Neeka8f; Tue, 20 Feb 2018 13:50:46 +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); Tue, 20 Feb 2018 13:50:46 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Tue, 20 Feb 2018 13:50:46 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: consultancy@vanderstok.org, Michel Veillette <Michel.Veillette@trilliant.com>, "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: <31028.1519130166@obiwan.sandelman.ca>
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>
Message-ID: <dd7093eb11fbb723d2d6a98cec15fa75@xs4all.nl>
X-Sender: stokcons@xs4all.nl
User-Agent: XS4ALL Webmail
X-CMAE-Envelope: MS4wfBuP3Hd3UB8SW2tIC36K10C8XkvRirpufjpxDLR7cwMgDIIqrpwOgAN9ozgtgZTXtvsYmovPBTd+o9k57y1S0eB9yK7Qp8CK37kpjDmUyxcD+XgrF2/b xrWuGooAP+7kdoL1xquNJ/3f5rAXcsr55a7nvmlk6rCXhsLe2JhKp5z9EDdJjGOK9H1nlxmABSi2nLzGxGuROYQzICfIzE4DJzjUuOIyhZRYuh8lsZpES8Dn ardF5EZf2Et7FPbI9Arhx5Nt5y0snDdKrqvHZAxw/jbru4ljVVJPUSjQqc7n9fIiacd4luK7tI+XCV7AVdGkdw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/58Xu55UNlDeRGjqkWFrJFxa2gzM>
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:50:51 -0000

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

I don't think that is needed.
As far as I remember the GROUPING was added to allow easy updates.
The consequence is that data node which use the voucher must be defined 
to specify storage of the voucher(s) in the server. Values of these 
nodes can be retrieved by RESTCONF, NETCONF of CoMI.

Peter

v2.23.0 | Report a Bug | By Email