Response Code for Dynamic Proxy Redirect
draft-rajesh-sipping-303-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rajesh Ramanathan | ||
| Last updated | 2007-03-07 | ||
| 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
The Session Initiation Protocol (SIP) allows for sessions to be redirected by the use of the 3xx response code. This response code allows redirect servers and proxies to redirect the session or for the message to be sent all the way back to the initiating client to recurse. There is no way to direct the domain responsible for the Request-URI to perform the redirection. This document defines a new response code that clients and redirect servers could use to ensure that recursion take place within the domain responsible for the Request-URI rather than allowing the initiating client do perform the redirect.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)