RFC 3436: Transport Layer Security over Stream Control Transmission Protocol
In plain English — editorial summary, not part of the RFC
This document describes the usage of the Transport Layer Security (TLS) protocol, as defined in RFC 2246, over the Stream Control Transmission Protocol (SCTP), as defined in RFC 2960 and RFC 3309. The user of TLS can take advantage of the features provided by SCTP, namely the support of multiple streams to avoid head of line blocking and the support of multi-homing to provide network level fault tolerance. Additionally, discussions of extensions of SCTP are also supported, meaning especially the support of dynamic reconfiguration of IP- addresses. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3436
- Published
- December 2002
- Authors
- A. Jungmaier; E. Rescorla; M. Tuexen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 9
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3708Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious RetransmissionsCurrent
February 2004
- RFC 3758Stream Control Transmission Protocol (SCTP) Partial Reliability ExtensionCurrent
May 2004
- RFC 3331Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation LayerCurrent
September 2002
- RFC 3546Transport Layer Security (TLS) ExtensionsObsoleted
June 2003
- RFC 3554On the Use of Stream Control Transmission Protocol (SCTP) with IPsecCurrent
July 2003
- RFC 3268Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)Obsoleted
July 2002
- RFC 3734Extensible Provisioning Protocol (EPP) Transport Over TCPObsoleted
March 2004
- RFC 3749Transport Layer Security Protocol Compression MethodsUpdated
May 2004
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?