At 8:28 PM -0600 2/7/07, Vijay K. Gurbani wrote:

 I have been selected as the General Area Review Team (Gen-ART)
 reviewer for this draft (for background on Gen-ART, please see
 http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Thanks for reviewing it.


 Please wait for direction from your document shepherd
 or AD before posting a new version of the draft.

Sorry, I sent in an -05 version earlier this week, based on all comments that had been received during IETF last call (just a few nits). However, it will be easy for me to produce an -06 and send that in.

 Document: draft-ietf-lemonade-deployments-04.txt
 Reviewer: Vijay K. Gurbani
 Review Date: Wed., Feb 07, 2007
 IESG Telechat date: 08 Feb 2007

 Summary: This draft is basically ready for publication, but has
 nits that should be fixed before publication.

 Comments: This draft discusses some interesting issues for
 deployment of mobile email when using the TCP transport.  More
 feedback is below, with substantive comments first followed
 by nits.

 Substantive comments:

 1) In S4, I find it rather odd that the first paragraph takes
  pains to mandate the use of TCP just to have the second para-
  graph negate that by saying that it is okay to use HTTP for
  webmail instead of opening a direct TCP connection.  I am
  unsure what is required: is TCP a MUST, or alternative
  transports like HTTP are okay?

The intent of S4 is to mandate support for TCP. The intent of the webmail/HTTP text is to explain that, if TCP can't be supported, while some form of mail can be offered, it isn't lemonade. Perhaps this can be made more clear by changing the start of that paragraph from "For environments" to "Note that, for environments", and changing the end from "must also be limited." to "must also be limited, and can't be lemonade compliant."


 2) In S4.2, would it help to have a MUST strength for
  turning off TCP keepalives?  More so since it is also harmful
  for dormancy (as discussed in S5.)

I'm fine with that, but I'd have to ask the AD and chairs if such a change requires an explicit blessing by the WG (if so, this could likely be done with a quick call for consensus rather than a new WGLC and IETF LC).



 3) In S6, please consider providing a reference for supporting
  the sentence "There is a body of best practices based on long
  experience in this area."  It may help the reader if he/she
  wants to explore this area in some more detail.

A reference would be nice, and I had tried to find a suitable one, but wasn't able to find one that I felt was OK for an RFC (e.g., not a wikipedia entry). If you have a suggestion I'd appreciate it.


 4) In S8, please consider putting a reference for STARTTLS
  extensions (it is described in RFC3207.)

I can do that.  It would be 3207 for SMTP and 2595 for IMAP.



 Nits:

 1) Just a suggestion: please consider expanding acronyms on
  first use.

I tried to follow a practice of expanding acronyms on first use except those that are in such wide use within the email area that doing so might be distracting (such as TLS, POP, IMAP, SMTP), but if it makes the document easier for non-experts to read, I'd be happy to expand others. Are there particular ones that you suggest expanding?


 2) In S3, may be a good idea to provide a reference for
  IMAP and Message Submission in the first sentence of the
  opening paragraph.

OK.

 3) S4, second paragraph: s/marjup/markup

Fixed in -05.


 Thank you.

Thank you for the detailed review -- I appreciate it.

--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
A successful tool is used to do something undreamed of by its author.
                                                          --Johnson

_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art

Reply via email to