60 likes | 71 Views
draft-ietf-sieve-notify-xmpp. Peter Saint-Andre & Alexey Melnikov IETF 70. Overview. A Sieve notification mechanism for sending notifications via XMPP (Jabber) Sieve engine has an XMPP address and sends Jabber IM messages as a result of Sieve script processing
E N D
draft-ietf-sieve-notify-xmpp Peter Saint-Andre & Alexey Melnikov IETF 70
Overview A Sieve notification mechanism for sending notifications via XMPP (Jabber) Sieve engine has an XMPP address and sends Jabber IM messages as a result of Sieve script processing Sieve script contains an XMPP URI (RFC4622) plus Sieve tags
Recent Changes (1) Mainly harmonization with draft-ietf-sieve-notify-mailto Not yet submitted Editorial changes Changed order of sections Test notify_method_capability section More examples
Recent Changes (2) Changed notification-capability test result from “no” to “maybe” if Sieve engine does not have explicit knowledge of network availability (reason: Sieve engine may not have access to presence information) Clarified that XMPP message subject can be specified in XMPP URI; if so specified, it SHOULD be used (if not, SHOULD use subject configured in Sieve engine)
Recent Changes (3) Clarified generation of XMPP message body: If Sieve script includes “:message” tag, MUST use that Else if XMPP URI specifies “body” parameter, SHOULD use that Else SHOULD use body configured in Sieve engine
Status Meets conformance requirements from section 3.8 of draft-ietf-sieve-notify Harmonized with mailto I-D No Last Call feedback received Ready to proceed with IESG review?