[V3] Centralized conference media

Cullen Jennings <fluffy@iii.ca> Fri, 27 March 2020 16:11 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: v3@ietfa.amsl.com
Delivered-To: v3@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E0A703A0C83 for <v3@ietfa.amsl.com>; Fri, 27 Mar 2020 09:11:01 -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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id GIRoDHP5IAvW for <v3@ietfa.amsl.com>; Fri, 27 Mar 2020 09:11:00 -0700 (PDT)
Received: from smtp76.ord1c.emailsrvr.com (smtp76.ord1c.emailsrvr.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F37C43A0C6B for <v3@ietf.org>; Fri, 27 Mar 2020 09:10:59 -0700 (PDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp26.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id F0F1AE02F7; Fri, 27 Mar 2020 12:10:58 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [] (S0106004268479ae3.cg.shawcable.net []) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by (trex/5.7.12); Fri, 27 Mar 2020 12:10:59 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_1269667F-8794-4909-987C-CF24C4464EE5"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <3595789d7a8d24671250e2ca04fcf78eb04179a4.camel@ericsson.com>
Date: Fri, 27 Mar 2020 10:10:58 -0600
Cc: "v3@ietf.org" <v3@ietf.org>
Message-Id: <43DAEFA6-7258-4477-8DD7-65B6FE7E1D5D@iii.ca>
References: <3595789d7a8d24671250e2ca04fcf78eb04179a4.camel@ericsson.com>
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.104.14)
X-Classification-ID: 9b5fb209-1ca6-4228-ba9e-4c1274872065-1-1
Archived-At: <https://mailarchive.ietf.org/arch/msg/v3/RFu05aK_Xskd4Qqx31lxqXT6sDU>
Subject: [V3] Centralized conference media
X-BeenThere: v3@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <v3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v3>, <mailto:v3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v3/>
List-Post: <mailto:v3@ietf.org>
List-Help: <mailto:v3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v3>, <mailto:v3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Mar 2020 16:11:02 -0000

> On Mar 27, 2020, at 8:23 AM, Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org> wrote:
> I am also very worried that if the model for the media transport is only point
> to point calls then we get something that will become obsolete or at least need
> hacks immediately. This thing need to support centralized conferences with
> cascaded or meshed central media nodes. So I think it is cruical that one define
> the usage model with switched central nodes and have that in mind so that one
> can actually support the applications needed. I think by defining a strict model
> one can actually avoid a lot of feature creep in the media transport. 

I think it does make sense to support some meta data on a media flow for centralized conferencing support. What semantic level information do you think is needed in the media ?