Skip to main content
  • 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
  • IETF email infrastructure transition planned for 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) is scheduled for 11 September 2026 starting at 2200UTC, with message delivery delayed up to 60 minutes. Further updates will be provided closer to the transition.

    28 Aug 2026
  • Post-Quantum Authentication: Up Next

    Post-quantum key establishment has moved from standards into deployment. Post-quantum authentication has not moved nearly as far, and specification work is no longer the only constraint. The IAB is holding a workshop in Prague on 11 and 12 October 2026 to bring deployment experience together with the people working on the relevant protocols and standards.

    27 Aug 2026
  • IETF 126 post-meeting survey: what we heard

    The IETF 126 Vienna meeting was held 18-24 July 2026 and the results of the post-meeting survey are now available.

    27 Aug 2026
  • Meet our new IETF NOC Lead

    Joe Clarke has been appointed as the new IETF NOC Lead and in this post Joe introduces himself and sets out his priorities for the IETF Network.

    10 Aug 2026

Filter by topic and date

Filter by topic and date

New working group aims to make spotting unwanted trackers easier

14 Mar 2024

Location-tracking accessories provide numerous benefits to users, such as being able to find where they left their keys. But they can also have security and privacy implications if used for malicious purposes. A newly formed IETF working group has taken on the task to standardize a protocol that protects people against being unknowingly tracked.

The newly-chartered Detecting Unwanted Location Trackers (DULT) working group was formed after intense discussions across two Birds of a Feather sessions.

DULT

While the working group goals may seem straightforward, the technical issues involved in defining a protocol that enables implementation across multiple device manufacturers require careful consideration. For example, the working group will consider mechanisms to ensure that devices that do not correctly implement or adhere to the DULT protocol can be detected and excluded from being trackable via crowdsourced location networks.

And, of course, the mechanisms specified by the WG must be designed to not create new vectors for user tracking.

The complete charter for the DULT working group provides further detail about how it will go about its work. For example, the charter calls for the working group to to work with gender-based violence experts throughout development of the protocol. The combination of the trauma-informed expertise with the technical knowledge will be an important aspect to address these specific threat models. Since most of the existing tracking accessories use Bluetooth, the DULT WG will coordinate, as needed, with the Bluetooth SIG and IETF 6lo WG

While the WG will aim to minimize hardware changes needed in tracking accessories to implement this protocol, it will also aim to not preclude adoption by manufacturers of larger devices whose primary purpose is not location tracking, but have location tracking capabilities (e.g., headphones, bicycles, and smartphones).

The DULT working group will meet for the first time at the upcoming IETF 119 meeting.


Share this page