Architecture for Event Notification Filters
draft-moran-sipping-filter-arch-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tim Moran , Sreenivas Addagatla | ||
| Last updated | 2002-10-24 | ||
| 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 document defines an extendible architecture whereby an event subscriber (client) may specify the rules for SIP event notification from the notifier (server). Potential solutions meeting the architecture specification are also provided in the annexes. Requirements for event filtering were previously described in [1].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)