Re: [dispatch] Request DISPATCH of RUM

Brian Rosen <> Fri, 01 February 2019 22:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 26F13130F66 for <>; Fri, 1 Feb 2019 14:10:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KJSUSDyR2cFq for <>; Fri, 1 Feb 2019 14:10:51 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::842]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 553BC130F67 for <>; Fri, 1 Feb 2019 14:10:51 -0800 (PST)
Received: by with SMTP id u47so9435609qtj.6 for <>; Fri, 01 Feb 2019 14:10:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Bb7J5jFNnqAv0QYFIkO9uS74WZg0ichpqiC3TK7vqdU=; b=TNaE+lEothjoJP75AisUuvCb0gIhRThO+0paUM/Svej8CEYnq9hnMqQSa4ioH6Hi1I S31MByt2OnftNB8yK8OIc3HhZyEntuaQEQ9kdnsv83N3pEfWSzLjxJeccf4veFt7o9EI gvvnBOoUuTGKd6LU11UtbmQuh/t+4aWoNQQJivCIVmbgxxaWrE8J9GOilwFDC9hyK3In Xcvs+eidgbuPB7kyDIKjfcEmw2rE3ZBfFUCpZMCmRNHCjSsscEhcHe4vrnI5yRPBu4TO qks/hj4BOPR2By0Hejl7ft+4Z7c7AE6nV4MOf+2jc+MYKsp9w+HMSEsjIS1T7C6JbuAi hq1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Bb7J5jFNnqAv0QYFIkO9uS74WZg0ichpqiC3TK7vqdU=; b=Mq7qMW6aNpkOOOx8k5RHEAjaaK/pZzjoLke0U0uN6C/aXUlUp3ORYI4jLvSuGfoQo/ vfOLQjpnQiVWrSicssrxgo1/6a6+g4flatgHetAAwUYPH377YAMufzfdnHsoquvlo1Qe E5recK3hiLyz93dkRJiRl6lodFlk+bMvVjH5ZXxyQTZLgV+ttVthLyQMDaFngUbC7QtU XRRHON43PxLxobe1p5SpqGiY1vDokX/LqiXXcKeckig6QT4K4o2Fn+vWl/ef7eevnk98 KGGiRd7qa//yltO1tP3gwzHrsJi1gvmSBxjMJ1WK2KtHljJXIqPdBy6uYJqe6HKzXMO1 Wrbg==
X-Gm-Message-State: AJcUukewF3EwHHRijedqzyahmlzKrRulNRpKGIr10q4rtqiW7Y+f5pYK U6Nv7bFxED5FZxzbrVAqx/esJg==
X-Google-Smtp-Source: ALg8bN7wVSaZQeWsQ+abRLP8t3Nf3yR6RnLySb5CGD72JY3p4W5c33tB398nmKwfuh7dEvxOYhwXmA==
X-Received: by 2002:ac8:7153:: with SMTP id h19mr38554461qtp.92.1549059050336; Fri, 01 Feb 2019 14:10:50 -0800 (PST)
Received: from brians-mbp.lan ( []) by with ESMTPSA id a3sm8297718qta.21.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Feb 2019 14:10:49 -0800 (PST)
From: Brian Rosen <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CFA01B90-CA07-4131-9B96-6257A7F1BCDD"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Fri, 01 Feb 2019 17:10:48 -0500
In-Reply-To: <>
Cc: Christer Holmberg <>, DISPATCH list <>
To: Richard Shockey <>
References: <> <> <> <>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <>
Subject: Re: [dispatch] Request DISPATCH of RUM
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 01 Feb 2019 22:11:00 -0000

The SIPForum did the provider profile.  That’s out of scope for this work.

I understand there is desire to spin that work, but I don’t know much about it.  This is the device side, not the provider side.


> On Feb 1, 2019, at 4:34 PM, Richard Shockey <> wrote:
> BTW if you want to revisit the entire VRS profile you are more than welcome to do so.
> — 
> Richard Shockey
> Shockey Consulting LLC
> Chairman of the Board SIP Forum
> <>
> <>
> richard<at> <>
> Skype-Linkedin-Facebook –Twitter  rshockey101
> PSTN +1 703-593-2683
> From: dispatch <> on behalf of Brian Rosen <>
> Date: Friday, February 1, 2019 at 4:23 PM
> To: Christer Holmberg <>
> Cc: DISPATCH list <>
> Subject: Re: [dispatch] Request DISPATCH of RUM
> We want to make sure the mechanisms interact reasonably.  We suspect this is mostly codec choices, etc.
> Brian
>> On Feb 1, 2019, at 4:11 PM, Christer Holmberg < <>> wrote:
>> Hi,
>> If the purpose of the WG is to define a SIP profile, I assume it does not matter if the SIP UAs are implemented using WebRTC or something else, so why does the charter need to talk about WebRTC?
>> If you want to look at some of the specific network technologies used by WebRTC, e.g., the data channel, I think should talk about that instead.
>> Regards,
>> Christer
>> From: dispatch < <>> on behalf of Brian Rosen < <>>
>> Sent: Friday, February 1, 2019 10:50:53 PM
>> To: DISPATCH list
>> Subject: [dispatch] Request DISPATCH of RUM
>> I would like dispatch to consider spinning up a mini-work group to create a sip device profile for use with Video Relay Services.  
>> The proposed charter is:
>> Relay User Machine (rum) Working Group Proposed Charter
>> ART Area
>> Many current instances of Video Relay Service (VRS), (sometimes called Video Interpretation Service.), use the Session Initiation Protocol (SIP) and other IETF multimedia protocols. VRSwhich is used bya service that deaf and hard- of- hearing persons and person with speech impairments use 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 on the PSTN to the hearing person. The hearing person can also reach D-HOH-SI individuals by in the same manner as calling any other phone number.  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.  VRS services are often government- supported.  In some countries, private companies provide the interpreters, and compete with one another.  Often these companies use proprietary implementations for user devices as a means of vendor lock in.  
>> 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.  The SIP protocol is complex enough that some form of profiling is needed to achieve interoperability between devices and providers. To ensure interoperability of the key features of this service, certain aspects (e.g., codecs, media transport, 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 negotiates.
>> 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 communicationsuch devices, including references to work beyond SIP (e.g., WebRTC and SLIM).  No protocol changes are anticipated by this work.
>> While WebRTC could be used to implement a RUM, the group’s work will focusis on the device-to-provider interface.  A WebRTC- based RUM couldwould create a SIP interface (using, e.g., SIP over WebSockets) towards the provider that conformed to the document RUMrum will produce.  Such an implementation should be possible, ideally without requiring a media gateway.
>> 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, i.e., 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 RUMrum device and are in scope for this work.  
>> Although the interface between providers also requires standardization to enable multi-provider point-to-point calls, that  interface has already been defined in a SIP Forum document and is thus out of scope for RUM.
>> _______________________________________________
>> dispatch mailing list
>> <>
>> <>
> _______________________________________________ dispatch mailing list <> <>