Mapping and interworking of Diversion information Between Diversion and History-Info Headers in the Session Initiation Protocol (SIP)
draft-mohali-rfc6044bis-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-02-23 (latest revision 2015-02-17)
Stream ISE
Intended RFC status Informational
Formats plain text pdf html bibtex
IETF conflict review conflict-review-mohali-rfc6044bis
Stream ISE state Finding Reviewers
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to "Nevil Brownlee" <rfc-ise@rfc-editor.org>
Network Working Group                                          M. Mohali
Internet-Draft                                                    Orange
Obsoletes: 6044 (if approved)                          February 18, 2015
Intended status: Informational
Expires: August 22, 2015

Mapping and interworking of Diversion information Between Diversion and
     History-Info Headers in the Session Initiation Protocol (SIP)
                       draft-mohali-rfc6044bis-01

Abstract

   Although the SIP History-Info header field is the solution adopted in
   IETF, the non-standard Diversion header field is nevertheless already
   implemented and used for conveying call diversion related information
   in the Session Initiation Protocol (SIP) signaling.
   On one hand, the non-standard Diversion header field is described, as
   Historic, in [RFC5806].  On the other hand, the History-Info header
   field is described in [RFC7044] that obsoletes the original[RFC4244]
   describing the History-Info header field.  [RFC7044] defines the SIP
   header field, History-Info, for capturing the history information in
   requests and new 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.  [RFC7044] also defines a value for the
   Privacy header field that directs the anonymization of values in the
   History-Info header field.

   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.  In addition, an interworking
   policy is proposed to manage the headers' coexistence.  This work is
   intended to enable the migration from non-standard implementations
   and deployments toward IETF specification-based implementations and
   deployments.
   This document obsoletes [RFC6044]that describes the interworking
   between the Diversion header field [RFC5806] and the obsoleted
   History-Info header field as defined on [RFC4244].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

Mohali                   Expires August 22, 2015                [Page 1]
Internet-Draft    Mapping of Diversion and History-Info    February 2015

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 22, 2015.

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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Background  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  From RFC4244 to RFC7044 . . . . . . . . . . . . . . . . .   4
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Interworking requirements and scope . . . . . . . . . . .   5
     2.2.  Interworking recommendations  . . . . . . . . . . . . . .   7
       2.2.1.  SIP network/terminal using Diversion to SIP
               network/terminal using History-Info header  . . . . .   7
       2.2.2.  SIP network/terminal using History-Info header to SIP
               network/terminal using Diversion header . . . . . . .   9
   3.  Header fields syntaxes reminder . . . . . . . . . . . . . . .  10
     3.1.  History-Info header syntax  . . . . . . . . . . . . . . .  10
     3.2.  Diversion header syntax . . . . . . . . . . . . . . . . .  13
   4.  Headers in SIP Method . . . . . . . . . . . . . . . . . . . .  13
   5.  Diversion header to History-Info header . . . . . . . . . . .  14
   6.  History-Info header to Diversion header . . . . . . . . . . .  17
   7.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  19
     7.1.  Example with Diversion header changed into History-Info
           header  . . . . . . . . . . . . . . . . . . . . . . . . .  19
Show full document text