Re: [sipcore] Reason as a parameter rather than an escaped header

<marianne.mohali@orange-ftgroup.com> Thu, 25 November 2010 22:47 UTC

Return-Path: <marianne.mohali@orange-ftgroup.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F91C3A69C2 for <sipcore@core3.amsl.com>; Thu, 25 Nov 2010 14:47:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 DdpyHN7eEh5a for <sipcore@core3.amsl.com>; Thu, 25 Nov 2010 14:47:21 -0800 (PST)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 4CCDB3A69BF for <sipcore@ietf.org>; Thu, 25 Nov 2010 14:47:21 -0800 (PST)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id A9F996C0007; Thu, 25 Nov 2010 23:48:46 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id 9E0D66C0002; Thu, 25 Nov 2010 23:48:46 +0100 (CET)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Thu, 25 Nov 2010 23:48:22 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 25 Nov 2010 23:48:19 +0100
Message-ID: <B11765B89737A7498AF63EA84EC9F5772378AA@ftrdmel1>
In-Reply-To: <3A8FC9BC-3112-492A-87C2-3B5290A2D36D@acmepacket.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sipcore] Reason as a parameter rather than an escaped header
Thread-Index: AcuMl99FA/lF6V1FR3y5kQR+r7oSCAAWVKMA
References: <CD5674C3CD99574EBA7432465FC13C1B2202288A06@DC-US1MBEX4.global.avaya.com><4CDC04F2.3010701@cisco.com><AANLkTi=utzFcqg_QTfurdB0WKK8MRAny8Pb8CEE=s60L@mail.gmail.com><4CEC570D.8080700@cisco.com> <3A8FC9BC-3112-492A-87C2-3B5290A2D36D@acmepacket.com>
From: <marianne.mohali@orange-ftgroup.com>
To: <HKaplan@acmepacket.com>, <pkyzivat@cisco.com>
X-OriginalArrivalTime: 25 Nov 2010 22:48:22.0218 (UTC) FILETIME=[DCA842A0:01CB8CF2]
Cc: dworley@avaya.com, sipcore@ietf.org
Subject: Re: [sipcore] Reason as a parameter rather than an escaped header
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Nov 2010 22:47:22 -0000

 Hi,

My adding [MM]

Marianne

> -----Message d'origine-----
> De : sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] De la part de Hadriel Kaplan
> Envoyé : jeudi 25 novembre 2010 12:57
> À : Paul Kyzivat
> Cc : Worley, Dale R (Dale); sipcore@ietf.org
> Objet : Re: [sipcore] Reason as a parameter rather than an 
> escaped header
> 
> 
> On Nov 23, 2010, at 7:06 PM, Paul Kyzivat wrote:
> 
> > But my remaining concern is about the rules in 4244bis 
> regarding how 
> > and when Reason headers are included in the H-I entries. It still 
> > seems to me that the text only talks about including them due to a 
> > response having been received. Where is the language that discusses 
> > adding a reason when retargeting is performed for some reason 
> > unrelated to a response?
> > 
> > While I think one can argue that a server doing such 
> retargeting can 
> > imagine having sent the request to a virtual redirect 
> server and then 
> > processing the response from it, ISTM that would then call 
> for adding 
> > H-I entries for those steps.
> 
> Right, that's the main piece to figure out first.  We already 
> agreed that 4244bis tells proxies to create H-I entries for 
> internal retargeting decisions.  What's not clear is what 
> internal H-I entries have to be created, and whether the 
> embedded Reason header value of the *SIP* type can be used 
> for such cases.
> 
> For example, suppose Alice called Bob, and proxy-1 internally 
> diverts it to Charlie because it knows Bob is busy, *without* 
> having to send the INVITE to Bob and getting a 486 response.
> 
> Is it legit for the H-I look like this:
> History-Info: <sip:bob@example.com?Reason=SIP%3Bcause%3D486>;index=1
> History-Info: <sip:charlie@example.com>;index=1.1;mp=1
> History-Info: <sip:charlie@192.1.2.3>;index=1.1.1;rc=1.1
> 
> Or does it have to look like this:
> History-Info: <sip:bob@example.com>;index=1
> History-Info: <sip:bob@127.0.0.1?Reason=SIP%3Bcause%3D486>;index=1.1
> History-Info: <sip:charlie@example.com>;index=1.2;mp=1
> History-Info: <sip:charlie@192.1.2.3>;index=1.2.1;rc=1.2
> 
> Or does it have to do something like this:
> History-Info: 
> <sip:bob@example.com?Reason=Internal%3Bcause%3D486>;index=1
> History-Info: <sip:charlie@example.com>;index=1.1;mp=1
> History-Info: <sip:charlie@192.1.2.3>;index=1.1.1;rc=1.1
> 
[MM] Or (as per 3GPP CDIV 24.604 for call forwarding busy)
History-Info: <sip:bob@example.com>;index=1
History-Info: <sip:charlie@example.com;cause=486>;index=1.1;mp=1
History-Info: <sip:charlie@192.1.2.3>;index=1.1.1;rc=1.1

> -hadriel
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>