Delivery of Request-URI Targets to User Agents
draft-rosenberg-sip-target-uri-delivery-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christer Holmberg , Jonathan Rosenberg , Shida Schubert | ||
| Last updated | 2009-07-20 (Latest revision 2009-03-09) | ||
| Replaced by | draft-rosenberg-sipcore-target-uri-delivery | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-rosenberg-sipcore-target-uri-delivery | |
| 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
When a Session Initiation Protocol (SIP) proxy receives a request targeted at a URI identifying a user or resource it is responsible for, the proxy translates the URI to a registered or configured contact URI of an agent representing that user or resource. In the process, the original URI is removed from the request. Numerous use cases have arisen which require this information to be delivered to the user agent. This document describes these use cases and defines an extension to the History-Info header field which allows it to be used to support those cases.
Authors
Christer Holmberg
Jonathan Rosenberg
Shida Schubert
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)