%% You should probably cite rfc7462 instead of this I-D. @techreport{ietf-salud-alert-info-urns-12, number = {draft-ietf-salud-alert-info-urns-12}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-salud-alert-info-urns/12/}, author = {Laura Liess and Roland Jesske and Alan Johnston and Dale R. Worley and Paul Kyzivat}, title = {{URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)}}, pagetotal = 43, year = 2014, month = mar, day = 3, 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 field. However, the reference (typically a URL) addresses only a specific network resource with specific rendering properties. There is currently no support for 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 these limitations and support new applications, a new family of URNs for use in Alert-Info header fields (and situations with similar requirements) is defined in this specification. This document normatively updates the RFC 3261, which defines the Session Initiation Protocol (SIP): It changes the usage of the Alert- Info header field defined in the RFC 3261 by additionally allowing its use in all provisional responses to INVITE (except the 100 response).}, }