Michael Richardson <mcr+i...@sandelman.ca> wrote:
> * I will merge in the changes to ietf-voucher and ietf-voucher-request
from
> draft-ietf-anima-constrained-voucher. At which point, the document title
> will *really really* be wrong, since it won't even contain the voucher,
> just constrained-BRSKI. But, we fixed the title awhile ago.
> I propose to do this in -03, so one can see a clear progression of
changes.
I have merged the changes into to the -03 draft, which has just been posted.
(I hope that these baby steps are useful to people)
One thing that we could include at this point is a created-on/expired-on
(and last-renewal-date) encoded as an integer seconds since epoch.
(CBOR Tag 1)
YANG might look like:
leaf created-on-epoch {
type uint64;
mandatory false;
description
"A value in seconds since EPOCH (CBOR Tag 1) indicating
the date this voucher was created. This leaf replaces
created-on, and one of the two MUST be present.
This node is primarily for human consumption and auditing. ";
}
leaf expires-on-epoch {
type uint64;
must 'not(../expires-on)';
description
"A value in seconds since EPOCH (CBOR Tag 1) indicating
when this voucher expires. This leaf replaces expires-on.";
}
leaf last-renewal-date-epoch {
type uint64;
must '../expires-on';
description
"The date (in seconds since EPOCH) that the MASA projects
to be the last date it will renew a voucher on. This
field is merely informative; it is not processed by pledges.";
}
--
Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
