Re-INVITE Handling in the Session Initiation Protocol (SIP)
draft-camarillo-sipping-reinvite-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Gonzalo Camarillo | ||
| Last updated | 2009-07-20 (Latest revision 2009-03-03) | ||
| Replaced by | draft-camarillo-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-camarillo-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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)