IETF Logo Mail Archive

Re: [MMUSIC] comments on draft-even-mmusic-application-token-01

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 28 October 2013 17:33 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 A75C811E833B for <mmusic@ietfa.amsl.com>; Mon, 28 Oct 2013 10:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.057
X-Spam-Level:
X-Spam-Status: No, score=0.057 tagged_above=-999 required=5 tests=[AWL=-0.106, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_54=0.6, RDNS_NONE=0.1]
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 nc-3HckcXbOX for <mmusic@ietfa.amsl.com>; Mon, 28 Oct 2013 10:32:59 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id F3A8511E833C for <mmusic@ietf.org>; Mon, 28 Oct 2013 10:32:39 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta13.westchester.pa.mail.comcast.net with comcast id ibtN1m0061GhbT85DhYf3A; Mon, 28 Oct 2013 17:32:39 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta07.westchester.pa.mail.comcast.net with comcast id ihYf1m0063ZTu2S3ThYfs9; Mon, 28 Oct 2013 17:32:39 +0000
Message-ID: <526E9FB7.2060000@alum.mit.edu>
Date: Mon, 28 Oct 2013 13:32:39 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>, 'Martin Thomson' <martin.thomson@gmail.com>
References: <526D5CDD.40805@alum.mit.edu> <CABkgnnVekG9bDbO7mvNPcKHH1w3JmvKTcT2K=D1-ERW-vr2GLA@mail.gmail.com> <526D8FA3.1030503@alum.mit.edu> <CABkgnnXTYCx8uWZPUq7KgGdSr1w64kq_SCTDVP56p5DEjaYj3g@mail.gmail.com> <019f01ced3ed$f83e1090$e8ba31b0$@gmail.com>
In-Reply-To: <019f01ced3ed$f83e1090$e8ba31b0$@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382981559; bh=pZZquBZcU1U3FLP47mcFvttLoycWtN1cWZvx8+UAdiw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=YoMhBvy0LAtsD13oFq2rN8rJwkBuB/vzeNLIN76jRH/x6U3n1+UTn09X6WDsUx70p Thz5zhbWVwjAEY4M3yLWCLtA7tOCS7D6c2KQBmKWRjrJoGa3DMMAaQx+LLtvmyRBnk 16cGWNegVtM1kUhbt9cTtzEPJ5i7r0lFSMVOvIsddF20W4zQ1wyB76RTshl2ubPXmu 0IjVY8Vb4tBflGLlwMe7dFI7kc5NQ2rrYX8sTYRrNGPz2zSGZDbIMIxGxNZOHFyvQ7 nTNFVAptFf3WXUSCegnu5Xbt75e0dfqp/zwlW0h9HDWGV2EawSEyEztYLEW03Ra/xk U9hoGJ60f+TnQ==
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] comments on draft-even-mmusic-application-token-01
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: Mon, 28 Oct 2013 17:33:03 -0000

Roni,

On 10/28/13 10:57 AM, Roni Even wrote:
> Hi,
> The appId is used to map to an SSRC so in the unified plan there can be more
> than one RTP stream from a source like simulcast (see the new avtcore
> simulcast-03 draft) but there can be an m-line for RTP stream like the CLUE
> signaling examples.
> So there should be a different appIDd to the source and repair streams and
> the association  is done using SDP group (RFC5956), note that the
> association is very flexibly and the example we give is the case when one
> repair stream is repairing three source streams from different cameras which
> are different sources. This is feasible for a TP system.
> Having this FEC repair stream raises
>   The question what is the msid of the repair stream and my thought was that
> there is none (or all three?)

I *think* you are confirming what I wrote in my original comment:

> - an RTP session MAY have one or more appid tokens
> - at any point in time each appid token maps to at most
>   one stream (SSRC) within the session.
> - *new* appid:ssrc mappings MAY be initialized via SDP
> - new appid:ssrc mappings MAY be initialized via receipt
>   of the new RTPC SDES message or header extension
> - existing appid:ssrc mappings MAY be updated via
>   receipt of the new RTCP SDES message or header extension.

including the 2nd point above. Is that true?

	Thanks,
	Paul

> Roni
>
>> -----Original Message-----
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
>> Of Martin Thomson
>> Sent: 28 October, 2013 4:46 AM
>> To: Paul Kyzivat
>> Cc: mmusic@ietf.org
>> Subject: Re: [MMUSIC] comments on draft-even-mmusic-application-token-01
>>
>> On 27 October 2013 15:11, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>> I *thought* that for instance in case of FEC, the original stream and
> the
>> repair stream would have the same appid. But the example showed otherwise.
>>
>> That's odd.  I'd have thought that too.
>>
>>> I'd like the model to be spelled out. Then we wouldn't be wondering.
>>
>> Yep.  Much better.  All it takes is something like 1 appid = 1 media
> source.
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>
>

v2.23.0 | Report a Bug | By Email