Sieve Notification Mechanisms

(last updated 2009-02-02)

Registries included below:
- Sieve Notification Mechanisms


Registry Name: Sieve Notification Mechanisms
Reference: [RFC5435]
Range               Registration Procedures   Note
------------------  ------------------------  ---------------------------------
Vendor-controlled   First Come First Served   Template available in Section 9.2
IETF-controlled     Specification Required

Registry:
Mechanism name: mailto
Mechanism URI: [RFC2368]
Mechanism-specific options: none
Permanent and readily available reference: [RFC5436]
Person and email address to contact for further information:
    Michael Haardt <michael.haardt&freenet.ag>

Mechanism name: xmpp
Mechanism URI: [RFC5122]
Mechanism-specific options: none
Permanent and readily available reference: [RFC5437]
Person and email address to contact for further information:
   Peter Saint-Andre <stpeter&jabber.org>


References
----------
[RFC2368]  P. Hoffman, L. Masinter, J. Zawinski, "The mailto URL scheme", 
           RFC 2368, July 1998.

[RFC5122]  P. Saint-Andre, "Internationalized Resource Identifiers (IRIs) and 
           Uniform Resource Identifiers (URIs) for the Extensible Messaging 
           and Presence Protocol (XMPP)", RFC 5122, February 2008.

[RFC5435]  A. Melnikov, Ed., B. Leiba, Ed., W. Segmuller, T. Martin, "SIEVE 
           Email Filtering: Extension for Notifications", RFC 5435, January 2009.

[RFC5436]  B. Leiba, M. Haardt, "Sieve Notification Mechanism: mailto", 
           RFC 5436, January 2009.

[RFC5437]  P. Saint-Andre, A. Melnikov, "Sieve Notification Mechanism: xmpp",
           RFC 5437, January 2009.

(registry created 2008-01-30)

[]