IETF Logo Mail Archive

Re: [AVTCORE] draft-ietf-avtcore-multi-party-rtt-mix Issue 1: transport

Gunnar Hellström <gunnar.hellstrom@ghaccess.se> Mon, 18 May 2020 17:46 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 4066A3A0AB7 for <avt@ietfa.amsl.com>; Mon, 18 May 2020 10:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 x_sr1CB1U-IY for <avt@ietfa.amsl.com>; Mon, 18 May 2020 10:46:07 -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 0744B3A0AB2 for <avt@ietf.org>; Mon, 18 May 2020 10:46:04 -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) server-digest SHA256) (No client certificate requested) (Authenticated sender: gunnar.hellstrom@ghaccess.se) by smtp.egensajt.se (Postfix) with ESMTPSA id 90EF92028E; Mon, 18 May 2020 19:46:02 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=egensajt.se; s=dkim; t=1589823962; bh=vGFi1in5uJDeYszDUfRcXC+k8zghXXeczjBrFekLguo=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=XnIthE5IoLpeAxNyTlsfoeSPLgm5L4LE1pAiCKIF6FvXL9fvyKyYHRAvS/52K2Ycy Qc6pe+HWLeqX7YLGnXsv+oZc5DDg9HFPCgMiGjcHCSpoTti8a2JWOk+Igy6IvJgh0v d0QVojwhXDx1328u4hd+BSWF4hEbw4mJNpmg/V5E=
To: Christer Holmberg <christer.holmberg@ericsson.com>, Brian Rosen <br@brianrosen.net>
Cc: "avt@ietf.org" <avt@ietf.org>
References: <158895171474.17391.16816077344810423489@ietfa.amsl.com> <e462ea93-e084-5c55-1ade-521424884d41@ghaccess.se> <e6d35436-0ba4-6347-6990-46bbf5b4e5b3@ghaccess.se> <a2a1add6-7934-6371-81a0-8e3dc6735045@ghaccess.se> <C8BCBCFE-EA60-4964-A969-320265A89FA7@brianrosen.net> <06d6a0e7-8a0b-6177-ebcb-b03d3396e6cb@ghaccess.se> <0104AEDD-A7FC-4FC9-9E9E-8858D258581D@brianrosen.net> <633edda9-2a36-bc9b-b98e-577f97de7c73@alum.mit.edu> <f61dc7d6-1fbf-2052-b1b9-b5c2d346948a@ghaccess.se> <7455653A-5769-42F2-8867-EFC9852758FF@brianrosen.net> <A44560D0-39C3-4BD0-B4F0-A65E22C7DC06@ericsson.com>
From: Gunnar Hellström <gunnar.hellstrom@ghaccess.se>
Message-ID: <d718e82d-c733-d4ec-cebe-ddf50047bc08@ghaccess.se>
Date: Mon, 18 May 2020 19:45:59 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <A44560D0-39C3-4BD0-B4F0-A65E22C7DC06@ericsson.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: sv
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/5AEp_-re_PaMd-rxh65mDhYLcMo>
Subject: Re: [AVTCORE] draft-ietf-avtcore-multi-party-rtt-mix Issue 1: transport
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 17:46:11 -0000

Hi,

Den 2020-05-18 kl. 18:10, skrev Christer Holmberg:
> Hi,
>
> ---
>
>> 1) A mechanism that the mixer can use when it is revealed that the endpoint does not support proper multi-party presentation. There are functional limitations,
>> but it works reasonably well, especially for few parties taking turns in reasonably good order. It is specified in section 13.2 and is called "Multi-party mixing for
>> multi-party unaware endpoints".
> Why not simply call it "Multi-party mixing for single-party endpoints"?

Maybe.

I initially used "conference-unaware", in order to use the same term as 
in RFC 4353 and RFC 4579 SIP central conferencing. The most urgent 
applications claim that they use that framework.

But then I realized that for our case it was more important how the 
media format was composed than how the multi-party session was signaled, 
so I started to call it "multi-party aware" and "multi-party unaware".  
It still has similarities with the nomenclature of the conferencing 
framework.

If we were to change terms, I think it would be better with two-party 
endpoints, because they are made for two-party sessions. On the other 
hand, multi-party-aware endpoints can also handle two-party sessions.

So the difference is really that the endpoint is unaware of the 
charcteristics in the media format that tells about different parties.

What do you think?

Thanks,

Gunnar


>
> Regards,
>
> Christer
>
-- 
Gunnar Hellström
GHAccess
gunnar.hellstrom@ghaccess.se

v2.23.0 | Report a Bug | By Email