
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8366
Discuss this RFC: Send questions or comments to the mailing listanima@ietf.org
Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8366
This document defines a strategy to securely assign a pledge to anowner using an artifact signed, directly or indirectly, by thepledge's manufacturer. This artifact is known as a "voucher".
This document defines an artifact format as a YANG-defined JSONdocument that has been signed using a Cryptographic Message Syntax(CMS) structure. Other YANG-derived formats are possible. Thevoucher artifact is normally generated by the pledge's manufacturer(i.e., the Manufacturer Authorized Signing Authority (MASA)).
This document only defines the voucher artifact, leaving it to otherdocuments to describe specialized protocols for accessing it.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.