RFC 8366: A Voucher Artifact for Bootstrapping Protocols
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8366
- Published
- May 2018
- Authors
- K. Watsen; M. Richardson; M. Pritikin; T. Eckert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8995Bootstrapping Remote Secure Key Infrastructure (BRSKI)Current
May 2021
- RFC 8368Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM)Current
May 2018
- RFC 8990GeneRic Autonomic Signaling Protocol (GRASP)Current
May 2021
- RFC 8991GeneRic Autonomic Signaling Protocol Application Program Interface (GRASP API)Current
May 2021
- RFC 8993A Reference Model for Autonomic NetworkingCurrent
May 2021
- RFC 8994An Autonomic Control Plane (ACP)Current
May 2021
- RFC 8992Autonomic IPv6 Edge Prefix Management in Large-Scale NetworksCurrent
May 2021
- RFC 9222Guidelines for Autonomic Service AgentsCurrent
March 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?