Joern,
See comments below.
Francois
>-----Original Message-----
>From: Joern Sierwald [mailto:joern.sierwald@F-Secure.com]
>Sent: Wednesday, June 21, 2000 1:54 PM
>To: ipsec@lists.tislabs.com
>Subject: RE: Minimum IP Compression Algorithm for Interoperability
>
>Francois wrote:
>
>>Based on the comments made on this thread, does someone know when
>>the DOI [RFC2407] will be updated to make the current DEFLATE
>>transform ID historical and add a new DEFLATE transform ID without
>>the extra header and Alder checksums, which would be the official on?
>
>Ain't gonna happen. That was actually my proposal, but the general reply
>was "Why should the people who got it _right_ change their implementation
>(switch to other ID), making the new version incompatible to their old
>versions?
>And BTW, learn how to read, especially RFCs."
>
>Fair enough. The general suggestion in this case would be
>"Will the programmers please fix their broken software".
I agree with the general consensus of not updating RFC2407.
>>In addition, do someone also know when RFC2394 will be updated
>>to clarify the use and non-use of the extra header and Alder checksums
>>with DEFLATE?
>
>Well, it's not a draft, it's a RFC already. Changing it is not trivial.
>Tero suggested the same, but I think it would be better to put that
>information
>into another place:
>
>Into the zlib documentation!
However, although RFC2394 is an RFC, it is not yet on the standard track and could be replaced by an updated version containing an Appendix clarifying the non-use of the extra header and Adler checksum as suggested by others.
>J-rn
>
___________________________________
Francois Rousseau
Director of Standards and Conformance
Chrysalis-ITS
1688 Woodward Drive
Ottawa, Ontario, CANADA, K2C 3R7
frousseau@chrysalis-its.com Tel. (613) 723-5076 ext. 419
http://www.chrysalis-its.com Fax. (613) 723-5078