[MMUSIC] RTSP 2.0: Additional change in Section 10.4 Timing out connections
Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 09 October 2013 11:15 UTC
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 310CA21E813F for <mmusic@ietfa.amsl.com>; Wed, 9 Oct 2013 04:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.154
X-Spam-Level:
X-Spam-Status: No, score=-105.154 tagged_above=-999 required=5 tests=[AWL=1.095, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbCnfS5274Oi for <mmusic@ietfa.amsl.com>; Wed, 9 Oct 2013 04:15:20 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 440A521F9CBF for <mmusic@ietf.org>; Wed, 9 Oct 2013 04:15:20 -0700 (PDT)
X-AuditID: c1b4fb25-b7eff8e000000eda-64-52553ac6cd2b
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id AC.2D.03802.6CA35525; Wed, 9 Oct 2013 13:15:18 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.32) with Microsoft SMTP Server id 14.2.328.9; Wed, 9 Oct 2013 13:15:18 +0200
Message-ID: <52553B01.9080602@ericsson.com>
Date: Wed, 09 Oct 2013 13:16:17 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>, Elwyn Davies <elwynd@folly.org.uk>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLJMWRmVeSWpSXmKPExsUyM+Jvre4xq9Agg0M/rSyOH9jBbjF1+WMW ByaPryfbWTyWLPnJFMAUxWWTkpqTWZZapG+XwJXxc3kTW8FagYo97y+wNzBu4O1i5OSQEDCR aG7axgphi0lcuLeerYuRi0NI4DCjxKFJrxghnGWMEj9Xr2cHqeIV0JZ40zyHDcRmEVCRWHCz hwXEZhOwkLj5oxEsLioQLNG+/SsbRL2gxMmZT8BqRAS8JV5f/8EMYgsD2Ys/PmWD2CwpsW3R MbD5zAJ6ElOutjBC2PISzVtng9ULAe1taOpgncDIPwvJ2FlIWmYhaVnAyLyKkT03MTMnvdxo EyMwyA5u+a26g/HOOZFDjNIcLErivB/eOgcJCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYFTd vd3cVUSGoffZ8n6uY18erjQPfPTcJrJ8mkVDqjjzEn2BgztST0enxru4TU4tV2zZbH/zgN3z mWs2x09+fOneqXDzCW3TnP/u+XV7TrXvs0f/mtkeF0xaV7z+xSLvVaciFS0Eiu4db/Iv2HH+ wr8e7X72uGlmuv/v8H6dm1W41f0w2zfXdg0lluKMREMt5qLiRACmnyX/AAIAAA==
Subject: [MMUSIC] RTSP 2.0: Additional change in Section 10.4 Timing out connections
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Oct 2013 11:15:28 -0000
WG, Elwyn, is in the process of sending my editorial comments for the changes since the IETF last call comments was addressed. As part of this he spotted that in section 10.4 there is a note that contains what probably should be specification text. Thus the suggestion is to change the note to a regular text and use RFC 2119 normative language when appropriate. Thus the suggestion is that the fourth paragraph of Section 10.4 will read: In cases multiple RTSP sessions share the same transport connection, abandoning a request and closing the connection may have significant impact on those other sessions. First of all, other RTSP requests may have become queued up due to the request taking long time. Secondly also those sessions loose the possibility to receive server to client requests. To mitigate that situation the RTSP agent SHOULD establish a new connection and send any queued up and non-responded requests on this new connection. Secondly, to ensure that the RTSP server knows which connection that is valid for a particular RTSP session, the RTSP agent SHOULD send a keep-alive request, if no other request will be sent immediately for that RTSP session, for each RTSP session on the old connection. The keep-alive request will normally be a GET_PARAMETER with a session header to inform the server that this agent cares about this RTSP session. Comments and feedbacks on this change. I hope to be able to submit a update with Elwyn's editorial suggestions, and the above change this week. Then I will request that the chairs and AD move forward with the document. Cheers Magnus Westerlund ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com ----------------------------------------------------------------------
- [MMUSIC] RTSP 2.0: Additional change in Section 1… Magnus Westerlund