Skip to main content

Interoperability Profile for Relay User Equipment

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: The IESG <>,,,,,,
Subject: Protocol Action: 'Interoperability Profile for Relay User Equipment' to Proposed Standard (draft-ietf-rum-rue-11.txt)

The IESG has approved the following document:
- 'Interoperability Profile for Relay User Equipment'
  (draft-ietf-rum-rue-11.txt) as Proposed Standard

This document is the product of the Relay User Machine Working Group.

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet Draft is:

Ballot Text

Technical Summary

   Video Relay Service (VRS) is a term used to describe a method by
   which a hearing person can communicate with a deaf, hard of hearing
   or hearing impaired 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 employed 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 deaf/HoH users.  It is desirable
   that the videophones used by the deaf, hard of hearing or hearing
   impaired user conform to a standard so that any device may be used
   with any provider and that direct video calls between deaf, hard of
   hearing or hearing impaired users work.  This document describes the
   interface between a videophone and a provider

Working Group Summary

There was not a lot of energy in the group to move the work along. Notably, the representatives of VRS providers were reluctant to contribute and mostly offered objections. Reaching consensus under these conditions was challenging and often consensus was quite rough.

Document Quality

There is a partial implementation by Mitre. This is intended as a verification and test vehicle. They have committed to creating a full implementation when the document becomes an RFC.
But the most likely vendors are the VRS providers. They do what they are required to do by the FCC. It is expected that the FCC will mandate this and then they will implement it.

No particular reviews (that haven't already happened) are warranted.


Paul Kyzivat is the document shepherd.
Murray Kucherawy is the responsible Area Director.

RFC Editor Note