RE: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments

[<[e-mail]>]

I hope it's not too late.
1. Typo in section 2:
When a TLS librarly

2. Wording change suggestion in section 2:
all protocols that use TLS automatically are compressed
to:
all protocols that use TLS are automatically compressed

3. Wording change suggestion in section 3:
OK The server will compress its responses and expects the client to compress its commands.
to:
OK The server and the client will compress all data that it may send

4. Wording change suggestion in section 3:
The client MUST NOT send any further commands until it has seen the result of COMPRESS.
to:
After the client has sent the COMPRESS command, the client MUST NOT send any commands until it has seen the result of COMPRESS.

5. Clarification/wording change suggestion in section 3:
(Responses issued by the server before the OK response will, of course, still be uncompressed.)
to:
Therefore, responses issued by the server before the OK response will all be uncompressed, and delayed client requests that have been sent uncompressed (before turning compression on) may result in compressed responses.

6. Typo in section 4:
so any compression algorith

7. Wording change suggestion in section 4:
the same way as is recommended for servers
the same way as it is recommended for servers later

8. Question/suggestion in section 4:
Multiple occurances of "base-64" - this is BASE64 as in RFC4648, right? If so, I would suggest correction (base-64 -> BASE64) and adding a reference.

9. Question in section 5:
capability  =/ "COMPRESS=" algorithm
                      ;; multiple COMPRESS capabilities allowed
So, if I had multiple algorithms, would it be COMPRESS=1,2,3 or COMPRESS=1,COMPRESS=2,COMPRESS=3? I would guess the second.

10. Question in section 6:
Should we add ZLIB here? ZLIB already had some history...

11. Wording change suggestion in section 7:
The IANA is requested to add COMPRESS=DEFLATE the list
to:
The IANA is requested to add COMPRESS=DEFLATE to the list

12. Wording change suggestion in section 7:
and another compression is added at that time, it would then be appropriate to create a registry
to:
and any additional compression algorithms are introduced at that time, then the registry should be created

Thank You.

Best regards: Zoltán Ördögh
E-mail: zoltan dot ordogh at nokia dot com
Phone: [phone]

 

>-----Original Message-----
>From: ext [e-mail] [mailto:[e-mail]] 
>Sent: 02 October, 2006 17:50
>To: [e-mail]
>Cc: [e-mail]
>Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt 
>
>A New Internet-Draft is available from the on-line 
>Internet-Drafts directories.
>This draft is a work item of the Enhancements to Internet 
>email to support diverse service environments Working Group of 
>the IETF.
>
>	Title		: The IMAP COMPRESS Extension
>	Author(s)	: A. Gulbrandsen
>	Filename	: draft-ietf-lemonade-compress-05.txt
>	Pages		: 9
>	Date		: 2006-10-2
>	
>The COMPRESS extension allows an IMAP connection to be effectively
>    and efficiently compressed.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-lemonade-compress-05.txt
>
>To remove yourself from the I-D Announcement list, send a 
>message to [e-mail] with the word 
>unsubscribe in the body of the message. 
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>to change your subscription settings.
>
>Internet-Drafts are also available by anonymous FTP. Login 
>with the username "anonymous" and a password of your e-mail 
>address. After logging in, type "cd internet-drafts" and then 
>"get draft-ietf-lemonade-compress-05.txt".
>
>A list of Internet-Drafts directories can be found in 
>http://www.ietf.org/shadow.html or 
>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>	[e-mail].
>In the body type:
>	"FILE /internet-drafts/draft-ietf-lemonade-compress-05.txt".
>	
>NOTE:	The mail server at ietf.org can return the document in
>	MIME-encoded form by using the "mpack" utility.  To use this
>	feature, insert the command "ENCODING mime" before the "FILE"
>	command.  To decode the response(s), you will need "munpack" or
>	a MIME-compliant mail reader.  Different MIME-compliant 
>mail readers
>	exhibit different behavior, especially when dealing with
>	"multipart" MIME messages (i.e. documents which have been split
>	up into multiple messages), so check your local documentation on
>	how to manipulate these messages.
>
>Below is the data which will enable a MIME compliant mail 
>reader implementation to automatically retrieve the ASCII 
>version of the Internet-Draft.
>

_______________________________________________
lemonade mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/lemonade