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

Owen DeLong <owen@delong.com> Thu, 25 June 2015 19:24 UTC

Return-Path: <owen@delong.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 F37B21ACCFC for <v6ops@ietfa.amsl.com>; Thu, 25 Jun 2015 12:24:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.111
X-Spam-Level:
X-Spam-Status: No, score=-1.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 bn7Hv0XknmoY for <v6ops@ietfa.amsl.com>; Thu, 25 Jun 2015 12:24:51 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 6C6791ACD03 for <v6ops@ietf.org>; Thu, 25 Jun 2015 12:24:50 -0700 (PDT)
Received: from [IPv6:2620::930:0:ae87:a3ff:fe29:7192] ([IPv6:2620:0:930:0:ae87:a3ff:fe29:7192]) (authenticated bits=0) by owen.delong.com (8.14.5/8.14.2) with ESMTP id t5PJOmb4010471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 25 Jun 2015 12:24:48 -0700
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <20150625191428.GJ67883@Space.Net>
Date: Thu, 25 Jun 2015 12:24:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCC35075-B5C1-43A5-A69C-2CFF5B40B063@delong.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> <558BC5AF.3060406@gmail.com> <1A95A912-FC46-4D61-9AB1-8D8E4D33AC89@delong.com> <20150625191428.GJ67883@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/CRXk1QTcz6_ibrKbPqEsQcePQZ0>
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 19:24:52 -0000

> 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

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