Re: [MMUSIC] Some more thoughts on the simulcast discussion

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 15 October 2015 21:43 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 E9B131A6F61 for <mmusic@ietfa.amsl.com>; Thu, 15 Oct 2015 14:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level:
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, SPF_SOFTFAIL=0.665] autolearn=no
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 CEEGtmZnx7ZR for <mmusic@ietfa.amsl.com>; Thu, 15 Oct 2015 14:43:25 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A70AB1A6F34 for <mmusic@ietf.org>; Thu, 15 Oct 2015 14:43:25 -0700 (PDT)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-10v.sys.comcast.net with comcast id VZiy1r0082TL4Rh01ZjQvx; Thu, 15 Oct 2015 21:43:24 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-17v.sys.comcast.net with comcast id VZjQ1r0073Ge9ey01ZjQAs; Thu, 15 Oct 2015 21:43:24 +0000
To: mmusic@ietf.org
References: <561DFFF3.5040703@alvestrand.no> <561E8A27.9000202@alum.mit.edu> <561EBAD5.1020502@alvestrand.no> <562010BF.8060306@nostrum.com> <56201405.4080106@alvestrand.no>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <56201DFB.3030100@alum.mit.edu>
Date: Thu, 15 Oct 2015 17:43:23 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <56201405.4080106@alvestrand.no>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1444945404; bh=tL4Yc7vOJwDIJCzSWDk40u3aKnRxl7n99ZXAmo317Mo=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=NQplDarMk8VXWqdbDSvTzpVW8RQ5V73hudwOxYfunDKcSJbZY9V/hTDBsV0h01k3r 5VAcmoz1vfPTTwifW6bgKxmLt3ZalPUiUy4QAGt2UrQuTJ5CYUjLYcwmGvwZ9b5m+k Sq31gLkFVfoK1rs7L4yLhdaj0M4Ht0ZVZPTnfjtVtJfzn3GMlCZLYbrezId0PZebuR 4k07UNxMI+H5p4VKn4RyTlGSmVaTNoCiwNYyz+rkiDkJtL/AWpmd3HyPdGqmLasiun SriGHOP3BO7n1frh/xJ+gBpzq16Oc1j7PbwjhA7OVAN2rr06ElknHhNhRC0oPA3JTq y0gmY/yDMcnUw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/fq7Jv37ONvOmLW3u915UtajSkiE>
Subject: Re: [MMUSIC] Some more thoughts on the simulcast discussion
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 15 Oct 2015 21:43:27 -0000

On 10/15/15 5:00 PM, Harald Alvestrand wrote:
> On 10/15/2015 10:46 PM, Adam Roach wrote:
>> On 10/14/15 15:28, Harald Alvestrand wrote:
>>> On 10/14/2015 07:00 PM, Paul Kyzivat wrote:
>>>> On 10/14/15 3:10 AM, Harald Alvestrand wrote:
>>>> What seems clear is that SDP doesn't get the granularity right about
>>>> the stuff it can reference. So people end up using things that aren't
>>>> quite right, and adjusting their usage to align with what it is
>>>> possible to describe.
>>> We are worrying about the same set of issues.
>>>
>>
>> This is actually the exact problem that RID seeks to solve: by
>> defining a new construct rather than trying to leverage existing ones
>> (which, as you observe, end up being ill-fitting in many cases), we
>> are able to point quite precisely at the *thing* of interest, instead
>> of obliquely waving at some badly-matched proxy for that thing.
>
> That is the good thing about RID: That it is able to point precisely at
> one specific media stream.

I think we should carefully identify what we are talking about within 
the terminology of the taxonomy document.

> [distraction: can two media streams have the same RID but different
> SSRCs? What does that mean if it's legal? Where do we enforce the
> restriction if it's illegal?]

That is an important thing to resolve.

> That was also the good thing about a=SSRC (modulo the collision problem).
>
> Now we "only" have to define:
>
> - What exactly we can state about the thing we're pointing at
> - What language(s) we use to make those statements
> - How those statements are resolved against all the *other* tools inside
> SDP that can be used to make statements about things that might also
> happen to refer to the thing we're pointing at.

This last point is important. (And hard.)

> It's possible that we can define RID in such a way that the answers are
> simple enough that they can be written down and agreed upon quickly.
>
> But I can't see us succeeding without at least considering the issues.

Yup.

	Thanks,
	Paul