Requirements for Server-to-Server Event Pipeline Protocols
draft-dusseault-s2s-event-reqs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Lisa M. Dusseault | ||
| Last updated | 2003-02-25 | ||
| 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
Server-to-server event pipelines are required in situations where an event source generates events for a number of end-users (or simply generates events without an idea of who the end recipients might be), and sends these events to an event or notification aggregator service. These kinds of event source servers are common in messaging (for example, voice messaging servers and calendar servers might send events to a user's main messaging server or to a single-purpose notification server). A general set of requirements is outlined here for the server-to-server aspect of these kinds of scenarios.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)