Re: Vehicle's VIN in IPv6.

Alexandru Petrescu <> Thu, 31 March 2011 13:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 70E6128C168 for <>; Thu, 31 Mar 2011 06:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.83
X-Spam-Status: No, score=-4.83 tagged_above=-999 required=5 tests=[AWL=0.769, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZkYb1dxZhuMl for <>; Thu, 31 Mar 2011 06:50:25 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3E26228C141 for <>; Thu, 31 Mar 2011 06:50:25 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1986264wwa.13 for <>; Thu, 31 Mar 2011 06:52:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Wdc2e43vekdvSZJy8jn3+bxArjcAdsZbqlbA55CIPEg=; b=gLrvXbIZfe1zNMDmbhrcBHeQeEOs3RL6XmUw8wHGeKjxgeZR7YWpukhc4Ltih7idum T4T9T3jQWnke1P/VeXSWx3ZpJsh0WYfKcsROVXyldI2hP4c+g4j9y1w3KTsjgvWBnQ2O N7bn11OexkwOWWB4xUqKrIFoAAestPwm256dA=
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=K3ePrCokbiu+Vv8WBBC8k7RcBF3qMtucM5VdD/v/LlxOsxuQ5kJ/mRU+0VsI2gNlSV RRyZTSSFudR5pNSP3YVXhREKxFm9elTtplG7EhYftDqz6J9e0SJxJpUDd+CP8TpPbeqm CV8+KFzw0Gruql4ihll5aab6lINywtbesTg6k=
Received: by with SMTP id r14mr520387wbz.30.1301579524350; Thu, 31 Mar 2011 06:52:04 -0700 (PDT)
Received: from [] ( []) by with ESMTPS id x1sm665699wbh.19.2011. (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 06:52:03 -0700 (PDT)
Message-ID: <>
Date: Thu, 31 Mar 2011 15:52:00 +0200
From: Alexandru Petrescu <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv: Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Roland Bless <>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit
Cc:, =?ISO-8859-2?Q?Radek_Wr=F3bel?= <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 31 Mar 2011 13:50:26 -0000

Le 31/03/2011 12:26, Roland Bless a écrit :
> 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).

I quickly get confused on id/loc split discussions.  I meant to say that
it is wonderful to request Internet to let a vehicle connect to it
anywhere in the world and, moreover, solution should not be exclusively 

>>> 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 agree, appropriate security is useful.  What's ECU? (other than the

> 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.

For entertainment, passengers may like to youtube without policy
enforcement, i.e. all laptops in the vehicle be each IP-addressable.

In other cases, only the OBU would be IP-addressable and it would be
connect on its ingress interface to rs232/can devices (but it would
still need a 2nd IP address on that interface).


> Regards, Roland