Sieve Email Filtering: Sieves and Display Directives in XML
draft-freed-sieve-in-xml-07
Yes
(Lisa Dusseault)
No Objection
(Adrian Farrel)
(Dan Romascanu)
(Jari Arkko)
(Lars Eggert)
(Pasi Eronen)
(Ralph Droms)
(Ron Bonica)
(Ross Callon)
(Tim Polk)
Note: This ballot was opened for revision 07 and is now closed.
Lisa Dusseault Former IESG member
Yes
Yes
()
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
()
Unknown
Alexey Melnikov Former IESG member
No Objection
No Objection
(2009-08-12)
Unknown
Extensions can add new controls, actions, tests, or new arguments to existing controls or actions. Extensions have also changed how string content is interpreted, although this is not relevant to this specification. However, it is especially important to note that so far no Sieve extension has added a new control to the language and it This is not quite correct, as demonstrated by the Sieve MIME Loops document, which adds "break" and "foreverypart" control commands. seems safe to assume that due to their nature future addition of controls will be rare.
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Lars Eggert Former IESG member
No Objection
No Objection
()
Unknown
Pasi Eronen Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Ralph Droms Former IESG member
No Objection
No Objection
()
Unknown
Robert Sparks Former IESG member
No Objection
No Objection
(2009-08-12)
Unknown
Please consider being even more explicit about not including double-quotes in the <str> elements. The examples reinforce this, but some text directly stating what should happen would not hurt. when representing fileinto "folder"; <action name="fileinto"><str>folder</str></action> is good. <action name="fileinto"><str>"folder"</str></action> isn't what you want.
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss)
No Objection
No Objection
(2009-08-13)
Unknown
Security Considerations, last paragraph: You mention that potentially executable content can be introduced via other namespaces, and that "appropriate security precautions" should be taken. I think this needs more discussion, as I am not sure an implementor will understand what the authors considered appropriate. Nits/editorial comment: Section 3, last paragraph: First sentence is repeated.
Tim Polk Former IESG member
No Objection
No Objection
()
Unknown