Browse Prior Art Database

Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in the Session Initiation Protocol (SIP) (RFC6044) Disclosure Number: IPCOM000200921D
Original Publication Date: 2010-Oct-01
Included in the Prior Art Database: 2010-Oct-30
Document File: 48 page(s) / 55K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Mohali: AUTHOR


1.1. Overview

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Independent Submission                                         M. Mohali Request for Comments: 6044                         France Telecom Orange Category: Informational                                     October 2010 ISSN: 2070-1721

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


   Although the SIP History-Info header is the solution adopted in IETF,    the non-standard Diversion header is nevertheless widely implemented    and used for conveying call-diversion-related information in SIP    signaling.

   This document describes a recommended interworking guideline between    the Diversion header and the History-Info header to handle call    diversion information.  In addition, an interworking policy is    proposed to manage the headers' coexistence.  The History-Info header    is described in RFC 4244 and the non-standard Diversion header is    described, as Historic, in RFC 5806.

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

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

 Mohali                        Informational                     [Page 1]
 RFC 6044           Mapping Diversion and History-Info       October 2010

 Copyright Notice

   Copyright (c) 2010 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    ( 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 ....................