RFC 4413: TCP/IP Field Behavior
In plain English — editorial summary, not part of the RFC
This memo describes TCP/IP field behavior in the context of header compression. Header compression is possible because most header fields do not vary randomly from packet to packet. Many of the fields exhibit static behavior or change in a more or less predictable way. When a header compression scheme is designed, it is of fundamental importance to understand the behavior of the fields in detail. An example of this analysis can be seen in RFC 3095. This memo performs a similar role for the compression of TCP/IP headers. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4413
- Published
- March 2006
- Authors
- M. West; S. McCann
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 44
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4163RObust Header Compression (ROHC): Requirements on TCP/IP Header CompressionCurrent
August 2005
- RFC 4828TCP Friendly Rate Control (TFRC): The Small-Packet (SP) VariantCurrent
April 2007
- RFC 4850Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node ArchitectureObsoleted
April 2007
- RFC 3720Internet Small Computer Systems Interface (iSCSI)Obsoleted
April 2004
- RFC 3374Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access NetworkCurrent
September 2002
- RFC 3347Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design ConsiderationsCurrent
July 2002
- RFC 2581TCP Congestion ControlObsoleted
April 1999
- RFC 4571Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented TransportCurrent
July 2006
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?