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

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 09 September 2010 05:58 UTC

Return-Path: <christer.holmberg@ericsson.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 F2AB53A6A14 for <sipcore@core3.amsl.com>; Wed, 8 Sep 2010 22:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.688
X-Spam-Level:
X-Spam-Status: No, score=-4.688 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, FR_3TAG_3TAG=1.758, 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 TINjsP7bVsB7 for <sipcore@core3.amsl.com>; Wed, 8 Sep 2010 22:57:53 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 114EF3A6A11 for <sipcore@ietf.org>; Wed, 8 Sep 2010 22:57:52 -0700 (PDT)
X-AuditID: c1b4fb39-b7b91ae000001aef-f5-4c88777ba204
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id E1.ED.06895.B77788C4; Thu, 9 Sep 2010 07:58:19 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.78]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Thu, 9 Sep 2010 07:58:19 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Date: Thu, 09 Sep 2010 07:58:18 +0200
Thread-Topic: Draft new version: draft-ietf-sipcore-keep-06
Thread-Index: ActPuHRamKRULZ3/Qw+VCKOJRLrX0wAKwz/Q
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585016943D1@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A058501613B27@ESESSCMS0356.eemea.ericsson.se> <4C882E64.2060305@cisco.com>
In-Reply-To: <4C882E64.2060305@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "SIPCORE (Session Initiation Protocol Core) WG" <sipcore@ietf.org>, Adam
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 05:58:03 -0000

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."

Regards,

Christer





> 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
> >  
>