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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 26 June 2015 15:07 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 2181B1B3098 for <v6ops@ietfa.amsl.com>; Fri, 26 Jun 2015 08:07:15 -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 GFHoemMxMeny for <v6ops@ietfa.amsl.com>; Fri, 26 Jun 2015 08:07:13 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 799861B3096 for <v6ops@ietf.org>; Fri, 26 Jun 2015 08:07:13 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t5QF79i1002954; Fri, 26 Jun 2015 17:07:09 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 72781203F2F; Fri, 26 Jun 2015 17:10:07 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 63EBA203891; Fri, 26 Jun 2015 17:10:07 +0200 (CEST)
Received: from [127.0.0.1] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t5QF78hN008103; Fri, 26 Jun 2015 17:07:08 +0200
Message-ID: <558D6A9C.6070206@gmail.com>
Date: Fri, 26 Jun 2015 17:07:08 +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: Owen DeLong <owen@delong.com>, Gert Doering <gert@space.net>
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> <558BC5AF.3060406@gmail.com> <1A95A912-FC46-4D61-9AB1-8D8E4D33AC89@delong.com> <20150625191428.GJ67883@Space.Net> <BCC35075-B5C1-43A5-A69C-2CFF5B40B063@delong.com>
In-Reply-To: <BCC35075-B5C1-43A5-A69C-2CFF5B40B063@delong.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/83Ikv3sCoaNPzzzxt_3ML0c3lWo>
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: Fri, 26 Jun 2015 15:07:15 -0000


Le 25/06/2015 21:24, Owen DeLong a écrit :
>
>> For the typical driver who is already challenged pairing his mobile via
>> BT with his car's handsfree?  No go.  Do one thing, do it well, and NEVER
>> ask a car owner (or any normal Internet user) about technical decisions.
>
> We can agree to disagree. IMHO, this should be as simple as two settings.
>
> One on the phone: Provide Internet Access to Car: ON/OFF
>
> One in the car: Get internet access from: CAR <-> PHONE

Except that one wants the car to get Internet access from the 
passenger's smartphone, and other times from in-house hotspot, from the 
PLC-enabled-charging-station at home, from the WiFi or 802.11p hotspots 
in some areas like Parking or gas station.

Alex

>
> As to the typical driver being challenged pairing his mobile, frankly, I’m challenged
> with that on many occasions, not because I don’t know how to do it and not because
> I don’t understand what is involved or can’t follow directions, but because BlueTooth
> pairing implementation on most cars and most devices is a steaming pile of poorly
> written and even less well tested code that is fragile, buggy, and unreliable.
>
> Assuming that the underlying connectivity code works, the above two settings
> should not be difficult to implement correctly. They are far less complex than
> Bluetooth.
>
> Owen
>
>
>