The SIP Refer Method
draft-sparks-sip-refer-3265disc-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robert Sparks | ||
| Last updated | 2002-06-12 | ||
| 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 IS AN INDIVIDUAL SUBMISSION PROPOSING A CHANGE TO draft-ietf- sip-refer. IT IS FOR DISCUSSION ONLY. This document defines the REFER method. This SIP extension requests that the recipient REFER to a resource provided in the request. It provides a mechanism allowing the party sending the REFER to be notified of the outcome of the referenced request. This can be used to enable many applications, including call transfer. In addition to the REFER method, this document defines the referevent option tag, the refer event package, and the Refer-To request header.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)