Subject: Re: [Yot] SID values for voucher

From: Michael Richardson <[email-masked]>
Date: Thu, 15 Feb 2018 10:44:17 -0500

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 <[email-masked]> 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 <[email-masked]>, Sandelman Software Works
 -= IPv6 IoT consulting =-