RFC 5705: Keying Material Exporters for Transport Layer Security (TLS)
In plain English — editorial summary, not part of the RFC
A number of protocols wish to leverage Transport Layer Security (TLS) to perform key establishment but then use some of the keying material for their own purposes. This document describes a general mechanism for allowing that. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5705
- Published
- March 2010
- Authors
- E. Rescorla
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 7
- Also known as
- —
Topics
Referenced by
3 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 5697Other Certificates ExtensionCurrent
November 2009
- RFC 5723Internet Key Exchange Protocol Version 2 (IKEv2) Session ResumptionCurrent
January 2010
- RFC 5685Redirect Mechanism for the Internet Key Exchange Protocol Version 2 (IKEv2)Current
November 2009
- RFC 5739IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)Current
February 2010
- RFC 5746Transport Layer Security (TLS) Renegotiation Indication ExtensionCurrent
February 2010
- RFC 5749Distribution of EAP-Based Keys for Handover and Re-AuthenticationCurrent
March 2010
- RFC 5660IPsec Channels: Connection LatchingCurrent
October 2009
- RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted
January 2010
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?