RFC 9952: Application-Layer Protocol Negotiation (ALPN) ID for CoAP over DTLS
In plain English — editorial summary, not part of the RFC
This document specifies an Application-Layer Protocol Negotiation (ALPN) ID for Constrained Application Protocol (CoAP) services that are secured by DTLS.
Document record
- Document ID
- RFC9952
- Published
- March 2026
- Authors
- M. S. Lenders; C. Amsüss; T. C. Schmidt; M. Wählisch
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9953DNS over CoAP (DoC)Current
March 2026
- RFC 9876Updates to the IANA Registration Procedures for Constrained Application Protocol (CoAP) Content-FormatsCurrent
November 2025
- RFC 9443Multiplexing Scheme Updates for QUICCurrent
July 2023
- RFC 9423Constrained RESTful Environments (CoRE) Target Attributes RegistryCurrent
April 2024
- RFC 9290Concise Problem Details for Constrained Application Protocol (CoAP) APIsCurrent
October 2022
- RFC 9176Constrained RESTful Environments (CoRE) Resource DirectoryCurrent
April 2022
- RFC 9175Constrained Application Protocol (CoAP): Echo, Request-Tag, and Token ProcessingCurrent
February 2022
- RFC 8833Application-Layer Protocol Negotiation (ALPN) for WebRTCCurrent
January 2021
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?