RFC 6358: Additional Master Secret Inputs for TLS
In plain English — editorial summary, not part of the RFC
This document describes a mechanism for using additional master secret inputs with Transport Layer Security (TLS) and Datagram TLS (DTLS). This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6358
- Published
- January 2012
- Authors
- P. Hoffman
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 4
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7457Summarizing Known Attacks on Transport Layer Security (TLS) and Datagram TLS (DTLS)Current
February 2015
- RFC 7525Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Obsoleted
May 2015
- RFC 5027Security Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
October 2007
- RFC 9662Updates to the Cipher Suites in Secure SyslogCurrent
October 2024
- RFC 6353Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)Updated
July 2011
- RFC 6367Addition of the Camellia Cipher Suites to Transport Layer Security (TLS)Updated
September 2011
- RFC 6347Datagram Transport Layer Security Version 1.2Obsoleted
January 2012
- RFC 6394Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)Current
October 2011
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?