| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 15 Jul 2025 15:24:05 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95fa43c09e9be9c3-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5705 » RFC Editor
Search RFCs
RFC 5705
Keying Material Exporters for Transport Layer Security (TLS), March 2010
- File formats:
- Status:
- PROPOSED STANDARD
- Updated by:
- RFC 8446, RFC 8447
- Author:
- E. Rescorla
- Stream:
- IETF
- Source:
- tls (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5705
Discuss this RFC: Send questions or comments to the mailing list tls@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5705
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us