Re: [dispatch] Request DISPATCH of RUM

Brian Rosen <br@brianrosen.net> Mon, 04 February 2019 20:04 UTC

Return-Path: <br@brianrosen.net>
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 9B4D4124B0C for <dispatch@ietfa.amsl.com>; Mon, 4 Feb 2019 12:04:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.032
X-Spam-Level:
X-Spam-Status: No, score=-2.032 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
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 75bSM8TEjATF for <dispatch@ietfa.amsl.com>; Mon, 4 Feb 2019 12:04:11 -0800 (PST)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96168126BED for <dispatch@ietf.org>; Mon, 4 Feb 2019 12:04:09 -0800 (PST)
Received: by mail-qt1-x82b.google.com with SMTP id u47so1367091qtj.6 for <dispatch@ietf.org>; Mon, 04 Feb 2019 12:04:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hUJfOiwtqQEljAU9JQIbrRItDitRxadEs/Il3WHiilc=; b=kajqykKAwD5HMN1C32d03Om40M9Vv4Jj9fJrr2MJiT1vGAbVhZ3dkMryd0+yhruaqy ZqNuymUZDn7wwRsx7uC6irOnKxTTYwbPKXjLy8sdRFqOoHZ2uSJdlNMPXpuWkVBlC0Ws Qfoko/7jKU5j3mW3JVbUZsvippeCIE+DIMtGU9R5t1gtBnLtdDIY9gxInu6PY0PKgHca ZVpSEwjVmfWSj9Uj3vy5jhO8OD8K0GituqjMqZoRX+43eBIRczNnCKbTWfhi4jEsVvQX /iyjWeyhtNDyUt30evjZUB4C5y0+XpTew1OiOhejyVVgNzscalWuhWooyM3q/TZKAIJw TU5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hUJfOiwtqQEljAU9JQIbrRItDitRxadEs/Il3WHiilc=; b=Tyo7zLXDLf3H0L3N4JsGd7dKAOkpSnkMKhICzwZRloRePwa39v5wvISiS+K3Xa+wt1 jOclHmB6DR0isT69D0ttRVQB/fy/XklWib12tiUXA9Gk/uoEGTv5osCaWXn86wUzOQvL qc6e7TuGj4fYdXQw7FB2ei/gJUzhV+6W7x8p9nCVuaGjekCt8yYA6/bZMUpaP3smwnOb DkFc2ETy+eoaE9TyQnnMAk7f7gAEyLxaKAVgPL4nEz8rBLRLI2S6pW0jJqpZEfqtZNUQ Gvzhcr1MlLsntnu39pn83NJWeUU2Jdt76qOU22DIEB5yf3MR4z+h2fFOhTZoWXgplgDY 9Xog==
X-Gm-Message-State: AHQUAuaAtxgSx+2bW6IANNHAlNasAzhp0F3yzipLE4/GBXQ1Yz8heJjV 8xsO8RqRRuwQe1OWxO9AxrMzeg==
X-Google-Smtp-Source: AHgI3Ia8cWazS+7tI2tU09mkhG2+b1Guc2eIUDPszF9LNHe+J3CRnBRY9mQp1upcDtHLmlbDAamiHw==
X-Received: by 2002:ac8:5354:: with SMTP id d20mr861845qto.73.1549310648657; Mon, 04 Feb 2019 12:04:08 -0800 (PST)
Received: from brians-mbp.lan (dynamic-acs-72-23-220-152.zoominternet.net. [72.23.220.152]) by smtp.gmail.com with ESMTPSA id p48sm16686212qtp.62.2019.02.04.12.04.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Feb 2019 12:04:08 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <c5c22e36-5a06-df93-d8d3-fc5ede6dade0@alum.mit.edu>
Date: Mon, 4 Feb 2019 15:04:05 -0500
Cc: =?utf-8?Q?Gunnar_Hellstr=C3=B6m?= <gunnar.hellstrom@omnitor.se>, dispatch@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAB7DDA1-C282-4658-88F7-AFCB1934AC3B@brianrosen.net>
References: <37j5vgxgoeutl6ve8dhojsc4.1549227362745@email.android.com> <F9AD2250-378C-41FD-A51E-681B3C08B7F4@brianrosen.net> <c5c22e36-5a06-df93-d8d3-fc5ede6dade0@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/VDxNXb4bIMOiDqB1VQgB7Dohm6E>
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 20:04:12 -0000

Hah, probably not, but up to the wg to decide.

I better soften the WebRTC language so the WG can decide how far it wants to go,

Update of charter proposal text coming soon.

Brian


> On Feb 4, 2019, at 2:58 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> 
> 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
>