Thanks, just one small change, the refinement of "voucher/pinned-domain-cert"
should read:
refine "voucher/pinned-domain-cert" {
mandatory false;
description "A pinned-domain-cert field
is not valid in a voucher request, and
any occurrence MUST be ignored";
}
Best regards
Thomas
-----Ursprüngliche Nachricht-----
Von: Michael Richardson <[email protected]>
Gesendet: Montag, 31. August 2020 22:01
An: [email protected]
Cc: Werner, Thomas (CT RDA CST SEA-DE) <[email protected]>
Betreff: Re: BRSKI#43, Figure 5 YANG Tree diagram for Voucher-Request
Thomas has pointed out that the "pinned-domain-cert" and "last-renewal-date"
fields which are defined in RFC8366 are not clearly specified for the
voucher-request.
Neither are needed or appropriate in a voucher-request.
I have edited the YANG to include:
refine "voucher/pinned-domain-cert" {
mandatory false;
description "A voucher-request field
is not valid in a voucher request, and
any occurrence MUST be ignored";
}
refine "voucher/last-renewal-date" {
description "A last-renewal-date field
is not valid in a voucher request, and
any occurrence MUST be ignored";
}
This is, I think, an editorial change.
--
Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6
IoT consulting =-
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima
