Suspending and Resuming for Modification
draft-gaoyang-sipcore-suspending-and-resuming-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Gao yang | ||
| Last updated | 2009-08-25 | ||
| 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
RFC3312 & 4032 has defined semantics of suspending and resuming for session establishment. But suspending and resuming for session modification needs clarification, especially for modification with part of the streams with precondition. This text just aims for giving out some use case for further analysis. And if we need do some standard track for this issue, IMO, the "Re-INVITE Handling" draft can be more proper and systematic.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)