Re: [sipcore] [Sip] Draft new version: draft-holmberg-sipcore-keep-00 (previouslyknown as draft-holmberg-sip-keep)

"Bharrat, Shaun" <SBharrat@sonusnet.com> Mon, 04 May 2009 12:47 UTC

Return-Path: <SBharrat@sonusnet.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 BB2F13A69D6 for <sipcore@core3.amsl.com>; Mon, 4 May 2009 05:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 l7LnuCNLsj9J for <sipcore@core3.amsl.com>; Mon, 4 May 2009 05:47:04 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by core3.amsl.com (Postfix) with ESMTP id 3AF873A703D for <sipcore@ietf.org>; Mon, 4 May 2009 05:47:04 -0700 (PDT)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id n44CmPA2006705; Mon, 4 May 2009 08:48:25 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 04 May 2009 08:44:42 -0400
Message-ID: <637C77B6763BB54ABF989B6B21D5323502EF24E7@sonusmail05.sonusnet.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0CC259AF@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Draft new version: draft-holmberg-sipcore-keep-00 (previouslyknown as draft-holmberg-sip-keep)
Thread-Index: Acm+bcAszQkyqV++Ts+HPG29TfGFgALlQSopAIXeZxAAJri/0A==
From: "Bharrat, Shaun" <SBharrat@sonusnet.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, sipcore@ietf.org
Subject: Re: [sipcore] [Sip] Draft new version: draft-holmberg-sipcore-keep-00 (previouslyknown as draft-holmberg-sip-keep)
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: Mon, 04 May 2009 12:47:10 -0000

Christer:

> Also, the parameter is inserted in the Via of the request, so 
> it will be copied into whatever response is generated based 
> on the request.

I understand that the parameter itself will be copied back. What I
am wondering is whether it needs to be set to "yes" in every 
response or can this work if it is set to "yes" in the final response
but not necessarily in the 100 or provisionals.

Support of this functionality is not necessarily global (within
a box). There are architectures where it will not be possible to know
whether support is enabled for that peer at the time or place that 
the 100 is sent. If no one else envisions a problem along those lines, 
then I guess my concern is moot.  

Cheers,
Shaun


> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: Monday, May 04, 2009 6:09 AM
> To: Bharrat, Shaun; sipcore@ietf.org
> Subject: RE: [Sip] Draft new version: 
> draft-holmberg-sipcore-keep-00 (previouslyknown as 
> draft-holmberg-sip-keep)
> 
> 
> Hi Shaun, 
> 
> >> When a UAS that supports the method defined in this specification 
> >> recieves an initial SIP request which contains a "keep" 
> parameter in 
> >> the topmost Via header, and the UAS wants to allow the 
> sender of the 
> >> initial SIP request to send keep-alives towards the UAS during the 
> >> duration of the call, the UAS proxy MUST add a "yes" value to the 
> >> "keep" parameter.  In addition the UAS MAY include a Flow-Timer 
> >> header field if the associated initial SIP response.
> >
> >Which response is this text referring to when this is for a call?
> >Does this include the 100 trying? If in the 100 trying, does the keep
> need to be in all responses to the INVITE? WHat about the Flow-Timer?
> >
> >The reason I'm asking is that 100 trying is often generated at a very
> different place than the other responses. It may or may not 
> be feasible to provide the relevant information in that response.
> >I'm trying to understand the intent...
> 
> The keep-alives are always sent between two entities 
> communicating directly with each other (we don't expect SIP 
> proxies for forward STUN requests etc).
> 
> Also, the parameter is inserted in the Via of the request, so 
> it will be copied into whatever response is generated based 
> on the request.
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> -----Original Message-----
> From: sip-bounces@ietf.org on behalf of Christer Holmberg
> Sent: Thu 4/16/2009 4:31 AM
> To: sipcore@ietf.org; sip@ietf.org
> Cc: Adam Roach; Gonzalo Camarillo; Mary Barnes
> Subject: [Sip] Draft new version: 
> draft-holmberg-sipcore-keep-00 (previouslyknown as 
> draft-holmberg-sip-keep)
>  
> 
> Hi,
> 
> I've submitted a draft-holmberg-sipcore version of the keep draft.
> 
> The draft is identical to the previous version (for which 
> Mary sent out the ask-for-support e-mail), but I have added 
> one more example.
> 
> The draft can also be found at:
> 
> http://users.piuha.net/cholmber/drafts/draft-holmberg-sipcore-
> keep-00.tx
> t
> 
> 
> Regards,
> 
> Christer
> 
> Ps. I applogize for sending this e-mail to both SIP and 
> SIPCORE, but since everyone may not have subscribed to SIPCORE yet...
> 
> 
> 
> 
> 
>