[rfc-dist] RFC 9248 on Interoperability Profile for Relay User Equipment
rfc-editor@rfc-editor.org Thu, 09 June 2022 18:08 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A7FD2C15D899; Thu, 9 Jun 2022 11:08:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1654798123; bh=jTvhI5TcCCXdtbFLGqMFdYTO4soF9BX6yv3z0NuxssA=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=RCaOzh+e43IA4QQ5+otpBdEX54oh8VseXa0RA8BFc4cOcYcD4zMSjYgOxhrkmCFiF lOQAhskHP/dwWIheB1Dys6JdQ2bhsgm0v4zW1+7dlFLMRfDL3agbsf06Wj+IwzzrBr jfbi2+cPXeqxtD4v52Ok6N+NpfHe1MAgCq1z3RnY=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Thu Jun 9 11:08:43 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E62EC157B4C; Thu, 9 Jun 2022 11:08:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1654798123; bh=jTvhI5TcCCXdtbFLGqMFdYTO4soF9BX6yv3z0NuxssA=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=RCaOzh+e43IA4QQ5+otpBdEX54oh8VseXa0RA8BFc4cOcYcD4zMSjYgOxhrkmCFiF lOQAhskHP/dwWIheB1Dys6JdQ2bhsgm0v4zW1+7dlFLMRfDL3agbsf06Wj+IwzzrBr jfbi2+cPXeqxtD4v52Ok6N+NpfHe1MAgCq1z3RnY=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F99EC157903; Thu, 9 Jun 2022 11:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.654
X-Spam-Level:
X-Spam-Status: No, score=-1.654 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wR46C18G2CS7; Thu, 9 Jun 2022 11:08:37 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9857C14CF0E; Thu, 9 Jun 2022 11:08:37 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 8886A4C1CE; Thu, 9 Jun 2022 11:08:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rum@ietf.org
Message-Id: <20220609180837.8886A4C1CE@rfcpa.amsl.com>
Date: Thu, 09 Jun 2022 11:08:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/mEvByzUAqnig_OWvBpxfNAZwfws>
Subject: [rfc-dist] RFC 9248 on Interoperability Profile for Relay User Equipment
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
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 _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org