RFC 4895: Authenticated Chunks for the Stream Control Transmission Protocol (SCTP)
In plain English — editorial summary, not part of the RFC
This document describes a new chunk type, several parameters, and procedures for the Stream Control Transmission Protocol (SCTP). This new chunk type can be used to authenticate SCTP chunks by using shared keys between the sender and receiver. The new parameters are used to establish the shared keys. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4895
- Published
- August 2007
- Authors
- M. Tuexen; R. Stewart; P. Lei; E. Rescorla
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4086Randomness Requirements for SecurityCurrent
June 2005
- RFC 9154Extensible Provisioning Protocol (EPP) Secure Authorization Information for TransferCurrent
December 2021
- RFC 4898TCP Extended Statistics MIBCurrent
May 2007
- RFC 4923Quality of Service (QoS) Signaling in a Nested Virtual Private NetworkCurrent
August 2007
- RFC 4860Generic Aggregate Resource ReSerVation Protocol (RSVP) ReservationsCurrent
May 2007
- RFC 4953Defending TCP Against Spoofing AttacksCurrent
July 2007
- RFC 4960Stream Control Transmission ProtocolObsoleted
September 2007
- RFC 4820Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP)Current
March 2007
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?