Re: [MMUSIC] Why do we need rtcp-mux-exclusive?

Eric Rescorla <ekr@rtfm.com> Sat, 05 March 2016 14:28 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E99521B32E7 for <mmusic@ietfa.amsl.com>; Sat, 5 Mar 2016 06:28:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] autolearn=no
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 7C-M8J91b7Zo for <mmusic@ietfa.amsl.com>; Sat, 5 Mar 2016 06:28:28 -0800 (PST)
Received: from mail-yk0-x235.google.com (mail-yk0-x235.google.com [IPv6:2607:f8b0:4002:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFE271B32E6 for <mmusic@ietf.org>; Sat, 5 Mar 2016 06:28:27 -0800 (PST)
Received: by mail-yk0-x235.google.com with SMTP id h197so13209193yke.2 for <mmusic@ietf.org>; Sat, 05 Mar 2016 06:28:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TiRxM7ahwvyuqHz1Wdsbk4e3D8/GddzZr2ddrD7v0cs=; b=AZgCv5utqP0vrZd6psQGdmzK2oYUI9CrpRzUV62z6Cl5nBig7jsxl57Ed572ZoIW5p GihQ1RKH2+yrNaXYp8X53waX1TsUiU2/5/NuwXsQ3TFU6quwcqgaZADJA1f3Ir+4BQ0n bwrNYI830CA5XPdtUL7EesMtmny2KRvxydVNupb0PRSiTArBy9nuY0wX0wlOeS7pSAV5 Xp30aDxA9JeLfDofEDH4o9Bpja599xGUS2PEO8LtvJskss/w4HkSJ2R4m84KdT8xC1HI NhocaAaZPlhPZQZBPKTaOtyZCagZXbQlypGonEoFT9f8zIE5E/RVXt20yugID4CbSA3E YlgA==
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; bh=TiRxM7ahwvyuqHz1Wdsbk4e3D8/GddzZr2ddrD7v0cs=; b=CuUBO337g12QSVUc+CZD9OmBHNGm/1zxNU9PoO/mkoasL+BE9w06dMQ4of5Qgklt6+ uwJKZDcL6+LPvrNIhZKIS4Ld95jhvs+6tgfzDpDk/IjvU8iv3qWRyNIOq7WlDGG25K6R cqRV7Xm18tkrT/WaIMYEwzzb1Ern2d+/ZbjDpc9zfhNp84ZcjQv+7mzHBXD2tx3pT8bL LpXppB4RSv5s++lHN6liGi0hWTlWRW6hPA30VKj2T4FTWTck3lFOcS4PQmvuKk8D4xDr hiTi1NQeMOnFYvkva0nzk2iykbpAuYaSzN/w/ZdN8GnT9kY2I3/x1keHJB5tS+7YPYh9 OaCg==
X-Gm-Message-State: AD7BkJKcAsDo0EunsyqK7bYXa1a33TeRYFIttGlFxg0pkrd83kxz2ztMqtnN8JqF1bpE72axXFKkqz8+yaeksA==
X-Received: by 10.37.231.130 with SMTP id e124mr7200031ybh.146.1457188107087; Sat, 05 Mar 2016 06:28:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.13.249.5 with HTTP; Sat, 5 Mar 2016 06:27:47 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37E7236F@ESESSMB209.ericsson.se>
References: <CABcZeBNsJkqGcU3Z=eekP4ntj7r3WMz6YOSiFt=u+HdDH2Zk3Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37E5A4E2@ESESSMB209.ericsson.se> <CABcZeBOGpguqkEeUoH35R2S_fOU=eGWgG7r5gmH3T_UHXqRRjg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37E5BBC1@ESESSMB209.ericsson.se> <CABcZeBOQKX+LKu1vafq227wv4sy+AApmixGB4fb7wTeuByYTMQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37E5C345@ESESSMB209.ericsson.se> <CABcZeBPNOCTT1ahJsH0OSaOwFnLicFSjHWUbAXxQ3sFu5tUdjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37E7236F@ESESSMB209.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 05 Mar 2016 06:27:47 -0800
Message-ID: <CABcZeBNtmfjrETCerCu=A5BXt5HRCG+nO4KZ4ze3sBEeRNnX_A@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="94eb2c0b12ee7ea79e052d4e0bff"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/eKH95C6uR8nPwzg8subEr4nDLmY>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Why do we need rtcp-mux-exclusive?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Mar 2016 14:28:29 -0000

On Sat, Mar 5, 2016 at 6:13 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:
>
> > Yes, of course, but the question is how they will behave if they receive
> rtcp-mux-exclusive.
>
> IF (for whatever reason) non-mux is required on the "other side" of the
> gateway then the gateway will do "transcoding" between mux and non-mux.
>

Given that essentially every Web browser is going to do only mux, it seems
like the gateway
can just infer this. In fact, since in most of these cases, the gateway and
the Web app are
related entities, that should be extremely straightforward.


> Can we get those implementors to speak up on the list?
>
> I represent one of those implementers :)
>

Yes, I had assumed so.

Bottom line, this seems like just another piece of complexity for minimal
value, so I
propose dropping it. Does anyone else want to speak up for it?

-Ekr