[BLISS] New draft submission

<marianne.mohali@orange-ftgroup.com> Tue, 15 July 2008 12:29 UTC

Return-Path: <bliss-bounces@ietf.org>
X-Original-To: bliss-archive@optimus.ietf.org
Delivered-To: ietfarch-bliss-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03FEF3A6992; Tue, 15 Jul 2008 05:29:12 -0700 (PDT)
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D01F3A698D; Tue, 15 Jul 2008 05:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level:
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.835, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 bPwjcIcgXi5Y; Tue, 15 Jul 2008 05:29:10 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 1F6E53A6992; Tue, 15 Jul 2008 05:29:09 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 15 Jul 2008 14:29:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 15 Jul 2008 14:29:33 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02605B8622A@ftrdmel2>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: New draft submission
Thread-Index: Acjmdm+3acX2c1qQSmqpbUpwLWo3KQ==
From: marianne.mohali@orange-ftgroup.com
To: sipping@ietf.org, bliss@ietf.org
X-OriginalArrivalTime: 15 Jul 2008 12:29:34.0828 (UTC) FILETIME=[7083E2C0:01C8E676]
Subject: [BLISS] New draft submission
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1979612815=="
Sender: bliss-bounces@ietf.org
Errors-To: bliss-bounces@ietf.org

Hi,

I've just submitted the following draft: 
http://tools.ietf.org/html/draft-mohali-diversion-history-info-00

The motivation of the draft is to provide guidelines on mapping between
the Diversion header and the History-Info header and possibly a
Voicemail-uri. 

We believe that having clearly defined mapping procedures between these
two headers will greatly facilitate migration from the Diversion header
to the History-Info header.

Lack of clear mapping between both headers could result in significant
interoperability issues and therefore delay widespread implementation of
the History-Info header. 

As you can see from the list of co-authors this issue is of interest to
a number of people. We would like to get more feedback on the proposed
solution and confirmation of interest from the IETF community. 

Best Regards,
Marianne Mohali

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss