The changes in version 08 are editorial only, adding

(a) A statement that the document obsoletes RFC 2393.

(b) The list of changes made since RFC 2393 of which an implementer of
RFC 2393 should be aware.  This section summarizes the release notes
that were posted to the lists with each change of the I-D.

43a44,45
>    This document obsoletes RFC 2393.
> 
467a470,495
> 7. Changes made since RFC 2393
> 
>    This section summarizes the changes in this document from RFC 2393 of
>    which an implementer of RFC 2393 should be aware.  All the changes
>    are meant to clarify the negotiation of an IPComp Association (IPCA)
>    using IKE [IKE] in the context of IPsec.
> 
>    1) Added a clarification that IPComp can be negotiated stand-alone or
>    bundled with other protocols in a Protection Suite.
> 
>    2) Defined the CPI in the SPI field of an IKE proposal: two-octet
>    field is a SHOULD, four-octet a MAY.  Defined the placement of the
>    16-bit CPI in a four-octet field.  Specified that a receiver MUST
>    process both field sizes.
> 
>    3) Added wording to define the default Encapsulation Mode to be
>    Transport Mode.  Required that an IPComp proposal MUST include an
>    Encapsulation Mode attribute when it suggests a non-default
>    encapsulation, such as Tunnel Mode.
> 
>    4) Added the Lifetime attribute to the list of supported attributes
>    (along with Transport Mode).
>
>    5) Specified the handling of attributes of transforms in a Protection
>    Suite that are not applicable to IPComp: These attributes SHOULD NOT
>    be included in an IPComp proposal and MUST be ignored when setting
>    IPCA and in the operation of IPComp.  IPComp implementations MUST
>    never reject an IPCOMP proposal that does not include attributes of
>    other transforms.
>
>    6) Added implementation notes on the negotiation and usage of CPIs in
>    the predefined (well-known) range.
>
473c507
< 7. References
---
> 8. References