Le 19/02/2013 15:40, Brian E Carpenter a écrit :
I do not understand the following:
Bits 55 and 56 that correspond to U/L bits are set accordingly to
the recommendations.
I suppose the reference is to the U and G bits (in positions 6 and 7
in the IID, or 70 and 71 in the IPv6 address, in IETF notation). But
what "recommendations" apply? The description in RFC 4291 refers to
the equivalent bits in an IEEE address, so there is no recommendation
that is relevant to a VIN.
(will check)
Also, I do not wish to broadcast my VIN number to the world. While
VIN numbers are not a big secret, associating my on line transactions
with my car's identity is definitely a big no-no.
YEs, I agree with the concern.
Such a concern would be all the more valid if there were a specification
which said 'each vehicle MUST form its IIDs based on their VINs'. But
this is not the case. We are not trying for such a definitive document.
We are certain that some vehicles will never use this VIN-based
addressing scheme. At that point, someone receiving a packet with a
certain source address will never know whether that packet is from a
vehicle or from something else. A reversal of the IP into a number will
never be sure to be a VIN.
Alex
Regards Brian
--------------------------------------------------------------------
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
--------------------------------------------------------------------
