Constrained firmware update problem statement
draft-richardson-fud-constrained-update-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Michael Richardson | ||
| Last updated | 2017-10-18 (Latest revision 2017-04-16) | ||
| 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 document details the problems of upgrading small devices that need complete firmware replacements, but which do not have enough storage to keep an entire copy of the replacement image. In addition to detailing the specific challenge, a conceptual architecture for a solution is posited involving use of DTLS session resumption tickets with CoAP Block Transfer mode.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)