IETF Logo Mail Archive

Re: Vehicle's VIN in IPv6.

Jared Mauch <jared@puck.nether.net> Thu, 31 March 2011 15:13 UTC

Return-Path: <jared@puck.nether.net>
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 220C83A69BE for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level:
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599]
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 WdxBtSYkDgpo for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:13:17 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by core3.amsl.com (Postfix) with ESMTP id 257113A680E for <ipv6@ietf.org>; Thu, 31 Mar 2011 08:13:16 -0700 (PDT)
Received: from [10.0.0.137] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.4/8.12.9) with ESMTP id p2VFEnTA067914 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 31 Mar 2011 11:14:50 -0400 (EDT) (envelope-from jared@puck.nether.net)
Subject: Re: Vehicle's VIN in IPv6.
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <4D94791F.1010709@gmail.com>
Date: Thu, 31 Mar 2011 11:14:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <584CBCD9-DDB5-46EE-ABB2-51B6BFDC9D04@puck.nether.net>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <4D94446C.40008@inria.fr> <575406.83799.qm@web111414.mail.gq1.yahoo.com> <4D94791F.1010709@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Thu, 31 Mar 2011 11:14:51 -0400 (EDT)
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 15:13:18 -0000

On Mar 31, 2011, at 8:52 AM, Alexandru Petrescu wrote:

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

This is the same question I have.  What is the communications phy that will interface with the outside world?  I'm sure it's going to be something where there is an existing bit of hardware that requires a ieee ethernet/mac or other addressable interface.  seems like the VIN would be best put in a datagram transmitted over that phy.

- Jared

v2.23.0 | Report a Bug | By Email