Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and Enclosure
Note: This ballot was opened for revision 09 and is now closed.
(Lisa Dusseault) Yes
(Jari Arkko) No Objection
(Ron Bonica) No Objection
(Ross Callon) No Objection
(Lars Eggert) No Objection
(Pasi Eronen) No Objection
It could be useful if the examples 9.1 and 9.2 included a warning saying that circumventing these tests is easy (e.g. the list of file extensions that are considered "executable and unsafe" by Outlook is almost 100 entries, and other Content-Types may be used, too), so the SIEVE code here is not intended to be used in real world.
(Adrian Farrel) No Objection
I think the Introduction is a bit terse. It should at least have a very brief statement about what Sieve is with a reference to RFC 5228. This would then give context to the statement This extension defines mechanisms for performing tests on MIME body parts... === Section 2. Notwithstanding... Conventions for notations are as in [RFC5228] section 1.1. ...it would be helpful to include a normative reference to RFC 5234 === Section 4.1 Usage: The definition of [MIMEOPTS] is: I am not so hot on ABNF, but shouldn't this read... Usage: The definition of MIMEOPTS is: as the  is an ABNF notation not part of the name.
(Russ Housley) No Objection
(Tim Polk) (was No Record, Discuss) No Objection
There is at least one occurrence of "SIEVE" in section 11, but most (all?) other occurrences are "Sieve" For consistency, suggest the global change s/SIEVE/Sieve/