Asynchronous Service State Notifications From SIP Entities
draft-mahesh-sipping-svc-state-notify-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mahesh Govind | ||
| Last updated | 2006-03-27 | ||
| 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 describes the requirement for in-advance asynchronous service state notifications from a SIP[1] entity to its USER .The notifications MAY be about the state of the entity or the state of the session. It also explains certain mechanisms for implementing the same. This document is divided into three parts . 1)An Event Specification. 2)Use cases for event specification and mechanisms to extend this specification. 3)Limitations and Future work.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)