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

Brian Rosen <br@brianrosen.net> Wed, 04 September 2019 14:37 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B2B120120 for <rum@ietfa.amsl.com>; Wed, 4 Sep 2019 07:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
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 uCFw3-HNlLdO for <rum@ietfa.amsl.com>; Wed, 4 Sep 2019 07:37:47 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 BA7DD1201EA for <rum@ietf.org>; Wed, 4 Sep 2019 07:37:46 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id r15so18973403qtn.12 for <rum@ietf.org>; Wed, 04 Sep 2019 07:37:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=bO0SOYO+3foG2EJcPrWSqkaGbPQldI+0bUnW3WvyqbA=; b=Rp1N2m4DWRupcaiMi3I7SSj/QN7fGnttpDbUriT9OnqgUZ/9P43iRoaW1VLDzZLeRR uWVd6C6FNI25M6PoqWK/Bq1fuXBEC+EqlWYk/+P9XdPOowjAUWjS4kDXZHx22uLuQKc8 6e+ZG0fP12HfET7cwh0xSVFvqogbEvu3vxXGOniL7tFQ4mn+zJV7DrvX+eEytOshsM0X m8YSIYdEUI8UCc8C0KapcQHqaZPPw7Ab8+gp4Jdj5Dz2kU/ePDEKnyAQTY1PSf0ZL+sK U2lMKbpqP4ipi81e2k1JtE7+SltKAW7NzyU1finsVrrbrI28bGMASfqqdULlxSIl/bO/ 6tIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=bO0SOYO+3foG2EJcPrWSqkaGbPQldI+0bUnW3WvyqbA=; b=hCnQhf/ROZ+L5udg46oAXSwJ/0P/pV1Ep1aClFPZYxQF66+vjnnieLnPIJndsgxGmS EWy5HPBS0teTE8utJ5Dl1bUGY2ajJ7v5AbOsvfBkdPBZlBE55vuUQCntmvdWwv2zHRpH RMY/6OhUBvG/cCFUThJFR98s/npoOOAWrQu2xuZyMr1Wj2ZfPxApErAC/oT+HRcqqWDE G1ctgXDfK3gpZ90aTbbQe1juH6dGURUcpnujlZf+hcTRyfcHTcoT3KiHHLpdFiyH+I6V IDtq4gc1vdfeaiQ9chiGfmFm0EcHK9ttt6e+RpZfxRlMu+b8okBx02r7EAjyLgmWbJnS H1tw==
X-Gm-Message-State: APjAAAWEnamQDDKbmgaXuJr+i2k/5zhBX1zp0ibT5fBN11RslK+yYtFi iWH26AtkHD0erfXJwXsspDGbcA==
X-Google-Smtp-Source: APXvYqw6vZQboAbFLOGeTeiSxJIl8hXq8slK3uEB5A/n7lZl6Ec2JPdZE+31HV/AfpsnSL6XfM8Z5A==
X-Received: by 2002:a0c:cdcb:: with SMTP id a11mr6406610qvn.194.1567607865633; Wed, 04 Sep 2019 07:37:45 -0700 (PDT)
Received: from brians-mbp-2388.lan ([24.154.122.195]) by smtp.gmail.com with ESMTPSA id v13sm9840688qkj.109.2019.09.04.07.37.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Sep 2019 07:37:45 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <D7293188-DC0C-40A8-9514-308566342170@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_83789B43-4F84-4B95-A06F-AE5D4C142D9F"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 4 Sep 2019 10:37:43 -0400
In-Reply-To: <62dcb70c-dbb9-63d9-0470-3149fc67bca3@omnitor.se>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, rum@ietf.org
To: =?utf-8?Q?Gunnar_Hellstr=C3=B6m?= <gunnar.hellstrom@omnitor.se>
References: <8FB5F5A0-E3FE-40F8-A6D0-35D9002C6770@brianrosen.net> <85828597-D024-4E7E-8876-F1C4753E6B7D@edvina.net> <64B406DC-4171-41EB-9171-A2AF7B78B409@brianrosen.net> <a3d82911-8d07-16a3-780b-0592e48e37bd@alum.mit.edu> <69F15B2A-0158-4D23-B090-642497E3BDC7@brianrosen.net> <fa8e7a65-d818-58eb-a432-f8a57ed6af95@nostrum.com> <3fdefa0c-3a64-3445-8ceb-d293fe4b4831@alum.mit.edu> <60DFA478-5042-41FD-87CD-DD2154D6B1E6@brianrosen.net> <C4670F1F-4AEC-45BE-9898-06FF2E28A6A9@standardstrack.com> <1fed09ae-8a03-2d82-3784-c4b47095cff0@alum.mit.edu> <1567413580412.20641@purple.us> <53694d4e-5d50-6848-d631-7367dd407793@alum.mit.edu> <4870F224-EB7F-4E58-99AD-19D5449E745F@brianrosen.net> <62dcb70c-dbb9-63d9-0470-3149fc67bca3@omnitor.se>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/XDoV3Y_EILN068EIm1Fk7w9S2TQ>
Subject: Re: [Rum] Codec requirements in draft-rosen-rue-01
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Sep 2019 14:37:54 -0000

