Extending the Session Initiation Protocol Reason Header to account for Preemption Events
draft-polk-sipping-reason-header-for-preemption-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | James Polk | ||
| Last updated | 2003-10-10 | ||
| 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
This document proposes an extension to the Session Initiation Protocol (SIP) Reason Header [1] to include in a BYE Method Request [2] as a result of a session preemption event either at a user agent (UA), or somewhere in the network using RSVP [3]. This document does not attempt to address routers failing in the packet path; but a deliberate event of tearing down a flow between UAs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)