Re: Vehicle's VIN in IPv6.

Brian Haberman <> Thu, 31 March 2011 12:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6A2953A6952 for <>; Thu, 31 Mar 2011 05:58:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gocKZWzhord9 for <>; Thu, 31 Mar 2011 05:57:59 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id ABDA33A6914 for <>; Thu, 31 Mar 2011 05:57:59 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTP id 9A2FF8826A for <>; Thu, 31 Mar 2011 05:59:39 -0700 (PDT)
Received: from (unknown []) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTP id C1524130002 for <>; Thu, 31 Mar 2011 05:59:38 -0700 (PDT)
Message-ID: <>
Date: Thu, 31 Mar 2011 08:59:37 -0400
From: Brian Haberman <>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv: Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <>
In-Reply-To: <>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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 12:58:00 -0000

On 3/31/11 4:40 AM, 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

This made me immediately think of HIP with the VIN being used as the
Host Identifier.

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