Deployment Considerations for Lemonade-Compliant Mobile Email
RFC 5383

Note: This ballot was opened for revision 09 and is now closed.

(Ted Hardie) Yes

(Chris Newman) Yes

Comment (2007-05-21 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Despite a document editor which produces document revisions in 1-2 business
days when asked, the IESG has introduced over 3 months of delay on this
document with DISCUSS comments.  As it crossed the AD transition, there are
no longer enough "yes" or "no objection" votes by current ADs for this to
pass.  Please work to get this passed ASAP as the lemonade WG is quickly
losing patience with the IESG on this one.

To view changes due to DISCUSS comments from previous IESG review:
  http://tinyurl.com/2w8ufb

(Jari Arkko) (was Discuss) No Objection

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Brian Carpenter) No Objection

(Lars Eggert) (was Discuss) No Objection

Comment (2007-02-22)
No email
send info
Section 4.2, paragraph 2:
>     To this end, client and server systems SHOULD NOT set the TCP
>     keep-alive socket option, and SHOULD NOT close a connection based on
>     ICMP host unreachable messages.

  RFC1122 describes "hard" and "soft" error conditions, depending on the
  code of ICMP message received, and prescribes different reactions to
  them. Does this sentence really want to only talk about one specific
  message (code 1)? Also note that many current stacks don't follow
  RFC1122 anymore (see raft-ietf-tcpm-tcp-soft-errors).

(Bill Fenner) No Objection

(Russ Housley) No Objection

Comment (2007-02-04 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
  Security considerations, 2nd paragraph, uses the word "insurance."  I
  strongly suspect that this is not talking about an insurance policy. I
  believe that it is really talking about confidence in the system, or
  "assurance."

(Cullen Jennings) (was Discuss) No Objection

Comment (2007-05-09)
No email
send info
Section 1 - KEYWORDS defines these for standards track document and is fairly debated what the meaning of them in a BCP is.

(David Kessens) No Objection

(Jon Peterson) No Objection

(Tim Polk) No Objection

(Dan Romascanu) No Objection

(Mark Townsley) No Objection

Magnus Westerlund (was Discuss, No Objection) No Objection