Re: [Rum] Codec requirements in draft-rosen-rue-01

Brian Rosen <> Wed, 28 August 2019 15:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E35CA1200E3 for <>; Wed, 28 Aug 2019 08:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id C5RJH48ozdUY for <>; Wed, 28 Aug 2019 08:36:57 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::832]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 414CA120059 for <>; Wed, 28 Aug 2019 08:36:57 -0700 (PDT)
Received: by with SMTP id t12so3472383qtp.9 for <>; Wed, 28 Aug 2019 08:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ce9KflWj9gq/A6MMHab4K5MjEIPSMHJTnMmNn0wdZK0=; b=gm4uxDsG6jaxwpsr3e89Ss86C4vsKWVKxWQaHt1S0EeszsfEjTRo/dHR113DPocvh0 HstGT8XPChFms7phWldd+/Dec2por9kZK84gMgpG9Tm1wD3zZH3ydaEeq2i1fKHbLQk9 BBuydz4ZYITPGzcCf4Do58VV2kkKTdzkiTiU3jyPp3IlNtpXwsJ5wHN7sU8WwkelpzQa cxUNP3FQxj32dnEHnYfGxPtzQYtD2XdoTqv3i/R9798yGaZKJThutlWXl3tG1cfmdaOT QKllf8gm0/F4m51LvJFtFDhXOw+6UPlre/7BlK5gcVvWg1ku+ch79ngF2xCMnH3FYnd7 SdjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ce9KflWj9gq/A6MMHab4K5MjEIPSMHJTnMmNn0wdZK0=; b=diSdOkb1f9zQfDadxr3JkZdyRAJpgW+P4jpx9Qyjv8TLvDk+2AwWI8ObMwawNsqVx2 eR7DtOtV7P5q37gXwWfqiNl35IX1jmTrwslncNb6Lz2TzkfwUcGKi3c4/gna6sAOpvlG KNjvghzL+UbofciCCqzF1+aOOUBs3wC4AqEGNa+Yp5SgcbGoRbAM5Tk8Y0YkncmnzLWE FOGjA3ozRJJZnlWqO1qkv7MPUxG1oxqIqowcB2bG4ZAGek3ccPQnVk02f7vkIgs4oTYr 5URQWICkRCjaXdiy2sH6aKsmAsS4wnSeEBJM4VAgqJJ68jT4IllXFR9nB98c6w3L+FQs v7DQ==
X-Gm-Message-State: APjAAAV5yaY1DdD9FKnW1a8WFgxuAEACapRD8IJngD/rG9iGnzcPTZTW po5YLH6yxVhdsa0/9tFXtcXPGrfbNQQ=
X-Google-Smtp-Source: APXvYqwel1hCWLWPHLF99z0efQscK9acodx8xjMTLqoddD862DU55uklh5mycs9AVtaqEtXUAtAwMw==
X-Received: by 2002:ac8:4292:: with SMTP id o18mr4931810qtl.336.1567006616122; Wed, 28 Aug 2019 08:36:56 -0700 (PDT)
Received: from brians-mbp-2369.lan ([]) by with ESMTPSA id y23sm1394494qki.118.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Aug 2019 08:36:55 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Brian Rosen <>
In-Reply-To: <>
Date: Wed, 28 Aug 2019 11:36:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <>
To: Eric Burger <>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <>
Subject: Re: [Rum] Codec requirements in draft-rosen-rue-01
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 Aug 2019 15:37:00 -0000

That wouldn’t be needed, right?  If rum devices implemented both H.264 and VP8, and existing devices only implemented H.264, then we have backwards compatibility.  There are some details (profile, packetization, ..)

