RFC 3554: On the Use of Stream Control Transmission Protocol (SCTP) with IPsec
In plain English — editorial summary, not part of the RFC
This document describes functional requirements for IPsec (RFC 2401) and Internet Key Exchange (IKE) (RFC 2409) to facilitate their use in securing SCTP (RFC 2960) traffic. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3554
- Published
- July 2003
- Authors
- S. Bellovin; J. Ioannidis; A. Keromytis; R. Stewart
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 3526More Modular Exponential (MODP) Diffie-Hellman groups for Internet Key Exchange (IKE)Current
May 2003
- RFC 3947Negotiation of NAT-Traversal in the IKECurrent
January 2005
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 4304Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet Security Association and Key Management Protocol (ISAKMP)Current
December 2005
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
- RFC 4307Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)Obsoleted
December 2005
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?