Document: draft-ietf-lemonade-profile-07  
Reviewer: Spencer Dawkins [spencer@mcsr-labs.org]
Review Date:  Friday 1/27/2006 3:49 PM CST
IESG Telechat Date:  Thursday, 2 February 2006

Summary: This document is on the right track for publication as a Proposed 
Standard. Most of my comments involve SHOULD requirements.

Review Comments:

In Section 3, "Lemonade clients SHOULD take advantage of these features." 
doesn't look like a normative/2119 "SHOULD".

In section 3.3, I suppose the SHOULD NOT in

   A LEMONADE compliant client SHOULD use message size declaration. In

   particular it SHOULD NOT send a message to a mail submission server,

   if the client knows that the message exceeds the maximal message size

   advertised by the submission server.


is OK, but is this required? ("When is it OK to send a message that exceeds 
the maximal message size advertised by the submission server?")


Other Comments for Editors:

I'm somewhat surprised to see two methods of "forward without download" 
described in Section 2.4 (extended APPEND and BURL/BDAT), because I would 
have thought that profiles were trying to prevent this kind of duplication, 
but the WG should know best.

A significant portion of the document (Section 2.4) is an example that might 
make a good appendix - I'm not sure if it is (or needs to be) normative text 
for a Proposed Standard.

I am slightly confused about the target of Proposed Standard for profiles, 
but let's not even go there.