RE: [Sip] GRUU Comments and interaction with outbound-connection

hisham.khartabil@nokia.com Tue, 09 November 2004 13:36 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25238 for <sip-web-archive@ietf.org>; Tue, 9 Nov 2004 08:36:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRWB5-0003YT-MD for sip-web-archive@ietf.org; Tue, 09 Nov 2004 08:36:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRW8K-0004aB-2h; Tue, 09 Nov 2004 08:34:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRW0k-0003VI-Lz for sip@megatron.ietf.org; Tue, 09 Nov 2004 08:26:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24268 for <sip@ietf.org>; Tue, 9 Nov 2004 08:26:13 -0500 (EST)
From: hisham.khartabil@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRW1U-0003I8-Bu for sip@ietf.org; Tue, 09 Nov 2004 08:27:01 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iA9DQ7v26233; Tue, 9 Nov 2004 15:26:07 +0200 (EET)
X-Scanned: Tue, 9 Nov 2004 15:25:51 +0200 Nokia Message Protector V1.3.31 2004060815 - RELEASE
Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id iA9DPpmP019394; Tue, 9 Nov 2004 15:25:51 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 00FZXzzV; Tue, 09 Nov 2004 15:24:40 EET
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iA9DOUa17727; Tue, 9 Nov 2004 15:24:30 +0200 (EET)
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 9 Nov 2004 15:24:29 +0200
Received: from esebe056.NOE.Nokia.com ([172.21.143.51]) by esebe018.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 9 Nov 2004 15:24:29 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] GRUU Comments and interaction with outbound-connection
Date: Tue, 09 Nov 2004 15:24:29 +0200
Message-ID: <5816828233DEFA41807A6CFDFDF2343C3A8C39@esebe056.ntc.nokia.com>
Thread-Topic: [Sip] GRUU Comments and interaction with outbound-connection
Thread-Index: AcTF5Y3I4dx6sZ8iRdKBwr7XppTqmAAeaRmw
To: alan@jasomi.com, jdrosen@cisco.com
X-OriginalArrivalTime: 09 Nov 2004 13:24:29.0557 (UTC) FILETIME=[7123A250:01C4C65F]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable
Cc: fluffy@cisco.com, sip@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable

That's exactly what I was thinking. The Proxy/registrar can add the actual contact of the recipient as the first entry in the target set. That gets placed in the request-URI. Proxy routes to first route header (EP) in this case. EP routes to end point.

/Hisham

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org]On 
> Behalf Of ext
> Alan Hawrylyshen
> Sent: 09.November.2004 00:18
> To: Jonathan Rosenberg
> Cc: Cullen Jennings; sip@ietf.org
> Subject: [Sip] GRUU Comments and interaction with outbound-connection
> 
> 
> Re: the Edge Proxy, Reg/Prox RR problems....
> 
> Johnathan;
> 
> It strikes me that the EP can directly route the GRUU since it is 
> (except in the 3GPP case) in the same administrative / security / 
> policy domain as the registrar and SHOULD be capable of detecting the 
> GRUU's applicability when the initial request hits the EP.  An 
> appropriately constructed (encoded) GRUU could be decoded and dealt 
> with as soon as it reaches the UA's EP, no?
> 
> And as I write this, Cullen has just proposed the same thing.
> 
> Alan
> 
> 
> 
> a l a n a t j a s o m i d o t c o m
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip