Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
Paul Kyzivat <pkyzivat@cisco.com> Thu, 02 October 2008 23:20 UTC
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8469A3A6922; Thu, 2 Oct 2008 16:20:55 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A5323A6922 for <sip@core3.amsl.com>; Thu, 2 Oct 2008 16:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.442
X-Spam-Level:
X-Spam-Status: No, score=-6.442 tagged_above=-999 required=5 tests=[AWL=0.157, 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 zue27dkSTkxY for <sip@core3.amsl.com>; Thu, 2 Oct 2008 16:20:53 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 676323A6912 for <sip@ietf.org>; Thu, 2 Oct 2008 16:20:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,353,1220227200"; d="scan'208";a="23033962"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 02 Oct 2008 23:20:43 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m92NKhAZ027466; Thu, 2 Oct 2008 19:20:43 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m92NKh5T012171; Thu, 2 Oct 2008 23:20:43 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Oct 2008 19:20:43 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Oct 2008 19:20:42 -0400
Message-ID: <48E55749.5050105@cisco.com>
Date: Thu, 02 Oct 2008 19:20:41 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
References: <18656.60044.302965.535846@harjus.tutpro.com> <1ECE0EB50388174790F9694F77522CCF197351A7@zrc2hxm0.corp.nortel.com> <18657.2518.651908.902884@harjus.tutpro.com> <1ECE0EB50388174790F9694F77522CCF197354D8@zrc2hxm0.corp.nortel.com> <48E139E9.4050008@cisco.com> <B8B2BE35-DBD7-4751-8EF2-A37F148B5C32@softarmor.com> <1ECE0EB50388174790F9694F77522CCF198A6CF5@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF198A6CF5@zrc2hxm0.corp.nortel.com>
X-OriginalArrivalTime: 02 Oct 2008 23:20:42.0861 (UTC) FILETIME=[7D82E1D0:01C924E5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2606; t=1222989643; x=1223853643; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sip]=20configuration=20NOTIFY=20in=20e xample=209.1=20of=20outbound=20i-d |Sender:=20 |To:=20Francois=20Audet=20<audet@nortel.com>; bh=lqZtzw+0Ha5WNMtrZJPlrEdVsSzxmS7F9YofQ+c9FL0=; b=POte54LGJZ9bfFglewyFF2Ru+k3KWFJOTCdPtUloLsv2rmmDwFdYmyU6Y6 oNI7ylvPQZl/PPOtbMILscqHYYiin4eeRiZRvMi+KyjuZyjHpK48qgunj3kk ko2eSMKT+S;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: Cullen Jennings <fluffy@cisco.com>, Rohan Mahy <rohan@ekabal.com>, sip@ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
X-BeenThere: sip@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@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
I guess our replies overlapped. Francois Audet wrote: > My take on this is that Juha is right and the document should really say: > > If the UAC is sending a dialog-forming request, and wants all > subsequent requests in the dialog to arrive over the same > flow, the UAC MUST add an 'ob' parameter to its Contact header. > [ DELETE NEXT SENTENCE ENTIRELY ] > > In other words, GRUU is orthogonal and does NOT imply "ob" behavior. Not quite. If you have obtained a gruu after registering a contact with outbound, you don't have to put "ob" on the gruu. It wouldn't help, since it would get lost in the process of translating the gruu. Thanks, Paul > Clean and simple, and I *think* this was our intent (i.e., I think > this is an historical oversight). > > Cullen, can you confirm or clarify? > >> -----Original Message----- >> From: Dean Willis [mailto:dean.willis@softarmor.com] >> Sent: Thursday, October 02, 2008 15:56 >> To: Paul Kyzivat >> Cc: Audet, Francois (SC100:3055); Cullen Jennings; Rohan >> Mahy; sip@ietf.org >> Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d >> >> >> On Sep 29, 2008, at 3:26 PM, Paul Kyzivat wrote: >> >>> >>> Francois Audet wrote: >>>>>> Section 4.3 states (UA procedures): >>>>>> If the UAC is sending a dialog-forming request, and wants all >>>>>> subsequent requests in the dialog to arrive over the same >>>>> flow, the >>>>>> UAC adds an 'ob' parameter to its Contact header. Typically >>>>> this is >>>>>> desirable, but it is not necessary for example if the Contact >>>>> is a >>>>>> GRUU [I-D.ietf-sip-gruu]. >>>>> if contact is gruu, does it mean that 'ob' param is implicitly >>>>> included? >>>> I am not sure why this is worded like this. I was thinking >> that using >>>> a GRUU as a contact in a dialog-forming request would mandate that >>>> requests sent to that Contact would be sent using the same >> flow, but >>>> I see no such rule in draft-ietf-sip-gruu. >>> Gruu isn't dependent on outbound. >>> >>> >> So explain this one for me, please. >> >> Is it that, if the gruu was formed using outbound (that is, >> the "real" >> contact for which the gruu is an alias has an "ob") use of >> the gruu will use the "ob" in the dereferencing at the gruu-provider? >> >> So for the example referenced above may be correct, but >> incomplete -- it should talk about whether or not the gruu >> was formed using outbound, not just whether or not the >> contact isa gruu. >> >> -- >> Dean >> >> >> >> >> > _______________________________________________ Sip mailing list https://www.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] configuration NOTIFY in example 9.1 of outb… Juha Heinanen
- Re: [Sip] configuration NOTIFY in example 9.1 of … Francois Audet
- Re: [Sip] configuration NOTIFY in example 9.1 of … Juha Heinanen
- Re: [Sip] configuration NOTIFY in example 9.1 of … Francois Audet
- Re: [Sip] configuration NOTIFY in example 9.1 of … Paul Kyzivat
- Re: [Sip] configuration NOTIFY in example 9.1 of … Juha Heinanen
- Re: [Sip] configuration NOTIFY in example 9.1 of … Dean Willis
- Re: [Sip] configuration NOTIFY in example 9.1 of … Francois Audet
- Re: [Sip] configuration NOTIFY in example 9.1 of … Paul Kyzivat
- Re: [Sip] configuration NOTIFY in example 9.1 of … Paul Kyzivat
- Re: [Sip] configuration NOTIFY in example 9.1 of … Francois Audet
- Re: [Sip] configuration NOTIFY in example 9.1 of … Paul Kyzivat