[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

modifications in draft-ietf-ippcp-protocol-02.txt

Following the recent IPPCP WG mailing-list discussions, I modified the IP
Payload Compression Protocol document to include the requested
clarifications. The new document is titled <draft-ietf-ippcp-protocol-02.txt>.

A summary of the changes is attached.  Please, e-mail me directly requests
for the full text of the document. The plan is to submit the new draft prior
to the 11-21 deadline.

Looking forward to your prompt comments,
avram

Summary of the changes from <draft-ietf-ippcp-protocol-01.txt>:

a) 2.1.  Compressed Payload
Paragraph 4 - The compression algorithm is responsible to provide a
compressed payload in whole octet units.
Paragraph 5 - Refering to "The original content of the Next Header (IPv6) or
protocol (IPv4) field...", instead of using only "Next Header field".

b) 2.2.  Anti-Expansion Policy
Paragraph 4 - The compressibility test is "algorithm dependent", a phrase
more accurate than "implementation dependent."

c) 3.1. IPv4 Header Modifications
Explicit reference to Header Checksum.

d) 3.3.  IPComp Header Structure
Clarifications of CPI characteristics and usage:

   Compression Parameter Index (CPI)

        16-bit index.  The CPI is stored in network order.  The values
        0-63 are defined by IANA and are used for manual setup, which
        requires no additional information.  The values 64-61439 are
        negotiated between the two nodes in definition of an IPComp
        Association, as defined in section 4.  The values 61440-65535
        are for private use among mutually consenting parties.  Both
        nodes participating can select a CPI value independently of each
        other and there is no relationships between the two separately
        chosen CPIs.  The outbound IPComp header MUST use the CPI value
        chosen by the decompressing node.  The CPI in combination with
        the destination IP address uniquely identifies the compression
        algorithm characteristics for the datagram.

e) 5. Security Considerations
Paragraph 1 - Modified "...transport header fields..." to "...transport
layer header fields..."

f) Several typos were corrected.

=== end of summary ===