RFC 4366
Transport Layer Security (TLS) Extensions, April 2006
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 3546
- Obsoleted by:
- RFC 5246, RFC 6066
- Updates:
- RFC 4346
- Updated by:
- RFC 5746
- Authors:
- S. Blake-Wilson
M. Nystrom
D. Hopwood
J. Mikkelsen
T. Wright - Stream:
- IETF
- Source:
- tls (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4366
Discuss this RFC: Send questions or comments to the mailing list [email protected]
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4366
Abstract
This document describes extensions that may be used to add functionality to Transport Layer Security (TLS). It provides both generic extension mechanisms for the TLS handshake client and server hellos, and specific extensions using these generic mechanisms.
The extensions may be used by TLS clients and servers. The extensions are backwards compatible: communication is possible between TLS clients that support the extensions and TLS servers that do not support the extensions, and vice versa. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.