Server To Server Notification Protocol Requirements
draft-ietf-lemonade-notify-s2s-00
| Document | Type |
Expired Internet-Draft
(lemonade WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Gev Decktor | ||
| Last updated | 2015-10-14 (Latest revision 2004-08-08) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Informational | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Ted Hardie | ||
| 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 memo suggests a set of requirements for the implementation of a protocol in which a messaging system (e.g. email server, voice mail system, etc.) submit alerts, which describe potential notification events, regarding an end user mailbox status change (e.g. new message has arrived, mailbox is full, etc.). These alerts are sent to a notification service, which may, in turn, generate an end user alert notification.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)