Re: Vehicle's VIN in IPv6.

Behcet Sarikaya <behcetsarikaya@yahoo.com> Thu, 31 March 2011 12:27 UTC

Return-Path: <behcetsarikaya@yahoo.com>
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 7B8F428C108 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.088
X-Spam-Level:
X-Spam-Status: No, score=-3.088 tagged_above=-999 required=5 tests=[AWL=1.511, BAYES_00=-2.599, GB_I_LETTER=-2]
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 elbaVfPHhnuv for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:27:03 -0700 (PDT)
Received: from nm19.bullet.mail.sp2.yahoo.com (nm19.bullet.mail.sp2.yahoo.com [98.139.91.89]) by core3.amsl.com (Postfix) with SMTP id 5167D3A6AFA for <ipv6@ietf.org>; Thu, 31 Mar 2011 05:27:03 -0700 (PDT)
Received: from [98.139.91.64] by nm19.bullet.mail.sp2.yahoo.com with NNFMP; 31 Mar 2011 12:28:43 -0000
Received: from [98.139.91.21] by tm4.bullet.mail.sp2.yahoo.com with NNFMP; 31 Mar 2011 12:28:43 -0000
Received: from [127.0.0.1] by omp1021.mail.sp2.yahoo.com with NNFMP; 31 Mar 2011 12:28:42 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 993316.38435.bm@omp1021.mail.sp2.yahoo.com
Received: (qmail 93817 invoked by uid 60001); 31 Mar 2011 12:28:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1301574522; bh=/qef+yeFEjw0iwPbHa+F/nuiePsXHrCwOAVLFwPls4A=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ZAVqfz56TaWiLQsgwpsXqbqB7kugt9FLDn+gC++10FAi2+VtkjkOoI5gR9n2lmsrnAtXCxbGvRYYJe3G13n8dGca29XkG7QcvW1l4DbzNT6U1+11rl8cI7f3Gge4crZeZ/hyi3VqTl464Jp4OdWEGAw2yaCWhfuZpoqF6SLaKZ0=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=a+od5vZfstVo9x68Bf2fINF7BO2FN2jRHBQowf41PFzHLG6oykMwcuQfiKRD0cmajQmdstptxRCwIEEM+MsmKVrMywiVHmfc/CXXIRDvpyC6Whg5K9V8tmYpSnUtoEQvJsMFIDTlqG1vJaE1STW5VeOUcbsKf09cOmk9oqLk8LA=;
Message-ID: <575406.83799.qm@web111414.mail.gq1.yahoo.com>
X-YMail-OSG: 8A8Ufk8VM1k7q34dhaoDWffFxdwy3eeBbmzXTKFvcLXfvfe QAppw0e_mJPTyez4QhgJn6EvAAmr.slA.JgHH76bhxlbAVxC7t3.WrD1jtyM qfQiCm5tqWi7bdlrpa9tE0M7ce2MLBQC5euhVUBbsk_zlISPN9PtJU6VfLO6 aZP2xzRfciD3A_hjVkMYEIByks3UhWO5zwj4fmetqnV.i7pGgUhHesn_hklR ELfjUqVErX7pusFUFQ5bADnjHq0M8cEf8R3t92NYkNPuSqkhcNLRmiZOqQBZ RkeWhYn0qPJ6.cMtAdVPYEIYM1ooZxn6iHG5e08p81dWMxwIXDOdSZ_I3Eqx Y2h27b28v0tKMsTaE8LsO7Ga50zhwH378odYyC42Ll0WTSmjk9GbHfmKanMB hTNkgKjOoKL8-
Received: from [130.129.68.193] by web111414.mail.gq1.yahoo.com via HTTP; Thu, 31 Mar 2011 05:28:42 PDT
X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.109.295617
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <4D94446C.40008@inria.fr>
Date: Thu, 31 Mar 2011 05:28:42 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: Vehicle's VIN in IPv6.
To: Thierry Ernst <thierry.ernst@inria.fr>, ipv6@ietf.org
In-Reply-To: <4D94446C.40008@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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 12:27:04 -0000

I think the idea here is to use VIN as link layer id when assigning an 
address/prefix to a host in the car. The host can provide such an id in DHCP 
request message.

Regards,

Behcet

> Dear all,
> 
> I fail to see why a VIN would be mapped to an IPv6 address as  much as I fail 
>to see why a passport number would be mapped to an IPv6 number.  As said by 
>Scott, the purpose of the IP address is to forward packets to the  destination.
> 
> Such an idea is going against location privacy. To address  the location 
>privacy issue related to the ID of the vehicle used at the  networking layer, 
>the Car-to-Car Communication Consortium propose to use  pseudonyms; when it goes 
>to IPv6 communications (all communications are not  IP-based) this pseudonym is 
>used to configure an IPv6 address, i.e. a transient  address (you can check the 
>work of the SeVeCom project). In the meantime, the  vehicle also has a permanent 
>address (indeed, prefix) as which the vehicle is  reachable (using NEMO). Up to 
>now, there is no one in any of the standardisation  or consortium I know (ETSI 
>TC ITS, ISO TC204, ISO TC22, CEN TC278, Car2Car  Communication Consortium) who 
>is thinking about mapping a vehicle ID to the IPv6  address.
> 
> So, I'm afraid this idea is going  nowhere.
> 
> Regards,
> Thierry Ernst.
> 
> On 31/03/11 10:40, Scott Brim  wrote:
> > Hello Radek.
> > 
> > I have privacy concerns, because  the VIN is permanent for the vehicle.
> >   I suspect there is a good  chance that the vehicle's IP address will
> > not be used just for  diagnostics, but also for general purpose
> > connections to the Internet  (for example fetching a movie for the
> > children).  If an IP address  is based on VIN, then it will never
> > change, ever.  It will be  possible for observers to build up
> > information about what the vehicle's  users like to connect to.
> > 
> > Also, if you are a diagnostic center  and you receive packets from an
> > IP address claiming to have a particular  VIN number, how do you
> > authenticate it?  How do you know that is  really the vehicle it claims
> > to be?  You will need application  layer authentication in any case.
> > 
> > I believe it would be much  better to decouple "vehicle identification"
> > from "IP layer location"  (the IP address).  These tokens have
> > different purposes.  The  vehicle identification is for use with
> > database applications and  diagnostic applications, while the IP
> > address is for IP forwarding to  know how to reach the vehicle.  You
> > could possibly allow the  vehicle to connect to the network and get any
> > IP address -- any address  at all -- and then connect to the diagnostic
> > center and tell you its VIN  and authenticate, all in a higher layer
> > protocol.
> > 
> >  2011/3/30 Radek Wróbel<radoslaw.wrobel@pwr.wroc.pl>;:
> >>  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 (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.
> >> 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
> >> 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
> >  --------------------------------------------------------------------
> 
>