Skip to main content

Detecting Unwanted Location Trackers (DULT) / IETF118
bofreq-danyliw-detecting-unwanted-location-trackers-dult-ietf118-01

Document Type Approved BOF request
Title Detecting Unwanted Location Trackers (DULT) / IETF118
Last updated 2024-02-08
State Approved
Editor Roman Danyliw
Responsible leadership Roman Danyliw
Send notices to (None)
bofreq-danyliw-detecting-unwanted-location-trackers-dult-ietf118-01

Name: Detecting Unwanted Location Trackers (DULT)

--[ this entry is a scheduling placeholder for possible WG ]--

Description

The goal of the DULT WG is to standardize an application protocol for information exchange between location-tracking accessories and nearby devices, along with actions that these accessories and devices should take once unwanted tracking is detected. This protocol is intended to protect people against being unknowingly tracked. The intent of this WG is to make it easier for arbitrary devices to detect unwanted tracking by these accessories. The protocols and interactions between devices may be limited to certain states or modes, such as the accessory being separated from a paired/owner device.

DULT BoFs were previously convened at IETF 117 and IETF 118.

A consensus check of a refined charter for a proposed DULT WG is currently underway.

Required Details

  • Status: scheduling placeholder for possible WG
  • Responsible AD: Roman Danyliw
  • BOF proponents: Brent Ledvina <bledvina@apple.com>, Zach Eddinger <zae@google.com>
  • BOF chairs: TBD
  • Number of people expected to attend: 150
  • Length of session (1 or 2 hours): 2 hours
  • Conflicts (whole Areas and/or WGs)
  • Chair Conflicts: TBD
  • Technology Overlap: TBD
  • Key Participant Conflict: TBD

Information for IAB/IESG

To allow evaluation of your proposal, please include the following items:

  • Any protocols or practices that already exist in this space: Proprietary solutions by Apple, Google, Tile, Samsung, Chipolo

  • Which (if any) modifications to existing protocols or practices are required: N/A

  • Which (if any) entirely new protocols or practices are required: See IETF 118 BOF materials
  • Open source projects (if any) implementing this work: N/A

Agenda

TBD