IETF Logo Mail Archive

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

"Christer Holmberg" <christer.holmberg@ericsson.com> Mon, 04 May 2009 10:09 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 9855E28C14E for <sipcore@core3.amsl.com>; Mon, 4 May 2009 03:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.831
X-Spam-Level:
X-Spam-Status: No, score=-5.831 tagged_above=-999 required=5 tests=[AWL=0.418, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 SszOwWiUKGYL for <sipcore@core3.amsl.com>; Mon, 4 May 2009 03:09:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 7E4723A6FCD for <sipcore@ietf.org>; Mon, 4 May 2009 03:07:28 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b19ae000006089-fe-49febead4244
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id F5.5D.24713.DAEBEF94; Mon, 4 May 2009 12:08:46 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 May 2009 12:08:46 +0200
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 12:08:44 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0CC259AF@esealmw113.eemea.ericsson.se>
In-Reply-To: <637C77B6763BB54ABF989B6B21D5323502981F99@sonusmail05.sonusnet.com>
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+HPG29TfGFgALlQSopAIXeZxA=
References: <CA9998CD4A020D418654FCDEF4E707DF0C670C4E@esealmw113.eemea.ericsson.se> <637C77B6763BB54ABF989B6B21D5323502981F99@sonusmail05.sonusnet.com>
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Bharrat, Shaun" <SBharrat@sonusnet.com>, sipcore@ietf.org
X-OriginalArrivalTime: 04 May 2009 10:08:46.0036 (UTC) FILETIME=[4FAD4940:01C9CCA0]
X-Brightmail-Tracker: AAAAAA==
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 10:09:13 -0000

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

v2.23.0 | Report a Bug | By Email