Skip to main content

Lemonade Notifications Architecture
RFC 5551

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Notification and filtering mechanisms can make email more enjoyable on mobile and other constrained devices (such …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-10-14
(System) Notify list changed from lemonade-chairs@ietf.org, draft-ietf-lemonade-notifications@ietf.org to (None)
2009-08-20
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2009-08-20
Cindy Morgan [Note]: 'RFC 5551' added by Cindy Morgan
2009-08-19
(System) RFC published