Dear all, In draft-ietf-anima-bootstrapping-keyinfra-16 the "assertion" field seems mandatory in a voucher request by the Pledge, looking at Section 3.1 and the YANG definition. But one example of a possible value in the voucher request is "TBD" in Section 3.2. This doesn't appear in the allowed assertion strings by RFC 8366, so should this be fixed in the text? Maybe "logged" is intended there?
In general what types of assertions could a Pledge use if not "proximity"? The RFC 8366 descriptions are all written with a voucher in mind, not a voucher request. Perhaps the BRSKI document could detail this aspect more - if not described elsewhere at least. Best regards Esko Dijk
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
