RFC 9071 on RTP-Mixer Formatting of Multiparty Real-Time Text

rfc-editor@rfc-editor.org Tue, 06 July 2021 23:47 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 E0A793A010D; Tue, 6 Jul 2021 16:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.902
X-Spam-Level:
X-Spam-Status: No, score=-0.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, 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 94ChlvcACsf7; Tue, 6 Jul 2021 16:46:55 -0700 (PDT)
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 C188F3A00E3; Tue, 6 Jul 2021 16:46:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C0A2BF40722; Tue, 6 Jul 2021 16:46:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkwNzEgb24gUlRQLU1peGVyIEZvcm1hdHRpbmcgb2YgTXVsdGlwYXJ0eSBSZWFsLVRpbWUgVGV4dA==?=
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, avt@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210706234626.C0A2BF40722@rfc-editor.org>
Date: Tue, 6 Jul 2021 16:46:26 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/MFSNW7YVpjPgibAcnHlRHnX47UE>
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: Tue, 06 Jul 2021 23:47:01 -0000

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

        
        RFC 9071

        Title:      RTP-Mixer Formatting of Multiparty Real-Time 
                    Text 
        Author:     G. Hellström
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2021
        Mailbox:    gunnar.hellstrom@ghaccess.se
        Pages:      35
        Updates:    RFC 4103

        I-D Tag:    draft-ietf-avtcore-multi-party-rtt-mix-20.txt

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

        DOI:        10.17487/RFC9071

This document provides enhancements of real-time text (as specified
in RFC 4103) suitable for mixing in a centralized conference model,
enabling source identification and rapidly interleaved transmission
of text from different sources. The intended use is for real-time
text mixers and participant endpoints capable of providing an
efficient presentation or other treatment of a multiparty real-time
text session. The specified mechanism builds on the standard use of
the Contributing Source (CSRC) list in the Real-time Transport
Protocol (RTP) packet for source identification. The method makes use
of the same "text/t140" and "text/red" formats as for two-party
sessions. 

Solutions using multiple RTP streams in the same RTP session are
briefly mentioned, as they could have some benefits over the
RTP-mixer model. The RTP-mixer model was selected to be used for the
fully specified solution in this document because it can be applied
to a wide range of existing RTP implementations. 

A capability exchange is specified so that it can be verified that a
mixer and a participant can handle the multiparty-coded real-time
text stream using the RTP-mixer method. The capability is indicated
by the use of a Session Description Protocol (SDP) (RFC 8866) media
attribute, "rtt-mixer". 

This document updates RFC 4103 ("RTP Payload for Text Conversation").


A specification for how a mixer can format text for the case when the
endpoint is not multiparty aware is also provided.

This document is a product of the Audio/Video Transport Core Maintenance 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