Lemonade Server to Client Notifications
draft-ietf-lemonade-server-to-client-notifications-00
| Document | Type |
Replaced Internet-Draft
(lemonade WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Stéphane H. Maes | ||
| Last updated | 2004-07-19 | ||
| Replaced by | draft-smaes-lemonade-s2c-notification-reqs | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-smaes-lemonade-s2c-notification-reqs | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Lemonade server to client notifications provides some extensions to the IMAPv4 Rev1 protocol [RFC3501] for optimization in a mobile setting, aimed at delivering extended functionality for mobile devices with limited resources. These notifications support pushing crucial changes actively to a client, rather than requiring the client to initiate contact to ask for state changes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)