[{"author": "Robert Moskowitz", "text": "<p>Whoever that is lying down, it is 4am here...</p>", "time": "2025-03-20T08:00:19Z"}, {"author": "Kathleen Moriarty", "text": "<p>4AM here too!</p>", "time": "2025-03-20T08:01:56Z"}, {"author": "Sean Turner", "text": "<p>thanks to all those who got up early / stayed up late. I know it can be tough.</p>", "time": "2025-03-20T08:04:33Z"}, {"author": "Jonathan Hoyland", "text": "<p>So thinking of modified tags, could I set up a tag that only powers on once every hour, such that it wouldn't look like it was consistently following someone?</p>", "time": "2025-03-20T08:09:23Z"}, {"author": "Eric Rescorla", "text": "<p>I mean once you can modify the tags, you just  randomize the identifers</p>", "time": "2025-03-20T08:10:01Z"}, {"author": "Eric Rescorla", "text": "<p>Or rather rotate very quickly</p>", "time": "2025-03-20T08:10:53Z"}, {"author": "Jonathan Hoyland", "text": "<p>Sure, but that's a much harder modification than a timed switch.</p>", "time": "2025-03-20T08:11:00Z"}, {"author": "Eric Rescorla", "text": "<p>Well, that seems fairly easy to counter</p>", "time": "2025-03-20T08:13:05Z"}, {"author": "Alexis Hancock", "text": "<p>I have always approached this with the component of the added ease of deploying compliant trackers for unwanted use vs. modified or created trackers.</p>", "time": "2025-03-20T08:13:09Z"}, {"author": "Jonathan Hoyland", "text": "<p>Does it help if the tag can't be disposed of? I'm not going to want to throw away my laptop?</p>", "time": "2025-03-20T08:15:55Z"}, {"author": "Dan Sexton", "text": "<p>Is knowing which device(s) a tracker is paired to required to detect/find/disable a tracker? (per the high level requirements)</p>", "time": "2025-03-20T08:20:43Z"}, {"author": "Eric Rescorla", "text": "<p>So here is what Apple currently provides:     Serial number or device ID</p>\n<div class=\"codehilite\"><pre><span></span><code>Last four digits of the phone number or an obfuscated email address of the person who registered it. This can help you identify the owner, if you know them.\n</code></pre></div>", "time": "2025-03-20T08:20:53Z"}, {"author": "Eric Rescorla", "text": "<p>So it's not phrased in terms of paired devices</p>", "time": "2025-03-20T08:21:10Z"}, {"author": "Maggie Delano", "text": "<p>got it thanks</p>", "time": "2025-03-20T08:24:11Z"}, {"author": "Alexis Hancock", "text": "<p>Agreed</p>", "time": "2025-03-20T08:25:25Z"}, {"author": "Alexis Hancock", "text": "<p>This was Eva's elaboration:<br>\nThat would be fine. I just want to make sure that if a tag is reporting to multiple accounts that the person who is being followed by the tag has a way of knowing how many and having the same data about all of the accounts.</p>", "time": "2025-03-20T08:27:06Z"}, {"author": "Alexis Hancock", "text": "<p>If that helps</p>", "time": "2025-03-20T08:27:12Z"}, {"author": "Maggie Delano", "text": "<p>thanks</p>", "time": "2025-03-20T08:29:12Z"}, {"author": "Eric Rescorla", "text": "<p>Refreshing my memory, S 3.16.1 of the accessory protocol document covers this. It seems like if anything needs to change, it's a sentence that says \"if there are multiple owners, then this information shall be available for all of them\"</p>", "time": "2025-03-20T08:29:14Z"}, {"author": "Alexis Hancock", "text": "<p>Noted ^</p>", "time": "2025-03-20T08:30:48Z"}, {"author": "Maggie Delano", "text": "<p>Yes, would the protocol want to forbid different accounts pairing with a tag?</p>", "time": "2025-03-20T08:31:18Z"}, {"author": "Maggie Delano", "text": "<p>(or do we want to allow family sharing/)</p>", "time": "2025-03-20T08:31:30Z"}, {"author": "Eric Rescorla", "text": "<p>The tags <em>do</em> have rotating MAC addresses</p>", "time": "2025-03-20T08:35:40Z"}, {"author": "Dan Sexton", "text": "<p><span class=\"user-mention silent\" data-user-id=\"5796\">Maggie Delano</span> <a href=\"#narrow/stream/375-dult/topic/ietf-122/near/158756\">said</a>:</p>\n<blockquote>\n<p>Yes, would the protocol want to forbid different accounts pairing with a tag?</p>\n</blockquote>\n<p>Is the risk that a victim is being tracked by their own tag? (e.g., a tag is registered to both victim and attacker) - and would it be classed as an unwanted tracker at that point or would it be out of scope?</p>", "time": "2025-03-20T08:44:01Z"}, {"author": "Eric Rescorla", "text": "<p>Thanks, Maggie, for pointing out that there is a slight additional risk, which is that if I <em>steal</em> the tag I can put it in separated mode, but with only temporary access I can look up the serial number without having it for 24 hrs</p>", "time": "2025-03-20T08:49:07Z"}, {"author": "Brent Ledvina", "text": "<p>This is what's in the accessory protocol document right now: \"When in near-owner state, the accessory SHALL rotate its address every 15 minutes. This is a privacy consideration to deter tracking of the accessory by non-owners when it is in physical proximity to the owner.\"</p>", "time": "2025-03-20T09:08:47Z"}, {"author": "Brent Ledvina", "text": "<p>\"When in a separated state, the accessory SHALL rotate its address every 24 hours. \"</p>", "time": "2025-03-20T09:09:08Z"}, {"author": "Eric Rescorla", "text": "<p>Sorry, 15 minutes</p>", "time": "2025-03-20T09:10:22Z"}, {"author": "Eric Rescorla", "text": "<p>Thanks!</p>", "time": "2025-03-20T09:10:24Z"}, {"author": "Maggie Delano", "text": "<p>thanks Siddika!</p>", "time": "2025-03-20T09:10:32Z"}, {"author": "Eric Rescorla", "text": "<p>So, here is the relevant portion of the finding document <a href=\"https://www.ietf.org/archive/id/draft-ietf-dult-finding-00.html#section-4.2\">https://www.ietf.org/archive/id/draft-ietf-dult-finding-00.html#section-4.2</a></p>", "time": "2025-03-20T09:10:37Z"}, {"author": "Erica Olsen", "text": "<p>Thank you, Maggie and Siddika!</p>", "time": "2025-03-20T09:11:22Z"}, {"author": "Alexis Hancock", "text": "<p>Thank you everyone</p>", "time": "2025-03-20T09:11:30Z"}, {"author": "Brent Ledvina", "text": "<p>Thank you everyone!</p>", "time": "2025-03-20T09:11:37Z"}, {"author": "Kathleen Moriarty", "text": "<p>Thank you!</p>", "time": "2025-03-20T09:11:38Z"}]