Re: [rtcweb] Quick comments on draft-roach-rtcweb-glareless-add-00

Adam Roach <adam@nostrum.com> Thu, 09 May 2013 15:39 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B533821F925A for <rtcweb@ietfa.amsl.com>; Thu, 9 May 2013 08:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level:
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, SPF_PASS=-0.001, 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 ewHXnLIc5Jsl for <rtcweb@ietfa.amsl.com>; Thu, 9 May 2013 08:39:53 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2068921F905F for <rtcweb@ietf.org>; Thu, 9 May 2013 08:39:53 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r49Fdngp019099 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 9 May 2013 10:39:50 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <518BC345.6060807@nostrum.com>
Date: Thu, 09 May 2013 10:39:49 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <CA+9kkMDWy_Koq0Aun5A330O7OOMt9vimWPNe_uznAQdr0TSfow@mail.gmail.com> <51897B11.60004@nostrum.com> <518AB095.7010401@alum.mit.edu> <518AC143.2010006@nostrum.com> <518BBE2A.4060102@alum.mit.edu>
In-Reply-To: <518BBE2A.4060102@alum.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
Subject: Re: [rtcweb] Quick comments on draft-roach-rtcweb-glareless-add-00
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 May 2013 15:39:53 -0000

On 5/9/13 10:18, Paul Kyzivat wrote:
> On 5/8/13 5:18 PM, Adam Roach wrote:
>>
>> What I was trying to say above is that the only information you would
>> need to convey is literally one, two, or three <mediatype,ordinality>
>> pairs. You don't say what you're planning to do with them, just that you
>> need them.
>
> How is that possibly enough? What codecs and codec parameters/optons? 
> What bandwidth? What bundling options? The list goes on.

I apologize. I must have done a really poor job in the prose in my 
draft, since I clearly didn't communicate the fundamental mechanism that 
I had in mind at all.

Let me try with a ladder diagram to see whether that helps illuminate 
what I'm proposing.


Offerer                             Answerer
    |                                    |
    |<----------Solicitation-------------|
    |  (I need 1 new audio 1 new video)  |
    |                                    |
    |                                    |
    |-------------SDP Offer------------->|
    | (Contains two more m-line sections |
    | than the current session; one      |
    | audio, one video. Both recvonly.)  |
    |                                    |
    |                                    |
    |<------------SDP Answer-------------|
    | (Makes use of the two new m-line   |
    | sections by populating them with   |
    | codec parameters, options, ssrc    |
    | bandwidth, bundling, etc, etc.)    |


/a