The SIP SPECIFY Method
draft-sreeram-specify-method-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sreeram Kanumuri , Subhodeep Sarkar | ||
| Last updated | 2006-10-16 | ||
| 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 proposes an extension to the Session Initiation Protocol (SIP). This extension adds the SPECIFY method to the SIP protocol. The intent of the SPECIFY method is to allow conveying SIP entity's (Proxy, User Agent, Redirect Server) intention of asynchronous service change (i.e. to be taken out of service or has just return to service) with and with out a backup SIP entity within the same administrative domain.
Authors
Sreeram Kanumuri
Subhodeep Sarkar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)