Secure Reporting of Update Status
draft-moran-suit-report-01
| Document | Type |
Replaced Internet-Draft
(suit WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Brendan Moran | ||
| Last updated | 2021-05-25 (Latest revision 2021-02-22) | ||
| Replaced by | draft-ietf-suit-report | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-suit-report | |
| Consensus boilerplate | Unknown | ||
| 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
The Software Update for the Internet of Things (SUIT) manifest provides a way for many different update and boot workflows to be described by a common format. However, this does not provide a feedback mechanism for developers in the event that an update or boot fails. This specification describes a lightweight feedback mechanism that allows a developer in possession of a manifest to reconstruct the decisions made and actions performed by a manifest processor.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)