RFC 6044 on Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in the Session Initiation Protocol (SIP)
rfc-editor@rfc-editor.org Sat, 30 October 2010 02:05 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 40EBC3A63D2 for <ietf-announce@core3.amsl.com>; Fri, 29 Oct 2010 19:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.415
X-Spam-Level:
X-Spam-Status: No, score=-102.415 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VuNaWG6QEV-d for <ietf-announce@core3.amsl.com>; Fri, 29 Oct 2010 19:05:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 49B6D3A69E0 for <ietf-announce@ietf.org>; Fri, 29 Oct 2010 19:05:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A38B0E0704; Fri, 29 Oct 2010 19:07:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6044 on Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in the Session Initiation Protocol (SIP)
From: rfc-editor@rfc-editor.org
Message-Id: <20101030020749.A38B0E0704@rfc-editor.org>
Date: Fri, 29 Oct 2010 19:07:49 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Oct 2010 02:05:58 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6044
Title: Mapping and Interworking of Diversion
Information between Diversion and History-Info Headers
in the Session Initiation Protocol (SIP)
Author: M. Mohali
Status: Informational
Stream: Independent
Date: October 2010
Mailbox: marianne.mohali@orange-ftgroup.com
Pages: 24
Characters: 54486
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-mohali-diversion-history-info-07.txt
URL: http://www.rfc-editor.org/rfc/rfc6044.txt
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. This document is not an Internet
Standards Track specification; it is published for informational purposes.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC