[Rum] RFC 9248 on Interoperability Profile for Relay User Equipment

A new Request for Comments is now available in online RFC libraries.

        RFC 9248

        Title:      Interoperability Profile for Relay User Equipment 
        Author:     B. Rosen
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2022
        Mailbox:    br@brianrosen.net
        Pages:      36
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rum-rue-11.txt

        URL:        https://www.rfc-editor.org/info/rfc9248

        DOI:        10.17487/RFC9248

Video Relay Service (VRS) is a term used to describe a method by
which a hearing person can communicate with a sign language speaker
who is deaf, deafblind, or hard of hearing (HoH) or has a speech
disability using an interpreter (i.e., a Communications Assistant
(CA)) connected via a videophone to the sign language speaker 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 sign language speakers. It
is desirable that the videophones used by the sign language speaker
conform to a standard so that any device may be used with any
provider and that direct video calls between sign language speakers
work.  This document describes the interface between a videophone and
a provider.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC