Re: [v6ops] Apple and IPv6, a few clarifications - ND proxy for bridging hotspots

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 25 June 2015 09:11 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83EF11B3200 for <v6ops@ietfa.amsl.com>; Thu, 25 Jun 2015 02:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 3lNJNBsDetXc for <v6ops@ietfa.amsl.com>; Thu, 25 Jun 2015 02:11:17 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EECE51B31F4 for <v6ops@ietf.org>; Thu, 25 Jun 2015 02:11:16 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t5P9BEhI019992; Thu, 25 Jun 2015 11:11:14 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 838652030BD; Thu, 25 Jun 2015 11:14:11 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 76FFE202EBA; Thu, 25 Jun 2015 11:14:11 +0200 (CEST)
Received: from [127.0.0.1] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t5P9BBPj008673; Thu, 25 Jun 2015 11:11:14 +0200
Message-ID: <558BC5AF.3060406@gmail.com>
Date: Thu, 25 Jun 2015 11:11:11 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: james woodyatt <jhw@nestlabs.com>
References: <E1C235B5-1421-4DAF-A2F3-F963982233DF@apple.com> <1599CF94-9B35-4858-AD52-6FADC8F25671@apple.com> <558ABAC3.4010802@gmail.com> <4F519538-0706-4BBA-9508-3E59F7A8BB62@nestlabs.com>
In-Reply-To: <4F519538-0706-4BBA-9508-3E59F7A8BB62@nestlabs.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/v23AFOuy0aGs4pBKJs_f48G8iAs>
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Apple and IPv6, a few clarifications - ND proxy for bridging hotspots
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2015 09:11:18 -0000


Le 24/06/2015 20:38, james woodyatt a écrit :
> On Jun 24, 2015, at 07:12, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>>
> wrote:
>>
>> […] In the car use-case the smartphone connects to the dashboard
>> using a ptp link.  And it's the car's dashboard which offers a
>> WiFi hotspot.  These couldn't be bridged (ND proxy) by the
>> smartphone alone, it would need the dashboard router to participate
>> in this ND proxy. […]
>
> I suspect the point you may be missing here is the logic encoded
> elsewhere in iOS that restricts the use of Mobile Internet Sharing
> to the telephony uplink. It is not possible with iOS to share
> Internet access over the Wi-fi (or other interfaces) with tethered
> devices. Only the telephony data service is eligible for Mobile
> Internet Sharing.

That is a good point.

There is an ongoing technical debate in the car comm community - should
the smartphone provide Internet connectivity to the car?  Or should the
smartphone use the Internet connectivity offered by the car.

Right now where I live a large number of marketed cars are on the first
option.  It is on that option that I think smartphone's iOS Mobile
Internet Sharing can help, provided it does more than NDproxy.

> Shorter james: the automotive Wi-fi hotspot use case is like every
> other Wi-fi hotspot as far as iOS is concerned, i.e. every phone on
> Wi-fi is an ordinary host and not a ND proxy or a router.

Well I did not mean the smartphones using car's hotspots.  That's for
WiFi-only tablets.

The NDproxy problem in iOS is in the case where cars create hotspots by
their own means, but disconnected from the Internet.  All they need is
to reach the Internet somehow without having to put a SIMcard in the
car.  And that's where cars connect to the smartphone with Bluetooth.
(cars already connect to smartphone with bluetooth for Audio-Video
screen replication and phone calls (although phone calls are going to be
completely forbidden soon even for handsfree)).

Alex


>
> —james