RFC - 3546

Transport Layer Security (TLS) Extensions

Original:	ftp://ftp.isi.edu/in-notes/rfc3546.txt
Authors:	S. Blake-Wilson [BCI], M. Nystrom [RSA Security], D. Hopwood [Independent Consultant], J. Mikkelsen [Transactionware], T. Wright [Vodafone]
Date:	June 2003
Category:	Proposed Standard
This specification has been !!! obsoleted !!!

---

Obsoleted by:
RFC-4366prop	Transport Layer Security (TLS) Extensions

Updates:
RFC-2246prop	The TLS Protocol Version 1.0 (Obsoleted by RFC-4346prop) (Updated by RFC-3546prop)

Referred by:	10 RFC
Refers to:	13 RFC

---

Status

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].

---