Re: [Yot] SID values for voucher

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 15 February 2018 15:44 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 B3252127876 for <yot@ietfa.amsl.com>; Thu, 15 Feb 2018 07:44:20 -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 jI3Jt_x5_tlW for <yot@ietfa.amsl.com>; Thu, 15 Feb 2018 07:44:19 -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 E1BF7126BF6 for <yot@ietf.org>; Thu, 15 Feb 2018 07:44:18 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 759B120090; Thu, 15 Feb 2018 10:51:19 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DBD9280706; Thu, 15 Feb 2018 10:44:17 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: yot@ietf.org, consultancy@vanderstok.org
cc: Michel Veillette <Michel.Veillette@trilliantinc.com>
In-Reply-To: <09bfd7ea51f37d8e5f3cbe5baf37fda5@xs4all.nl>
References: <4f1149d42c4a0c1844c47e73f67df5c3@xs4all.nl> <BN6PR06MB23086B84740062597DB9F52AFEF70@BN6PR06MB2308.namprd06.prod.outlook.com> <4a8b31bbccdd72e299b1100258162f82@xs4all.nl> <BN6PR06MB230809C9EDDB171E831D38D2FEF60@BN6PR06MB2308.namprd06.prod.outlook.com> <20540.1518550077@obiwan.sandelman.ca> <BN6PR06MB230869497B807239C4B69D68FEF60@BN6PR06MB2308.namprd06.prod.outlook.com> <09bfd7ea51f37d8e5f3cbe5baf37fda5@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: Thu, 15 Feb 2018 10:44:17 -0500
Message-ID: <11348.1518709457@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/8-Z7B_0HjWuOXLS9galJGYiQ0Ss>
Subject: Re: [Yot] SID values for voucher
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: Thu, 15 Feb 2018 15:44:21 -0000

In draft-richardson-anima-constrained-voucher, we are deriving
(via augment) two objects:
     ietf-cwt-voucher
     ietf-cwt-voucher-request

From the YANG model created in draft-ietf-anima-voucher ("ietf-voucher").
The two models are very similiar, but not identical in what they add.
The common pieces from ietf-voucher are semantically equivalent.
For instance, there is a "created-on" attribute in both.

So do we wind up with different SID value for ietf-cwt-voucher.created-on
than for ietf-cwt-voucher-request.created-on.

Code wise, having the same value is easier, until someone wants to do
something where the semantics are slight different.  But perhaps that's
not a bug, if the semantics change, the SID value should change.


peter van der Stok <stokcons@xs4all.nl> wrote:
    >> As mentioned earlier, the removal to the grouping in 'ietf-voucher' is
    >> not required.

    >> Assuming we keep 'ietf-voucher' the way it is, your have two options :
    >> - The first option consists of performing an augment of the grouping

    >> and creating a YANG template with it (Test1).
    >> - The second option consists of performing an augment of the
    >> 'voucher-artifact' template (Test 2)

    >>
    >> The first option create a completely new template with 12 consecutive SIDs.
    >> The second option create an augment of the original 'voucher-artifact'
    >> template with 1 extra SID.

    > We agree here completely




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