Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)
RFC 5437
Yes
(Lisa Dusseault)
No Objection
Lars Eggert
(Dan Romascanu)
(David Ward)
(Jari Arkko)
(Jon Peterson)
(Magnus Westerlund)
(Mark Townsley)
(Ron Bonica)
(Ross Callon)
(Russ Housley)
(Tim Polk)
Note: This ballot was opened for revision 09 and is now closed.
Lars Eggert
(was No Record, No Objection)
No Objection
Lisa Dusseault Former IESG member
Yes
Yes
()
Chris Newman Former IESG member
(was Discuss)
No Objection
No Objection
(2008-01-02)
Stating that the "from:" header must be an email address is a bit imprecise as there are various syntax representations for an email address (e.g., RFC 2822 allows a display name and folding whitespace in the address). This could be clarified by specifically referring to RFC 2821 "Mailbox" ABNF rule.
Cullen Jennings Former IESG member
(was Discuss)
No Objection
No Objection
(2007-12-31)
few typos: ":messaga" should be ":message" and search for sewsion
Dan Romascanu Former IESG member
No Objection
No Objection
()
David Ward Former IESG member
No Objection
No Objection
()
Jari Arkko Former IESG member
No Objection
No Objection
()
Jon Peterson Former IESG member
No Objection
No Objection
()
Magnus Westerlund Former IESG member
No Objection
No Objection
()
Mark Townsley Former IESG member
No Objection
No Objection
()
Ron Bonica Former IESG member
No Objection
No Objection
()
Ross Callon Former IESG member
No Objection
No Objection
()
Russ Housley Former IESG member
No Objection
No Objection
()
Sam Hartman Former IESG member
No Objection
No Objection
(2007-12-17)
I'm a bit puzzled at why the requirement that the notification sender must be the notification service is at must level. That doesn't seem to be necessary for interoperability or security or for any of the other reasons we typically place requirements at must level. I think should would be more appropriate.
Tim Polk Former IESG member
No Objection
No Objection
()