Re: [MMUSIC] Relation between SRCNAME and MSID
"Roni Even" <ron.even.tlv@gmail.com> Tue, 06 November 2012 14:04 UTC
Return-Path: <ron.even.tlv@gmail.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 67EE521F8917 for <mmusic@ietfa.amsl.com>; Tue, 6 Nov 2012 06:04:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[AWL=0.478, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_57=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8mFdqjpP0Zm5 for <mmusic@ietfa.amsl.com>; Tue, 6 Nov 2012 06:04:54 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id AA30E21F8914 for <mmusic@ietf.org>; Tue, 6 Nov 2012 06:04:54 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id ro8so442774pbb.31 for <mmusic@ietf.org>; Tue, 06 Nov 2012 06:04:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=AQtYaxlFMPTwot1mFkdbLX8YDcOemAyKuAeCyheh68M=; b=zJecFHCpv50HdTIS6Jv7VVorMR3p3umlpkBO2qpZiYakd3b4GQ+3UgDNaI5k6qnaPT X3xbbMAtqh1zWjnZ0MtxCjjlfkDY2YwfDeB4L8g/9iS5YxwrkrO98N9eTvIydrt73ean DmgFe5DFbyQGytlH1oxLzei4HdCIYJv6Pk4EWC1UsOS4scKtrnzAP8YLJqXI63rAApk0 tlR2v8we2KrdFjzGd2N0AadBiibA5pja5aTNZI6o/LA7StG0JLO1dsyzZUDwBjrk8vya dp+DqDUYrlSriYKe23wMI9i9KDMTrDELl+Q8D7FCjv0CxScrfuTAkQjrMmDxicu8tKEu WQMg==
Received: by 10.68.115.75 with SMTP id jm11mr3730742pbb.28.1352210694490; Tue, 06 Nov 2012 06:04:54 -0800 (PST)
Received: from RoniE ([2001:df8:0:16:fcb4:4f05:b023:df17]) by mx.google.com with ESMTPS id m7sm7285079paz.3.2012.11.06.06.04.51 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 06 Nov 2012 06:04:53 -0800 (PST)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, "'mmusic (E-mail)'" <mmusic@ietf.org>
References: <50990A0D.305@ericsson.com>
In-Reply-To: <50990A0D.305@ericsson.com>
Date: Tue, 06 Nov 2012 09:02:18 -0500
Message-ID: <004f01cdbc27$57633bc0$0629b340$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK3qumR9zd0Tpbn0anlgsM+d1sGsJYI9s7w
Content-Language: en-us
Subject: Re: [MMUSIC] Relation between SRCNAME and MSID
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: Tue, 06 Nov 2012 14:04:55 -0000
Hi, I had the same question when looking at mapping RTP streams to CLUE media capture and after trying to address simulcast in that environment it looked to me that srcname can be used for mapping since if we look at hierarchy of CNAME.srcname we can say that if we have an endpoint that have multiple media sources (e.g. 3 cameras) this can be reflected using the same CNAME with srcnames V1,V2 and V3. If using srcname for the simulcast case it make sense not to have a different identifier for the non simulcast case. Roni Even -----Original Message----- From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of Magnus Westerlund Sent: 06 November, 2012 8:01 AM To: mmusic (E-mail) Subject: [MMUSIC] Relation between SRCNAME and MSID Hi, I got to reading the MSID this morning and as it was some questions how SRCNMANE (draft-westerlund-avtext-rtcp-sdes-srcname-02) relates to MSID (draft-alvestrand-mmusic-msid-01) I will give my view on this. So SRCNAME is a hierarchical structure who's root is a media stream source, i.e. a camera or a microphone. Its primary usage is to bind SSRCs that are all related to that media source together. A simple example would be if one produced simulcast, i.e. alternative encodings, of the same media source V1, you can have a source name that is V1.enc1 for the first encoding, V2.enc2 for the second one, and so on. When you apply RTP retransmission or FEC you do that to a particular SSRC, which then is one of the encodings. Or even more complex if an encoding is an SVC MST stream, then you have several streams in different RTP sessions for the different layers, and your FEC or retransmissions only applies to one of these substreams. Thus you can have a SSRC that carries a SRCNAME of V1.enc1.baselayer and use that label for both the media stream and on the FEC SSRC to tie them together. So SRCNAME shares a property with MSID that is that is ties SSRCs both within and across RTP Sessions together. So MSID, especially in its usage with WebRTC to create the WebRTC MediaStream actually have an interesting relation to SRCNAMES. As MSID are application level groupings of particular mediaStreamTracks, a MSID can be used to tie in RTP media stream and its related SSRCs (the ones carrying the FEC or the layers) into a MediaStream object. Lets try an simple example to illustrate. A WebRTC end-point has one video camera (V1) and one microphone (A1). The video is to be provided at two different encodings V1.enc1 and V1.enc2 in SRCNAME terms. But for a WebRTC application it can actually select to deal with these two encodings as two different WebRTC MediaStreams which I will give MSID values Var1 and Var2, where the variants contain one video encoding and the audio In SDP using a=ssrc to provide the SRCNAME it would look like this m=video a=ssrc: 1111 SRCNAME:V1.enc1 a=ssrc: 1111 msid:Var1 v1 a=ssrc: 2222 SRCNAME:V1.enc2 a=ssrc: 2222 msid:Var2 v1 a=audio a=ssrc: 3333 SRCNAME:A1 a=ssrc: 3333 msid:Var1 a1 a=ssrc: 3333 msid:Var2 a1 In other words a given SSRC might actually be a MediaStreamTrack in multiple MediaStreams and thus have multiple MSIDs. While a SSRC will only have one SRCNAME, but that one may specify to a higher detail. If we would have RTP retransmission in the above, a question around MSID arises. Should all SSRCs that are part of representing be given a MSID or would it be simpler to just label the media entry point to the hierarchical relations SRCNAME is capable of expressing? And I need to point out that MSID can't replace the SRCNAME as currently defined as it doesn't make clear the hierarchical relation of the SSRCs. If you are interested in discussion SRCNAME please show up in AVTEXT on Wednesday at 1300-1430. 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 mailing list mmusic@ietf.org https://www.ietf.org/mailman/listinfo/mmusic
- [MMUSIC] Relation between SRCNAME and MSID Magnus Westerlund
- Re: [MMUSIC] Relation between SRCNAME and MSID Roni Even