RFC 6574: Report from the Smart Object Workshop
In plain English — editorial summary, not part of the RFC
This document provides an overview of a workshop held by the Internet Architecture Board (IAB) on 'Interconnecting Smart Objects with the Internet'. The workshop took place in Prague on 25 March 2011. The main goal of the workshop was to solicit feedback from the wider community on their experience with deploying IETF protocols in constrained environments. This report summarizes the discussions and lists the conclusions and recommendations to the Internet Engineering Task Force (IETF) 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. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6574
- Published
- April 2012
- Authors
- H. Tschofenig; J. Arkko
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7397Report from the Smart Object Security WorkshopCurrent
December 2014
- RFC 7641Observing Resources in the Constrained Application Protocol (CoAP)Updated
September 2015
- RFC 8628OAuth 2.0 Device Authorization GrantCurrent
August 2019
- RFC 7452Architectural Considerations in Smart Object NetworkingCurrent
March 2015
- RFC 8240Report from the Internet of Things Software Update (IoTSU) Workshop 2016Current
September 2017
- RFC 7228Terminology for Constrained-Node NetworksCurrent
May 2014
- RFC 74006LoWPAN-GHC: Generic Header Compression for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)Current
November 2014
- RFC 7744Use Cases for Authentication and Authorization in Constrained EnvironmentsCurrent
January 2016
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?