IETF Logo Mail Archive

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

westhawk <thp@westhawk.co.uk> Sun, 15 April 2018 15:34 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 4647D124B18 for <rtcweb@ietfa.amsl.com>; Sun, 15 Apr 2018 08:34:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 6Qvv0x4zWNst for <rtcweb@ietfa.amsl.com>; Sun, 15 Apr 2018 08:34:53 -0700 (PDT)
Received: from smtp002.apm-internet.net (smtp002.apm-internet.net [85.119.248.221]) (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 F2996120454 for <rtcweb@ietf.org>; Sun, 15 Apr 2018 08:34:52 -0700 (PDT)
Received: (qmail 54171 invoked from network); 15 Apr 2018 15:34:51 -0000
X-APM-Authkey: 255286/0(159927/0) 210
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp002.apm-internet.net with SMTP; 15 Apr 2018 15:34:51 -0000
Received: from localhost (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id 596C218A04B3; Sun, 15 Apr 2018 16:34:51 +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 CE8LjxqFgRNQ; Sun, 15 Apr 2018 16:34:51 +0100 (BST)
Received: from phage-rock.fritz.box (p5B28C899.dip0.t-ipconnect.de [91.40.200.153]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id 0C38418A049B; Sun, 15 Apr 2018 16:34:50 +0100 (BST)
From: westhawk <thp@westhawk.co.uk>
Message-Id: <DDEE408B-B49E-465E-B17B-C2813AF4F2F4@westhawk.co.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_36D3BFB7-E504-4849-BA40-A692A8059329"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Sun, 15 Apr 2018 17:34:49 +0200
In-Reply-To: <CAOJ7v-0VNCjGdhtz56jwwksBcfPk=9wuxfMgwi8mq7ViFyWpuw@mail.gmail.com>
Cc: RTCWeb IETF <rtcweb@ietf.org>
To: Justin Uberti <juberti@google.com>
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> <4902F7BF-0D20-4EA6-9E78-D22C90EFCE22@westhawk.co.uk> <CAOJ7v-3NsqD6pq-kkMw81+2n_D8qf558CKeCE76ZypyxwCgs9g@mail.gmail.com> <CAOJ7v-2NJ1vhVUerZ1cn8MP9hD_vgAYBurjeQKMx76Aa_U=n=Q@mail.gmail.com> <A8B32C11-30BD-4DA8-9BAB-FA26747BFF66@westhawk.co.uk> <CAOJ7v-0VNCjGdhtz56jwwksBcfPk=9wuxfMgwi8mq7ViFyWpuw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/m9-dXsfhisCe0Ws3owVrDmJTifc>
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: Sun, 15 Apr 2018 15:34:55 -0000


> On 15 Apr 2018, at 17:12, Justin Uberti <juberti@google.com> wrote:
> 
> 
> An example of this may be an LTE phone that has a ‘data bearer channel’ and a ‘media bearer channel’ - the billing routability and QoS behaviour of these
> two interfaces will be different. I could imagine that a carrier app might want to use the media bearer for a voice call. (Sorry for my 3GPP  semi-ignorance).
> 
> I don't think this is relevant to this discussion; since this isn't surfaced upwards as different interfaces to the OS, any behavior here is the same as you would get in Mode 2 when using the cellular interface. 

That’s not the impression I got from this CCC talk https://events.ccc.de/congress/2015/Fahrplan/system/event_attachments/attachments/000/002/829/original/2015.12.28_CCC_Dissecting_VoLTE.pdf <https://events.ccc.de/congress/2015/Fahrplan/system/event_attachments/attachments/000/002/829/original/2015.12.28_CCC_Dissecting_VoLTE.pdf>

One of the slides explicitly shows 2 interfaces surfaced to the ifconfig in linux busybox. 
I realise that these slides are a couple of years old, but I doubt VoLTE has changed much in that time. (I’m still semi-ignorant on 3gpp )

Tim.

v2.23.0 | Report a Bug | By Email