Re: [rtcweb] WGLC for draft-ietf-rtcweb-ip-handling

westhawk <thp@westhawk.co.uk> Fri, 13 April 2018 06:59 UTC

Return-Path: <thp@westhawk.co.uk>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFB7127137 for <rtcweb@ietfa.amsl.com>; Thu, 12 Apr 2018 23:59:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 DKxVgKnijCfY for <rtcweb@ietfa.amsl.com>; Thu, 12 Apr 2018 23:59:18 -0700 (PDT)
Received: from smtp001.apm-internet.net (smtp001.apm-internet.net [85.119.248.220]) (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 37A2F126D45 for <rtcweb@ietf.org>; Thu, 12 Apr 2018 23:59:18 -0700 (PDT)
Received: (qmail 55135 invoked from network); 13 Apr 2018 06:59:16 -0000
X-APM-Authkey: 255286/0(159927/0) 73
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp001.apm-internet.net with SMTP; 13 Apr 2018 06:59:16 -0000
Received: from localhost (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id 1CB7518A06E9; Fri, 13 Apr 2018 07:59:16 +0100 (BST)
Received: from zimbra003.verygoodemail.com ([127.0.0.1]) by localhost (zimbra003.verygoodemail.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ErSuprRcdzQ8; Fri, 13 Apr 2018 07:59:16 +0100 (BST)
Received: from [192.168.0.3] (cable-82-119-15-228.cust.telecolumbus.net [82.119.15.228]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id D19BC18A0285; Fri, 13 Apr 2018 07:59:15 +0100 (BST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: westhawk <thp@westhawk.co.uk>
In-Reply-To: <CAOJ7v-2gmxpsGp=25pcJmnkYmipZdCFOqU4nLtAVSznLsZo9rQ@mail.gmail.com>
Date: Fri, 13 Apr 2018 08:59:13 +0200
Cc: Lennart Grahl <lennart.grahl@gmail.com>, RTCWeb IETF <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4902F7BF-0D20-4EA6-9E78-D22C90EFCE22@westhawk.co.uk>
References: <1D5B431C-801E-4F8C-8026-6BCBB72FF478@sn3rd.com> <63282b84-4493-3fcb-a95f-4afe17d96bb6@cs.tcd.ie> <CAOJ7v-1gTq+EEjb+-q-T-pABBW--rpNGegoj_d2_7f7AKGksCA@mail.gmail.com> <403713b4-31d4-9085-d639-d3f60935ed5a@cs.tcd.ie> <CAOJ7v-0ED-FK=JmSxBJYfM=PCdgY6kmbiq6aFLcP7OXugG07EA@mail.gmail.com> <e6938f7d-542d-736b-0a3d-9269d7dd06e5@cs.tcd.ie> <CAOW+2dv1ORz2tEkgDTvdM1DtgyOdgXqKU30T4QhLAp1NT+rirg@mail.gmail.com> <CAOJ7v-0tCcg3FdzyfSJ6Y3JaH-TivFf-Sey6+tD8BANJKsjqtQ@mail.gmail.com> <1fceb3c4-35f3-34f7-de1d-79d5805e6d22@gmail.com> <9517D601-D3E8-46E1-94E5-7EC29FD6319B@sn3rd.com> <b5d323ac-2205-2aee-05c9-f270e80215f5@gmail.com> <CAOJ7v-0+hr-NddbLCwgjkfyEFEzoLYW8BcE5OYZ+HUiqDRnarg@mail.gmail.com> <0dee004d-159a-a9be-a0b8-ecbfd4204d72@gmail.com> <06252a76-f12e-4d8d-4a07-5240a7605bce@gmail.com> <914e0220-e3cc-00d7-0925-e5deb8b07e75@nostrum.com> <AFDFD3F3-4798-4716-B26C-A67457BF2C65@sn3rd.com> <e5e2a517-d29a-117c-ab79-6f01fa62b843@gmail.com> <20180412144158.44733ac7@lminiero> <b767da79-7678-2a1c-ecb0-46a9a3bd9129@gmail.com> <CAOJ7v-2gmxpsGp=25pcJmnkYmipZdCFOqU4nLtAVSznLsZo9rQ@mail.gmail.com>
To: Justin Uberti <juberti=40google.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/QP2ZeeYwFgTLGLPiWCIBfRVrOLo>
Subject: Re: [rtcweb] WGLC for draft-ietf-rtcweb-ip-handling
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2018 06:59:21 -0000


> On 13 Apr 2018, at 02:22, Justin Uberti <juberti=40google.com@dmarc.ietf.org> wrote:
> 
> Being non-interactive, it's not clear that those cases require Mode 1 though; they should work well even in Mode 2. I also don't think that suggesting "more appropriate means" is useful when we as a WG haven't been able to come up with any.

Whoa there! Non interactive, that’s a big step from non-conversational !
So one current use-case is adjusting room lights over the data channel. You can literally see latency - an unnecessary cloud round-trip is entirely
visible.

Another is driving a droid over the datachannel using it’s camera to feed live video to see where it is going 
- again totally interactive, just not using local media at the user’s end (although we do use the 
motion sensors to give a steering wheel feel) - latency here causes crashes!

A third one is baby cams, where again the video feed is one-way but you’d really like to keep the media on the home wifi
if possible for cost (and privacy) reasons.

In all these I’ll have to introduce an otherwise needless GUM request to get the network behaviour I want. 

Perhaps I should present some of these non-call based usecases at a future F2F so that folks get a sense of the possibilities.

Tim.