Re: [V3] High level comments on the RIPT charter and scope

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

Return-Path: <fluffy@iii.ca>
X-Original-To: v3@ietfa.amsl.com
Delivered-To: v3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 631F83A0783 for <v3@ietfa.amsl.com>; Fri, 27 Mar 2020 09:24:53 -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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 QMbaXg17_HLO for <v3@ietfa.amsl.com>; Fri, 27 Mar 2020 09:24:47 -0700 (PDT)
Received: from smtp88.ord1d.emailsrvr.com (smtp88.ord1d.emailsrvr.com [184.106.54.88]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E6C33A0484 for <v3@ietf.org>; Fri, 27 Mar 2020 09:19:10 -0700 (PDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp4.relay.ord1d.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 4098040108; Fri, 27 Mar 2020 12:19:08 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.91] (S0106004268479ae3.cg.shawcable.net [50.66.148.85]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:25 (trex/5.7.12); Fri, 27 Mar 2020 12:19:08 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_21EC913E-35C6-4463-9068-08200770284A"
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:19:07 -0600
Cc: "v3@ietf.org" <v3@ietf.org>
Message-Id: <7028E641-D015-4E2B-BAA3-865B13535912@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: 3fb9c469-14cd-470a-bd21-4be7a68fc4fb-1-1
Archived-At: <https://mailarchive.ietf.org/arch/msg/v3/QR4iMW5G4uHTdA-B2-66_rnTHsY>
Subject: Re: [V3] High level comments on the RIPT charter and scope
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:24:54 -0000


> On Mar 27, 2020, at 8:23 AM, Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org> wrote:
> 
> The third big part is the media transport. I think we need to strongly consider
> if this can be broken out in to it seperate WG.

I think the WG we are talking about here is the WG to do media of H3. So we can talk about other things being in or out of it but that is the core thing. 

I would like to point out that one of the design properties that has been making this easier is that media is self describing. What I mean by that is that if a device receives media that is one of the supported formats and within in the limits of that device supports, the media has all the information the device needs to decode it. No out of band information needed. That is key to making this easier to deal with HA and scalability on cloud side. I think that is a good property for modern designs. We have been going that way for a long time with things like opus and it works out well. 

> here are several aspects here.
> First of the split in expertise between the media transport and the signalling
> folks. 

I’m not sure what you mean by signalling but the the singling here was mostly start media , stop media. It is not call routing, forking etc that is done by SIP.