Re: [Rum] [EXT] Re: Real-time text in WebRTC is discussed in mmusic - a topic closely telated to rum

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 29 August 2019 19:02 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 035C1120BB4 for <rum@ietfa.amsl.com>; Thu, 29 Aug 2019 12:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 CGiMjFTjrV1g for <rum@ietfa.amsl.com>; Thu, 29 Aug 2019 12:02:09 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (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 D3C91120BC0 for <rum@ietf.org>; Thu, 29 Aug 2019 12:02:08 -0700 (PDT)
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x7TJ25O8005924 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 29 Aug 2019 15:02:06 -0400
To: Brian Rosen <br@brianrosen.net>
Cc: Jim Malloy <jmalloy@mitre.org>, "rum@ietf.org" <rum@ietf.org>
References: <9a14addd-9a1c-6130-3880-a814be717323@omnitor.se> <D375F138-E997-4436-9A90-A5583CD0820B@brianrosen.net> <f476c7d1-1d99-17a9-bdb4-716eb5807160@omnitor.se> <59F6B4E5-16DF-42EB-A654-1749BC9487B5@brianrosen.net> <b4a1f825-cc00-66cf-44b7-d7aa2bcf2a49@omnitor.se> <25517_1567094729_5D67F7C4_25517_54_4_48c0bc62-0f75-4f83-6d9c-f763982dd000@alum.mit.edu> <BL0PR0901MB2386827A6082367FB85CF641B9A20@BL0PR0901MB2386.namprd09.prod.outlook.com> <272ED564-10A7-40C9-90BC-587A81C6B68C@brianrosen.net> <eb60bd6c-dd2e-5a12-6aef-1182b85dad2c@alum.mit.edu> <B3B17AF3-0549-446D-8D53-A4CC2D94212C@brianrosen.net>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <c943b2a0-699c-0cfa-0609-d649369f00e1@alum.mit.edu>
Date: Thu, 29 Aug 2019 15:02:05 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <B3B17AF3-0549-446D-8D53-A4CC2D94212C@brianrosen.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/1JojOtitB-FlcmCHQd9LMl4PWM4>
Subject: Re: [Rum] [EXT] Re: Real-time text in WebRTC is discussed in mmusic - a topic closely telated to rum
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, 29 Aug 2019 19:02:11 -0000

On 8/29/19 2:12 PM, Brian Rosen wrote:
> Inline
> 
>> On Aug 29, 2019, at 2:06 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>> On 8/29/19 1:17 PM, Brian Rosen wrote:
>>> I think we want a rum device to be able to be a good conference participant, but like nearly all conference participants, they only see a 2 party call and the bridge does the magic.
>>> I don’t think we need to require anything else.  I think we want a bridge to be able to host a rum-compliant endpoint.
>>
>> I agree conceptually. But we need to recognize that we are out ahead of VRS. Near term there is no way to get an audio/video/RTT bridge into a call with a VRS user. Because the bridge is not in the VRS iTRS it will only be able to get connected as an audio call with and interpreter
> Both the user and the VRS CA become members of the conference, and they arrange for the user to see the CA in the “big window”.  We did this in the IVC work although the FCC provided the interpreters instead of a VRS service.  The bridge they used had a few issues but mostly it worked.

Is this deployed and in use with actual providers on real VRS calls?

>> The first form of conference is likely to be for emergency calls. But there isn't yet a specification of how to connect VRS to ng911 to get an audio/video/RTT emergency call.
> That is incorrect.  It’s completely specified in NENA-STA-010

I haven't heard anything about this when working with providers on the 
VRS provider profile. But it doesn't show up on an interface between 
providers, so I guess there hasn't been any need for it to come up.

But because this is limited to a private interface between the providers 
and NENA it isn't applicable to any other cases.

>> The other possibility is via Direct Video Calling using the VATRP system from Mitre. I guess in theory that is possible now. But it will currently have VRS users that use VRS Provider proprietary devices. Anything to support conferencing that requires extra signaling won't work until VRS users can actually use RUM-compliant RUEs. But that could work with vanilla RTT as long as the DVC device sets up the conferencing.
> I still don’t think that surfaces any additional requirements for the rum-compatible device.

As long as no extra signaling is required. For instance, multiple RTT 
data channels signaled in SDP.

	Thanks,
	Paul