A Model for Service Invocation in SIP using ServiceCodes
draft-jfp-sip-servicecodes-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jon Peterson | ||
| Last updated | 2001-02-28 | ||
| 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
Although the Session Initiation Protocol (SIP) needs no special mechanism to enable network services and applications, in complex architectures, feature composition and service invocation become unmanageable without a mechanism for specifying the services that are associated with routes. This draft introduces distributed application architectures that span multiple administrative domains and proposes the use of ServiceCodes in SIP to allow service providers to compose chains of features across application servers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)