IMAP4 Extension for Returning MYRIGHTS Information in Extended LIST
RFC 8440
Yes
No Objection
Note: This ballot was opened for revision 04 and is now closed.
Alvaro Retana No Objection
Warren Kumari No Objection
(Alexey Melnikov; former steering group member) Yes
(Adam Roach; former steering group member) No Objection
(Alissa Cooper; former steering group member) No Objection
(Ben Campbell; former steering group member) No Objection
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.
(Benjamin Kaduk; former steering group member) No Objection
(Deborah Brungard; former steering group member) No Objection
(Eric Rescorla; former steering group member) No Objection
(Ignas Bagdonas; former steering group member) No Objection
(Martin Vigoureux; former steering group member) No Objection
(Mirja Kühlewind; former steering group member) No Objection
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?
(Spencer Dawkins; former steering group member) No Objection
(Suresh Krishnan; former steering group member) No Objection
(Terry Manderson; former steering group member) No Objection