RFC 9880: Semantic Definition Format (SDF) for Data and Interactions of Things
In plain English — editorial summary, not part of the RFC
The Semantic Definition Format (SDF) is a format for domain experts to use in the creation and maintenance of data and interaction models that describe Things, i.e., physical objects that are available for interaction over a network. An SDF specification describes definitions of SDF Objects/SDF Things and their associated interactions (Events, Actions, and Properties), as well as the Data types for the information exchanged in those interactions. Tools convert this format to database formats and other serializations as needed.
Document record
- Document ID
- RFC9880
- Published
- January 2026
- Authors
- M. Koster; C. Bormann; A. Keränen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 92
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9914Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
April 2026
- RFC 9940Some Key Terms for Network Fault and Problem ManagementCurrent
April 2026
- RFC 9820Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP)Current
September 2025
- RFC 9967System for Cross-Domain Identity Management (SCIM) Profile for Security Event Tokens (SETs)Current
May 2026
- RFC 9770Notification of Revoked Access Tokens in the Authentication and Authorization for Constrained Environments (ACE) FrameworkCurrent
June 2025
- RFC 9733BRSKI with Alternative Enrollment (BRSKI-AE)Current
March 2025
- RFC 9442Static Context Header Compression (SCHC) over Sigfox Low-Power Wide Area Network (LPWAN)Current
July 2023
- RFC 9441Static Context Header Compression (SCHC) Compound Acknowledgement (ACK)Current
July 2023
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?