Lemonade Notification protocol
draft-ietf-lemonade-notification-protocol-00
| Document | Type |
Expired Internet-Draft
(lemonade WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Stéphane H. Maes | ||
| Last updated | 2006-06-21 | ||
| 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 | Expired | |
| 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
This document introduces a notification protocol as a specified particular case of the notification mechanisms used by the Lemonade profile [LEMONADEPROFILEBIS] in [NOTIFICATIONS]. This document also discusses the use of Lemonade notifications to implement server to server notifications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)