Transport Layer Security (TLS) Extensions
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 30
- 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]
- Publication Date
- 2006-04-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4366- Link
- https://doi.org/10.17487/RFC4366
- Author(s)
- Simon Blake-WilsonMagnus NyströmDavid HopwoodJan MikkelsenTim Wright
- Keyword(s)
- TLS, Authentication, Privacy
Latest version of IETF RFC 4366
Document Versions — IETF RFC 4366
-
▶ IETF RFC 4366 (2006-04-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
- ISO.9594-8.2001 — X509-4th-TC1 EXTERNAL
- IETF RFC 2104 [Active, Amended*]
- IETF RFC 2119 [Active*]
- IETF RFC 2246 [Superseded*]
- IETF RFC 2434 [Superseded*]
- IETF RFC 2560 [Superseded*]
- IETF RFC 2585 [Active*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 3280 [Superseded*]
- IETF RFC 3490 [Superseded*]
- IETF RFC 3629 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 4346 [Superseded*]
Bibliographic Reference(s)
- J. Mikkelsen, R. Eberhard, and J. Kistler, "General ClientHello extension mechanism and virtual hosting," ietf-tls mailing list posting, August 14, 2000. EXTERNAL
- IETF RFC 2712 [Active*]
- IETF RFC 3268 [Superseded*]
- IETF RFC 3546 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4366.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4366, Transport Layer Security (TLS) Extensions. Available at https://doi.org/10.17487/RFC4366
Snippet:
IETF RFC 4366, Transport Layer Security (TLS) Extensions. Available at https://doi.org/10.17487/RFC4366
HTML (ISO 690 compliant)
Preview:
IETF RFC 4366, Transport Layer Security (TLS) Extensions. Available at https://doi.org/10.17487/RFC4366
Snippet:
<span class="citation"><cite>IETF RFC 4366</cite>, Transport Layer Security (TLS) Extensions. Available at <a href="https://doi.org/10.17487/RFC4366" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4366</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4366, Transport Layer Security (TLS) Extensions
doi: 10.17487/RFC4366
url: https://doi.org/10.17487/RFC4366
doi: 10.17487/RFC4366
url: https://doi.org/10.17487/RFC4366
Snippet:
<li> <cite id="bib-rfc4366">IETF RFC 4366</cite>, Transport Layer Security (TLS) Extensions <span class="doi">10.17487/RFC4366</span> </li>
Referenced By
- IETF RFC 4492 [Superseded*]
- IETF RFC 4507 [Superseded*]
- IETF RFC 4642 [Active*]
- IETF RFC 4680 [Active*]
- IETF RFC 4681 [Active*]
- IETF RFC 4975 [Active*]
- IETF RFC 4976 [Active*]
- IETF RFC 5019 [Superseded*]
- IETF RFC 5054 [Active*]
- IETF RFC 5077 [Superseded*]
- IETF RFC 5081 [Superseded*]
- IETF RFC 5216 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 5281 [Active*]
- IETF RFC 5288 [Active*]
- IETF RFC 5878 [Active*]
- IETF RFC 5922 [Active*]
- IETF RFC 5953 [Superseded*]
- IETF RFC 6353 [Active*]
- IETF RFC 6709 [Active*]
- IETF RFC 8422 [Superseded*]
- IETF RFC 8446 [Superseded*]
- IETF RFC 8447 [Active*]
- IETF RFC 8996 [Active*]