[secdir] [new-work] WG Review: Relay User Machine (rum)

The IESG <iesg@ietf.org> Fri, 08 March 2019 21:16 UTC

Return-Path: <new-work-bounces@ietf.org>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 567A3127988; Fri, 8 Mar 2019 13:16:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1552079815; bh=TulXgqHUov9avtA9CKLfFi6HciOhltkqeCUE1tusMpw=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=VQWOamHK5Fowxrg2qmPP+eTd7D83iAGqTlxSuKb1iytBiunuE8omfq16ENJgFAdc3 D9JgvsjhdXt+YUA59GbJukIoyPw1BHsa02OUu6T+j96v7mLPwJcgqXL8zLUNWpAcET 64U1uF7lWpW8i1UWtrarhoemrl0mHsiCteMc+EBw=
X-Mailbox-Line: From new-work-bounces@ietf.org Fri Mar 8 13:16:49 2019
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A94BD130F04; Fri, 8 Mar 2019 13:16:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1552079808; bh=TulXgqHUov9avtA9CKLfFi6HciOhltkqeCUE1tusMpw=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=kqy5RWh9epiJKaLIx632CQ5cgBgXtEceRIwXKLg+09GgFhAB5cikykQjzxF4XNlwS JRLVrLEJpSBpCjOHsJMlbz8eVSmqCax3wCxiS3FNrsmPaF/kuTBlXhY5U3l6YvL4fP raj7gOCFh4X+Hc8b7pjJ7A+f42jh3zsc0MW0uT/Q=
X-Original-To: new-work@ietf.org
Delivered-To: new-work@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0011277E7 for <new-work@ietf.org>; Fri, 8 Mar 2019 13:16:39 -0800 (PST)
MIME-Version: 1.0
From: The IESG <iesg@ietf.org>
To: <new-work@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.93.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Reply_to: <iesg@ietf.org>
Message-ID: <155207979962.3197.9894300550021556677.idtracker@ietfa.amsl.com>
Date: Fri, 08 Mar 2019 13:16:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-work/HX9GAwnwUVdA0IKrnugXjHheDJQ>
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.29
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: new-work-bounces@ietf.org
Sender: "new-work" <new-work-bounces@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/Mmu2SPqi-XDVGcAcrXkxLeHZqpI>
X-Mailman-Approved-At: Fri, 08 Mar 2019 14:00:32 -0800
Subject: [secdir] [new-work] WG Review: Relay User Machine (rum)
X-BeenThere: secdir@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Mar 2019 21:17:02 -0000

A new IETF WG has been proposed in the Applications and Real-Time Area. The
IESG has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send your
comments to the IESG mailing list (iesg@ietf.org) by 2019-03-18.

Relay User Machine (rum)
Current status: Proposed WG

  Brian Rosen <br@brianrosen.net>
  Paul Kyzivat <pkyzivat@alum.mit.edu>

Assigned Area Director:
  Adam Roach <adam@nostrum.com>

Applications and Real-Time Area Directors:
  Adam Roach <adam@nostrum.com>
  Ben Campbell <ben@nostrum.com>
  Alexey Melnikov <aamelnikov@fastmail.fm>

Mailing list:
  Address: rum@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/rum
  Archive: https://mailarchive.ietf.org/arch/browse/rum/

Group page: https://datatracker.ietf.org/group/rum/

Charter: https://datatracker.ietf.org/doc/charter-ietf-rum/

Many current instances of Video Relay Service (VRS), sometimes called Video
Interpretation Service, use the Session Initiation Protocol (SIP) and other
IETF multimedia protocols. VRS is used by deaf/hard-of-hearing persons and by
persons with speech impairments to communicate with hearing persons.  The
deaf, hard-of-hearing, or speech-impaired person (D-HOH-SI) uses a SIP-based
video phone to connect with an interpreter, and the interpreter places a
phone call to the hearing person. The hearing person can also reach D-HOH-SI
individuals in the same manner as calling any hearing user.  The D-HOH-SI
person uses sign language and possibly real-time text with the interpreter
and the interpreter uses spoken language with the hearing person, providing
on-line, real-time, two-way communication.

Having a standard interface between the end-user device and the VRS provider
allows vendors and open-source developers to build devices that work with
multiple service providers; devices can also be retained when changing
providers.  In this instance, “device” could be a purpose-built videophone or
could be downloadable software on a general purpose computing platform or
mobile phone. To ensure interoperability of the key features of this service,
certain aspects (e.g., codecs, media transport, addressing and SIP features)
must be specified as mandatory-to-implement for SIP-based VRS devices. These
specified features effectively form a profile for SIP and the media it

This working group will produce a single document: a profile of SIP and media
features for use with video relay services (which includes video, real time
text, and audio), and other similar interpretation services that require
multimedia.  It will reference the IETF’s current thinking on multimedia
communication, including references to work beyond SIP (e.g., WebRTC and
SLIM).  No protocol changes are anticipated by this work.

Often, the hearing user is on the PSTN, and RUM will include interoperability
specifications for that use, including the use of telephone numbers.  RUM
will not assume hearing users are on the PSTN.

While WebRTC could be used to implement a profile to fulfill RUM's
requirements, the group’s work will focus on the device-to-provider
interface.  The working group will consider ways for WebRTC based services to
interwork with a RUM-compliant provider, but is not required to make such
interwork possible.

RUM devices will be expected to be able to place emergency calls conforming
to the current IETF emergency call recommendations.

The scope of the work includes mechanisms to provision the user’s device with
common features such as speed dial lists, provider to contact, videomail
service interface point and similar items.  These features allow users to
more easily switch providers temporarily (a feature known as “dial around”)
or permanently, while retaining their data.

Devices used in VRS can be used to place point-to-point calls where both
communicating parties use sign language.  When used for point-to-point
calling where the participants are not served by the same VRS provider, or
when one provider provides the originating multimedia transport environment,
but another provides the interpreter (“dial-around call”), the call traverses
two providers.  Both of these uses impose additional requirements on a RUM
device and are in scope for this work.

Although the interface between providers also requires standardization to
enable multi-provider point-to-point and dial-around calls, that  interface
has already been defined in a SIP Forum document and is thus out of scope for


  Dec 2019 - Submit a profile of SIP and media features for use with video
  relay services to the IESG for publication

new-work mailing list