Re: [sipcore] Draft new version: draft-ietf-sipcore-keep-06

Paul Kyzivat <pkyzivat@cisco.com> Thu, 09 September 2010 13:47 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 ADF0D3A659A for <sipcore@core3.amsl.com>; Thu, 9 Sep 2010 06:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.634
X-Spam-Level:
X-Spam-Status: No, score=-109.634 tagged_above=-999 required=5 tests=[AWL=-0.793, BAYES_00=-2.599, FR_3TAG_3TAG=1.758, 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 LbyRXNUwEz2a for <sipcore@core3.amsl.com>; Thu, 9 Sep 2010 06:47:47 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 108B03A680F for <sipcore@ietf.org>; Thu, 9 Sep 2010 06:47:47 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKqCiExAaMHG/2dsb2JhbAChMXGiLZtkhT0EiiCCfA
X-IronPort-AV: E=Sophos;i="4.56,339,1280707200"; d="scan'208";a="360051583"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-1.cisco.com with ESMTP; 09 Sep 2010 13:48:13 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o89DmB6f012392; Thu, 9 Sep 2010 13:48:12 GMT
Message-ID: <4C88E597.5080705@cisco.com>
Date: Thu, 09 Sep 2010 09:48:07 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7F2072F1E0DE894DA4B517B93C6A058501613B27@ESESSCMS0356.eemea.ericsson.se> <4C882E64.2060305@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585016943D1@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A0585016943D1@ESESSCMS0356.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "SIPCORE (Session Initiation Protocol Core) WG" <sipcore@ietf.org>
Subject: Re: [sipcore] Draft new version: draft-ietf-sipcore-keep-06
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: Thu, 09 Sep 2010 13:47:52 -0000

Christer Holmberg wrote:
> Hi Paul, 
> 
>> I think this addresses all of my issues!
>>
>> I have one question on some new text introduced in section 4.1:
>>
>>     In general, it can be useful for SIP entities to indicate willingness
>>     to send keep-alives, even if they are not aware of any 
>>     necessity for them to send keep-alives, since the adjacent downstream SIP entity
>>     might have knowledge about the necessity.  Similarly, it can be
>>     useful for SIP entities to indicate willingness to receive keep-
>>     alives, even if they are not aware of any necessity for the adjacent
>>     upstream SIP entity to send them.
>>
>> Am I missing something? I don't see any way for an entity to 
>> indicate willingness to receive keep-alives if the upstream 
>> neighbor hasn't indicated a willingness to send them.
> 
> It DOES require that the upstream has indicated willingess to send them. I guess that could be clarified (<new></new>).
> 
> "Similarly, <new>if the adjacent upstream SIP entity has indicated willingess to send keep-alives,</new> it can be
> useful for SIP entities to indicate willingness to receive keep-alives, even if they are not aware of any necessity for the adjacent
> upstream SIP entity to send them."

OK, for me that helps. Its no big deal if it stays as it is - it just 
seemed a little confusing.

	Thanks,
	Paul