AW: [Sipping-tispan] Requirements 02e

"Jesske, R" <R.Jesske@t-com.net> Fri, 23 September 2005 10:49 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIl7k-00078L-UI; Fri, 23 Sep 2005 06:49:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIl7i-00077h-BA for sipping-tispan@megatron.ietf.org; Fri, 23 Sep 2005 06:49:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06916 for <sipping-tispan@ietf.org>; Fri, 23 Sep 2005 06:49:43 -0400 (EDT)
Received: from tcmail33.telekom.de ([217.6.95.240]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIlE8-0002h3-ID for sipping-tispan@ietf.org; Fri, 23 Sep 2005 06:56:24 -0400
Received: from S4DE8PSAANQ.mitte.t-com.de by tcmail31.dmz.telekom.de with ESMTP; Fri, 23 Sep 2005 12:49:36 +0200
Received: by S4DE8PSAANQ.blf.telekom.de with Internet Mail Service (5.5.2653.19) id <TGB279XW>; Fri, 23 Sep 2005 12:49:36 +0200
Message-Id: <E7666D92C64C2845AEF12636FF94F95202319F6C@S4DE8PSAAGQ.blf.telekom.de>
From: "Jesske, R" <R.Jesske@t-com.net>
To: jbemmel@lucent.com, pkyzivat@cisco.com, Miguel.An.Garcia@nokia.com
Subject: AW: [Sipping-tispan] Requirements 02e
Date: Fri, 23 Sep 2005 12:49:33 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: quoted-printable
Cc: sipping-tispan@ietf.org
X-BeenThere: sipping-tispan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of requirements for SIP introduced by ETSI TISPAN <sipping-tispan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sipping-tispan>
List-Post: <mailto:sipping-tispan@ietf.org>
List-Help: <mailto:sipping-tispan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=subscribe>
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org

In principle I have nothing against such an approach.
But what is in the case of diverting the communication.
So that the to header is different from the P-Asserted-Identity and the identity in the to header belongs not to the user where the communication was sent to originally?

Roland

> -----Ursprüngliche Nachricht-----
> Von: Bemmel, Jeroen van (Jeroen) [mailto:jbemmel@lucent.com] 
> Gesendet: Freitag, 23. September 2005 12:34
> An: Jesske, Roland; pkyzivat@cisco.com; Miguel.An.Garcia@nokia.com
> Cc: sipping-tispan@ietf.org
> Betreff: RE: [Sipping-tispan] Requirements 02e
> 
> 
> > So we want the have the same within SIP. In forward direction 
> > we have the From header and the P-Asserted-Identity. But in 
> > Backward direction the equivalent to the From header is missing.
> > 
> > So we need such an identity header for the backward direction 
> > setup from the callee.
> > 
> > Roland
> 
> What if the callee would simply add a parameter to the To 
> header? Something like
> To: 
> <sip:callee@provider.com>;tag=25425741;identity=user@altprovider.com
> 
> Jeroen
> 

_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan