Alert-Info URNs for the Session Initiation Protocol (SIP)

The information below is for an old version of the document
Document Type Expired Internet-Draft (salud WG)
Last updated 2013-04-05 (latest revision 2012-10-02)
Replaces draft-liess-dispatch-alert-info-urns
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 field. 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. This document normatively updates [RFC3261], the Session Initiation Protocol (SIP). It changes the usage of the SIP Alert-Info header field defined in the [RFC3261] by additionally allowing its use in all provisional responses to INVITE (except the 100 response).


Laura Liess (
Roland Jesske (
Alan Johnston (
Dale Worley (
Paul Kyzivat (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)