Re: [rtcweb] JSEP-06: max-bundle policy questions

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 03 March 2014 10:34 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 B04C61A0E72 for <rtcweb@ietfa.amsl.com>; Mon, 3 Mar 2014 02:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 osLJjI8Cpz4Q for <rtcweb@ietfa.amsl.com>; Mon, 3 Mar 2014 02:34:31 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id F41C51A0E92 for <rtcweb@ietf.org>; Mon, 3 Mar 2014 02:34:28 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-b0-53145ab1ac79
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 1B.17.04249.1BA54135; Mon, 3 Mar 2014 11:34:25 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 11:34:25 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Justin Uberti <juberti@google.com>
Thread-Topic: JSEP-06: max-bundle policy questions
Thread-Index: Ac8xgReyx0/WK3m4RUOln8j3WJLYRQE13CuAABzQDnA=
Date: Mon, 3 Mar 2014 10:34:24 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5C0A@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1B552E@ESESSMB209.ericsson.se> <CAOJ7v-1FoDyHS=b40VZQAcjrS06fvF1gabPjE6CFVaMSHRUHnA@mail.gmail.com>
In-Reply-To: <CAOJ7v-1FoDyHS=b40VZQAcjrS06fvF1gabPjE6CFVaMSHRUHnA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5C0AESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyM+Jvje7GKJFgg3PntC22ThWyWPuvnd2B yWPBplKPJUt+MgUwRXHZpKTmZJalFunbJXBlXH5xi72gw6Vi3oVmpgbGKU5djJwcEgImEo3L ZjFC2GISF+6tZ+ti5OIQEjjCKNF/aTWUs5hRYv7E18xdjBwcbAIWEt3/tEEaRATUJB7O2sUK YjMLqEvcWXyOHcQWFjCUWDplKRNEjZFEz6rZbBC2lUTnl5csIDaLgIrEun/bwGp4BXwlmhr/ MULsmsIose9jD9hQToFAiQc/t4HZjEDXfT+1hglimbjErSfzmSCuFpBYsuc8M4QtKvHy8T9W CFtJYtHtz1D1+RJHNh6FWiYocXLmE5YJjKKzkIyahaRsFpKyWUAvMwtoSqzfpQ9Roigxpfsh O4StIdE6Zy47svgCRvZVjBzFqcVJuelGBpsYgRF1cMtvix2Ml//aHGKU5mBREuf9+NY5SEgg PbEkNTs1tSC1KL6oNCe1+BAjEwenVANjwFN/C7G+sP5FW34+f5TP5dNvn2/CurLyCmNu8EG1 9aqRU7WrN9vwJUXendY4i98i38jX6uWmtZEbam1Fj1pHmZuvS3JlDN6QcifjwqE/aXWnbQTP Ci/busfmeIbC4l0t03bf0pxwdxnvvep7vF7r7K1n8gnPytx+6pRvz5nGU69UDmr7FOsqsRRn JBpqMRcVJwIAprI66nYCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/kJ3-vqO37cdh2E6IOQG-db3O79c
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP-06: max-bundle policy questions
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: Mon, 03 Mar 2014 10:34:33 -0000

Hi,
Section 4.1.1 says:
“o  "max-bundle": The application will BUNDLE all of its media streams
      on a single transport.  All streams other than the first will be
      marked as bundle-only.  This policy aims to minimize candidate
      gathering and maximize multiplexing, at the cost of less
      compatibility with legacy endpoints.”
Q1:
I think it would be good to clarify that the application will BUNDLE all of its media streams *THAT THE APPLICATION IS ABLE TO DE-MULTIPLEX*.

I don't follow what you are saying here. How would a WebRTC application end up with streams it could not demultiplex?

Maybe someone is implementing some new media type, for which the bundling hasn’t been specified.

Regards,

Christer