Transport Layer Security Extensions
RFC 4366, “Transport Layer Security Extensions”, is a Proposed Standard document published in April 2006 by S. Blake-Wilson, M. Nystrom, D. Hopwood, J. Mikkelsen, T. Wright. It updates RFC 4346. It obsoletes RFC 3546. It has since been updated by RFC 5746. It has been obsoleted by RFC 5246, RFC 6066 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4366 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4365 Applicability Statement for BGP/MPLS IP Virtual Private Networks
- RFC 4367 What's in a Name: False Assumptions about DNS Names
- RFC 4364 BGP/MPLS IP Virtual Private Networks
- RFC 4368 Multiprotocol Label Switching Label-Controlled Asynchronous Transfer Mode and Frame-Relay Management Interface Definition
- RFC 4363 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions
- RFC 4369 Definitions of Managed Objects for Internet Fibre Channel Protocol
- RFC 4362 RObust Header Compression : A Link-Layer Assisted Profile for IP/UDP/RTP
- RFC 4370 Lightweight Directory Access Protocol Proxied Authorization Control