Re: Vehicle's VIN in IPv6.

Alexandru Petrescu <> Thu, 31 March 2011 10:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B74F63A69AC for <>; Thu, 31 Mar 2011 03:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.449
X-Spam-Status: No, score=-4.449 tagged_above=-999 required=5 tests=[AWL=0.850, BAYES_00=-2.599, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id e9iQAZGnud8u for <>; Thu, 31 Mar 2011 03:07:16 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5A9D43A697A for <>; Thu, 31 Mar 2011 03:07:16 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1822787wwa.13 for <>; Thu, 31 Mar 2011 03:08:55 -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=nvP6g5jZiFHUCuCxk/2rOjK61CX3tdieEN3Fwhvfgwo=; b=sfIuvVd0bLvlWtUuZVuiu1vLKiM699t2LehRGPVAWB7WR+STIZItRbR7XAzMWd6O3V iIg95y0j/QT+YjaLT9c0Rzt/d04htMakLB/elc/UkeEXKNCqRCTH5JFlvVxBEynvkSRa KiPycUlMDjTRoKRExztieDNohA5zThW2CXvEQ=
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=O+iVmsAkNknJHy9Mdkkd9Wp+NV1oKnAqp2W0og/hsHUC9fXPGTjSR1VyBpJ2VXYn/B 5dG+DEiKvzABSCaGkfIoO6iNU1xgGR53z4FY7jU+ZuF1Eq4J4kze8fLb2p4YkWS+/0Df A8b36MtO5wv/g5ZHZw9nb3GXfEbZAATFEbGnA=
Received: by with SMTP id i17mr1877479weo.71.1301566135277; Thu, 31 Mar 2011 03:08:55 -0700 (PDT)
Received: from [] ( []) by with ESMTPS id e13sm552215wbi.40.2011. (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 03:08:54 -0700 (PDT)
Message-ID: <>
Date: Thu, 31 Mar 2011 12:08:51 +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: =?ISO-8859-2?Q?Radek_Wr=F3bel?= <>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
In-Reply-To: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit
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 10:07:17 -0000

Le 30/03/2011 17:31, Radek Wróbel a écrit :
> Dear 6man! My name is Radek Wrobel, I'm writing from Poland (I'm
> working in Wroclaw University of Technology, Division of Car
> Vehicles and Combustion Engines). With this idea I wrote to IANA and
> Leo Vegoda redirected me to you. Vehicle / mechanic engineers are
> working on a new On Board Diagnosis standard for vehicles
> (

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

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

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

> (like it's in local IPv4)?

Hmm..?  What do you mean?  Has VIN been mapped to some reserved IPv4

> I've a few ideas about it and of course I can share them if you will
> be intersting in.

Well definitely I am interested to hear what the idea is about and what
the mapping could look like.

I am interested on everything about how to connect vehicles (cars,
buses, trains) to the Internet with IPv6.

FYI, the MEXT working group has discussed several times about vehicles
ans Internet, with protocol Mobile IPv6 and various extensions.  A
number of people are actively involved.  A specific "vehicular reqs"
draft exists expired in MEXT, as well as some solution individual drafts
(non wg item) for v2v communications.


> Also we cooperate with VW and Toyota. I think they will be
> interesting about it too. Best regards, Radek Wrobel. +48660406004
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list Administrative
> Requests:
> --------------------------------------------------------------------