Skip to main content

Bootstrapping Remote Secure Key Infrastructure (BRSKI)
RFC 8995

Revision differences

Document history

Date By Action
2021-10-20
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2021-07-14
(System) Received changes through RFC Editor sync (added Errata tag)
2021-05-26
(System) IANA registries were updated to include RFC8995
2021-05-21
(System)
Received changes through RFC Editor sync (created alias RFC 8995, changed title to 'Bootstrapping Remote Secure Key Infrastructure (BRSKI)', changed abstract to 'This document …
Received changes through RFC Editor sync (created alias RFC 8995, changed title to 'Bootstrapping Remote Secure Key Infrastructure (BRSKI)', changed abstract to 'This document specifies automated bootstrapping of an Autonomic Control Plane.  To do this, a Secure Key Infrastructure is bootstrapped.  This is done using manufacturer-installed X.509 certificates, in combination with a manufacturer's authorizing service, both online and offline.  We call this process the Bootstrapping Remote Secure Key Infrastructure (BRSKI) protocol.  Bootstrapping a new device can occur when using a routable address and a cloud service, only link-local connectivity, or limited/disconnected networks.  Support for deployment models with less stringent security requirements is included.  Bootstrapping is complete when the cryptographic identity of the new key infrastructure is successfully deployed to the device.  The established secure connection can be used to deploy a locally issued certificate to the device as well.', changed pages to 116, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-05-21, changed IESG state to RFC Published)
2021-05-21
(System) RFC published