Document: draft-friend-tls-lzs-compression-03
Reviewer: John Loughney
Date: May 26, 2004

Looks OK, couple of points:

1) Is there an external reference to the LZS compression mechanism?
   I wasn't clear if this is something that is entirely described within 
   the draft.
2) SSL used in some places (section 1.1) - should it be TLS?


NITS: 

1) 2026 broilerplate - needs updating
2) Should LZS be expanded in title, abstract & first usage?
3) Section 2.1 has a IANA request, might want to put a note for
   IANA to fill in the TBA, and perhaps put a back reference 
   to this section in the IANA considerations section.

   IANA has assigned <TBD> as compression method identifier for applying
   LZS compression to TLS record payloads.

4) Section 3.1, 'HiFn' I guess is a company, but I didn't quite get that
   point in section 3.1, would it be better to drop it?

old text:
   Starting with a sliding window compression history, similar to [LZ1],
   Hifn developed a new, enhanced compression algorithm identified as
   LZS. The LZS algorithm is a general-purpose lossless compression
   algorithm for use with a wide variety of data types.  It's encoding
   method is very efficient, providing compression for strings as short
   as two octets in length.

new text:

   Starting with a sliding window compression history, similar to [LZ1],
   a new, enhanced compression algorithm identified as LZS was developed.
   ....

John