Re: [AVTCORE] New Version Notification for draft-ietf-avtcore-multi-party-rtt-mix-09.txt

[Gunnar Hellström <[e-mail]>]

Version --09 of draft-ietf-avtcore-multi-party-rtt-mix has been submitted.

It is intended to fulfill all comments by Paul, one earlier by James 
Hamlin, and a number of editorials.

Regards

Gunnar

Den 2020-10-13 kl. 19:53, skrev [e-mail]:
> A new version of I-D, draft-ietf-avtcore-multi-party-rtt-mix-09.txt
> has been successfully submitted by Gunnar Hellstrom and posted to the
> IETF repository.
>
> Name:		draft-ietf-avtcore-multi-party-rtt-mix
> Revision:	09
> Title:		RTP-mixer formatting of multi-party Real-time text
> Document date:	2020-10-13
> Group:		avtcore
> Pages:		37
> URL:            https://www.ietf.org/archive/id/draft-ietf-avtcore-multi-party-rtt-mix-09.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-party-rtt-mix/
> Html:           https://www.ietf.org/archive/id/draft-ietf-avtcore-multi-party-rtt-mix-09.html
> Htmlized:       https://tools.ietf.org/html/draft-ietf-avtcore-multi-party-rtt-mix-09
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-multi-party-rtt-mix-09
>
> 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.
>
>                                                                                    
>
>
> 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.
>
> The IETF Secretariat
>
>
-- 
Gunnar Hellström
GHAccess
[e-mail]