An Analysis of Do Not Disturb (DND) Implementations in the Session Initiation Protocol (SIP)
draft-elwell-bliss-dnd-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | John Elwell , Srivatsa Srinivasan | ||
| Last updated | 2007-11-16 | ||
| 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
Do Not Disturb (DND) is a commonly used expression for indicating a condition where a human user of real-time communications does not wish to be interrupted by incoming calls or other forms of communication. This document discusses the nature of DND, ways of observing DND, and limitations of and possible improvements to DND support in the Session Initiation Protocol (SIP) and the Rich Presence Information Data Format (RPID). This work is being discussed on the bliss@ietf.org mailing list.
Authors
John Elwell
Srivatsa Srinivasan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)