Simple Notification and Alarm Protocol (SNAP)
draft-shapira-snap-05
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Noam Shapira | ||
Last updated | 2002-11-06 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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 memo suggests a protocol for messaging notification in which a messaging system (e.g. email server, voice mail system, etc.) notifies a notification service, and through it the user, that changes have occurred in a user's mailbox (new message arrived, mailbox is full, etc.). The protocol aims to provide the end-user with unified notification of events occurring on different messaging systems. A mailing list has been established to discuss this draft and promote the issue of Notification to RFC. To subscribe, send email with 'subscribe snap' to majordomo@lists.neystadt.org or using web at http://www.neystadt.org/cgi-bin/majordomo.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)