Re: [Rum] Distinguishing RUE and Provider requirements

Keith Drage <drageke@ntlworld.com> Tue, 05 November 2019 09:02 UTC

Return-Path: <drageke@ntlworld.com>
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 6C634120811 for <rum@ietfa.amsl.com>; Tue, 5 Nov 2019 01:02:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.849
X-Spam-Level:
X-Spam-Status: No, score=-0.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ntlworld.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 xCLSONsBXJo5 for <rum@ietfa.amsl.com>; Tue, 5 Nov 2019 01:02:00 -0800 (PST)
Received: from know-smtprelay-omc-9.server.virginmedia.net (know-smtprelay-omc-9.server.virginmedia.net [80.0.253.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D367120810 for <rum@ietf.org>; Tue, 5 Nov 2019 01:01:59 -0800 (PST)
Received: from [172.17.163.173] ([88.211.126.138]) by cmsmtp with ESMTPA id RuikijOXAVaV8RuiriNJDz; Tue, 05 Nov 2019 09:01:58 +0000
X-Originating-IP: [88.211.126.138]
X-Authenticated-User: drageke@ntlworld.com
X-Spam: 0
X-Authority: v=2.3 cv=PcnReBpd c=1 sm=1 tr=0 a=A23Of5e5ItRGPqVSphLRgg==:117 a=A23Of5e5ItRGPqVSphLRgg==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=r77TgQKjGQsHNAKrUKIA:9 a=HLLxP2VMAAAA:8 a=48vgC7mUAAAA:8 a=XOxgxf62AAAA:8 a=Y3tLPBFLhisjCoxZuhgA:9 a=TE5GW_2XkNF8Qr3h:21 a=ZLMWGgoe2RhcuM1r:21 a=QEXdDO2ut3YA:10 a=bfLuiRfvAAAA:8 a=3IUjVuUGSCqQ2_TVboYA:9 a=20XQwe6Uspf8kgHe:21 a=pzS6BCUO6nmqR8Ms:21 a=zePhiZYgjdljQ8yS:21 a=_W_S_7VecoQA:10 a=5oret6oapBRfLy7jekVI:22 a=w1C3t2QeGrPiZgrLijVG:22 a=gu-GzIYwBIvN1fC6SyRQ:22 a=u7KogQI6p9ntt2sFUKYF:22
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1572944518; bh=au8Ztpgkwc1nQ6pNJKh84aQmHMCre5Vu4aYyMBO8iHc=; h=Subject:To:References:From:Date:In-Reply-To; b=UKp73q8b7X4RowXdvzt6VQKdcQQbNYh5jzoMhyQbrKTZjRrj3b93NevZnhrQAkEmd UlXX0Z1lUOOlOIsW1ULpkADj2MgdQ6awBXktiVZK8b8XA55376aD7RIspXsabxxizB b3Ff8jJpzFWJgWvzPDEC4ppY5BMMaRIVINQ7I2oFd511y0IjH2eigVVCbaVN0jA4B0 wY9ZN4IJ01aXfXYdKrlBqajXgVFssji+toGx5Q0wb+LKsnU1T5ampFkwQrVDxJVHh3 2b5PliRtZ/wPqlRQRJt4V6fUESYw4J/HdCpm3D5Y1JdufeJfyj+BqZ9nH032ox3h+T S7nenLR+dVvIg==
To: rum@ietf.org
References: <a3d82911-8d07-16a3-780b-0592e48e37bd@alum.mit.edu> <ab68a7fb-7196-4374-7cd4-baf9a03cf6ff@alum.mit.edu> <1572872182151.78082@purple.us> <9717D87D-A48F-47C3-AD75-5908BAF7A649@brianrosen.net> <47E7BD6C-228D-450F-9ADE-9C0D7B2277DB@standardstrack.com>
From: Keith Drage <drageke@ntlworld.com>
Message-ID: <4d6550eb-e9b4-2ef7-e784-b561c6b5e7e5@ntlworld.com>
Date: Mon, 4 Nov 2019 18:38:02 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1
MIME-Version: 1.0
In-Reply-To: <47E7BD6C-228D-450F-9ADE-9C0D7B2277DB@standardstrack.com>
Content-Type: multipart/alternative; boundary="------------F19B9C8F6E97FD83CC4BC869"
Content-Language: en-GB
X-CMAE-Envelope: MS4wfHFOyH5dK7NJFx7ABDcOlTxH8j+H+XtoYllK+c2NFXMrKVso+fRkKhs+Bjo7bs4wZPzI8AgP8qhSOgbLll+w5v/CHFTlxT1QrRnG2bF5mRmQCAOMwEAU f6sTuCrm7GoAch7HFvaEvlhIFJwbRgDTIv0IN/9tQMJJQKpeumdce5hS
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/0r9ySDlfGHk_R0V9DFnmvKokRuQ>
Subject: Re: [Rum] Distinguishing RUE and Provider requirements
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: Tue, 05 Nov 2019 09:02:04 -0000

Out of interest, do you have any reference to research papers that have 
evaluated different codecs for use by the hard of hearing, and in 
particular that justify the statement "Opus is infinitely better for 
people with partial hearing loss than G.711".


Keith

On 04/11/2019 15:39, Eric Burger wrote:
> The point is that if we say it’s OK not to implement Opus, it means we 
> will still be using G.711 in 2120, long after the last 3,000 Hz toll 
> facility has crumbled into dust.
>
> By saying Opus is Mandatory to Implement, it means you can feel free 
> to use G.711 if that’s what is offered, but when you look in the other 
> direction you are able to accept a more modern codec. Also, Opus is 
> infinitely better for people with partial hearing loss than G.711 - it 
> can be the difference between being able to still use audio, being 
> able to use just a CTS service, or if needed a full VRS service. These 
> are the kinds of things we think about in the IETF to support legacy 
> networks while creating useful services that are not simply replicas 
> of legacy services.
>
>> On Nov 4, 2019, at 10:33 AM, Brian Rosen <br@brianrosen.net 
>> <mailto:br@brianrosen.net>> wrote:
>>
>> Mandatory to Implement doesn’t mean mandatory to use.  In the example 
>> of an incoming call from the PSTN, offering G.711 only is 
>> appropriate, and transcoding would not be advisable.
>>
>> The IETF folk understand MTI, but perhaps some explanatory text would 
>> be helpful in the document.
>>
>> Brian
>>
>>> On Nov 4, 2019, at 7:56 AM, James Hamlin <james.hamlin@purple.us 
>>> <mailto:james.hamlin@purple.us>> wrote:
>>>
>>> Paul
>>>
>>> In the draft-ietf-rum-rue-00, there's an exemption from VP8 support 
>>> for providers but no exemption from Opus support. The implication is 
>>> that, in a call from the PSTN using Voice Carry Over, the provider 
>>> must offer OPUS even though the audio content is constrained to 
>>> 8bit*8kHz PCM over the PSTN. I don't recall seeing any argument for 
>>> requiring transcoding in this case; there would be no benefit in 
>>> audio quality.
>>>
>>> Best regards
>>>
>>> James
>>>
>>> ________________________________________
>>> From: Rum <rum-bounces@ietf.org <mailto:rum-bounces@ietf.org>> on 
>>> behalf of Paul Kyzivat <pkyzivat@alum.mit.edu 
>>> <mailto:pkyzivat@alum.mit.edu>>
>>> Sent: 01 October 2019 20:15
>>> To:rum@ietf.org <mailto:rum@ietf.org>
>>> Subject: [Rum] Distinguishing RUE and Provider requirements
>>>
>>> In the discussion thread that followed the attached message it started
>>> to become apparent that there is a need to distinguish the requirements,
>>> and/or requirement strength, that apply to the RUE itself from those
>>> that apply when a RUE connects to a VRS Provider.
>>>
>>> Now that we have a wg draft to work from, I would like to see people
>>> step forward and make proposal(s) for what those differences should be.
>>>
>>> While the prior discussion focused on codecs, please also consider what
>>> else might need to differ.
>>>
>>>        Thanks,
>>>        Paul
>>>
>>> -------- Forwarded Message --------
>>> Subject: [Rum] Codec requirements in draft-rosen-rue-01
>>> Resent-From: pkyzivat@alum.mit.edu <mailto:pkyzivat@alum.mit.edu>
>>> Date: Mon, 12 Aug 2019 16:20:51 -0400
>>> From: Paul Kyzivat <pkyzivat@alum.mit.edu 
>>> <mailto:pkyzivat@alum.mit.edu>>
>>> To: rum@ietf.org <mailto:rum@ietf.org>
>>>
>>> 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 <mailto:Rum@ietf.org>
>>> https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.ietf.org%2fmailman%2flistinfo%2frum&c=E,1,Fpj3uNl4KHZVkbPWDbLGqfVwMGBdbeBLTsOB6QL2I3YozMnj25zcbabu7vIDBK1XllKKO2g7RstAehUCAqLal9VAcn2JjWNhbLeuauSs&typo=0
>>>
>>> --
>>> Rum mailing list
>>> Rum@ietf.org <mailto:Rum@ietf.org>
>>> https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.ietf.org%2fmailman%2flistinfo%2frum&c=E,1,G7A8JW3tfx9hiDhscPDTeHCoLWUSZAbId59jwHnCzDyqC39OUhM8kWYkfV9kiAEQFFRR9WYYMFy1o70xg8b-0emBXUamnQT4emSupy2-U8Yb5E-WvU4iSpdSVqQ,&typo=0
>>>
>>> --
>>> Rum mailing list
>>> Rum@ietf.org <mailto:Rum@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/rum
>>
>> -- 
>> Rum mailing list
>> Rum@ietf.org <mailto:Rum@ietf.org>
>> https://www.ietf.org/mailman/listinfo/rum
>
>