>>>>> "Scott" == Scott Brim <s...@internet2.edu> writes:
    >> So, I have a question: how much privacy is actually contained in
    >> the VIN or indexed by the VIN?   Given that it's printed on the
    >> windshield. Yes, it contains model, year and manufacturer of the
    >> car, but all of that information is also visible by looking at the
    >> vehicle.

    Scott> I figured you knew this already - it's about correlation.  IP
    Scott> addresses, for a familiar example, are not a problem in and of
    Scott> themselves.  However, they are considered personal
    Scott> information, not to

a) This is true of all IP addresses, regardless of how they are derived.

b) In general, we aren't talking about IP addresses that will be used to
   communicate out to the Internet, but rather within a vehicle, and 
   possibly with adjacent vehicles.
   (PLEASE recall, the internet protocol suite  is used for more than
   just the Internet) 

   So, while you can get correlation easily from addresses, you can also
   get them from license plates, and probably a dozen other wireless
   technologies already present in vehicles (like the tire pressure
   systems we keep hearing about)...

What *additional* privacy violation does knowledge of the VIN do?

Or alternatively, what network attacks become possible if you have
knowledge of the VIN, which means that you know what the internal
addresses are?

    Scott> goes to the FBI office in the next town, for example.  Same
    Scott> with a VIN 
    Scott> -- the problem is not exposing the VIN, it's having the VIN be
    Scott> associated with many other personal attributes on open networks.

I'm not convinced that there are any advantages to deriving a
vehicle-specific prefix from the VIN.  It seems that vendors should get
space from the RIRs, and allocate the numbers 1.2.3.4., etc.  
If they want to do this from the VIN, they should do this with a keyed
hash and keep the key private.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     m...@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
        



Attachment: pgpbAHuD7bKGL.pgp
Description: PGP signature

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to