Yes, for sure T.140 (RFC4103).
The providers have SBCs that anchor media, so they can handle security on one side but not the other.  That’s not a great answer, but it’s an answer.  Transcoding video is not reasonable.

Brian

> On Sep 4, 2019, at 10:35 AM, Gunnar Hellström <gunnar.hellstrom@omnitor.se> wrote:
> 
> 
> Den 2019-09-04 kl. 15:54, skrev Brian Rosen:
>> I think our consensus is MTI:
>> Audio: G.711 and Opus
>> Video: H.264
> 
>  Real-time text: T.140        (I think you said it is mandatory for clients, and optional for services.)
> 
> 
> All these need then transport and security details specified to assure interop with RUM.
> 
> How can you hope for backward compatibility with legacy devices when it is said in RUM that the security requirements must be met?
> 
> Regards
> 
> Gunnar
> 
>> 
>> We need to get into the details of H.264 to maintain compatibility with the WebRTC specs and as much backwards compatibility as possible.
>> 
>> Anyone object?
>> 
>> 
>> 
>>> On Sep 3, 2019, at 10:48 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>> 
>>> On 9/2/19 4:39 AM, James Hamlin wrote:
>>>> Just to add: the VRS industry supports a variety of endpoints, many of which are hardware based and not built by VRS providers themselves. H.264 and G..711 therefore need to be in the MTI list.
>>>> I believe the FCC order related to compensation by compliant providers not that every call had to come from a compliant endpoint.
>>> Sorry if I got that wrong. I wrote that from memory and perhaps my memory is faulty.
>>> 
>>> 	Thanks,
>>> 	Paul
>>> 
>>>> Best Regards
>>>> James
>>>> ________________________________________
>>>> From: Rum <rum-bounces@ietf.org> on behalf of Paul Kyzivat <pkyzivat@alum..mit.edu>
>>>> Sent: 28 August 2019 16:48
>>>> To: rum@ietf.org
>>>> Subject: Re: [Rum] Codec requirements in draft-rosen-rue-01
>>>> On 8/28/19 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.]
>>>> Lets be clear about what we mean by "RUM compatible".
>>>> When Henning and I were working on this with the providers in 2014 and
>>>> 2015 there was an expectation that the providers would be required to
>>>> support the defined RUE devices, but they would also be permitted to
>>>> support their existing proprietary devices. The RUE devices could have
>>>> requirements that their existing devices don't meet. But calls between
>>>> the two were expected to work.
>>>> There was great consternation when subsequently the FCC issued a
>>>> proposed order that said only VRS calls involving RUE-compatible devices
>>>> would be compensated. (But that was in 2015. I presume it has not happened.)
>>>> If there is an intent to exclude non-RUM-compliant devices from use in
>>>> VRS calls then there needs to be a migration plan to get from here to there.
>>>>         Thanks,
>>>>         Paul
>>>>>> On Aug 28, 2019, at 10:38 AM, Brian Rosen <br@brianrosen.net> 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 <pkyzivat@alum.mit.edu> 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 <pkyzivat@alum.mit.edu> 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@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/rum
>>>>> 
>>>> --
>>>> Rum mailing list
>>>> Rum@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rum
>>> -- 
>>> Rum mailing list
>>> Rum@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rum
> 
> -- 
> -----------------------------------------
> Gunnar Hellström
> Omnitor
> gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
> +46 708 204 288