RFC 7925: Transport Layer Security (TLS) / Datagram Transport Layer Security (DTLS) Profiles for the Internet of Things
In plain English — editorial summary, not part of the RFC
A common design pattern in Internet of Things (IoT) deployments is the use of a constrained device that collects data via sensors or controls actuators for use in home automation, industrial control systems, smart cities, and other IoT deployments. This document defines a Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) 1.2 profile that offers communications security for this data exchange thereby preventing eavesdropping, tampering, and message forgery. The lack of communication security is a common vulnerability in IoT products that can easily be solved by using these well-researched and widely deployed Internet security protocols.
Document record
- Document ID
- RFC7925
- Published
- July 2016
- Authors
- H. Tschofenig; T. Fossati
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 61
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8628OAuth 2.0 Device Authorization GrantCurrent
August 2019
- RFC 9140Nimble Out-of-Band Authentication for EAP (EAP-NOOB)Updated
December 2021
- RFC 9528Ephemeral Diffie-Hellman Over COSE (EDHOC)Current
March 2024
- RFC 8520Manufacturer Usage Description SpecificationCurrent
March 2019
- RFC 9668Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE)Current
November 2024
- RFC 9726Operational Considerations for Use of DNS in Internet of Things (IoT) DevicesCurrent
March 2025
- RFC 7924Transport Layer Security (TLS) Cached Information ExtensionCurrent
July 2016
- RFC 7929DNS-Based Authentication of Named Entities (DANE) Bindings for OpenPGPCurrent
August 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?