RFC 7462: URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) supports the capability to provide a reference to a specific rendering to be used by the User Agent (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 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 RFC 3261, which defines the Session Initiation Protocol (SIP). It changes the usage of the Alert-Info header field defined in RFC 3261 by additionally allowing its use in any non-100 provisional response to INVITE. This document also permits proxies to add or remove an Alert-Info header field and to add or remove Alert-Info header field values.
Document record
- Document ID
- RFC7462
- Published
- March 2015
- Authors
- L. Liess; R. Jesske; A. Johnston; D. Worley; P. Kyzivat
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 46
- Also known as
- —
- Updates:
- RFC 3261
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7463Shared Appearances of a Session Initiation Protocol (SIP) Address of Record (AOR)Current
March 2015
- RFC 7459Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO)Current
February 2015
- RFC 7434Interworking ISDN Call Control User Information with SIPCurrent
January 2015
- RFC 7433A Mechanism for Transporting User-to-User Call Control Information in SIPCurrent
January 2015
- RFC 7415Session Initiation Protocol (SIP) Rate ControlCurrent
February 2015
- RFC 7339Session Initiation Protocol (SIP) Overload ControlCurrent
September 2014
- RFC 7657Differentiated Services (Diffserv) and Real-Time CommunicationCurrent
November 2015
- RFC 7701Multi-party Chat Using the Message Session Relay Protocol (MSRP)Current
December 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?