[AVTCORE] New version available of draft-hellstrom-avtcore-multi-party-rtt-solutions-01.txt

Gunnar Hellström <gunnar.hellstrom@ghaccess.se> Mon, 15 June 2020 15:45 UTC

Return-Path: <gunnar.hellstrom@ghaccess.se>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 17E093A0E7A for <avt@ietfa.amsl.com>; Mon, 15 Jun 2020 08:45:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=egensajt.se
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id uOmSR4dboViG for <avt@ietfa.amsl.com>; Mon, 15 Jun 2020 08:45:08 -0700 (PDT)
Received: from smtp.egensajt.se (smtp.egensajt.se []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2AF53A0E74 for <avtcore@ietf.org>; Mon, 15 Jun 2020 08:45:06 -0700 (PDT)
Received: from [] (h83-209-156-116.cust.a3fiber.se []) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: gunnar.hellstrom@ghaccess.se) by smtp.egensajt.se (Postfix) with ESMTPSA id D779D201CA for <avtcore@ietf.org>; Mon, 15 Jun 2020 17:45:03 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=egensajt.se; s=dkim; t=1592235903; bh=I7T33DIs71lykypF9FQ4hUrAVP4eafTTAvF/dCMnres=; h=Subject:To:References:From:Date:In-Reply-To:From; b=SvD2rtGJiCApIqmIizjir+ifsQp7xgLpCuxh0Q0e1M5wSy60ubEBssSkByQztipa4 tYnc1xImS9q49EZSLKjHzELOjIjvLzp9/jW9CcsgpDD7zT0WlexMO5J2turfaaK5WV yMm6o385EBxdYMkxVasUhsOi6WpE8fyx8mNJm3js=
To: "avtcore@ietf.org" <avtcore@ietf.org>
References: <159223403453.14558.7371906162890184086@ietfa.amsl.com>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@ghaccess.se>
Message-ID: <cc37cc8d-8f0b-1c05-032d-4501923b7d10@ghaccess.se>
Date: Mon, 15 Jun 2020 17:44:59 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <159223403453.14558.7371906162890184086@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------FBF729F60003E28B9954B0D5"
Content-Language: sv
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/EmKQ_girmSJqsT5-PN7kaphZFLY>
Subject: [AVTCORE] New version available of draft-hellstrom-avtcore-multi-party-rtt-solutions-01.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2020 15:45:12 -0000

A new version of the overview of solutions for multi-party real-time 
text is available in draft-hellstrom-avtcore-multi-party-rtt-solutions-01.

This version is mainly done for checking that we are on the right track 
with the RTP-mixer based solution, specified in 

There are four alternatives in the new solutions draft which compete for 
being the favourite to be selected and thoroughly specified in the -mix 

They are:  RTP Mixer with multiple primary data in each packet
                  and individual sequence numbers . . . . . . . . . .  11  RTP Mixer with multiple primary data in each
                  packet  . . . . . . . . . . . . . . . . . . . . . .  12  RTP Mixer with RFC 5109 FEC and RFC 2198 redundancy  RTP Mixer with RFC 5109 FEC and RFC 2198 redundancy
                  and separate sequence number in the packets . . . .  15

Currently the -mix draft is based on section

Each of these four solutions has its own pros and cons.

Thus: has very good switching performance but cannot tell which source 
lost text if loss appears. Has same good switching performance and can tell which source 
lost text. Has better chance to recover text in bursty loss conditions, has 
lower but sufficient switching performance and cannot tell which source 
had loss. Is similar to but can tell which source lost text, but 
is less based on existing standards than

There are other comparison metrix in the draft. Are we on the right way 
to continue with



Den 2020-06-15 kl. 17:13, skrev internet-drafts@ietf.org:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>          Title           : Real-time text solutions for multi-party sessions
>          Author          : Gunnar Hellstrom
> 	Filename        : draft-hellstrom-avtcore-multi-party-rtt-solutions-01.txt
> 	Pages           : 40
> 	Date            : 2020-06-15
> Abstract:
>     This document specifies methods for Real-Time Text (RTT) media
>     handling in multi-party calls.  The main transport is to carry Real-
>     Time text by the RTP protocol in a time-sampled mode according to RFC
>     4103 [RFC4103].  The mechanisms enable the receiving application to
>     present the received real-time text media separated per source, in
>     different ways according to user preferences.  Some presentation
>     related features are also described explaining suitable variations of
>     transmission and presentation of text.
>     Call control features are described for the SIP environment.  A
>     number of alternative methods for providing the multi-party
>     negotiation, transmission and presentation are discussed and a
>     recommendation for the main ones is provided.  The main solution for
>     SIP based centralized multi-party handling of real-time text is
>     achieved through a media control unit coordinating multiple RTP text
>     streams into one RTP stream.
>     Alternative methods using a single RTP stream and source
>     identification inline in the text stream are also described, one of
>     them being provided as a lower functionality fallback method for
>     endpoints with no multi-party awareness for RTT.
>     Bridging methods where the text stream is carried without the
>     contents being dealt with in detail by the bridge are also discussed.
>     Brief information is also provided for multi-party RTT in the WebRTC
>     environment.
>     The intention is to provide background for decisions, specification
>     and implementation of selected methods.
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-hellstrom-avtcore-multi-party-rtt-solutions/
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-hellstrom-avtcore-multi-party-rtt-solutions-01
> https://datatracker.ietf.org/doc/html/draft-hellstrom-avtcore-multi-party-rtt-solutions-01
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-hellstrom-avtcore-multi-party-rtt-solutions-01
> 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/
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Gunnar Hellström