Session Date/Time: 06 Nov 2023 12:00

dult

Summary

This Birds of a Feather (BoF) session focused on detecting unwanted location trackers. The main goals were to review the proposed system architecture, discuss the charter, and determine if there's sufficient community agreement and interest to form a working group within the IETF. Key discussions revolved around the scope of the working group, particularly whether it should include a standardized definition or baseline algorithm for "unwanted tracking" detection, client authentication, and addressing privacy and security considerations, including potential harms to survivors of abuse. A vote was taken, and there was overwhelming support for forming a working group.

Key Discussion Points

Scope of "Unwanted Tracking" Detection: A central point of debate was whether the working group should define a standardized algorithm or guidance for detecting unwanted tracking, or focus solely on the underlying signals and protocols. Concerns were raised that excluding detection would render the group's work less useful and potentially introduce problems with false positives and implementation inconsistencies across different platforms.
Client Authentication: There was a discussion about requiring client authentication for trackers participating in the network to prevent unauthorized devices from using the network and potentially engaging in malicious activities.
Privacy and Security Considerations: Participants emphasized the importance of considering privacy and security implications, including potential harms to survivors of intimate partner violence and the need to avoid creating new tracking vectors. Engagement with advocacy groups and experts in gender-based violence was strongly encouraged.
Evidence of Efficacy: A call was made for the working group to demonstrate the efficacy of its proposed solutions in reducing harm before publishing RFCs. This sparked debate about how to measure efficacy and what constitutes sufficient evidence.
Device Scope: Clarification was sought on the types of devices considered in scope. The consensus was to focus on accessories with low inherent location capabilities, excluding phones, tablets, watches, and laptops.
Legacy Device Handling: Ensuring that the protocol can properly detect and act on devices that cannot be firmware updated

Decisions and Action Items

Charter Modifications: The chairs and document editors will incorporate the following changes into the charter:
- Incorporate Ecker's suggestion on baseline algorithms
- Expand the background section to acknowledge the existence of tracker networks and highlight the gap being addressed.
- Add a requirement for client authentication, expressed as a desired security property rather than a specific mechanism.
- Add a statement about working with abuse advocacy groups
- Add language requiring a global perspective
- Clarify the role of the IETF and it's members to solve for the need that all devices should not be tracked, and provide better on/off controls
Next Consensus Call: The revised charter will be circulated to the mailing list for a final consensus call before submission to the IESG.

Next Steps

The chairs will refine the charter based on the feedback received during the BoF session and circulate it to the mailing list.
After the charter is available, another consensus call will be announced.
Once consensus is confirmed, the charter will be submitted to the IESG for consideration.