%% You should probably cite rfc7462 instead of this I-D. @techreport{ietf-salud-alert-info-urns-07, number = {draft-ietf-salud-alert-info-urns-07}, 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/07/}, author = {Laura Liess and Roland Jesske and Alan Johnston and Dale R. Worley and Paul Kyzivat}, title = {{Alert-Info URNs for the Session Initiation Protocol (SIP)}}, pagetotal = 39, year = 2012, month = oct, day = 2, 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 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).}, }