RFC 3173 on IP Payload Compression Protocol
RFC Editor <rfc-ed@ISI.EDU> Wed, 12 September 2001 23:20 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05221; Wed, 12 Sep 2001 19:20:07 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA07213 for ietf-123-outbound.10@ietf.org; Wed, 12 Sep 2001 19:15:00 -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 TAA07180 for <all-ietf@loki.ietf.org>; Wed, 12 Sep 2001 19:08:45 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04936 for <all-ietf@ietf.org>; Wed, 12 Sep 2001 19:08:16 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id f8CN8HQ16510; Wed, 12 Sep 2001 16:08:17 -0700 (PDT)
Message-Id: <200109122308.f8CN8HQ16510@boreas.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: Wed, 12 Sep 2001 16:08:17 -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.
- RFC 3173 on IP Payload Compression Protocol RFC Editor
- RFC 3173 on IP Payload Compression Protocol RFC Editor