An Extension to the Session Initiation Protocol (SIP) for Request History Information (RFC7044)
Original Publication Date: 2014-Feb-01
Included in the Prior Art Database: 2014-Feb-05
Internet Society Requests For Comment (RFCs)
M. Barnes: AUTHOR [+5]
Many services that SIP is anticipated to support require the ability to determine why and how a SIP request arrived at a specific application. Examples of such services include (but are not limited to) sessions initiated to call centers via "click to talk" SIP Uniform Resource Locators (URLs) on a web page, "call history/ logging"-style services within intelligent "call management" software for SIP user agents (UAs), and calls to voicemail servers. Although SIP implicitly provides the retarget capabilities that enable SIP requests to be routed to chosen applications, there is a need for a standard mechanism within SIP for communicating the retargeting history of the requests. This request history information allows the receiving application to obtain information about how and why the SIP request arrived at the application/user.
Internet Engineering Task Force (IETF) M. Barnes Request for Comments: 7044 Polycom Obsoletes: 4244 F. Audet Category: Standards Track Skype ISSN: 2070-1721 S. Schubert NTT J. van Elburg Detecon International Gmbh C. Holmberg Ericsson February 2014
An Extension to the Session Initiation Protocol (SIP) for Request History Information
This document defines a standard mechanism for capturing the history information associated with a Session Initiation Protocol (SIP) request. This capability enables many enhanced services by providing the information as to how and why a SIP request arrives at a specific application or user. This document defines an optional SIP header field, History-Info, for capturing the history information in requests. The document also defines SIP header field parameters for the History-Info and Contact header fields to tag the method by which the target of a request is determined. In addition, this specification defines a value for the Privacy header field that directs the anonymization of values in the History-Info header field. This document obsoletes RFC 4244.
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/rfc7044.
Barnes, et al. ...