[Unwanted-trackers] Crowd-source locating trackers

[Robert Moskowitz <[e-mail]>]

This is a follow up of last nights IETF119 session (well last night for 
me!).

One of the documents to comment per one of the last slides was on 
crowd-source discovery? of trackers.

I do not see such a draft the wg document page on datatracker. Where 
will I find it?

draft-detecting-unwanted-location-trackers-01 mentions crowd-source 3 
times but does not have any content on the matter.

Note that I have written a crowd-source HARVESTing draft for Uncrewed 
Aircraft:

https://datatracker.ietf.org/doc/draft-moskowitz-drip-crowd-sourced-rid/

Now this is a bit of an inverse problem.  To get information about UA 
into the UAS Traffic Management (UTM) system.  For all UA: those that 
play fair (by some definition of fair) and those that do not (use 
something like LIDAR).

There are already commercial proprietary solutions, I know of one that 
uses MQTT for the Finder to communicate to the Surveillance Service 
Provider (yes this is an official term used).  I really don't think MQTT 
is the right tool here.

Multilateration is expect to be used as even if the UA is playing fair 
and reporting its location, consumer grade GPS systems on the UA 
altitude can be off by 15M! (it is the ionsphere's fault!).  So the UA 
may be reporting it is way overhead or in the ground, but can you get 
decent GPS location from the cellphone (E911 location accuracy blocked 
from non-E911 app by FCC regulations on privacy concerns).  We have 
spent MONTHS discussing (debating with FAA who is a proxy for other 
agencies) location accuracy and format for reporting in ASTM.  You 
probably don't have as much of a similar issue with tracker devices?

Anyway, there is one implementation of my draft being tested at a DoD 
location.  I know of one other in development.  But then DULT's 
crowd-sourcing approach may be way different, but I might think there is 
a common Finder to Surveillance protocol that we both can use.

I really don't want to use Github.  I have never really gotten Github; 
this old dog is not really groking that trick.  Mailing lists and draft 
repositories is what I use...

So, I can lend a hand on this subject and like I indicated, there may be 
a common protocol (and common location challenges) here.

Bob Moskowitz