RFC 8865 on T.140 Real-Time Text Conversation over WebRTC Data Channels

rfc-editor@rfc-editor.org Wed, 20 January 2021 00:21 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA3F3A0B23; Tue, 19 Jan 2021 16:21:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.922
X-Spam-Level:
X-Spam-Status: No, score=-0.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jeKAO85qDf7K; Tue, 19 Jan 2021 16:21:52 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F03E23A09EF; Tue, 19 Jan 2021 16:21:45 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9A111F4076D; Tue, 19 Jan 2021 16:21:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4NjUgb24gVC4xNDAgUmVhbC1UaW1lIFRleHQgQ29udmVyc2F0aW9uIG92ZXIgV2ViUlRDIERhdGEgQ2hhbm5lbHM=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mmusic@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210120002129.9A111F4076D@rfc-editor.org>
Date: Tue, 19 Jan 2021 16:21:29 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/PELRgdQ2ZsywZm9gZ-TXtJ8JOsI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2021 00:22:01 -0000

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

        
        RFC 8865

        Title:      T.140 Real-Time Text Conversation over 
                    WebRTC Data Channels 
        Author:     C. Holmberg,
                    G. Hellström
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    christer.holmberg@ericsson.com,
                    gunnar.hellstrom@ghaccess.se
        Pages:      18
        Updates:    RFC 8373

        I-D Tag:    draft-ietf-mmusic-t140-usage-data-channel-14.txt

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

        DOI:        10.17487/RFC8865

This document specifies how a Web Real-Time Communication (WebRTC)
data channel can be used as a transport mechanism for real-time text
using the ITU-T Protocol for multimedia application text conversation
(Recommendation ITU-T T.140) and how the Session Description Protocol
(SDP) offer/answer mechanism can be used to negotiate such a data
channel, referred to as a T.140 data channel. This document updates
RFC 8373 to specify its use with WebRTC data channels.

This document is a product of the Multiparty Multimedia Session Control 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