Re: [sipcore] IETF#101: Session-timer slides

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 20 March 2018 15:35 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 D0A09127077 for <sipcore@ietfa.amsl.com>; Tue, 20 Mar 2018 08:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 joizce9CdIQF for <sipcore@ietfa.amsl.com>; Tue, 20 Mar 2018 08:35:14 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12D57126579 for <sipcore@ietf.org>; Tue, 20 Mar 2018 08:35:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1521560112; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=JbtXjAqUTTxeMmE2Jakv27oo20uyxcF8x21E3KVNmSA=; b=IJ0O6FOTkEIuePizYfDnqbz7ekVCJ2ACxBf/NbvKGcsA7k1nMBubQkpzF2WDxA4N +71Ot4Fz2Blr5JUZHnxGefoOpAefrLUYWCzehtPpRzJNPM5MXQGUTcEnV3vUKqgc 1qKyUN2s54kWs+JLSEBaYFJq+s9QpeCZcr4Mriy9k7A=;
X-AuditID: c1b4fb30-6ebff7000000095a-b2-5ab12a300591
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 14.AC.02394.03A21BA5; Tue, 20 Mar 2018 16:35:12 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.172]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0382.000; Tue, 20 Mar 2018 16:35:11 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] IETF#101: Session-timer slides
Thread-Index: AdO/ZxYTW+Gr+7RqQ8muZoBFJ0+HigA7FxwAAALkA5A=
Date: Tue, 20 Mar 2018 15:35:10 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C212F94@ESESSMB109.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B6C20E97D@ESESSMB109.ericsson.se> <4fb49fec-a63e-3375-fa92-bf33f756db96@alum.mit.edu>
In-Reply-To: <4fb49fec-a63e-3375-fa92-bf33f756db96@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.170]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2J7iK6B1sYog977fBYrNhxgtfj6YxOb A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJXRfPkLS0EnX8WK+5dZGhhXcHcxcnJICJhI HJr+jRHEFhI4zCix6TpvFyMXkL2EUeL01I1MXYwcHGwCFhLd/7RBakQEAiWuLpnADGILC5hK zD/6lBkibibx5u9edgjbSuLfr+NgNouAqsSibz9YQWxeAV+Jz5cusULsamaUmPtGHcTmFHCQ 2PfiLlg9o4CYxPdTa5hAbGYBcYlbT+YzQdwpILFkz3lmCFtU4uXjf6wQtpLEmU3PWSDqdSQW 7P7EBmFrSyxb+JoZYq+gxMmZT1gmMIrMQjJ2FpKWWUhaZiFpWcDIsopRtDi1OCk33chIL7Uo M7m4OD9PLy+1ZBMjMBoObvltsIPx5XPHQ4wCHIxKPLxlihujhFgTy4orcw8xSnAwK4nwZioA hXhTEiurUovy44tKc1KLDzFKc7AoifOe9OSNEhJITyxJzU5NLUgtgskycXBKNTAymUyuDWdc LJt0bYLpfbs33C8edltb9ZeUv4hdxGGqYBITtVhA6uGHvaoRG8w3L1TfFLfopxq3xc7Lpw0d d7z7eWsp24FXEqc10qdEBp/fasoeEtYZc2X6avZA9cvO+xac7mB3jw512LXzGPvk/Zv2mq6O +58mz9o9/3eL9Uq34w8q6wr2iCkrsRRnJBpqMRcVJwIAFDHRpYICAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/yKj9hss2cMOIJqb4tRSebAKqn6w>
Subject: Re: [sipcore] IETF#101: Session-timer slides
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 20 Mar 2018 15:35:16 -0000

Hi Paul,

>> As some people are going to participate remotely, before I upload the 
>> slides I have put the current version on GitHub.
>> 
>> https://github.com/cdh4u/draft-sessiontimer-race/blob/master/IETF101_S
>> IPCORE_SESSION-RACE.pdf
>> 
>> We will discuss the technical stuff during the meeting, but if there 
>> is something you think could be clarified then please let me know.
>
> I went and reviewed the draft and rfc again, and I still think the fix in your 3.1 (to section 7.2 of 4028) is over broad.
>
> Consider a case where a session timer has already been established between Alice and Bob. 
> We are mid-dialog and there are no transactions in progress. Now Alice decides she wants to disable the session timer.
>
> How can she do that? Following 4028, she does that by sending an INVITE or UPDATE with no Session-Expires. 
> The response to that also has no Session-Expires, and then session timer is cancelled.
>
> But with your revision, because the request did not contain Session-Expires, the response does not cancel the session timer.

If that's what the text is saying, we need to fix it. My intention is not to remove the generic ability to remove the session-timer.

Note, though, that I am not going to discuss the text at the meeting. The focus will be on the overall principle. Once we can agree on that, we'll sort out the text.

> To avoid the problem, the behavior of leaving a s-t running after receiving a response without Session-Expires must be 
> limited to UPDATE transactions embedded within INVITE transactions.

Correct. I think the focus shall be on UPDATE transactions that take place within INVITE transactions (or, during session-timer negotiations).

Regards,

Christer