Re: [MMUSIC] RTSP questions in regards to the control channel socket

Magnus Westerlund <magnus.westerlund@ericsson.com> Fri, 14 March 2014 10:18 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 203E31A010F for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 03:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 ZRxswT17TiHu for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 03:17:56 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8261A00ED for <mmusic@ietf.org>; Fri, 14 Mar 2014 03:17:54 -0700 (PDT)
X-AuditID: c1b4fb25-b7f038e000005d01-bc-5322d74bdc05
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id C8.BC.23809.B47D2235; Fri, 14 Mar 2014 11:17:47 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.44) with Microsoft SMTP Server id 14.2.347.0; Fri, 14 Mar 2014 11:17:45 +0100
Message-ID: <5322D749.8020306@ericsson.com>
Date: Fri, 14 Mar 2014 11:17:45 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Craig Matsuura <cmatsuura@vivint.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <53223DAA.4040107@vivint.com>
In-Reply-To: <53223DAA.4040107@vivint.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmluLIzCtJLcpLzFFi42KZGfG3Rtf7ulKwQfdvXYvdl74yW0xd/pjF gcljyZKfTB7nnl1lDWCK4rJJSc3JLEst0rdL4MpoWNzPUvBfuOLzh7PsDYzdAl2MnBwSAiYS p0/fZIewxSQu3FvP1sXIxSEkcIhRornjHjOEs5xRYu3/00wgVbwC2hLntm4G62ARUJW4seQh mM0mYCFx80cjG4gtKhAssfPAb0aIekGJkzOfsIDYIgJ+EjMu/wabIyzgKzHl7FqwGiEBTYkl 59cC9XJwcApoSfzZ7gViSgiIS/Q0BoFUMAvoSUy52sIIYctLNG+dzQzRqS3R0NTBOoFRcBaS ZbOQtMxC0rKAkXkVI3tuYmZOernRJkZgQB7c8lt1B+OdcyKHGKU5WJTEeT+8dQ4SEkhPLEnN Tk0tSC2KLyrNSS0+xMjEwSnVwFi4n8dI8nSz3tWIkkl7ysq89nzbcKSO1eqK8+2P8Wz7OPgT oiZWH6mrm5B01qYg0pxRdOWsom8nef1WtX1+/e1u03thC+7E5qCXFSaPzp7utqx4GZG56vm2 pc8ent1767PifQ8x+4rHc5WfX9scUrmD/X9nvWBiS+GhSxtX+nqkHdh/udK29YwSS3FGoqEW c1FxIgCyC7l6FgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/xiYiNL75vHAv_JeL1n6KFtGmRvM
Subject: Re: [MMUSIC] RTSP questions in regards to the control channel socket
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 14 Mar 2014 10:18:02 -0000

On 2014-03-14 00:22, Craig Matsuura wrote:
> Hi this is my first time posting here.  I have a basic question about 
> how a RTSP server should handled a connect and disconnect for what I am 
> calling the control channel (connection or transport). The control 
> channel (please correct me) is what sends the DESCRIBE, SETUP, OPTIONS, 
> PLAY commands to the RTSP SERVER.
> 
> Should a server treat the first DESCRIBE connection as its session. So 
> in the case where a socket connects to a RTSP server and sends a 
> DESCRIBE, is disconnected either by the client or some failure on the 
> server should the following SETUP succeed?

No, DESCRIBE is a state less operation. If one needs a linkage between
the Describe response body and the setup, then one should use etags and
conditional requests to ensure that one is establishing the session with
a relevant session description.

> 
> Also if using a RTSP Proxy and in the same scenario, but after the 
> DESCRIBE and closing of the socket a new socket is open to send an 
> OPTIONS (for keepalive) should the following SETUP succeed?

Yes the SETUP should succeed if otherwise valid.

> 
>  From what I understood from the RFC2326 Section 1.7 RTSP State, it 
> should not matter how many connections are used to control the RTSP Stream.
> 
> 1. Control Socket is not prevent a client from connecting and 
> disconnecting to send Transport commands.

I am uncertain what you mean with the Control socket, if you means the
Socket the server listens to incoming TCP connection establishments and
their data, it needs to be accepting those comming and going.

> 2. The keep-alive for a session should not start until a SETUP command, 
> which can optional report the timeout for the session.

Exact, the keep-alive is associated with the RTSP session, not the
signalling connection used to send RTSP requests and response between
the server and client.

You might find RTSP 2.0's text on this being clearer:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------