W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2014

Proposal for RTCRtcpMuxPolicy

From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 29 Dec 2014 15:38:56 -0800
Message-ID: <CAJrXDUFsKGSYP3MCKOWBb_fA3PuUG8yOAQF4hmuhF3EaYuVCAQ@mail.gmail.com>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
At IETF 91, we decided to split the bundle policy an rtcp mux policy into
separate policies in JSEP (instead of having "max-bundle-and-rtcp-mux").

Meanwhile, I also created a pull request for RTCBundlePolicy, based on
previous discussion on the list: https://github.com/w3c/webrtc-pc/issues/137
 (the PR has balanced, max-bundle, and max-compat, but not

So, now we need an RTCRtcpMuxPolicy.  I propose we make it just like
RTCBundlePolicy, which is, to add it to RTCConfiguration like so:

enum RTCRtcpMuxPolicy {
  "optional"  // RTCP candidates are gathered, but discarded if the remote
endpoint can mux RTCP.
  "required",  // RTCP candidates are not gathered

dictionary RTCConfiguration {
  // ... iceServers, bundlePolicy, etc
  DOMString rtcpMuxPolicy = "optional"; // see RTCBundlePolicy

Of course, we want this to match JSEP, so we may need to wait to see what
JSEP decides are the names for "optional" and "required".
Received on Monday, 29 December 2014 23:40:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:42 UTC