An Extension to the Session Initiation Protocol (SIP) for Request History Information
RFC 7044
Document | Type |
RFC - Proposed Standard
(February 2014; Errata)
Obsoletes RFC 4244
|
|
---|---|---|---|
Authors | Mary Barnes , Francois Audet , Shida Schubert , Hans van Elburg , Christer Holmberg | ||
Last updated | 2015-10-14 | ||
Replaces | draft-barnes-sipcore-rfc4244bis | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 7044 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Richard Barnes | ||
IESG note | Paul Kyzivat (pkyzivat@alum.mit.edu) is the document shepherd. | ||
Send notices to | (None) | ||
IANA | IANA review state | IANA - Review Needed | |
IANA action state | RFC-Ed-Ack |
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 Abstract 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. Standards Track [Page 1] RFC 7044 History-Info February 2014 Copyright Notice Copyright (c) 2014 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. Barnes, et al. Standards Track [Page 2] RFC 7044 History-Info February 2014 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4 3. Background . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. History-Info Header Field Protocol Structure . . . . . . . . 7 5.1. History-Info Header Field Example Scenario . . . . . . . 10 6. User Agent Handling of the History-Info Header Field . . . . 12 6.1. User Agent Client (UAC) Behavior . . . . . . . . . . . . 12 6.2. User Agent Server (UAS) Behavior . . . . . . . . . . . . 12 6.3. Back-to-Back User Agent (B2BUA) Behavior . . . . . . . . 12 7. Proxy/Intermediary Handling of History-Info Header Fields . . 13 8. Redirect Server Handling of History-Info Header Fields . . . 13 9. Handling of History-Info Header Fields in Requests andShow full document text