Re: Vehicle's VIN in IPv6.

Scott Brim <> Thu, 31 March 2011 09:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CFFD428C186 for <>; Thu, 31 Mar 2011 02:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -103.596
X-Spam-Status: No, score=-103.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4qlNKZvtmiYg for <>; Thu, 31 Mar 2011 02:10:56 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 90EF53A6B00 for <>; Thu, 31 Mar 2011 02:10:55 -0700 (PDT)
Received: by iye19 with SMTP id 19so2508378iye.31 for <>; Thu, 31 Mar 2011 02:12:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=5D0d/MSllTBo5AhOt0B+fSvXtGWHMT3KtkGw96DznXo=; b=wELiNB/Wf+Eql8ha24uHTeKV3D77GSmRn4x+1blIGiaCSYXCBUaX0dqQmNpRqjUvgM j4ZR+8g9zl8T43tde8CnhEJGg95wACCXK03hahsejaUEuPzB5HUtsZfP/qfBGCtWQqlr 93G7qOznkT8Ygrzoot00lzERO0La/E855Gl8Q=
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=f//a+Qp8Px5W/7P8NUixoooOGOF4dRH51XendMaiwkpae44i8ypke9evcMSUrzFcev b0X44BKiLXsX0D9cBgN3c4492MPAnM9rg0rN9mg7S7lYFaBoqWb0c56q0IbdJ3MdjOq0 v01ZP24im0oNQjmHHDQOs12W2K1rMOlKu9Fow=
Received: by with SMTP id a8mr2716004ict.415.1301562755014; Thu, 31 Mar 2011 02:12:35 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Thu, 31 Mar 2011 02:12:14 -0700 (PDT)
In-Reply-To: <>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <> <>
From: Scott Brim <>
Date: Thu, 31 Mar 2011 11:12:14 +0200
Message-ID: <>
Subject: Re: Vehicle's VIN in IPv6.
To: George Michaelson <>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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 09:10:56 -0000

On Thu, Mar 31, 2011 at 10:45, George Michaelson <>; wrote:
> There is a general model here which will re-occur many many times.
> manufacturers have context-specific serial numbers which behave in context like EUI164.
> It is reasonable (from their perspective) to ask if there is an address management function which can suit their context, to exploit IPv6. Perhaps a private overlay network for IPSEC trusted remote upload and download. re-blow your SONY TV on any Internet via a trust path homed inside the manufacturer. 'ET call home' models of device management.

An overlay sure.  One could use IPv6 addresses the way back-to-my-Mac
does.  But I would like it to be clear that

  Internet location


  Endpoint identification for use by applications

are totally different functions and in the long run everything is
easier if they are kept separate.  It's taken us 20 years to get to
the point where we might be able to separate them.  Let's help others
not go through the same learning experience.