Re: Vehicle's VIN in IPv6.

Brian,

On Mar 31, 2011, at 11:10 AM, Brian E Carpenter wrote:

> I rather like the thought that each BMW will need its own BGP4
> advertisement. Boeing tried that for a while with airplanes, and
> it didn't work out too well.

BGP is overkill :-)  I thought the problem with the Boeing service was largely financial, their BGP based technical solution did work.  At least the number of commercial airplanes isn't too large a number.

They could use a fixed car address and use mobile IPv6 with a provider based address.  

Bob

> 
>    Brian
> 
> 
> On 2011-03-31 22:03, Roland Bless wrote:
>> Hi Radek,
>> 
>> On 30.03.2011 17:31, Radek Wróbel wrote:
>>> 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.
>> 
>> There is already related work for this.
>> You should be aware of a US Patent of 2005 "Method for Setting an
>> Internet Protocol Address using a vehicle identification number".
>> US 2005/0273505 A1, first hit
>> http://www.google.com/patents?q=VIN+IPv6&btnG=Search+Patents
>> (no comment on its usefulness here...)
>> BMW has also recently filed a patent application with a VIN7 to IPv6
>> address mapping.
>> It's not totally clear to me what _problem_ you want to solve.
>> Depending on that several options exist.
>> However, I share the concerns that Scott Brim already expressed in his
>> mail.
>> 
>> Regards,
>> Roland
>> --------------------------------------------------------------------
>> 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
> --------------------------------------------------------------------