RFC 2507 on IP Header Compression

RFC Editor <rfc-ed@ISI.EDU> Thu, 04 February 1999 21:25 UTC

Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id QAA14680 for ietf-123-outbound.10@ietf.org; Thu, 4 Feb 1999 16:25:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA14585 for <all-ietf@ietf.org>; Thu, 4 Feb 1999 16:23:07 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id NAA14516; Thu, 4 Feb 1999 13:21:52 -0800 (PST)
Message-Id: <199902042121.NAA14516@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2507 on IP Header Compression
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 04 Feb 1999 13:21:52 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2507: 

        Title:	    IP Header Compression
	Author(s):  M. Degermark, B. Nordgren, S. Pink
	Status:     Proposed Standard
	Date:       February 1999
        Mailbox:    micke@sm.luth.se, bcn@lulea.trab.se,
		    steve@sm.luth.se
        Characters: 106292
        Updates/Obsoletes/See Also: None    
        I-D Tag:    draft-degermark-ipv6-hc-08.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2507.txt


This document describes how to compress multiple IP headers and TCP
and UDP headers per hop over point to point links. The methods can be
applied to of IPv6 base and extension headers, IPv4 headers, TCP and
UDP headers, and encapsulated IPv6 and IPv4 headers.

This document is a product of the IPNG Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc2507.txt"><ftp://ftp.isi.edu/in-notes/rfc2507.txt>