1 / 6

Sieve XMPP Notification Mechanism for Sending Jabber IM Messages

A Sieve notification mechanism using XMPP for sending Jabber IM messages. Contains XMPP URI and tags. Recent changes clarify message body and notification capability testing. Harmonized with mailto. Ready for IESG review.

jarmando
Download Presentation

Sieve XMPP Notification Mechanism for Sending Jabber IM Messages

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-ietf-sieve-notify-xmpp Peter Saint-Andre & Alexey Melnikov IETF 70

  2. 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

  3. 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

  4. 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)

  5. 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

  6. 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?

More Related