Re: Vehicle's VIN in IPv6.

Roland Bless <roland.bless@kit.edu> Thu, 31 March 2011 10:25 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 12F7F3A6B1E for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.267
X-Spam-Level:
X-Spam-Status: No, score=-7.267 tagged_above=-999 required=5 tests=[AWL=0.982, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_DE=0.35, 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 VMqKw9Tt+KGU for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:25:14 -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 C538B3A6AF3 for <ipv6@ietf.org>; Thu, 31 Mar 2011 03:25:13 -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 1Q5F5T-0001HO-34; Thu, 31 Mar 2011 12:26:52 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 81C042C6; Thu, 31 Mar 2011 12:29:41 +0200 (CEST)
Message-ID: <4D9456E6.90608@kit.edu>
Date: Thu, 31 Mar 2011 12:26:46 +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: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D9452B3.2010504@gmail.com>
In-Reply-To: <4D9452B3.2010504@gmail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 7bit
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 1301567213.037497000
Cc: ipv6@ietf.org, =?ISO-8859-2?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
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 10:25:15 -0000

Hi Alexandru,

On 31.03.2011 12:08, Alexandru Petrescu wrote:
> Thanks for the pointer, I am discovering OBD.  We are also interested in
> wireless usage of IP within the vehicle, with off-the-shelf links (i.e.
> consumer electronics market wifi, bluetooth, ant) together with OBD if
> needed.

See below.

>> 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.
> 
> Excellent requirement to IP.

Maybe to some mapping system, but not directly to IPv6
(ID/Loc split).

>> 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
> 
> Hmm... sounds as good idea.  But there may be several IP addresses
> within a vehicle, one for the obu, one for map device, etc.

> In case one would like to map VIN to an IPv6 address one would consider
> first an Interface Identifier of the IPv6 address. (rightmost 64 bits).
> Interface Identifier is about an Interface, and I am not sure VIN is
> about an interface, or is it. (like Interface is the Ethernet interface
> of this pc).

Yes, but from a security point of view, it would be a nightmare
if some hacker could directly send IP packets to the ECU controlling
your airbag or other safety relevant ECUs etc. So a strong
security architecture is a MUST. I'm not sure that there is a need
to _directly_ address any internal car devices. A security gateway
as policy enforcement point seems to be required at least.

Regards,
 Roland