IETF Logo Mail Archive

Re: [rtcweb] BUNDLE with implicit rtcp-mux

Justin Uberti <juberti@google.com> Thu, 13 March 2014 16:17 UTC

Return-Path: <juberti@google.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 990CF1A0A1E for <rtcweb@ietfa.amsl.com>; Thu, 13 Mar 2014 09:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level:
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, 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 eA4jNjSrltlx for <rtcweb@ietfa.amsl.com>; Thu, 13 Mar 2014 09:17:24 -0700 (PDT)
Received: from mail-vc0-x235.google.com (mail-vc0-x235.google.com [IPv6:2607:f8b0:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 957971A073C for <rtcweb@ietf.org>; Thu, 13 Mar 2014 09:17:24 -0700 (PDT)
Received: by mail-vc0-f181.google.com with SMTP id id10so1364786vcb.12 for <rtcweb@ietf.org>; Thu, 13 Mar 2014 09:17:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=XMbokdT/7IEZLTI+MRPPImSu9RUyp9K9yNOSccnCGfk=; b=kYdQvSirt2BVuUDzZlgkhIosy05Yku4Wk2X/fIaLEEcLrgkL83gytcmM25mpSvK7/D J9vPsJUy7TjK9gqbtjl7g0jIRkr6dphtVzfuJ4t/1DedQi1yZkUxngQcTr9q/bOXpuQU Rx1cOLu4Hi4bZo6c1C+/eepF3GFN40s8I4rWQF2gPGXJ8UC3Y2iHffaXVYwvmOcdbO+8 2CN8NhJc5saFpjbooQmPjfdicNBE6rFa68yN2Jfs4THCH6qKTlAI6S6ihQGEdp/5INJR Jfmtfzf5z0xZv3cQZOzdT808P3x/eTlLMRyrR54Dslucn+8ypGFTjJOlxXFkz++bz7Se wz/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=XMbokdT/7IEZLTI+MRPPImSu9RUyp9K9yNOSccnCGfk=; b=jMb1P4RW3OEAji7k33D9HBru2/Dft7Ja4hJo0DkTtEVOtcdZM33fNl3hhVC2LUNYDe 1hCmKh/XW0fVvwq7RWyzvuaKEIe3T24A4Zb2fuDrIySBF5ZItnVE9Wl4EecwBkFzgkFB 9npIBvg/rJjnDdqGWHlSZfGsqq65SlLnhI08a8HusfDFYyLvLDrf89CXKRjiELQuqs/t AGKjA87KXhJQFW49As7modVeVNKsUIDBatLuaKrA0yqnzeizXKaWL1W/GYDRAe8eaaHS ndH2FtRDrB+eD5df4S8CfGNHQSf/x4ozNE1myNulGtK1O0EuLtIuWNnK+8Int/V3w5IL e3VA==
X-Gm-Message-State: ALoCoQldpshApVPx4RaIzRvHjd8pABgQylPCtWHcp0gipWxxhrPr7ilARLzFdPjB5uFL4NSq1EaTIARlJ/4WdUAZUpDl68Olq9VmFSG0xUGlF+xUhKOJkXNbLMlzNNH7mLQrdDSNMegdTNCE69uiVSHiz8Aa5VUHIJo+9cfLN1GQw/u3Wf+iU2pzbUL5YLHJVzeKBMsA+2Kq
X-Received: by 10.220.109.1 with SMTP id h1mr2151039vcp.20.1394727437931; Thu, 13 Mar 2014 09:17:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Thu, 13 Mar 2014 09:16:57 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D212A7E@ESESSMB209.ericsson.se>
References: <CAOJ7v-063mGE_zndtAqAMN2fJw7kWvUHX2SgyDMryfw_-aS-9w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1F1892@ESESSMB209.ericsson.se> <531DC52B.6020500@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D1FA6BC@ESESSMB209.ericsson.se> <531DCBE9.70701@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D1FA7B2@ESESSMB209.ericsson.se> <531DD756.50900@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D200086@ESESSMB209.ericsson.se> <532017DD.1060500@ericsson.com> <CAOJ7v-1u6eO4b1Qr4josdNoNBtW7s0Z82y570X4RwV0C4es2hg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D212A7E@ESESSMB209.ericsson.se>
From: Justin Uberti <juberti@google.com>
Date: Thu, 13 Mar 2014 09:16:57 -0700
Message-ID: <CAOJ7v-1YF+6Hfid+pPAHWZnjPeXJ+T81eV7Wk83+z4eCtUAgYw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="001a11c308d67f312904f47f49f6"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/4og_nu4vOzhWfyxOzU-eKQi91wM
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] BUNDLE with implicit rtcp-mux
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, 13 Mar 2014 16:17:26 -0000

On Thu, Mar 13, 2014 at 5:52 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi Justin,
>
> > I think rtcp-mux has to be a MUST use when BUNDLE is used between the
> two endpoints. (If the endpoint doesn't support
> > BUNDLE, rtcp-mux is not required.)
> >
> > Otherwise, you get into weird edge cases, such as where you have a data
> channel (no RTCP component), and then want
> > to add audio (with RTP and RTCP components). You could bundle the audio
> RTP over the existing data channel transport,
> > but it's not clear what you should do with the RTCP component. Mandating
> rtcp-mux avoids this issue completely.
>
> According to section 4 in RFC 5761, if you multiplex RTP and RTCP on the
> same port, you need to assign dedicated PT values to the RTCP packets,
> which means that at least PT values 64-95 cannot be used for RTP.
>
> As you have been one of those talking about the risk of running out of PT
> values, I just want to make sure you have taken this into consideration :)
>
>
Yes. The upside of rtcp-mux far outweighs this minor limitation.

v2.23.0 | Report a Bug | By Email