Lemonade Notifications Architecture
RFC 5551, “Lemonade Notifications Architecture”, is an Informational document published in August 2009 by R. Gellens. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5551 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5550 The Internet Email to Support Diverse Service Environments Profile
- RFC 5552 SIP Interface to VoiceXML Media Services
- RFC 5549 Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
- RFC 5553 Resource Reservation Protocol Extensions for Path Key Support
- RFC 5548 Routing Requirements for Urban Low-Power and Lossy Networks
- RFC 5554 Clarifications and Extensions to the Generic Security Service Application Program Interface for the Use of Channel Bindings
- RFC 5547 A Session Description Protocol Offer/Answer Mechanism to Enable File Transfer
- RFC 5555 Mobile IPv6 Support for Dual Stack Hosts and Routers