A Voucher Artifact for Bootstrapping Protocols
RFC 8366

Received changes through RFC Editor sync (changed abstract to 'This document defines a strategy to securely assign a pledge to an owner using an artifact signed, directly or indirectly, by the pledge's manufacturer. This artifact is known as a "voucher".

This document defines an artifact format as a YANG-defined JSON document that has been signed using a Cryptographic Message Syntax (CMS) structure. Other YANG-derived formats are possible. The voucher 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 other documents to describe specialized protocols for accessing it.')

Received changes through RFC Editor sync (changed abstract to 'This document defines a strategy to securely assign a pledge to an
owner using an artifact signed, directly or indirectly, by the
pledge's manufacturer.  This artifact is known as a "voucher".  This document defines an artifact format as a YANG-defined JSON
document that has been signed using a Cryptographic Message Syntax
(CMS) structure.  Other YANG-derived formats are possible.  The
voucher 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 other
documents to describe specialized protocols for accessing it.')

Received changes through RFC Editor sync (created alias RFC 8366, changed title to 'A Voucher Artifact for Bootstrapping Protocols', changed abstract to 'This document defines a strategy to securely assign a pledge to an owner using an artifact signed, directly or indirectly, by the pledge's manufacturer. This artifact is known as a "voucher".', changed pages to 23, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-05-09, changed IESG state to RFC Published)