[Sip] Flow-timer in requests

"Christer Holmberg" <christer.holmberg@ericsson.com> Wed, 05 December 2007 18:30 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izz14-0004xI-Pc; Wed, 05 Dec 2007 13:30:38 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Izz13-0004x3-79 for sip-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 13:30:37 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izz12-0004wu-S6 for sip@ietf.org; Wed, 05 Dec 2007 13:30:36 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Izz12-0000a2-9m for sip@ietf.org; Wed, 05 Dec 2007 13:30:36 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id D272120D9F; Wed, 5 Dec 2007 19:28:52 +0100 (CET)
X-AuditID: c1b4fb3c-aff97bb0000030cf-e9-4756ede4ea3b
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id C0715207E8; Wed, 5 Dec 2007 19:28:52 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Dec 2007 19:28:52 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 05 Dec 2007 19:28:50 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF037DA749@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Flow-timer in requests
Thread-Index: Acg3bK62Et1wzVycQYu9TRi3baxcJQ==
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: sip@ietf.org, rohan@ekabal.com, "Niemi Aki (Nokia-NRC/Helsinki)" <aki.niemi@nokia.com>
X-OriginalArrivalTime: 05 Dec 2007 18:28:52.0347 (UTC) FILETIME=[AFADFCB0:01C8376C]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc:
Subject: [Sip] Flow-timer in requests
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1262358338=="
Errors-To: sip-bounces@ietf.org

Hi,

As indicated in the meeting, I wonder what people think about allowing
the Flow-timer parameter also in request messages. It would provide the
following:

1) The UA can indicate the minimum keep-alive timer, which can be based
on battery life, CPU power, or whatever... We also need some wording and
guidance about what to do if the value in the response is too small for
the UA.

2) The UA can indicate that it is able to perform keep-alives (similar
to the "keepalive" option-tag), even if the UA does not support
outbound, and/or if the registrar does not support outbound, or outbound
is disabled for whatever other reason.

Regards,

Christer
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip