[AVTCORE] I-D Action: draft-ietf-avtcore-multi-party-rtt-mix-09.txt

internet-drafts@ietf.org Tue, 13 October 2020 17:53 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: avt@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: avt@ietf.org
Message-ID: <160261160031.17061.16528358272381131929@ietfa.amsl.com>
Date: Tue, 13 Oct 2020 10:53:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/FjwrqI_3HBo8Qsclw153zzFGgBY>
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-multi-party-rtt-mix-09.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Core Maintenance WG of the IETF.

        Title           : RTP-mixer formatting of multi-party Real-time text
        Author          : Gunnar Hellstrom
	Filename        : draft-ietf-avtcore-multi-party-rtt-mix-09.txt
	Pages           : 37
	Date            : 2020-10-13

Abstract:
   Real-time text mixers for multi-party sessions need to identify the
   source of each transmitted group of text so that the text can be
   presented by endpoints in suitable grouping with other text from the
   same source.

   Regional regulatory requirements specify provision of real-time text
   in multi-party calls.  RFC 4103 mixer implementations can use
   traditional RTP functions for source identification, but the mixer
   source switching performance is limited when using the default
   transmission characteristics with redundancy.

   Enhancements for RFC 4103 real-time text mixing is provided in this
   document, suitable for a centralized conference model that enables
   source identification and source switching.  The intended use is for
   real-time text mixers and multi-party-aware participant endpoints.
   The specified mechanism build on the standard use of the CSRC list in
   the RTP packet for source identification.  The method makes use of
   the same "text/red" format as for two-party sessions.

   A capability exchange is specified so that it can be verified that a
   participant can handle the multi-party coded real-time text stream.
   The capability is indicated by use of a media attribute "rtt-mixer".

   The document updates RFC 4103[RFC4103]

   A specifications of how a mixer can format text for the case when the
   endpoint is not multi-party aware is also provided.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-party-rtt-mix/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-avtcore-multi-party-rtt-mix-09.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-multi-party-rtt-mix-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[AVTCORE] I-D Action: draft-ietf-avtcore-multi-pa… internet-drafts