Skip to main content
  • Suggested IETF 127 Sessions for Getting Familiar with New Topics

    These IETF 127 meeting sessions are likely to include discussions and proposals that are accessible to a broad range of Internet technologists whether they are new to the IETF or long-time participants.

    30 Oct 2026
  • New features for RFC-Editor.org

    Several new features implemented on RFC-Editor.org aim to make the site more useful and engaging for RFC consumers.

    30 Sep 2026
  • IETF email infrastructure transition completed on 11 September

    A transition to a new modern, modular, and containerized infrastructure for email services provided for ietf.org, iab.org, irtf.org, rfc-editor.org (including email lists) was completed on 11 September 2026.

    11 Sep 2026
  • Survey to gather input on ISE selection criteria

    The survey to gather input for Independent Series Editor (ISE) selection criteria survey is live and we welcome your input on the capabilities and expectations the Internet Architecture Board (IAB) should consider when selecting a future ISE.

    10 Sep 2026
  • IETF 126 Highlights

    The IETF 126 meeting was held 18–24 July 2026 at the Hilton Vienna Park in Vienna, Austria, and online, hosted by Cisco. The week included the IETF Hackathon and Code Sprint, the New Participants' Program, five Birds-of-a-Feather (BoF) sessions, and more than 100 working group and research group sessions. The Applied Network Research Workshop also took place during the IETF 126 meeting week.

    1 Sep 2026

Filter by topic and date

Filter by topic and date

MAC Privacy

15 Nov 2014

This week at IETF91 we carried out an experiment to randomize Wi-Fi MAC addresses of users to improve privacy.

MAC addresses used in over-the-air communications by protocols such as the IEEE 802.11 WLAN have been identified as privacy risks that expose individuals to unauthorized tracking. As part of the joint collaboration between IAB/IESG and IEEE 802, and the work carried out by the IEEE 802 EC Privacy SG, an experiment was suggested to assess implications of MAC address changes on Layer 2 and Layer 3 protocols.

A parallel network was setup for this experiment. An ietf-RandPrivMAC SSID was broadcast during the meeting and users were asked to run some scripts in their laptops to randomize their MAC address when connecting to this network. The network was isolated from the rest of the IETF meeting by means of using a different VLAN with separate DHCP and switching infrastructure. Statistics were captured and a detailed analysis will be performed over the next few days. Nevertheless, preliminary observations show that several client drivers support this technique, no major changes are required on the network configuration, and the probability of address duplication in a network like this is negligible. This is the first time we try this technique outside the lab, and now that we know more what to expect we can fine tune the setup in the future to have a better understanding of the different practical implications.

IETF is the best place to carry out an experiment like this, as users are not only willing to participate, but also provide active support and very smart observations. We received a number of suggestions about how to make the experiment more interesting, from adding support for more client devices to providing guidelines about improving DHCP allocations and usage of MAC addresses in IEEE protocols. The IETF NOC team was instrumental and extremely helpful before and during the experiment. Overall, this has been an excellent learning experience and we believe it is a first step in the right direction to provide better privacy for users of this widespread technology.

Juan Carlos Zuniga


Share this page