RFC 4820: Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP)
In plain English — editorial summary, not part of the RFC
This document defines a padding chunk and a padding parameter and describes the required receiver side procedures. The padding chunk is used to pad a Stream Control Transmission Protocol (SCTP) packet to an arbitrary size. The padding parameter is used to pad an SCTP INIT chunk to an arbitrary size. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4820
- Published
- March 2007
- Authors
- M. Tuexen; R. Stewart; P. Lei
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 6
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4804Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE TunnelsCurrent
February 2007
- RFC 4782Quick-Start for TCP and IPCurrent
January 2007
- RFC 4860Generic Aggregate Resource ReSerVation Protocol (RSVP) ReservationsCurrent
May 2007
- RFC 4774Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) FieldUpdated
November 2006
- RFC 4895Authenticated Chunks for the Stream Control Transmission Protocol (SCTP)Current
August 2007
- RFC 4898TCP Extended Statistics MIBCurrent
May 2007
- RFC 4923Quality of Service (QoS) Signaling in a Nested Virtual Private NetworkCurrent
August 2007
- RFC 4953Defending TCP Against Spoofing AttacksCurrent
July 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?