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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 26 June 2015 15:15 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 60A101A007F for <v6ops@ietfa.amsl.com>; Fri, 26 Jun 2015 08:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.084
X-Spam-Level:
X-Spam-Status: No, score=-5.084 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, 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 QYn5IGWvBBzZ for <v6ops@ietfa.amsl.com>; Fri, 26 Jun 2015 08:15:27 -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 7E0D71A0064 for <v6ops@ietf.org>; Fri, 26 Jun 2015 08:15:27 -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 t5QFFQBe005813 for <v6ops@ietf.org>; Fri, 26 Jun 2015 17:15:26 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 62A5E204E14 for <v6ops@ietf.org>; Fri, 26 Jun 2015 17:18:24 +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 5A99A203F2F for <v6ops@ietf.org>; Fri, 26 Jun 2015 17:18:24 +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 t5QFFPF3017453 for <v6ops@ietf.org>; Fri, 26 Jun 2015 17:15:25 +0200
Message-ID: <558D6C8D.6080603@gmail.com>
Date: Fri, 26 Jun 2015 17:15:25 +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: v6ops@ietf.org
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> <m1Z8Pnq-0000HRC@stereo.hq.phicoh.net>
In-Reply-To: <m1Z8Pnq-0000HRC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/DS82LkqevNTk3izb6HaqZnCfoMU>
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:15:29 -0000


Le 26/06/2015 11:20, Philip Homburg a écrit :
> In your letter dated Thu, 25 Jun 2015 21:14:28 +0200 you wrote:
>> No.
>>
>> For *you* this might make sense and be a useful feature.  For me, I
>> might like it, but will never actually use it (because I'm way too
>> lazy to be interested in multiple possible Internet uplinks for my
>> car - and why I should bother to trade the nice *external* antenna
>> of the car with the great reception of a typical smartphone inside
>> a large moving metal box).
>
> I hope that car manufacturers will find their way back into modular
> electronics, just like car radios ages ago.
>
> With he current rate of development, car electronics are obsolete for
> most of the car's lifetime.
>
> A good example is built-in navigation systems, where car manufactures
> have a hard time understanding what to charge for updating maps, so
> people just use a standalone device next to the built-in one.

I fully agree.  NAvigation systems continue to be a large fiasco since
they first appeared on the market.  There is still no easy way to update
them - IMHO the reason has to do with policy: who controls the car, who
writes the software, wo controls the communication system... these are
typically very different industries.

> Android devices typically receive their last update 1.5 years after
> the devices were last sold. Nice driving around with an unpatched,
> internet connected car entertainment system.

:-)

There is another tendency here: car manufacturers consider TomTom,
google and a few others to be the best source of information on
geography.  Whereas the best source of information comes from the
authority who controls these roads.

> With modular electronics, those who want their pi powered hadoop
> cluster can just by an aftermarket upgrade.

YEs, but car manufacturers dont want the same aftermarket upgrade to 
work on their cars as simply as it works on competition's cars, and 
that's a problem.

Alex

>
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>
>