Re: Vehicle's VIN in IPv6.

Roland Bless <roland.bless@kit.edu> Thu, 31 March 2011 09:02 UTC

Return-Path: <roland.bless@kit.edu>
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 1331E28C181 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.066
X-Spam-Level:
X-Spam-Status: No, score=-7.066 tagged_above=-999 required=5 tests=[AWL=0.883, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 BNJ6qWsCh58b for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:02:04 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id C152828C188 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:02:03 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25 id 1Q5Dmw-0002u2-3E; Thu, 31 Mar 2011 11:03:42 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 4A6AA2C6; Thu, 31 Mar 2011 11:06:28 +0200 (CEST)
Message-ID: <4D944365.4020809@kit.edu>
Date: Thu, 31 Mar 2011 11:03:33 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: =?ISO-8859-2?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
In-Reply-To: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1301562222.752788000
Cc: ipv6@ietf.org
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:02:05 -0000

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