Re: [sipcore] Session-timer: Result below an acceptable value
"Roland Jesske" <roland.jesske@web.de> Thu, 04 October 2018 14:39 UTC
Return-Path: <roland.jesske@web.de>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AACE5130E60 for <sipcore@ietfa.amsl.com>; Thu, 4 Oct 2018 07:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.866
X-Spam-Level:
X-Spam-Status: No, score=-1.866 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rUiDu-sbo_yv for <sipcore@ietfa.amsl.com>; Thu, 4 Oct 2018 07:39:51 -0700 (PDT)
Received: from mout.web.de (mout.web.de [212.227.15.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4517C130E3C for <sipcore@ietf.org>; Thu, 4 Oct 2018 07:39:51 -0700 (PDT)
Received: from [202.175.115.43] ([202.175.115.43]) by msvc-mesg-web104.server.lan (via HTTP); Thu, 4 Oct 2018 16:39:45 +0200
MIME-Version: 1.0
Message-ID: <trinity-c86d5df9-d1ca-4c1f-91ea-c9bacd24fece-1538663985514@msvc-mesg-web104>
From: Roland Jesske <roland.jesske@web.de>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Roman Shpount <roman@telurix.com>, OKUMURA Shinji <ietf.shinji@gmail.com>, SIPCORE <sipcore@ietf.org>
Content-Type: text/html; charset="UTF-8"
Importance: normal
Date: Thu, 04 Oct 2018 16:39:45 +0200
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-Provags-ID: V03:K1:CwC6LwkgvJkFxNkhKYdV5suDOtPul9yuUznrLLnrYIgWaBAmu7CU7cRWsVK0pyVRt2LCT EeW7Q4Zj7AQs5hSEVKGyv6pj6HMKn178M/l7auA6upqkdZP2DQDiH6ondhW6/tlEMlWHmrXJGuCQ /A3WTZErWkoFzEWPcJi2+BsXwbN1P800FhL0nYRl2grCKfyiTciGMoNQbJX7UtYhcJTA0inEQQTH Pl1pv/0r9uwSzGO9VmA5UPzZz8ymlTzJ/UWvI0cb//wD8LQp9DL6yxyzFgUgDzImm94avLN+L50+ Ck=
X-UI-Out-Filterresults: notjunk:1;V01:K0:V9EV2VGhU0k=:WQC4UMoX0cwINNvvhTkEHU uPWuOXep4LzOiBxieHfHphwekdGMoqWj324wBGd7mQdiAonagbwlept197WabxiencZ/vX6/n muYmwvM3dUrZ6vcPg0JZ/363E8iMwnhLhyEVfzMgYC++GdvVSDJOfmrmqhE5J2l2kjlm/2aHs FS2wvyWjoNENDLy6PQTKtc9vgzUKl6wAYYaGNCYr0n9mUyKRbCLmiL9OOMzR7/zl2Eva4KWMF VkHZIVc5RzlKCKQ8rAlolpqsRIeVzoOEzaegGg+EqyUcNZtyxlHd/DE/VCWRWupFQVsnyECGn 5xs0zeLNj1VuXJPynsV2g7rMR5K0g90+RoPN/fYoOj34bYNHmghpFosqR5hgNX9J1nmGSGV0P qqNvyVyeNtzxaOqZlrISp+uvI9r99vrQoByH8SR8Ks6jGPF6InyQkXvVk7NxfbTigyl9kGHUM 54DstG2LUEfTgalcJUSo22Ucz6bN9SrlZYIzvLa+OdC3ZU8/TNxyfnun9HGrAPy6HHxd4di8c t1sqeOhE86qMW5AGDRFJno=
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/jdciQoPan-e7r_E1_N_AswhRkpI>
Subject: Re: [sipcore] Session-timer: Result below an acceptable value
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 04 Oct 2018 14:39:54 -0000
Hi,
The UAS is not allowed to include Min-SE to begin with (unless it sends a 422 response).
The UAS is currently allowed to reduce the S-E value in the response, as long as it it's larger than the Min-SE value in the corresponding request. My suggestion would be to say that a UAS SHOULD NOT reduce the S-E. Again, assuming the proxies know better how often they want session refreshes, there is no need for the UAS to reduce the value.
Regards,
Christer
From: roland.jesske@web.de <roland.jesske@web.de>
Sent: Thursday, October 4, 2018 4:21 PM
To: Christer Holmberg
Cc: Roman Shpount; OKUMURA Shinji; SIPCORE
Subject: Re: [sipcore] Session-timer: Result below an acceptable valueHiReading this. I understand that the proxy should be allowed to increase the Min SE.For my understanding.Following that the UAS cannot lower it again. Correct?That would be my understanding.
Best RegardsRoland
Am 04.10.2018 20:05 schrieb Christer Holmberg <christer.holmberg@ericsson.com>:
Hi,
In order to keep track of the suggested RFC modifications, I suggest that we create GitHub issues.
As an example, I created one for Shinji's suggestion to allow a proxy to increase the Min-SE header field value.
https://github.com/cdh4u/draft-sessiontimer-race/issues/1" id="LPlnk170673" class="OWAAutoLink" rel="nofollow">https://github.com/cdh4u/draft-sessiontimer-race/issues/1
https://github.com/cdh4u/draft-sessiontimer-race/issues/1" target="_blank" rel="nofollow">https://avatars0.githubusercontent.com/u/9333380?s=400&v=4"> https://github.com/cdh4u/draft-sessiontimer-race/issues/1" target="_blank" rel="nofollow">Proxy allowed to increase Min-SE header field value · Issue #1 · cdh4u/draft-sessiontimer-raceBACKGROUND: Section 8.1 of RFC 4028 says: "A proxy MUST NOT insert a Min-SE header field or modify the value of an existing header field in a proxied request if that request contains a Support...
(As always, any formal decision whether to modify something will be made on the list)
Regards,
Christer
From: sipcore <sipcore-bounces@ietf.org> on behalf of Christer Holmberg <christer.holmberg@ericsson.com>
Sent: Thursday, October 4, 2018 2:43 PM
To: Roman Shpount
Cc: OKUMURA Shinji; SIPCORE
Subject: Re: [sipcore] Session-timer: Result below an acceptable valueHi,
Sorry, I read your first e-mail wrong: I thought you said that the proxy would DECREASE Min-SE. But, now I see that you talk about INCREASE 😊
I see no reason why a proxy couldn't increase Min-SE.
As we have learned, the main users of session timer are proxies, not UAs, so a UA should not care if the minimum value is increased.
>Technically speaking UA still care about how often they need to generate refresh since this can result in extra load on the UA.
Sure, but increasing the Min-SE value will not result in extra load - on the contrary it may reduce load :)
>When session timer is negotiated, S-E specifies the max acceptable value and Min-SE specifies min acceptable value, so proxy should be able to increase Min-SE and decrease SE.
Correct.
Regards,
Christer
- [sipcore] Session-timer: Result below an acceptab… OKUMURA Shinji
- Re: [sipcore] Session-timer: Result below an acce… Christer Holmberg
- Re: [sipcore] Session-timer: Result below an acce… OKUMURA Shinji
- Re: [sipcore] Session-timer: Result below an acce… Christer Holmberg
- Re: [sipcore] Session-timer: Result below an acce… Roman Shpount
- Re: [sipcore] Session-timer: Result below an acce… Christer Holmberg
- Re: [sipcore] Session-timer: Result below an acce… Christer Holmberg
- Re: [sipcore] Session-timer: Result below an acce… roland.jesske
- Re: [sipcore] Session-timer: Result below an acce… Christer Holmberg
- Re: [sipcore] Session-timer: Result below an acce… Roland Jesske
- Re: [sipcore] Session-timer: Result below an acce… OKUMURA Shinji
- Re: [sipcore] Session-timer: Result below an acce… Paul Kyzivat
- Re: [sipcore] Session-timer: Result below an acce… Christer Holmberg
- Re: [sipcore] Session-timer: Result below an acce… Roman Shpount
- Re: [sipcore] Session-timer: Result below an acce… Christer Holmberg
- Re: [sipcore] Session-timer: Result below an acce… Roman Shpount