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

James Hamlin <james.hamlin@purple.us> Thu, 07 November 2019 17:40 UTC

Return-Path: <james.hamlin@purple.us>
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 9CE9D1208A4 for <rum@ietfa.amsl.com>; Thu, 7 Nov 2019 09:40:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 hFntSFhXZT7q for <rum@ietfa.amsl.com>; Thu, 7 Nov 2019 09:40:07 -0800 (PST)
Received: from 1pmail.ess.barracuda.com (1pmail.ess.barracuda.com [209.222.82.103]) (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 20C3C120089 for <rum@ietf.org>; Thu, 7 Nov 2019 09:40:06 -0800 (PST)
Received: from smtp.purple.us (unknown [208.17.91.144]) by mx12.us-east-2b.ess.aws.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NO); Thu, 07 Nov 2019 17:40:02 +0000
Received: from 1-WP-402-EXCH.purplenetwork.net (10.0.10.144) by 1-wp-402-exch.purplenetwork.net (10.0.10.144) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 7 Nov 2019 09:39:58 -0800
Received: from 1-WP-402-EXCH.purplenetwork.net ([fe80::b41b:40df:b152:6817]) by 1-wp-402-exch.purplenetwork.net ([fe80::b41b:40df:b152:6817%27]) with mapi id 15.00.1263.000; Thu, 7 Nov 2019 09:39:58 -0800
From: James Hamlin <james.hamlin@purple.us>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "rum@ietf.org" <rum@ietf.org>
Thread-Topic: [Rum] I-D Action: draft-ietf-rum-rue-01.txt
Thread-Index: AQHVk1XNq3ZXe2FDzkOPjnZjRliuSKd9cZIAgAKKNh0=
Date: Thu, 7 Nov 2019 17:39:58 +0000
Message-ID: <1573148398003.49735@purple.us>
References: <157290244575.13960.5728950433793071735@ietfa.amsl.com>, <57728288-27e6-4598-09a4-3bcc9b0bff04@alum.mit.edu>
In-Reply-To: <57728288-27e6-4598-09a4-3bcc9b0bff04@alum.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.0.10.15]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BESS-ID: 1573148398-893023-24127-27889-1
X-BESS-VER: 2019.1_20191106.2224
X-BESS-Apparent-Source-IP: 208.17.91.144
X-BESS-Outbound-Spam-Score: 0.00
X-BESS-Outbound-Spam-Report: Code version 3.2, rules version 3.2.2.220148 [from cloudscan10-55.us-east-2a.ess.aws.cudaops.com] Rule breakdown below pts rule name description ---- ---------------------- -------------------------------- 0.00 BSF_BESS_OUTBOUND META: BESS Outbound
X-BESS-Outbound-Spam-Status: SCORE=0.00 using global scores of KILL_LEVEL=7.0 tests=BSF_BESS_OUTBOUND
X-BESS-BRTS-Status: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/FKPfKRkJxJe7vVIQPxbUMNdwJ_Q>
Subject: Re: [Rum] I-D Action: draft-ietf-rum-rue-01.txt
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: Thu, 07 Nov 2019 17:40:11 -0000

Paul

We've discussed rtcweb-overview provides for a "WebRTC-compatible Endpoint"; the intent is to support legacy systems such as the PSTN and older VRS endpoints.

This text would clarify things:-

At the start of section 6:-

On the Relay Service Provider side of the RUM interface, there are connections to the PSTN and legacy endpoints which cannot be upgraded soon. The Relay Service Provider is regarded here as a WebRTC-compatible Endpoint as described in draft-ietf-rtcweb-overview. Relay Service Providers therefore do not have to offer, or be willing to accept all the WEBRTC codecs but will always have at least one codec in common with any RUE that is compliant with this profile.

In section 6.3 Video:-

The RUE and Relay Service Provider MUST conform to [RFC7742] with the exception that, since backwards compatibility is desirable and older devices do not support VP8, that only H.264, as specified in [RFC7742] is Mandatory to Implement by Relay Service Providers.

In section 6.4.  Audio:-

The RUE and Relay Service Provider MUST conform to [RFC7874] with the exception that, since backwards compatibility is desirable and older devices only G.711 is mandatory to implement by Relay Service Provider.

Best regards

James

________________________________________
From: Rum <rum-bounces@ietf.org> on behalf of Paul Kyzivat <pkyzivat@alum.mit.edu>
Sent: 05 November 2019 18:44
To: rum@ietf.org
Subject: Re: [Rum] I-D Action: draft-ietf-rum-rue-01.txt

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, internet-drafts@ietf.org 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2fdatatracker.ietf.org%2fdoc%2fdraft-ietf-rum-rue%2f&c=E,1,I2pLDuP9kDOqy0C6pdthtTmu_RFATqCMS2D_LN1CQtPuT_R5nJ1R1LBA2mSUavnqIsghvMURdwO20SVX6HUM7nJMmiPmxU_8Vwhd6_0QNbI5n-yKP8Z5U7v9rl0,&typo=0
>
> There are also htmlized versions available at:
> https://linkprotect.cudasvc.com/url?a=https%3a%2f%2ftools.ietf.org%2fhtml%2fdraft-ietf-rum-rue-01&c=E,1,MWR5OWQx40XIr3x539rleCUMVJqMml6UoobFNi3LqtVYvskf4qmVHelEG7DXIxYrxWKq2Y6m26xEiUE1MjQEXUXQpV8erzhIVOCdMbvXXyyFxZ4QKaEfPeiulw,,&typo=0
> https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fdatatracker.ietf.org%2fdoc%2fhtml%2fdraft-ietf-rum-rue-01&c=E,1,i5xFLAheos-mTzQGdU3JuMkX5DtrGxCWlemx7HGjphPZ37P_zsYYxsNx46meAjeouqBKqpkDDBzy-gXRZnQZVvR1YgLTcNVg_mByKniPQIiV1QF5MA,,&typo=0
>
> A diff from the previous version is available at:
> https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.ietf.org%2frfcdiff%3furl2%3ddraft-ietf-rum-rue-01&c=E,1,TEmEj1k443-Te2py0L7ec5xiK5pD7ITyazUQoeW05PZGB0vPhi90ohpiMxSiPoemnM7gM9mQ80ouGMzTTOnR_M07J5SWRbygAAnoF30JcA,,&typo=0
>
>
> 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:
> https://linkprotect.cudasvc.com/url?a=ftp%3a%2f%2fftp.ietf.org%2finternet-drafts%2f&c=E,1,F5kMy0HPxpwZGTTbkvKinQAFkSsDV0z9S1IYNgIdQMiPISfCgHuB8foYzOnXJ7dtY1kJ21GHgi4v_hFKHIHY3C8_3DxLOLQ0akYcSaJNZbw8CsQ,&typo=0
>

--
Rum mailing list
Rum@ietf.org
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.ietf.org%2fmailman%2flistinfo%2frum&c=E,1,ANxha7oZqejOC1IAQ9J9lBR5rVW3cOiTi5v5Y3XBZwV-QxAHx3Z0BNmJco8zmLV5hWyxbIu5F4ptM7kQ3E8cqrl5o7sLgrOfmJCv9Dd_&typo=0