Re: [dispatch] Request DISPATCH of RUM

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 04 February 2019 19:58 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B370E130EF3 for <dispatch@ietfa.amsl.com>; Mon, 4 Feb 2019 11:58:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 IDUtX_FF_uU7 for <dispatch@ietfa.amsl.com>; Mon, 4 Feb 2019 11:58:49 -0800 (PST)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4C4B126BED for <dispatch@ietf.org>; Mon, 4 Feb 2019 11:58:48 -0800 (PST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x14Jwih4025522 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 4 Feb 2019 14:58:45 -0500
To: Brian Rosen <br@brianrosen.net>, =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Cc: dispatch@ietf.org
References: <37j5vgxgoeutl6ve8dhojsc4.1549227362745@email.android.com> <F9AD2250-378C-41FD-A51E-681B3C08B7F4@brianrosen.net>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <c5c22e36-5a06-df93-d8d3-fc5ede6dade0@alum.mit.edu>
Date: Mon, 4 Feb 2019 14:58:44 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <F9AD2250-378C-41FD-A51E-681B3C08B7F4@brianrosen.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/JomX6pSkduiplLVVTZKku8nklMQ>
Subject: Re: [dispatch] Request DISPATCH of RUM
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2019 19:58:54 -0000

On 2/4/19 10:46 AM, Brian Rosen wrote:

I do think re-using the media specs from WebRTC is the
> right set of choices to make for this profile, independent of whether 
> the user has a WebRTC client or a native SIP client.

Do you mean to include bundling of audio, video on a single address/port?

Note that if the goal is for a WebRTC gateway to avoid being a media 
relay for audio and video, while gatewaying text from data channel to 
RTT/RTP, then bundling them all together will prevent that.

	Thanks,
	Paul