[AVTCORE] Next steps for draft-ietf-avtcore-multi-party-rtt-mix

Gunnar Hellström <gunnar.hellstrom@ghaccess.se> Mon, 18 May 2020 19:30 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 0FB5B3A09AC for <avt@ietfa.amsl.com>; Mon, 18 May 2020 12:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=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 N9erH_RdarnN for <avt@ietfa.amsl.com>; Mon, 18 May 2020 12:30:36 -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 ED6E13A0FB7 for <avtcore@ietf.org>; Mon, 18 May 2020 12:30:07 -0700 (PDT)
Received: from [192.168.2.136] (h79-138-72-251.cust.a3fiber.se [79.138.72.251]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) (Authenticated sender: gunnar.hellstrom@ghaccess.se) by smtp.egensajt.se (Postfix) with ESMTPSA id 0DE5C2012C for <avtcore@ietf.org>; Mon, 18 May 2020 21:30:05 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=egensajt.se; s=dkim; t=1589830205; bh=l/uaXN6IUPrJOnOol3A5pA+Mgl2yHm1yI0O6D0JLgQU=; h=To:From:Subject:Date:From; b=Mtn+XVCH5A41PJFTKCFZvMGqqILOqrNAFawLtQRw3WtE5CfZfOfeAV2tH/QJCTD3t u4TpBmY2EiCMF0/qJ26B17Uglquj/O6p9kTNaG+MEr0bSZIlOnK7yBKEnqa5GfJPVj t3xNuR0MS8hssbLUy9U38v+MDyvJrLfgAg7Jnmgg=
To: "avtcore@ietf.org" <avtcore@ietf.org>
From: Gunnar Hellström <gunnar.hellstrom@ghaccess.se>
Message-ID: <ef9dab12-0dbb-726e-e3f2-554e22d96664@ghaccess.se>
Date: Mon, 18 May 2020 21:30:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: sv
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/uBoc_FXBZneRiXPi6z7uigaecEo>
Subject: [AVTCORE] Next steps for draft-ietf-avtcore-multi-party-rtt-mix
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, 18 May 2020 19:30:40 -0000

I am aware of a few issues in draft-ietf-avtcore-multi-party-rtt-mix-01 
that require action.

The topics are:

1) SDP examples and better description and visibility of security by 
OSRTP RFC 8634.

2) Expand the description of gatewaying to WebRTC data channel.

3) Consider moving 13.2 - multi-party unaware mixing, to an appendix, 
leaving a very brief intro of the topic in 13.2.  That would make it 
more evident that it is a completely different method and just a fall-back.

4) Should there be a negotiable limit of the number of possible 
simultaneous participants sending text? And if so, how shall a case be 
handled when the limit is reached?

5) Improve in chapter 2  the description of the redundancy header and 
text areas in the packet: The number of bits for each piece, the value 
of the timestamp offsets. The order of the different parts etc.

I am editing on these topics and plan to provide a new version soon.

Regards


Gunnar



-- 
Gunnar Hellström
GHAccess
gunnar.hellstrom@ghaccess.se