RFC 4680: TLS Handshake Message for Supplemental Data
In plain English — editorial summary, not part of the RFC
This specification defines a TLS handshake message for exchange of supplemental application data. TLS hello message extensions are used to determine which supplemental data types are supported by both the TLS client and the TLS server. Then, the supplemental data handshake message is used to exchange the data. Other documents will define the syntax of these extensions and the syntax of the associated supplemental data types. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4680
- Published
- October 2006
- Authors
- S. Santesson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 4346
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4681TLS User Mapping ExtensionUpdated
October 2006
- RFC 4934Extensible Provisioning Protocol (EPP) Transport Over TCPObsoleted
May 2007
- RFC 5018Connection Establishment in the Binary Floor Control Protocol (BFCP)Updated
September 2007
- RFC 5054Using the Secure Remote Password (SRP) Protocol for TLS AuthenticationUpdated
November 2007
- RFC 4217Securing FTP with TLSUpdated
October 2005
- RFC 4169Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2Current
November 2005
- RFC 5288AES Galois Counter Mode (GCM) Cipher Suites for TLSUpdated
August 2008
- RFC 5289TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)Updated
August 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?