Ad-Hoc URI List Management in the Session Initiation Protocol (SIP)
draft-camarillo-sipping-adhoc-management-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Gonzalo Camarillo | ||
| Last updated | 2004-02-09 | ||
| 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 defines two mechanisms to manage ad-hoc URI lists in SIP. In the first mechanism, the user agent sends an updated version of the entire list to the server. In the second mechanism, the server provides the user agent with a URI (e.g., http) that can be used to manipulate the list using an out-of-band mechanim (e.g., XCAP). We define the Associated-List-Manipulation header field that carries a URI that allows manipulating an ad-hoc list.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)