Fwd: I-D ACTION:draft-shacham-ippcp-rfc2393bis-01.txt
Avram Shacham <shacham@cisco.com> Wed, 13 October 1999 09:02 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by mail.imc.org (8.9.3/8.9.3) with ESMTP id CAA16261; Wed, 13 Oct 1999 02:02:36 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id DAA19634 Wed, 13 Oct 1999 03:08:36 -0400 (EDT)
Message-Id: <199910130705.AAA03327@honeybee.cisco.com>
X-Sender: shacham@honeybee.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2
Date: Wed, 13 Oct 1999 00:05:29 -0700
To: ippcp@external.cisco.com
From: Avram Shacham <shacham@cisco.com>
Subject: Fwd: I-D ACTION:draft-shacham-ippcp-rfc2393bis-01.txt
Cc: ipsec@lists.tislabs.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
For those who are not on IETF-Announce, attached is the announcement of the new version of rfc2393bis. (For some reason, no message was posted to the requested lists.) The change in the -01 version reflects comments that were posted to the lists -- see the attached diff. Regards, avram >X-SMAP-Received-From: outside >To: IETF-Announce:; >From: Internet-Drafts@ietf.org >Reply-to: Internet-Drafts@ietf.org >Subject: I-D ACTION:draft-shacham-ippcp-rfc2393bis-01.txt >Date: Tue, 12 Oct 1999 06:55:52 -0400 >Sender: nsyracus@cnri.reston.va.us > >A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : IP Payload Compression Protocol (IPComp) > Author(s) : A. Shacham, R. Monsour, R. Pereira, M. Thomas > Filename : draft-shacham-ippcp-rfc2393bis-01.txt > Pages : 9 > Date : 11-Oct-99 > >This document describes a protocol intended to provide lossless >compression for Internet Protocol datagrams in an Internet >environment. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-shacham-ippcp-rfc2393bis-01.txt > >Internet-Drafts are also available by anonymous FTP. Login with the username >"anonymous" and a password of your e-mail address. After logging in, >type "cd internet-drafts" and then > "get draft-shacham-ippcp-rfc2393bis-01.txt". > >A list of Internet-Drafts directories can be found in >http://www.ietf.org/shadow.html >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > >Internet-Drafts can also be obtained by e-mail. > >Send a message to: > mailserv@ietf.org. >In the body type: > "FILE /internet-drafts/draft-shacham-ippcp-rfc2393bis-01.txt". > >NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > >Below is the data which will enable a MIME compliant mail reader >implementation to automatically retrieve the ASCII version of the >Internet-Draft. >Content-Type: text/plain >Content-ID: <19991011110653.I-D@ietf.org> > >ENCODING mime >FILE /internet-drafts/draft-shacham-ippcp-rfc2393bis-01.txt > ><ftp://ftp.ietf.org/internet-drafts/draft-shacham-ippcp-rfc2393bis-01.txt> > 352c352,358 < value of Transport Mode is assumed. --- > value of Transport Mode is assumed. When IPComp is negotiated as > part of a Protection Suite, and when the negotiation protocol > requires that all the logically related offers must be consistent, > the IPComp proposals MUST include all the attributes of every > transform being negotiated, but those attributes not relevant to > IPComp MUST be ignored when setting the IPCA and therefore ignored in > the operation of IPComp. === eom ===
- Fwd: I-D ACTION:draft-shacham-ippcp-rfc2393bis-01… Avram Shacham