Security Classes For Software Updates for IoT
draft-urien-suit-security-classes-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Pascal Urien | ||
| Last updated | 2019-10-23 (Latest revision 2019-04-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This draft attempts to define security classes for devices targeted by SUIT protocols. A device security is characterized by five Boolean security attributes: firmware loader (FLD), one time programmable memory (OTP), secure firmware loader (FLD-SEC), tamper resistant key (TRT-KEY) and diversified key (DIV-KEY). This classification creates 18 device classes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)