I have the usual concerns about privacy. I have no problem with someone knowing the endpoint that is communicating is associated with a vehicle (or that I, a human, am communicating from a vehicle). However, if someone can map easily from an IP address to a VIN (thus knowing the specific vehicle from which the communication is happening), and I have no choice but to reveal that information in order to communicate at all, I am not comfortable. In general, as an architectural principle, I want the option to control how much personal information I reveal. That's called privacy.
... Scott On 02/18/13 13:49, sofiane Imadali allegedly wrote: > Hello 6MAN folks, > > I would like to announce, on behalf of the co-authors, the submission > of 2 drafts relating to VIN-based IPv6 addressing. > VIN stands for Vehicle Identification Number, and it is specifically > used in a context of IPv6 vehicular communications. These proposals > aim at providing discussion about a new mapping/conversion method from > VIN to ULA prefixes (guaranteed unique) and Interface Identifiers. > > Please find the above mentioned documents at: > 1) Vehicle Identification Number-Based IPv6 Interface Identifier > (VIID), at: http://tools.ietf.org/html/draft-imadali-its-vinipv6-viid-00 > 2) Vehicle Identification Number-Based Unique Local IPv6 Unicast > Addresses (VULA), at: > http://tools.ietf.org/html/draft-imadali-its-vinipv6-vula-00 > > Your comments are welcome, > > Cheers, > Sofiane. > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > [email protected] > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
