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

Gunnar Hellström <> Mon, 18 May 2020 17:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4066A3A0AB7 for <>; Mon, 18 May 2020 10:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.001
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id x_sr1CB1U-IY for <>; Mon, 18 May 2020 10:46:07 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0744B3A0AB2 for <>; Mon, 18 May 2020 10:46:04 -0700 (PDT)
Received: from [] ( []) (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: by (Postfix) with ESMTPSA id 90EF92028E; Mon, 18 May 2020 19:46:02 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; 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 <>, Brian Rosen <>
Cc: "" <>
References: <> <> <> <> <> <> <> <> <> <> <>
From: Gunnar Hellström <>
Message-ID: <>
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: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: sv
Archived-At: <>
Subject: Re: [AVTCORE] draft-ietf-avtcore-multi-party-rtt-mix Issue 1: transport
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 18 May 2020 17:46:11 -0000


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"?


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 

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?



> Regards,
> Christer
Gunnar Hellström