Architectural Considerations for Providing Carrier Class Telephony Services Utilizing SIP-based Distributed Call Control Mechanisms
draft-dcsgroup-sip-arch-06
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. K. K. Ramakrishnan , Matt Osman , Flemming Andreasen , Doc Evans | ||
| Last updated | 2002-03-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 document provides an overview of a SIP-based Distributed Call Signaling (DCS) architecture to support carrier class packet-based documents address a specific set of SIP 2.0 protocol extensions and usage rules that are necessary to implement the DCS architecture in an interoperable fashion.
Authors
Dr. K. K. Ramakrishnan
Matt Osman
Flemming Andreasen
Doc Evans
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)