RFC 7452: Architectural Considerations in Smart Object Networking
In plain English — editorial summary, not part of the RFC
The term "Internet of Things" (IoT) denotes a trend where a large number of embedded devices employ communication services offered by Internet protocols. Many of these devices, often called "smart objects", are not directly operated by humans but exist as components in buildings or vehicles, or are spread out in the environment. Following the theme "Everything that can be connected will be connected", engineers and researchers designing smart object networks need to decide how to achieve this in practice. This document offers guidance to engineers designing Internet- connected smart objects.
Document record
- Document ID
- RFC7452
- Published
- March 2015
- Authors
- H. Tschofenig; J. Arkko; D. Thaler; D. McPherson
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6574Report from the Smart Object WorkshopCurrent
April 2012
- 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 9124A Manifest Information Model for Firmware Updates in Internet of Things (IoT) DevicesCurrent
January 2022
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?