On 1/7/14, 10:59 PM, "Eliot Lear" <[email protected]> wrote:
> >On 1/8/14 7:52 AM, Stefan Winter wrote: > >> In short: MAC addresses are NOT necessarily local to the LAN; if they >> leak beyond, privacy is at risk. The LAN may be IEEE's domain; protocols >> that transport information about MAC addresses on the layers above are >> most certainly IETF work. So Š this year as we introduce Œephemeral MAC addresses¹ into 802.11. The IETF should be prepared to fix upper layers as they break :-) The simplest change is for hourly or daily changes of a link local MAC address. This breaks the long term tracking and any usage of MAC address for authentication. Longer term, the ephemeral address could be bound to an authentication process. My favored key centric approach would be mac_address = h(pk, nonce)[:6] | 0x800000000000 # upper 6 octets with bitwise to set link local Paul >> >> > >Indeed. Mac addresses are also found in location registrations for some >services. > >Eliot >_______________________________________________ >perpass mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/perpass _______________________________________________ perpass mailing list [email protected] https://www.ietf.org/mailman/listinfo/perpass
