Re: Vehicle's VIN in IPv6.

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 31 March 2011 12:51 UTC

Return-Path: <alexandru.petrescu@gmail.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 4F6A33A6B3C for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.72
X-Spam-Level:
X-Spam-Status: No, score=-4.72 tagged_above=-999 required=5 tests=[AWL=0.879, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
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 N9S6t61V9q+u for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:51:13 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 964E33A6B12 for <ipv6@ietf.org>; Thu, 31 Mar 2011 05:51:12 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1936531wwa.13 for <ipv6@ietf.org>; Thu, 31 Mar 2011 05:52:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; 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=NE9p0r8MKbIbg/QT5V9YOdfOXo7f5f2vFMInjTbcsZk=; b=jngYOpnXI1XTBZk4WiQQpLkuJV/HTKK5UORo1u+rkQ/IAsa6sjyFOWfkxEMqv25RF5 xDa+3c7GZSVfrBPP3SKLhS0R7hBt1eBTs3rly4qavq9oIq7vUMWbyWEJLAiWMTo907/Y IL32RqrqTC8EeTtOaNkLuLBgg0CBpuVsRISb8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=QzC5mJgpecfOY2ODSQObhkSQVqvEq2Q7+DN87Ske14mYofRU3+LL0/dH3Y4CAmZsZ6 GBbgYW/dNsONkjXWjACXlR48IT+F3alFZNjDOR9NVLTqt27BSiyiHPH/eb58KNHzJaxI CmMGMwHzdARKIcB67GOompTerAb5axPxgEkqU=
Received: by 10.216.143.74 with SMTP id k52mr2087295wej.8.1301575971676; Thu, 31 Mar 2011 05:52:51 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id ed10sm636372wbb.15.2011.03.31.05.52.49 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 05:52:50 -0700 (PDT)
Message-ID: <4D94791F.1010709@gmail.com>
Date: Thu, 31 Mar 2011 14:52:47 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <4D94446C.40008@inria.fr> <575406.83799.qm@web111414.mail.gq1.yahoo.com>
In-Reply-To: <575406.83799.qm@web111414.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Behcet Sarikaya <behcetsarikaya@yahoo.com>, 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 12:51:15 -0000

hmm... sounds as there would be a VIN-specific link layer? (not ieee 
ethernet, not usb, not bluetooth)?  Which is that?

Alex


Le 31/03/2011 14:28, Behcet Sarikaya a écrit :
> 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
>>>   --------------------------------------------------------------------
>>
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------