RFC 3173 on IP Payload Compression Protocol

RFC Editor <rfc-ed@ISI.EDU> Sat, 20 October 2001 03:09 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16170; Fri, 19 Oct 2001 23:09:20 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id WAA11114 for ietf-123-outbound.10@ietf.org; Fri, 19 Oct 2001 22:55:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA07605 for <all-ietf@loki.ietf.org>; Fri, 19 Oct 2001 18:40:12 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03775 for <all-ietf@ietf.org>; Fri, 19 Oct 2001 18:40:07 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id f9JMeAH02786; Fri, 19 Oct 2001 15:40:10 -0700 (PDT)
Message-Id: <200110192240.f9JMeAH02786@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3173 on IP Payload Compression Protocol
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 19 Oct 2001 15:40:10 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 3173

        Title:	    IP Payload Compression Protocol (IPComp)
        Author(s):  A. Shacham, B. Monsour, R. Pereira, M. Thomas 
        Status:     Standards Track
	Date:       September 2001
        Mailbox:    shacham@shacham.net, bob@bobmonsour.com,
                    royp@cisco.com, matt@3am-software.com
        Pages:      13
        Characters: 27060
        Obsoletes:  2393

        I-D Tag:    draft-shacham-ippcp-rfc2393bis-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3173.txt


This document describes a protocol intended to provide lossless
compression for Internet Protocol datagrams in an Internet
environment.

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 Sandy Ginoza
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/rfc3173.txt"><ftp://ftp.isi.edu/in-notes/rfc3173.txt>