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

Christer Holmberg <> Mon, 03 March 2014 10:34 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B04C61A0E72 for <>; Mon, 3 Mar 2014 02:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id osLJjI8Cpz4Q for <>; Mon, 3 Mar 2014 02:34:31 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id F41C51A0E92 for <>; Mon, 3 Mar 2014 02:34:28 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-b0-53145ab1ac79
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 1B.17.04249.1BA54135; Mon, 3 Mar 2014 11:34:25 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 11:34:25 +0100
From: Christer Holmberg <>
To: Justin Uberti <>
Thread-Topic: JSEP-06: max-bundle policy questions
Thread-Index: Ac8xgReyx0/WK3m4RUOln8j3WJLYRQE13CuAABzQDnA=
Date: Mon, 03 Mar 2014 10:34:24 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
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=
Cc: "" <>
Subject: Re: [rtcweb] JSEP-06: max-bundle policy questions
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 03 Mar 2014 10:34:33 -0000

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.”
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.