Notification-Capability Parameters

(last updated 2008-02-01)

Registries included below:
- Notification-Capability Parameters


Registry Name: Notification-Capability Parameters
Reference: [RFC-ietf-sieve-notify-12.txt]
Range               Registration Procedures   Note
------------------  ------------------------  ---------------------------------
Vendor-controlled   First Come First Served   Template available in Section 9.3
IETF-controlled     Specification Required

Note:
Vendor-controlled notification-capability values have the format as 
defined in the following paragraph and may be registered on a "First 
Come First Served" basis [RFC2434] by applying to IANA with a template. 
Notification-capability values that do not begin with "vnd." are 
registered using the "Specification Required" policy [RFC2434].

Vendor-controlled notification-capability values MUST have the form
"vnd.<vendor-name>.<capability-name>", where <vendor-name> is as
specified in the ACAP Vendor Subtree registry [RFC2244].

Registry:
Capability name: online
Description: Returns whether the entity identified by the
   notification-uri parameter to the notify_method_capability test can
   receive a notify notification immediately.
Syntax: Can contain one of three values: "yes", "no" and "maybe".
   Values MUST be in lowercase.
Permanent and readily available reference(s): [RFC-ietf-sieve-notify-12.txt]
Contact information: The Sieve discussion list <ietf-mta-filters&imc.org>


References
----------
[RFC2244]  C. Newman, J. Myers, "ACAP -- Application Configuration
           Access Protocol", RFC 2244, November 1997.

[RFC2434]  T. Narten, H. Alvestrand, "Guidelines for Writing an IANA 
           Considerations Section in RFCs", RFC 2434, October 1998.

[RFC-ietf-sieve-notify-12.txt]
           A. Melnikov, Ed., B. Leiba, Ed., W. Segmuller, T. Martin, "SIEVE 
           Email Filtering: Extension for Notifications", RFC XXXX, Month Year.

(registry created 2008-01-30)

[]