[AVTCORE] Fwd: New Version Notification for draft-hellstrom-avtcore-multi-party-rtt-solutions-04.txt

Gunnar Hellström <gunnar.hellstrom@ghaccess.se> Sat, 31 October 2020 10:03 UTC

Return-Path: <gunnar.hellstrom@ghaccess.se>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C5D3A0D33 for <avt@ietfa.amsl.com>; Sat, 31 Oct 2020 03:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OW3s2Im5pcEr for <avt@ietfa.amsl.com>; Sat, 31 Oct 2020 03:02:58 -0700 (PDT)
Received: from smtp.egensajt.se (smtp.egensajt.se [194.68.80.251]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59F1F3A0D32 for <avtcore@ietf.org>; Sat, 31 Oct 2020 03:02:56 -0700 (PDT)
Received: from [192.168.2.137] (h77-53-37-134.cust.a3fiber.se [77.53.37.134]) (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 95856201B2 for <avtcore@ietf.org>; Sat, 31 Oct 2020 11:02:54 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=egensajt.se; s=dkim; t=1604138574; bh=yR0BIHlSZekF4XEKPhBRISwrSkkgbEcMeczal11NJfs=; h=Subject:References:To:From:Date:In-Reply-To:From; b=YfTBMQXxNu/r6E13n1aULIqldq26fI3GRN+lQXgz0W1EZnDTuiZk0id9H2A32JFeo LVdeeETLYbBOktKPCdOwck7cQAAi4l8qz+HVqIZpjjSWu/+wvHTiEitjWKwefZ7kbn Knso6vyW1hIy4kyni1B9FekLy4mjiklgk/OyDwz4=
References: <160409552608.4190.11676564308170987012@ietfa.amsl.com>
To: "avtcore@ietf.org" <avtcore@ietf.org>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@ghaccess.se>
X-Forwarded-Message-Id: <160409552608.4190.11676564308170987012@ietfa.amsl.com>
Message-ID: <c4f2e2db-52a2-798a-e675-1661f6995ac6@ghaccess.se>
Date: Sat, 31 Oct 2020 11:02:52 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <160409552608.4190.11676564308170987012@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------F1311F2DB56AC02AEF860649"
Content-Language: sv
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/hNnUD1WX88tyKAgwoyMnfGvoQro>
Subject: [AVTCORE] Fwd: New Version Notification for draft-hellstrom-avtcore-multi-party-rtt-solutions-04.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: Sat, 31 Oct 2020 10:03:02 -0000

A new version (-04) is available for 
draft-hellstrom-avtcore-multi-party-rtt-solutions

The document is mainly intended as a background for the specification of 
multi-party procedures for real-time text in 
https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-party-rtt-mix/

The change from version -03 to -04 is mainly an alignment of the name of 
the sdp attribute "rtt-mix" used for capability negotiation of the 
multi-party procedures.

Regards
Gunnar


-------- Vidarebefordrat meddelande --------
Ämne: 	New Version Notification for 
draft-hellstrom-avtcore-multi-party-rtt-solutions-04.txt

	

	

	

A new version of I-D, 
draft-hellstrom-avtcore-multi-party-rtt-solutions-04.txt
has been successfully submitted by Gunnar Hellstrom and posted to the
IETF repository.

Name: draft-hellstrom-avtcore-multi-party-rtt-solutions
Revision: 04
Title: Real-time text solutions for multi-party sessions
Document date: 2020-10-30
Group: Individual Submission
Pages: 45
URL: 
https://www.ietf.org/archive/id/draft-hellstrom-avtcore-multi-party-rtt-solutions-04.txt
Status: 
https://datatracker.ietf.org/doc/draft-hellstrom-avtcore-multi-party-rtt-solutions/
Html: 
https://www.ietf.org/archive/id/draft-hellstrom-avtcore-multi-party-rtt-solutions-04.html
Htmlized: 
https://tools.ietf.org/html/draft-hellstrom-avtcore-multi-party-rtt-solutions-04
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-hellstrom-avtcore-multi-party-rtt-solutions-04

Abstract:
This document specifies methods for Real-Time Text (RTT) media
handling in multi-party calls. The main discussed transport is to
carry Real-Time text by the RTP protocol in a time-sampled mode
according to RFC 4103. 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.



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