RFC 9146: Connection Identifier for DTLS 1.2
In plain English — editorial summary, not part of the RFC
This document specifies the Connection ID (CID) construct for the Datagram Transport Layer Security (DTLS) protocol version 1.2. A CID is an identifier carried in the record layer header that gives the recipient additional information for selecting the appropriate security association. In "classical" DTLS, selecting a security association of an incoming DTLS record is accomplished with the help of the 5-tuple. If the source IP address and/or source port changes during the lifetime of an ongoing DTLS session, then the receiver will be unable to locate the correct security context. The new ciphertext record format with the CID also provides content type encryption and record layer padding. This document updates RFC 6347.
Document record
- Document ID
- RFC9146
- Published
- March 2022
- Authors
- E. Rescorla; H. Tschofenig; T. Fossati; A. Kraus
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 14
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9147The Datagram Transport Layer Security (DTLS) Protocol Version 1.3Updated
April 2022
- RFC 9148EST-coaps: Enrollment over Secure Transport with the Secure Constrained Application ProtocolUpdated
April 2022
- RFC 9149TLS Ticket RequestsCurrent
April 2022
- RFC 9142Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)Current
January 2022
- RFC 9140Nimble Out-of-Band Authentication for EAP (EAP-NOOB)Updated
December 2021
- RFC 9155Deprecating MD5 and SHA-1 Signature Hashes in TLS 1.2 and DTLS 1.2Current
December 2021
- RFC 9158Update to the Object Identifier Registry for the PKIX Working GroupCurrent
November 2021
- RFC 9133Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal ChannelCurrent
September 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?