Re-INVITE and Target-refresh Request Handling in the Session Initiation Protocol (SIP)
draft-camarillo-sipcore-reinvite-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gonzalo Camarillo , Christer Holmberg , Gao yang | ||
| Last updated | 2010-01-13 (Latest revision 2009-10-26) | ||
| Replaces | draft-camarillo-sipping-reinvite | ||
| Replaced by | draft-ietf-sipcore-reinvite | ||
| 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-ietf-sipcore-reinvite | |
| 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
In this document, we clarify the handling of re-INVITEs in SIP. We clarify in which situations a UAS (User Agent Server) should generate a success response and in which situations a UAS should generate an error response to a re-INVITE. Additionally, we clarify issues related to target-refresh requests.
Authors
Gonzalo Camarillo
Christer Holmberg
Gao yang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)