Re: Vehicle's VIN in IPv6.

Thierry Ernst <thierry.ernst@inria.fr> Thu, 31 March 2011 09:38 UTC

Return-Path: <thierry.ernst@inria.fr>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBB7D28C0FA for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.749
X-Spam-Level:
X-Spam-Status: No, score=-11.749 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHpLPXqnIE0a for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:38:52 -0700 (PDT)
Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by core3.amsl.com (Postfix) with ESMTP id C14E428C203 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:38:22 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.63,274,1299452400"; d="vcf'?scan'208"; a="104116796"
Received: from dhcp-rocq-243.inria.fr ([128.93.62.243]) by mail1-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 31 Mar 2011 11:40:01 +0200
Message-ID: <4D944BF1.205@inria.fr>
Date: Thu, 31 Mar 2011 11:40:01 +0200
From: Thierry Ernst <thierry.ernst@inria.fr>
Organization: INRIA
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>
In-Reply-To: <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>
Content-Type: multipart/mixed; boundary="------------050308080503070507090303"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 09:38:55 -0000

>> I rather like the thought that each BMW will need its own BGP4
>> advertisement. Boeing tried that for a while with airplanes, and
>> it didn't work out too well.
> BGP is overkill :-)  I thought the problem with the Boeing service was largely financial, their BGP based technical solution did work.  At least the number of commercial airplanes isn't too large a number.
>
> They could use a fixed car address and use mobile IPv6 with a provider based address.
This is what the intend to do:

  Slides presented at the ITU Fully Networked Car Workshop may be of 
interest to you.

  Convergence of car connectivity

Bernadette Villeforceix (Orange) and Stéphane Petti (Orange)

http://www.itu.int/dms_pub/itu-t/oth/06/41/T06410000700002PDFE.pdf

Regards,
Thierry Ernst.
> Bob
>
>
>>     Brian
>>
>>
>> On 2011-03-31 22:03, Roland Bless wrote:
>>> Hi Radek,
>>>
>>> On 30.03.2011 17:31, Radek Wróbel wrote:
>>>> Vehicle / mechanic engineers are working on a new On Board Diagnosis
>>>> standard for vehicles
>>>> (http://en.wikipedia.org/wiki/On-board_diagnostics). Today EOBDv1 can
>>>> diagnose (quasi online) 849 failures. One of most important advantage of
>>>> EOBDv2 (but not only it) will be constant, real time communication with
>>>> service. The best way of them will be indyvidual number for every car
>>>> vehicles in the world. This number ought to cooporate with global
>>>> networking - TCP/IP (IPv6). All cars have indyvidual number - VIN
>>>> (17 characters which indicates on a country of production  and mark of
>>>> the car: digits and letters A-X). Maybe there is time when someone must
>>>> think about conversion VIN to IPv6 (like it's in local IPv4)? I've a few
>>>> ideas about it and of course I can share them if you will be intersting in.
>>> There is already related work for this.
>>> You should be aware of a US Patent of 2005 "Method for Setting an
>>> Internet Protocol Address using a vehicle identification number".
>>> US 2005/0273505 A1, first hit
>>> http://www.google.com/patents?q=VIN+IPv6&btnG=Search+Patents
>>> (no comment on its usefulness here...)
>>> BMW has also recently filed a patent application with a VIN7 to IPv6
>>> address mapping.
>>> It's not totally clear to me what _problem_ you want to solve.
>>> Depending on that several options exist.
>>> However, I share the concerns that Scott Brim already expressed in his
>>> mail.
>>>
>>> Regards,
>>> Roland
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------