URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)
RFC 7462
| Document | Type |
RFC - Proposed Standard
(March 2015; No errata)
Updates RFC 3261
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Replaces | draft-liess-dispatch-alert-info-urns | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Christer Holmberg | ||
| Shepherd write-up | Show (last changed 2014-03-10) | ||
| IESG | IESG state | RFC 7462 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Richard Barnes | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) L. Liess, Ed.
Request for Comments: 7462 R. Jesske
Updates: 3261 Deutsche Telekom AG
Category: Standards Track A. Johnston
ISSN: 2070-1721 Avaya
D. Worley
Ariadne
P. Kyzivat
Huawei
March 2015
URNs for the Alert-Info Header Field of the
Session Initiation Protocol (SIP)
Abstract
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.
Liess, et al. Standards Track [Page 1]
RFC 7462 Alert URNs March 2015
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7462.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Liess, et al. Standards Track [Page 2]
RFC 7462 Alert URNs March 2015
Table of Contents
1. Introduction ....................................................5
2. Requirements Language ...........................................7
3. Terminology .....................................................7
4. Updates to RFC 3261 .............................................7
4.1. Allow Alert-Info in Provisional Responses ..................7
4.2. Proxies May Alter Alert-Info Header Fields .................8
5. Requirements ....................................................8
6. Use Cases ......................................................10
Show full document text