Re: [Rum] I-D Action: draft-ietf-rum-rue-01.txt

[Eric Burger <[e-mail]>]

The Pulakka paper I referenced for Keith might be why one would transcode from G.711 to Opus. However, I would not mandate it.
https://www.isca-speech.org/archive/archive_papers/interspeech_2006/i06_1245.pdf <https://www.isca-speech.org/archive/archive_papers/interspeech_2006/i06_1245.pdf>


> On Nov 5, 2019, at 1:44 PM, Paul Kyzivat <[e-mail]> wrote:
> 
> The new text in section 6 on Mandatory to Implement is confusing. A G.711 call originating in the PSTN is never going to be *originated* by a RUE.
> 
> Calls *originated* by a RUE should *offer* all MTI codecs including OPUS. If the call terminates in the PSTN then OPUS won't be selected in the answer.
> 
> OTOH, a VRS provider when relaying a call to a RUE that originated in the PSTN may offer G.711 and not OPUS. In normal use cases such a call will be a VRS call with an interpreter. I *think* in that case audio gets relayed to the RUE, in which case continuing G.711 makes sense. But does audio from interpreter also go to the RUE? If so, transcoding up to OPUS and then mixing in the interpreter might make sense.
> 
> So this is heavily entangled in the need for different requirements for the RUE and the VRS Provider.
> 
> 	Thanks,
> 	Paul
> 
> On 11/4/19 4:20 PM, [e-mail] wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the Relay User Machine WG of the IETF.
>>         Title           : Interoperability Profile for Relay User Equipment
>>         Author          : Brian Rosen
>> 	Filename        : draft-ietf-rum-rue-01.txt
>> 	Pages           : 28
>> 	Date            : 2019-11-04
>> Abstract:
>>    Video Relay Service (VRS) is a term used to describe a method by
>>    which a hearing persons can communicate with deaf/Hard of Hearing
>>    user using an interpreter ("Communications Assistant") connected via
>>    a videophone to the deaf/HoH user and an audio telephone call to the
>>    hearing user.  The CA interprets using sign language on the
>>    videophone link and voice on the telephone link.  Often the
>>    interpreters may be supplied by a company or agency termed a
>>    "provider" in this document.  The provider also provides a video
>>    service that allows users to connect video devices to their service,
>>    and subsequently to CAs and other dead/HoH users.  It is desirable
>>    that the videophones used by the deaf/HoH/H-I user conform to a
>>    standard so that any device may be used with any provider and that
>>    video calls direct between deaf/HoH users work.  This document
>>    describes the interface between a videophone and a provider.
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-rum-rue/
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-rum-rue-01
>> https://datatracker.ietf.org/doc/html/draft-ietf-rum-rue-01
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-rum-rue-01
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
> 
> --
> Rum mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rum