[rfc-dist] RFC 4413 on TCP/IP Field Behavior
rfc-editor@rfc-editor.org
rfc-editor at rfc-editor.org
Fri Mar 10 15:53:33 PST 2006
A new Request for Comments is now available in online RFC libraries.
RFC 4413
Title: TCP/IP Field Behavior
Author: M. West, S. McCann
Status: Informational
Date: March 2006
Mailbox: mark.a.west at roke.co.uk,
stephen.mccann at roke.co.uk
Pages: 44
Characters: 28435
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rohc-tcp-field-behavior-04.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc4413.txt
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.
This document is a product of the Robust Header Compression
Working Group of the IETF
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
More information about the rfc-dist
mailing list