A new Request for Comments is now available in online RFC libraries.
RFC 9146
Title: Connection Identifier for DTLS 1.2
Author: E. Rescorla, Ed.,
H. Tschofenig, Ed.,
T. Fossati,
A. Kraus
Status: Standards Track
Stream: IETF
Date: March 2022
Mailbox: [email protected],
[email protected],
[email protected],
[email protected]
Pages: 14
Updates: RFC 6347
I-D Tag: draft-ietf-tls-dtls-connection-id-13.txt
URL: https://www.rfc-editor.org/info/rfc9146
DOI: 10.17487/RFC9146
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.
This document is a product of the Transport Layer Security Working Group of the
IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
TLS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tls
