Re: [sipcore] Editorial comments on rfc4244bis-02

Paul Kyzivat <pkyzivat@cisco.com> Sun, 07 November 2010 15:35 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 915C53A67D4 for <sipcore@core3.amsl.com>; Sun, 7 Nov 2010 07:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level:
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 d9-hnqjldQ84 for <sipcore@core3.amsl.com>; Sun, 7 Nov 2010 07:35:35 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 529D33A679C for <sipcore@ietf.org>; Sun, 7 Nov 2010 07:35:35 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEALZV1kxAaMHG/2dsb2JhbACiCnGdappLhUgEhFiFfYMK
X-IronPort-AV: E=Sophos;i="4.58,310,1286150400"; d="scan'208";a="289516993"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-2.cisco.com with ESMTP; 07 Nov 2010 15:35:53 +0000
Received: from [10.75.235.198] (hkidc-vpn-client-235-198.cisco.com [10.75.235.198]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id oA7FZn2T013774; Sun, 7 Nov 2010 15:35:51 GMT
Message-ID: <4CD6C753.7010807@cisco.com>
Date: Sun, 07 Nov 2010 10:35:47 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <0CDF97F6-E125-45F8-B266-65E79BAE6F1A@acmepacket.com> <4CD648A4.60301@cisco.com> <CED3FB69-CDF1-4DEA-AE66-D12294FF664E@acmepacket.com>
In-Reply-To: <CED3FB69-CDF1-4DEA-AE66-D12294FF664E@acmepacket.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] Editorial comments on rfc4244bis-02
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Nov 2010 15:35:36 -0000

On 11/7/2010 7:26 AM, Hadriel Kaplan wrote:
>
> True, I forgot about the forked case... but I don't think that's what they're talking about here, since regardless it's in the reverse direction towards the UAC and follows the SUBSCRIBE's (or REFER's) route set.  Or is the intent to use H-I for requests from the UAS to the UAC as well, in which case why isn't it used in in-dialog requests? (I don't see the point of it, but that's never stopped us before ;)

Sorry - I did just reply narrowly.
You are right - every NOTIFY, even the "dialog initiating" ones are 
requests that are "in dialog" and hence AFAIK don't get H-I in them, nor 
AFAIK can they affect the H-I of the SUBSCRIBE or REFER that caused them.

	Thanks,
	Paul

> -hadriel
>
>
> On Nov 7, 2010, at 1:35 AM, Paul Kyzivat wrote:
>
>> On 11/6/2010 11:48 PM, Hadriel Kaplan wrote:
>>
>>> 5) Section 7.1 says: "...plus NOTIFY requests that initiate a dialog."  Ummm... what type of NOTIFY requests would those be?? (other than proprietary)  Actually, that raises a question - can this appear in proprietary methods?
>>
>> In case of forking, NOTIFY requests can initiate a dialog.
>> And with 3256bis dialogs are *always* initiated by NOTIFY.
>>
>> 	Thanks,
>> 	Paul
>> _______________________________________________
>> sipcore mailing list
>> sipcore@ietf.org
>> https://www.ietf.org/mailman/listinfo/sipcore
>
>