[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Proposed solution for UA loose/target/History-Info problem
Agree here.
I was just trying to say, "hey, if you don't care or don't want anythinFrom sip-bounces at ietf.org Mon Jul 28 10:20:53 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id EC34128C228;
Mon, 28 Jul 2008 10:20:52 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id E41FB28C20C
for <sip at core3.amsl.com>; Mon, 28 Jul 2008 10:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 TMCeuJqHga1u for <sip at core3.amsl.com>;
Mon, 28 Jul 2008 10:20:47 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
by core3.amsl.com (Postfix) with ESMTP id 9E78A28C1C6
for <sip at ietf.org>; Mon, 28 Jul 2008 10:20:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,266,1215388800"; d="scan'208";a="15618358"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
by ams-iport-1.cisco.com with ESMTP; 28 Jul 2008 17:20:55 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m6SHKtFq022082;
Mon, 28 Jul 2008 19:20:55 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
[144.254.231.87])
by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m6SHKtOJ017429;
Mon, 28 Jul 2008 17:20:55 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 28 Jul 2008 19:20:55 +0200
Received: from [10.61.65.89] ([10.61.65.89]) by xfe-ams-332.cisco.com with
Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 Jul 2008 19:20:55 +0200
Message-ID: <488DFFFF.7090904 at cisco.com>
Date: Mon, 28 Jul 2008 13:21:03 -0400
From: Jonathan Rosenberg <jdrosen at cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Francois Audet <audet at nortel.com>
References: <488D061B.2070009 at cisco.com>
<E6C2E8958BA59A4FB960963D475F7AC30EFFC85ED3 at mail.acmepacket.com>
<1ECE0EB50388174790F9694F77522CCF1832D419 at zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1832D419 at zrc2hxm0.corp.nortel.com>
X-OriginalArrivalTime: 28 Jul 2008 17:20:55.0187 (UTC)
FILETIME=[4AFDBE30:01C8F0D6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2237; t=1217265655;
x=1218129655; c=relaxed/simple; s=amsdkim1002;
h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
d=cisco.com; i=jdrosen at cisco.com;
z=From:=20Jonathan=20Rosenberg=20<jdrosen at cisco.com>
|Subject:=20Re=3A=20[Sip]=20Proposed=20solution=20for=20UA=
20loose/target/History-Info=20problem |Sender:=20;
bh=VchpKcbcvGnDQw5u0G4b2yALE9dh/gx8Hfyti4i4pO8=;
b=nO4gjsxbftMAujegJ6CbIAQ89V2Y+PGF31lXlxtDz3dA1Wp7HIDLlpfgzF
Puw4f6k7fnCvcvVAG7x9otX5MHDFtjbU+T1lYFzwhvineodgDzMNFZqk2tWP
uwU2LrIXl6;
Authentication-Results: ams-dkim-1; header.From=jdrosen at cisco.com; dkim=pass (
sig from cisco.com/amsdkim1002 verified; );
Cc: IETF SIP List <sip at ietf.org>
Subject: Re: [Sip] Proposed solution for UA loose/target/History-Info problem
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
Agree here.
I was just trying to say, "hey, if you don't care or don't want anything
but this basic usage of HI, this is what you'd do". A spec would say
something like MAY remove or MAY append. Main thing is, if you append,
you do need to check to make sure the incoming RURI is not already
there, and if it is, add the target attribute. So its simpler if you
just remove everything and re-add, but destroys other usages of HI.
-Jonathan R.
Francois Audet wrote:
Yeah, that was exactly my concern.
It should ADD the entries to the existing History-Info if
present.
-----Original Message-----
From: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org] On
Behalf Of Hadriel Kaplan
Sent: Monday, July 28, 2008 03:28
To: Jonathan Rosenberg; IETF SIP List
Subject: Re: [Sip] Proposed solution for UA
loose/target/History-Info problem
-----Original Message-----
From: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org] On
Behalf Of
Jonathan Rosenberg
For a proxy:
If the proxy is rewriting the r-uri as a consequence of
looking it
up in a registration database, it looks at the incoming request. It
removes any existing H-I values. It then adds two H-I
values that look like this:
History-Info: <sip:incoming-ruri>;target;index=1
<sip:outgoing-ruri>;target;index=1.1
and thats it. So really easy for a proxy.
I'm confused. Why is it removing any existing HI values?
Doesn't that break its compatibility with legacy HI usage?
-hadriel
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
--
Jonathan D. Rosenberg, Ph.D. 499 Thornall St.
Cisco Fellow Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen at cisco.com
http://www.jdrosen.net PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
g
but this basic usage of HI, this is what you'd do". A spec would say
something like MAY remove or MAY append. Main thing is, if you append,
you do need to check to make sure the incoming RURI is not already
there, and if it is, add the target attribute. So its simpler if you
just remove everything and re-add, but destroys other usages of HI.
-Jonathan R.
Francois Audet wrote:
Yeah, that was exactly my concern.
It should ADD the entries to the existing History-Info if
present.
-----Original Message-----
From: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org] On
Behalf Of Hadriel Kaplan
Sent: Monday, July 28, 2008 03:28
To: Jonathan Rosenberg; IETF SIP List
Subject: Re: [Sip] Proposed solution for UA
loose/target/History-Info problem
-----Original Message-----
From: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org] On
Behalf Of
Jonathan Rosenberg
For a proxy:
If the proxy is rewriting the r-uri as a consequence of
looking it
up in a registration database, it looks at the incoming request. It
removes any existing H-I values. It then adds two H-I
values that look like this:
History-Info: <sip:incoming-ruri>;target;index=1
<sip:outgoing-ruri>;target;index=1.1
and thats it. So really easy for a proxy.
I'm confused. Why is it removing any existing HI values?
Doesn't that break its compatibility with legacy HI usage?
-hadriel
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
--
Jonathan D. Rosenberg, Ph.D. 499 Thornall St.
Cisco Fellow Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen at cisco.com
http://www.jdrosen.net PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip