Mapping and Interworking of Diversion Information between Diversion and History-Info Header Fields in the Session Initiation Protocol (SIP)
RFC 7544

Document Type RFC - Informational (August 2015; Errata)
Obsoletes RFC 6044
Was draft-mohali-rfc6044bis (individual)
Last updated 2015-10-14
Stream ISE
Formats plain text pdf html bibtex
IETF conflict review conflict-review-mohali-rfc6044bis
Stream ISE state Published RFC
Consensus Boilerplate Unknown
Document shepherd Nevil Brownlee
Shepherd write-up Show (last changed 2015-03-09)
IESG IESG state RFC 7544 (Informational)
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IC
Independent Submission                                         M. Mohali
Request for Comments: 7544                                        Orange
Obsoletes: 6044                                              August 2015
Category: Informational
ISSN: 2070-1721

Mapping and Interworking of Diversion Information between Diversion and
  History-Info Header Fields in the Session Initiation Protocol (SIP)

Abstract

   Although the SIP History-Info header field described in RFC 7044 is
   the solution adopted in IETF, the non-standard Diversion header field
   described, as Historic, in RFC 5806 is nevertheless already
   implemented and used for conveying call-diversion-related information
   in Session Initiation Protocol (SIP) signaling.

   RFC 7044 obsoletes the original RFC 4244 and redefines the History-
   Info header field for capturing the history information in requests.

   Since the Diversion header field is used in existing network
   implementations for the transport of call diversion information, its
   interworking with the SIP History-Info standardized solution is
   needed.  This document describes a recommended interworking guideline
   between the Diversion header field and the History-Info header field
   to handle call diversion information.  This work is intended to
   enable the migration from non-standard implementations toward IETF
   specification-based implementations.

   This document obsoletes RFC 6044, which describes the interworking
   between the Diversion header field defined in RFC 5806 and the
   obsoleted History-Info header field defined on RFC 4244.

Mohali                        Informational                     [Page 1]
RFC 7544          Mapping of Diversion and History-Info      August 2015

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any other
   RFC stream.  The RFC Editor has chosen to publish this document at
   its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor are not a candidate for any level of Internet
   Standard; see 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/rfc7544.

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.

Mohali                        Informational                     [Page 2]
RFC 7544          Mapping of Diversion and History-Info      August 2015

Table of Contents

   1. Introduction ....................................................4
      1.1. Overview ...................................................4
      1.2. Background .................................................4
      1.3. From RFC 4244 to RFC 7044 ..................................5
   2. Problem Statement ...............................................5
   3. Interworking Recommendations ....................................7
      3.1. General Recommendations ....................................7
      3.2. Privacy Considerations .....................................8
      3.3. Headers in SIP Method .....................................10
      3.4. SIP Network/Terminal Using Diversion Header Field
           to SIP Network/Terminal Using History-Info Header Field ...10
      3.5. SIP Network/Terminal Using History-Info Header
           Field to SIP Network/Terminal Using Diversion
           Header Field ..............................................12
   4. Reminder of the Syntax for Header Fields .......................13
      4.1. History-Info Header Field Syntax ..........................13
      4.2. Diversion Header Field Syntax .............................16
   5. Diversion Header Field to History-Info Header Field ............16
   6. History-Info Header Field to Diversion Header Field ............20
   7. Examples .......................................................22
     7.1.  Example with Diversion Header Field Changed into
           History-Info Header Field .................................22
     7.2.  Example with History-Info Header Field Changed into
           Diversion Header Field ....................................22
     7.3.  Example with Two SIP Networks Using History-Info Header
Show full document text