IETF Logo Mail Archive

Re: [rtcweb] 5 tuples and rmcat-cc-requirements-01

Harald Alvestrand <harald@alvestrand.no> Thu, 02 January 2014 07:16 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAF631AD6D2 for <rtcweb@ietfa.amsl.com>; Wed, 1 Jan 2014 23:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538] autolearn=ham
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 JvBLEXM88nsI for <rtcweb@ietfa.amsl.com>; Wed, 1 Jan 2014 23:16:45 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [IPv6:2001:700:1:2:213:72ff:fe0b:80d8]) by ietfa.amsl.com (Postfix) with ESMTP id 922AA1AD1F5 for <rtcweb@ietf.org>; Wed, 1 Jan 2014 23:16:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id EB76E39E127; Thu, 2 Jan 2014 08:16:42 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CR44MvSQKnl6; Thu, 2 Jan 2014 08:16:42 +0100 (CET)
Received: from [IPv6:2001:470:de0a:27:60c4:879c:21ee:c898] (unknown [IPv6:2001:470:de0a:27:60c4:879c:21ee:c898]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 002A439E080; Thu, 2 Jan 2014 08:16:41 +0100 (CET)
Message-ID: <52C51279.2000304@alvestrand.no>
Date: Thu, 02 Jan 2014 08:17:13 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Eric Rescorla <ekr@rtfm.com>
References: <CAA93jw7FDddn2n23fm=rdUsDyGakNfyLkJDgNjoC43fSc4GnSA@mail.gmail.com> <CABkgnnUR1ARiMRTKwieQmNz3qg=RiagF=zdo6LYf02pQaz+7nQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C432187@ESESSMB209.ericsson.se> <CABcZeBNv1AyVmj2we=wBZjOSNnt-P0HbQdK91TsMxnstzrOadg@mail.gmail.com> <52C4910B.3000209@alvestrand.no> <CABcZeBOf9E+_WxCRMPc8zqXnXVR=BDtw9VHpz44FC_n7ks=L-w@mail.gmail.com>
In-Reply-To: <CABcZeBOf9E+_WxCRMPc8zqXnXVR=BDtw9VHpz44FC_n7ks=L-w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070403000902000407080403"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] 5 tuples and rmcat-cc-requirements-01
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Jan 2014 07:16:48 -0000

On 01/01/2014 11:28 PM, Eric Rescorla wrote:
> On Wed, Jan 1, 2014 at 2:04 PM, Harald Alvestrand <harald@alvestrand.no> wrote:
>> On 01/01/2014 04:40 PM, Eric Rescorla wrote:
>>> Is there some reason why people are avoiding the obvious avenue
>>> of creating an API to control BUNDLE? We already need one for
>>> BUNDLE-only anyway.
>>>
>>>
>> I've been thinking that the bundle-only properties of tracks belong with the
>> SenderController.
>>
>> The decision on whether or not to do BUNDLE probably belongs to the
>> PeerConnection initialization parameters. Should be easy enough to specify,
>> once we all agree that we want it to exist.
> Why do you think one wouldn't want to be able to individually specify
> bundle for some of the the m-lines but not others?
>
I didn't say that!

Some people have said that they want to be able to turn off the entire 
BUNDLE mechanism (no multiplexing at all) - with SDP manipulation, that 
can be accomplished by removing the relevant SDP-session-level line 
(a=group:BUNDLE); since this is an SDP session level attribute, it would 
seem to be reasonable to have the corresponding control on 
PeerConnection initialization.

This is in addition to the disable/enable per track, which I would 
assume would be an extension to the current transmission controller 
proposal, which is at 
http://www.w3.org/2011/04/webrtc/wiki/Transport_Control#API_proposals - 
I haven't seen a specific proposal here yet, but it seems easy enough to 
make.

(now officially back from vacation, so will respond a bit faster now. 
Happy new year, everyone!)

v2.23.0 | Report a Bug | By Email