RFC 8240: Report from the Internet of Things Software Update (IoTSU) Workshop 2016
In plain English — editorial summary, not part of the RFC
This document provides a summary of the Internet of Things Software Update (IoTSU) Workshop that took place at Trinity College Dublin, Ireland on the 13th and 14th of June, 2016. The main goal of the workshop was to foster a discussion on requirements, challenges, and solutions for bringing software and firmware updates to IoT devices. This report summarizes the discussions and lists recommendations to the standards community. Note that this document is a report on the proceedings of the workshop. The views and positions documented in this report are those of the workshop participants and do not necessarily reflect IAB views and positions.
Document record
- Document ID
- RFC8240
- Published
- September 2017
- Authors
- H. Tschofenig; S. Farrell
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8576Internet of Things (IoT) Security: State of the Art and ChallengesCurrent
April 2019
- RFC 8628OAuth 2.0 Device Authorization GrantCurrent
August 2019
- RFC 7744Use Cases for Authentication and Authorization in Constrained EnvironmentsCurrent
January 2016
- RFC 7397Report from the Smart Object Security WorkshopCurrent
December 2014
- RFC 8752Report from the IAB Workshop on Exploring Synergy between Content Aggregation and the Publisher Ecosystem (ESCAPE)Current
March 2020
- RFC 7687Report from the Strengthening the Internet (STRINT) WorkshopCurrent
December 2015
- RFC 6574Report from the Smart Object WorkshopCurrent
April 2012
- RFC 2979Behavior of and Requirements for Internet FirewallsCurrent
October 2000
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?