Alert-Info URNs for the Session Initiation Protocol (SIP)
draft-liess-dispatch-alert-info-urns-03
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Laura Liess , Denis Alexeitsev , Roland Jesske , Alan Johnston , Anwar A. Siddiqui | ||
Last updated | 2012-04-26 (Latest revision 2010-10-19) | ||
Replaced by | draft-ietf-salud-alert-info-urns | ||
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-ietf-salud-alert-info-urns | |
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
The Session Initiation Protocol (SIP) supports the capability to provide a reference to a specific rendering to be used by the UA when the user is alerted. This is done using the Alert-Info header. However, the reference addresses only network resources with specific rendering properties. There is currently no support for predefined standard identifiers for describing the semantics of the alerting situation or the characteristics of the alerting signal, without being tied to a particular rendering. To overcome this limitation and support new applications, a new family of URNs for use in SIP Alert-Info header fields is defined in this specification.
Authors
Laura Liess
Denis Alexeitsev
Roland Jesske
Alan Johnston
Anwar A. Siddiqui
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)