RFC 6066 - TLS Extensions: Extension Definitions

Abstract

This document provides specifications for existing TLS extensions. It is a companion document for RFC 5246, "The Transport Layer Security (TLS) Protocol Version 1.2". The extensions specified are server_name, max_fragment_length, client_certificate_url, trusted_ca_keys, truncated_hmac, and status_request.

Document Information

• RFC Number: 6066
• Obsoletes: RFC 4366
• Category: Standards Track
• Published: January 2011
• Author: D. Eastlake 3rd (Huawei)

Status of This Memo

This is an Internet Standards Track document.

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6066.

Copyright Notice

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

This RFC consists of the following sections:

• 1. Introduction
• 2. Extensions to the Handshake Protocol
• 3. Server Name Indication
• 4. Maximum Fragment Length Negotiation
• 5. Client Certificate URLs
• 6. Trusted CA Indication
• 7. Truncated HMAC
• 8. Certificate Status Request
• 9. Error Alerts
• 10. IANA Considerations
• 11. Security Considerations
• 12. Normative References
• 13. Informative References
• Appendix A. Changes from RFC 4366
• Appendix B. Acknowledgements

Keywords

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 RFC 2119.

Related RFCs

• RFC 5246 - TLS 1.2 Protocol Specification
• RFC 4366 - TLS Extensions (obsoleted by this RFC)
• RFC 2560 - OCSP (Online Certificate Status Protocol)
• RFC 5890 - IDNA (Internationalized Domain Names in Applications)