RFC 3546 (rfc3546) - Page 1 of 29
Transport Layer Security (TLS) Extensions
Alternative Format: Original Text Document
Network Working Group S. Blake-Wilson
Request for Comments: 3546 BCI
Updates: 2246 M. Nystrom
Category: Standards Track RSA Security
D. Hopwood
Independent Consultant
J. Mikkelsen
Transactionware
T. Wright
Vodafone
June 2003
Transport Layer Security (TLS) Extensions
Status of this Memo
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 "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
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 1.0 clients that support the extensions and TLS 1.0
servers that do not support the extensions, and vice versa.
Conventions used in this Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[KEYWORDS].
Blake-Wilson, et. al. Standards Track