IMAP4 Extension for Returning MYRIGHTS Information in Extended LIST
RFC 8440

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

Alexey Melnikov Yes

Ignas Bagdonas No Objection

Deborah Brungard No Objection

Ben Campbell No Objection

Comment (2018-06-06 for -05)
No email
send info
Please consider using the boilerplate from RFC 8174 instead of 2119. The draft includes at least one lower case "may". That boilerplate also enables things like lower-case "should" rather than the more awkward "ought to", which has connotations of criticism or moral judgement in much of the US.

Alissa Cooper No Objection

Spencer Dawkins No Objection

Benjamin Kaduk No Objection

Comment (2018-06-05 for -05)
No email
send info
Please consider using the RFC 8174 boilerplate (instead of the RFC 2119 one) -- there is
a lowercased "may" in the document.

Per the secdir review, please incorporate the security
considerations of RFC 4314 (e.g., by reference).

Suresh Krishnan No Objection

Warren Kumari No Objection

Mirja K├╝hlewind No Objection

Comment (2018-06-06 for -05)
No email
send info
Comment to the AD: All IMAP shepherd write-ups say "7. There have been no IPR disclosures for this spec.", however, questions 7 is about confirming that the authors are not aware of any IPR (that might not have been disclosed yet). Was that checked with the authors?

Also sec 3: "This document extends the LIST command with a new return option
   [RFC5258], "MYRIGHTS", which allows the client to request all of the
   desired information in a single command. "
 The "which" clause is confusing to me...  or should this also be attribute and "LIST-MYRIGHTS" here?

Terry Manderson No Objection

Eric Rescorla No Objection

Alvaro Retana No Objection

Adam Roach No Objection

Comment (2018-06-06 for -05)
No email
send info
> 9.  Acknowledgments
>
>   This document is based largely on RFC5819.

Please consider adding RFC 5819 as an informative reference.

Martin Vigoureux No Objection