Re: [Sip] Re: draft-ietf-sip-gruu-09
Paul Kyzivat <pkyzivat@cisco.com> Thu, 27 July 2006 13:14 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G65h6-0000GL-9n; Thu, 27 Jul 2006 09:14:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G65h4-0000GG-Um for sip@ietf.org; Thu, 27 Jul 2006 09:14:26 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G65h2-0006R1-Kl for sip@ietf.org; Thu, 27 Jul 2006 09:14:26 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 27 Jul 2006 06:14:24 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.07,187,1151910000"; d="scan'208"; a="33571164:sNHT23032792"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k6RDEOYP031093 for <sip@ietf.org>; Thu, 27 Jul 2006 09:14:24 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k6RDENdU020217 for <sip@ietf.org>; Thu, 27 Jul 2006 09:14:23 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Jul 2006 09:14:23 -0400
Received: from [161.44.79.104] ([161.44.79.104]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Jul 2006 09:14:23 -0400
Message-ID: <44C8BC2F.1000406@cisco.com>
Date: Thu, 27 Jul 2006 09:14:23 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [Sip] Re: draft-ietf-sip-gruu-09
References: <720BC7A4-8BFF-412E-A6BC-FAC41FA1289B@cisco.com> <44C83461.4020806@cisco.com>
In-Reply-To: <44C83461.4020806@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jul 2006 13:14:23.0569 (UTC) FILETIME=[941EF410:01C6B17E]
DKIM-Signature: a=rsa-sha1; q=dns; l=1659; t=1154006064; x=1154870064; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:Re=3A=20[Sip]=20Re=3A=20draft-ietf-sip-gruu-09 |To:Jonathan=20Rosenberg=20<jdrosen@cisco.com>; X=v=3Dcisco.com=3B=20h=3DDdl47GubvF6uOC1GO+DkIQwpfTE=3D; b=pMr1Y5LuCGi2+OQdiTfHXYlp6eq5o7FnkKYiIn7bPIvvu6lH1XIBoiID4UgWGwvAXRsZXpaV PzkhIDbzEslXBUQo5n/z4sCP00fxWJ3tSibmBhihWzm4v0jpejZpbKOi;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Cullen Jennings <fluffy@cisco.com>, IETF SIP List <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>
Errors-To: sip-bounces@ietf.org
Jonathan Rosenberg wrote: > Cullen Jennings wrote: >> Section 6, page 12, 4th para or so ... you are talking about mid- >> dialog requests. Might be nice to mention how a transaction stateful >> proxy knows if something is a middialog request or not. > > These days I recommend topmost route URI over tags, since its easy to > fool a proxy into thinking something is a mid-dialog request by faking a > tag. Its harder to fake a route URI. > > Text now reads: > > <t> Mid-dialog requests will also be sent to GRUUs, as they are > included as the remote-target in dialog-forming and target refresh > requests and responses. However, in those cases, a proxy SHOULD only > apply services that are meaningful for mid-dialog requests, generally > speaking. This excludes screening functions, as well as forwarding > ones. A proxy can determine that a request is a mid-dialog request > based on the Route header field in the request it receives. If the > topmost URI matches one that the proxy placed into the Record-Route > header field of a dialog-forming request, then the request is a > mid-dialog request. </t> Is it really harder to fake? Suppose Alice is permitted to call Bob, but not to subscribe to the reg event package. So Alice first calls Bob, and notes the Record-Route that results. Then in a separate dialog, Alice sends a SUBSCRIBE to the reg event package, including a Route header with a URI of Bob's home proxy extracted from the old R-R. Seems like this strategy also requires some protection against a "replay attack" like this. But that isn't really an issue for this draft. Paul _______________________________________________ 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] draft-ietf-sip-gruu-09 Dale.Worley
- [Sip] draft-ietf-sip-gruu-09 Cullen Jennings
- [Sip] Re: draft-ietf-sip-gruu-09 Jonathan Rosenberg
- [Sip] Re: draft-ietf-sip-gruu-09 Juha Heinanen
- Re: [Sip] draft-ietf-sip-gruu-09 Jonathan Rosenberg
- Re: [Sip] Re: draft-ietf-sip-gruu-09 Jiri Kuthan
- Re: [Sip] Re: draft-ietf-sip-gruu-09 Jiri Kuthan
- Re: [Sip] Re: draft-ietf-sip-gruu-09 Paul Kyzivat
- Re: [Sip] draft-ietf-sip-gruu-09 Paul Kyzivat
- Re: [Sip] draft-ietf-sip-gruu-09 Jonathan Rosenberg
- Re: [Sip] Re: draft-ietf-sip-gruu-09 Jonathan Rosenberg
- Re: [Sip] Re: draft-ietf-sip-gruu-09 Jiri Kuthan