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

Paul Kyzivat <pkyzivat@cisco.com> Thu, 09 September 2010 00:46 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 0CF303A6872 for <sipcore@core3.amsl.com>; Wed, 8 Sep 2010 17:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.512
X-Spam-Level:
X-Spam-Status: No, score=-110.512 tagged_above=-999 required=5 tests=[AWL=0.087, 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 GRUyc76R1RFn for <sipcore@core3.amsl.com>; Wed, 8 Sep 2010 17:46:04 -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 6D9AE3A6781 for <sipcore@ietf.org>; Wed, 8 Sep 2010 17:46:04 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJ/Lh0xAZnwN/2dsb2JhbAChK3GkTZtThT0Eih+Cew
X-IronPort-AV: E=Sophos;i="4.56,336,1280707200"; d="scan'208";a="157183146"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 09 Sep 2010 00:46:31 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o890kVAo005438; Thu, 9 Sep 2010 00:46:31 GMT
Message-ID: <4C882E64.2060305@cisco.com>
Date: Wed, 08 Sep 2010 20:46:28 -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>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A058501613B27@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 00:46:06 -0000

[as individual]

Christer,

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.

	Thanks,
	Paul

Christer Holmberg wrote:
>  
> Hi,
>  
> I've submitted a new version of the keep draft.
>  
> Based on the WGLC feedback from, and discussions with, Paul, I've 
> re-introducted section 6 (Connection reuse). This time, however, rather 
> than only talking about RFC 5923, it talks more general about connection 
> reuse. It clarifies that the keep draft does NOT specify a connection 
> reuse mechanism, and that entities MUST use other mechanisms for 
> connection re-use. I also added text to the security considerations 
> about that.
>  
> Based on the WGLC feedback from Hadriel, I also added text to the 
> security considerations regarding harm that can be done by a 
> man-in-the-middle.
>  
> The draft can also be found at:
>  
> _http://users.piuha.net/cholmber/drafts/draft-ietf-sipcore-keep-06.txt_
>  
> Regards,
>  
> Christer
>