> On Aug 28, 2019, at 11:25 AM, Eric Burger <> wrote:
> I guess the question is whether we want today’s devices to have a chance of being RUM compatible. I don’t think anyone will be surprised if a five-year-old device is history. Is it realistic for current devices to get VP8 upgrade? [Would be nice for some manufacturers or others building such devices to pipe in here.]
>> On Aug 28, 2019, at 10:38 AM, Brian Rosen <> wrote:
>> If we require OPUS and G.711 as MTI and we require both H.264 and VP8 as MTI, then we get backwards compatibility without transcoding and forwards compatibility with WebRTC.  Isn’t that what we want?
>> Brian
>>> On Aug 28, 2019, at 10:15 AM, Paul Kyzivat <> wrote:
>>> Inline...
>>> On 8/27/19 5:57 PM, Adam Roach wrote:
>>>> I certainly have thoughts. The executive summary is that I personally believe RUM should specify Opus as the one audio codec MTI, and match RFC 7742's "Non-Browser" requirements for the video codec MTI. Rationale below.
>>>> From an interop perspective, the important thing is that any given profile has (at least) one MTI video codec and (at least) one MTI audio codec. I know there is a strong desire -- one that I share -- that these endpoints can talk to/be implemented in web browsers without the need for media transcoding.
>>>> For audio: WebRTC selected G.711 and Opus as both MTI; the former because it works without transcoding to landline PSTN destinations, and the latter because it sounds much, much better. RUM could make the same decision; or it could decide to move away from a codec that is as old as I am and opt to designate Opus as the only MTI. Given that RUM inherently needs to deploy into audio/video environments, backwards compatibility with the PSTN seems to be unnecessary baggage.
>>> Please keep in mind where we are coming from. The RUM will be a new interface to the *existing* VRS infrastructure. That infrastructure currently has proprietary devices that serve the RUE function, deployed to VRS users and to Communications Assistants (CAs, Interpreters). These have G.711 MTI, and also *recommend* G.722.2.
>>> Making OPUS the only MTI audio codec would be problematic.
>>>> For video: While specifying either VP8 or H.264 would be sufficient for system interop, and for interop with compliant WebRTC endpoints, I'd really prefer not to re-live the WebRTC video codec wars. Concretely, what I would propose is that RUM indicate that the video codec requirements are defined to be identical to those defined for "WebRTC Non-Browsers" in Section 5 of RFC 7742. It should be made clear that RUM endpoints *are* *not* WebRTC Non-Browsers per se; merely that they comply with the same video codec requirements as WebRTC Non-Browsers.
>>> Continuing my comment above, existing devices have H.264 Constrained Baseline Profile, Level 1.3, packetization mode 1 as the MTI codec. Odds are many of these devices aren't capable of VP8.
>>> We can't realistically require a wholesale swap out of existing devices before the RUE defined by RUM can work. We can *discuss* whether forcing the providers to transcode is a practical way forward. I'm dubious.
>>> 	Thanks,
>>> 	Paul
>>>> /a
>>>> On 8/27/19 2:34 PM, Brian Rosen wrote:
>>>>> Well, we certainly want interoperability, and I think we can only get that with MTI codecs.
>>>>> I think we really are talking about a WebRTC-compatible endpoint, but we want interoperability with a WebRTC browser endpoint.
>>>>> Not sure how to say this.  Maybe Adam can help.
>>>>> Brian
>>>>>> On Aug 12, 2019, at 4:20 PM, Paul Kyzivat <> wrote:
>>>>>> draft-rosen-rue-01 changes the video codec requirements. It now simply references webrtc RFC7742.
>>>>>> RFC7742 distinguishes three types of endpoints: "WebRTC browser", "WebRTC non-browser", and "WebRTC-compatible endpoint". AFAIK it assumes that each end is one of these.
>>>>>> Is the expectation here that both the RUE and the provider comply with one of these? In particular, that the provider may simply be a "WebRTC-compatible endpoint? Notably:
>>>>>>  "WebRTC-compatible endpoints" are free to implement any video codecs
>>>>>>  they see fit.  This follows logically from the definition of "WebRTC-
>>>>>>  compatible endpoint".  It is, of course, advisable to implement at
>>>>>>  least one of the video codecs that is mandated for WebRTC browsers,
>>>>>>  and implementors are encouraged to do so.
>>>>>> Similarly, the audio requirements have been changed to reference webrtc RFC7874. That one doesn't have the distinction between "WebRTC browser", "WebRTC non-browser", and "WebRTC-compatible endpoint". It applies the same requirements to all. In particular, it requires OPUS support. I don't know why it doesn't make the same endpoint distinctions as for video.
>>>>>> I think simply referencing these documents isn't sufficient. Seems like we need a more nuanced specification of what is required, though we may still reference these docs with qualifications.
>>>>>>   Thanks,
>>>>>>   Paul
>> --
>> Rum mailing list
> -- 
> Rum mailing list