Re: [MMUSIC] RTSP for data recorder design

Magnus Westerlund <magnus.westerlund@ericsson.com> Fri, 06 September 2013 07: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 585CA11E8168 for <mmusic@ietfa.amsl.com>; Fri, 6 Sep 2013 00:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.632
X-Spam-Level:
X-Spam-Status: No, score=-105.632 tagged_above=-999 required=5 tests=[AWL=0.617, 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 KUIQ9lCOrbJb for <mmusic@ietfa.amsl.com>; Fri, 6 Sep 2013 00:15:09 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 808C311E8122 for <mmusic@ietf.org>; Fri, 6 Sep 2013 00:15:08 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f738e000003ee3-03-522980fa9e4b
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id FA.42.16099.AF089225; Fri, 6 Sep 2013 09:15:06 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.17) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.2.328.9; Fri, 6 Sep 2013 09:15:06 +0200
Message-ID: <5229813F.4030207@ericsson.com>
Date: Fri, 06 Sep 2013 09:16:15 +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: "Saylor, Kase J." <kase.saylor@swri.org>
References: <862F245D-0795-48E1-8D5A-FEA6A0792D44@swri.org> <5203EABF.2080907@alum.mit.edu> <1383B2A3-D18B-4EC7-87EC-9AE93AE492DA@swri.org> <5D319E1E-0055-408A-8973-E110DFBC9BBD@swri.org> <5225C5DE.5040207@ericsson.com> <72859288-FDC7-41A9-AD33-96E56501E13F@swri.org> <52282A01.1040102@ericsson.com> <B5D6CC7B-D209-41E6-A46C-40BB81BB6B09@swri.org>
In-Reply-To: <B5D6CC7B-D209-41E6-A46C-40BB81BB6B09@swri.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprILMWRmVeSWpSXmKPExsUyM+Jvje6vBs0gg6cXTC3OHP3NZDF1+WMW ByaPJUt+Mnl8nf2GOYApissmJTUnsyy1SN8ugSvj8/n9rAWXhSuudPezNTBO5O9i5OSQEDCR uHbqDzuELSZx4d56ti5GLg4hgcOMErM2tLJCOEsZJS6cPs4EUsUroC2x5PpEZhCbRUBFYtKB TrBuNgELiZs/GtlAbFGBYIn27V/ZIOoFJU7OfMICYosI6Eh0XF8JNJSDg1lAXeLq4iCQsLCA scSn583MELtuM0msPPSAFSTBKWAjcXfNPVaI6yQlti06BraLWUBPYsrVFkYIW16ieetssHuE gG5raOpgncAoNAvJ6llIWmYhaVnAyLyKkT03MTMnvdxwEyMwWA9u+a27g/HUOZFDjNIcLEri vJv0zgQKCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYGT3f7TBheNDD6NqfMy+Ja+OGnLqLZSe 6JTzMvcS08aDJ4JNHy4p/ffoeNlRZlWv5JA06VOPX8le9OHPuqSpbaqzb+uakA2fDZmzec5V J6ddyeacZO8997ePaO6l2LNcKud/vlzbeGKf46n7HQmcqxOPnJgyVSljo5ztq4uf6u7fCi/Y KBN46J0SS3FGoqEWc1FxIgCQ6cyIJAIAAA==
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] RTSP for data recorder design
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: Fri, 06 Sep 2013 07:15:15 -0000

On 2013-09-05 16:21, Saylor, Kase J. wrote:
> Let me try an example (if you don't mind) to see if I'm following this
> correctly:
> 
> We have a multicast message that get sent on our system (periodic data
> and event-based data) and we have defined the structure of the datagram.
> Let's call our defined datagram as FOO (sorry that I'm not being
> original here). For RTSP 1.0 (I cannot use 2.0 at this time) I would do
> the following?
> 
> transport-protocol  =    "IP"
> profile             =    "FOO"
> lower-transport     =    "UDP"
> 
> 
> 
>     C->S: SETUP rtsp://example.com/foo RTSP/1.0
>           CSeq: 302
>           Transport: IP/FOO/UDP;multicast;ttl=127;port=5200
> 
>     S->C: RTSP/1.0 200 OK
>           CSeq: 302
>           Date: 23 Jan 1997 15:35:06 GMT
>           Session: 47112344
>           Transport: IP/FOO/UDP;multicast;
>             ttl=127;port=5200
> 


The only think missing from the above is the IP address in an
destination parameter.

But, for the above instead of IP/FOO/UDP, it would rather be FOO/UDP. IP
is ommitted here. In RTSP 2.0 we allow a more flexible specification
with more than three levels if needed.

> 
> 
> You said something about registering parameters. Where/how would I do
> that? Thank you again for your time and help :-)

So for the above it would be basically be to register the transport
FOO/UDP. If you have no new parameters you don't need to register anything.

And for RTSP 1.0 there exist no registry for this parameters. Only the
most high level concept has been retrofitted with registries, i.e.
methods, headers, status codes and option tags.

If you are going this direction and you settle on a particular protocol
names and combinations. An email to this list about this at leas allows
us to know that you are using that combination. Possibly you would like
to register this for RTSP 2.0. The relevant registry has the policy of
specification required. See Section 22.13.1 of
draft-ietf-mmusic-rfc2326bis.

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
----------------------------------------------------------------------