IETF Logo Mail Archive

Re: Vehicle's VIN in IPv6.

Roland Bless <roland.bless@kit.edu> Thu, 31 March 2011 09:37 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 6E64E3A6AFA for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.272
X-Spam-Level:
X-Spam-Status: No, score=-6.272 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, 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 a5u5j-nXL17G for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:37:26 -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 0376D3A6949 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:37:23 -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 1Q5ELB-0000qq-79; Thu, 31 Mar 2011 11:39:02 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 829102C6; Thu, 31 Mar 2011 11:41:51 +0200 (CEST)
Message-ID: <4D944BB0.5080900@kit.edu>
Date: Thu, 31 Mar 2011 11:38:56 +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: Thierry Ernst <thierry.ernst@inria.fr>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <4D94446C.40008@inria.fr>
In-Reply-To: <4D94446C.40008@inria.fr>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="ISO-8859-1"
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 1301564342.802590000
Cc: 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 09:37:27 -0000

Hi Thierry,

On 31.03.2011 11:07, Thierry Ernst wrote:
> 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

There may be scenarios where it may be useful to uniquely address
a particular car, e.g., for (remote) diagnosis, remote unlocking
services etc. However, doing this by statically mapping the VIN to an
IPv6 address (either into the IID part or the network prefix part)
is for several reasons not a great idea.

> Such an idea is going against location privacy. To address the location

Yep.

Regards,
 Roland

v2.23.0 | Report a Bug | By Email