Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)
RFC 5437
Yes
No Objection
Note: This ballot was opened for revision 09 and is now closed.
Lars Eggert (was No Record, No Objection) No Objection
(Lisa Dusseault; former steering group member) Yes
(Chris Newman; former steering group member) (was Discuss) No Objection
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 steering group member) (was Discuss) No Objection
few typos: ":messaga" should be ":message" and search for sewsion
(Dan Romascanu; former steering group member) No Objection
(David Ward; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Jon Peterson; former steering group member) No Objection
(Magnus Westerlund; former steering group member) No Objection
(Mark Townsley; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Ross Callon; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Sam Hartman; former steering group member) No Objection
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 steering group member) No Objection