Requirements for Binding Published Data to SIP Services
draft-campbell-pub-bind-reqs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ben Campbell | ||
| Last updated | 2002-05-03 | ||
| 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
A growing number of SIP based services depend on the idea that clients may publish service-related information to network elements. This information may then affect further processing of the service. Examples of such services include presence and CPL. Multiple protocols may exists for the actual publication of such data. But regardless of the protocol, a client must know where to send it. This document describes requirements for a mechanism to inform clients where and how to publish service related information.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)