changes in draft-ietf-ippcp-protocol-05.txt
Avram Shacham <shacham@cisco.com> Wed, 28 January 1998 19:42 UTC
Return-Path: shacham@cisco.com
Received: from bubbuh.cisco.com (bubbuh.cisco.com [198.92.30.35]) by ftp-eng.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id LAA18912 for <ippcp-archive-file@ftp-eng.cisco.com>; Wed, 28 Jan 1998 11:42:01 -0800 (PST)
Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by bubbuh.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id LAA29063 for <ippcp@external.cisco.com>; Wed, 28 Jan 1998 11:40:16 -0800 (PST)
Received: from shacham-home-pc-4.cisco.com (shacham-home-pc-4.cisco.com [171.69.149.181]) by pita.cisco.com (8.8.5-Cisco.1/8.6.5) with SMTP id LAA11104 for <ippcp@external.cisco.com>; Wed, 28 Jan 1998 11:40:15 -0800 (PST)
Message-Id: <2.2.32.19980128193921.006c0b90@pita.cisco.com>
X-Sender: shacham@pita.cisco.com
X-Mailer: Windows Eudora Pro Version 2.2 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 28 Jan 1998 11:39:21 -0800
To: ippcp@external.cisco.com
From: Avram Shacham <shacham@cisco.com>
Subject: changes in draft-ietf-ippcp-protocol-05.txt
Following the IESG last call and the comments by IANA and Thomas Narten, I submitted version 05 of the IPComp I-D. The editorial changes in this version are attached. Regards, avram === changes to draft-ietf-ippcp-protocol-05.txt === 1. Introduction In the last paragraph, a new sentence clarifies that the compression algorithms are beyond the scope of the I-D: Other documents shall specify how a specific compression algorithm can be used with the IP payload compression protocol. Such algorithms are beyond the scope of this document. ^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3.3. IPComp Header Structure The reference to the DOI values is worded as requested by IANA: Compression Parameter Index (CPI) 16-bit index. The CPI is stored in network order. The values 0-63 define well-known compression algorithms, which require no additional information, and are used for manual setup. The values themselves are identical to IPCOMP Transform identifiers as defined in [SECDOI]. Consult [SECDOI] for an initial set of defined values and for instructions on how to assign new values.
- changes in draft-ietf-ippcp-protocol-05.txt Avram Shacham