Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 3261

Authors:

L. Liess, Ed.
R. Jesske
A. Johnston
D. Worley
P. Kyzivat

Stream:

IETF

Source:

salud (rai)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7462

Discuss this RFC: Send questions or comments to the mailing listsalud@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7462

Abstract

The Session Initiation Protocol (SIP) supports the capability toprovide a reference to a specific rendering to be used by the UserAgent (UA) as an alerting signal (e.g., a ring tone or ringback tone)when the user is alerted. This is done using the Alert-Info headerfield. However, the reference (typically a URL) addresses only aspecific network resource with specific rendering properties. Thereis currently no support for standard identifiers for describing thesemantics of the alerting situation or the characteristics of thealerting signal, without being tied to a particular rendering. Toovercome these limitations and support new applications, a new familyof URNs for use in Alert-Info header fields (and situations withsimilar requirements) is defined in this specification.

This document normatively updates RFC 3261, which defines the SessionInitiation Protocol (SIP). It changes the usage of the Alert-Infoheader field defined in RFC 3261 by additionally allowing its use inany non-100 provisional response to INVITE. This document alsopermits proxies to add or remove an Alert-Info header field and toadd or remove Alert-Info header field values.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.