SIP and SOAP
draft-deason-sip-soap-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Neil Deason | ||
| Last updated | 2000-07-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 describes an extension to the Session Initiation Protocol (SIP) [1] . The purpose of this extension is to provide an extremely generic and extensible framework through which SIP nodes can request additional services from remote nodes. Examples of such nodes include SIP Network Servers, SIP User Agents, SIP/PSTN Gateways, SIP/H.323 Gateways and SIP Enabled Application Service Brokers. It also a candidate for providing a remote procedure call mechanism for Call Processing Language (CPL) scripts [2] . This proposal is based upon a new SIP method, called SERVICE. The SERVICE method can carry a Simple Object Access Protocol (SOAP) [3] message as it's payload. SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. SOAP defines a framework for encoding request and response messages in XML. Typically SOAP uses HTTP as a transport protocol but this proposal enables SIP to be used instead.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)