Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 dynamic change of MAC addresses refs

[Alexandre Petrescu <[e-mail]>]

Le 11/02/2017 à 05:28, Dick Roy a écrit :
> There are still problems with the text.  First 802.11p is NOT a
> standard and no longer exists (trivial point, but nonetheless true).

This will get fixed in -01 version, some time next week.

> Second, fixed MAC addresses have been proven to pose a privacy risk
> (remember the trash cans in London!).  There is work ongoing in 802
> and other place on this issue (see for example IEEE 802c which is
> currently in ballot). I would replace this entire paragraph with a
> simple statement that tumbling of MAC addresses in the local address
> space is one of the mechanisms used to address the privacy issue
> where it arises (see IEEE 1609 ...)

Please propose text.

Alex

>
> Cheers,
>
> RR
>
> -----Original Message----- From: Alexandre Petrescu
> [mailto:[e-mail]] Sent: Friday, February 10, 2017
> 2:08 AM To: [e-mail] Subject: [ipwave]
> draft-ietf-ipwave-ipv6-over-80211ocb-00 dynamic change of MAC
> addresses refs
>
> draft-ietf-ipwave-ipv6-over-80211ocb-00 dynamic change of MAC
> addresses refs
>
> Hello IPWAVErs,
>
> We received a comment about the text describing the need for
> dynamically changing the MAC addresses for privacy reasons.
>
> The old text being commented is the following:
>> o	In vehicular communications using 802.11p links, there are
>> strong privacy concerns with respect to addressing.  While the
>> 802.11p standard does not specify anything in particular with
>> respect to MAC addresses, in these settings there exists a strong
>> need for dynamic change of these addresses (as opposed to the
>> non-vehicular settings - real wall protection - where fixed MAC
>> addresses do not currently pose some privacy risks).  This is
>> further described in section Section 8.
>
> The new next is:
>> [same] and in function addressed in IEEE 1609.3, clause 5.5.1 and
>> IEEE 1609.4, clause 6.7.
>
> Alex
>
>
>