Lemonade Notifications Architecture
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 12
- Abstract
- Notification and filtering mechanisms can make email more enjoyable on mobile and other constrained devices (such as those with limited screen sizes, memory, data transfer rates, etc.). Notifications make the client aware of significant events (such as the arrival of new mail) so it can react (such as by fetching interesting mail immediately). Filtering reduces the visible mail to a set of messages that meet some criteria for "interesting". This functionality is included in the goals of the Lemonade (Enhancements to Internet email to Support Diverse Service Environments) Working Group. This document also discusses the use of server-to-server notifications, and how server to server notifications fit into an architecture that provides server to client notifications. This memo provides information for the Internet community.
- Publication Date
- 2009-08-01
- Status Note
- Informational
- DOI
10.17487/RFC5551- Link
- https://doi.org/10.17487/RFC5551
- Author(s)
- Randall Gellens
Latest version of IETF RFC 5551
Document Versions — IETF RFC 5551
-
▶ IETF RFC 5551 (2009-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 3501 [Superseded*]
- IETF RFC 5550 [Active*]
Bibliographic Reference(s)
- Open Mobile Alliance Mobile Email Requirement Document, (Work in progress). http://www.openmobilealliance.org/ EXTERNAL
- Leiba, B., "Support for Sieve in Internet Message Access Protocol (IMAP4)", Work in Progress, February 2008. EXTERNAL
- Melnikov, A., Ed., and T. Martin, "A Protocol for Remotely Managing Sieve Scripts", Work in Progress, September 2008. EXTERNAL
- IETF RFC 2177 [Active*]
- IETF RFC 4146 [Active*]
- IETF RFC 4467 [Active*]
- IETF RFC 4551 [Superseded*]
- IETF RFC 5228 [Active*]
- IETF RFC 5229 [Active*]
- IETF RFC 5267 [Active*]
- IETF RFC 5423 [Active*]
- IETF RFC 5435 [Active*]
- IETF RFC 5442 [Active*]
- IETF RFC 5465 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5551.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5551, Lemonade Notifications Architecture. Available at https://doi.org/10.17487/RFC5551
Snippet:
IETF RFC 5551, Lemonade Notifications Architecture. Available at https://doi.org/10.17487/RFC5551
HTML (ISO 690 compliant)
Preview:
IETF RFC 5551, Lemonade Notifications Architecture. Available at https://doi.org/10.17487/RFC5551
Snippet:
<span class="citation"><cite>IETF RFC 5551</cite>, Lemonade Notifications Architecture. Available at <a href="https://doi.org/10.17487/RFC5551" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5551</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5551, Lemonade Notifications Architecture
doi: 10.17487/RFC5551
url: https://doi.org/10.17487/RFC5551
doi: 10.17487/RFC5551
url: https://doi.org/10.17487/RFC5551
Snippet:
<li> <cite id="bib-rfc5551">IETF RFC 5551</cite>, Lemonade Notifications Architecture <span class="doi">10.17487/RFC5551</span> </li>
Referenced By
- IETF RFC 5550 [Active*]