CAAs [1] worldwide have initiated rule making for UAS [2] RID [3]. The US FAA [4] has published a NPRM [5]. CAAs currently promulgate performance-based regulations that do not mandate specific techniques, but rather cite industry consensus technical standards as acceptable means of compliance. One key standard is ASTM WK65041 [6]. Network RID defines a set of information for UAS to make available globally indirectly via the Internet. Broadcast RID defines a set of messages for UA [7] to send locally directly one-way over Bluetooth or Wi-Fi. WK65041 addresses how to neither populate/query registries, ensure trustworthiness of information nor make it instantly useful. TM-RID’s goal is to make RID immediately actionable, in both Internet and local-only connected scenarios, especially emergencies, in severely constrained UAS environments [8], balancing legitimate (e.g. public safety) authorities’ Need To Know trustworthy information with UAS operators’ privacy. To accomplish this, TM-RID will liaise with SDOs [9] and complement their standards with IETF work to meet this urgent need. An Applicability Statement RFC for UAS RID, showing how to use IETF standardized technologies for this purpose, will be a central work product. Technical Specification RFCs will address any necessary enhancements of specific supporting protocols. TM-RID potentially could be applied to verifiably identify other types of registered things reported to be in specified physical locations, but the urgent motivation and clear initial focus is UAS. One possible approach leverages Internet domain name registration business models, infrastructure and standards, including EPP [10], RDAP [11] and DNS [12], plus the HIP [13] HIT [14], with UTM [15] system USS [16] as registries. This provides stronger privacy and authenticity than other FAA NPRM / ASTM standard UAS ID Types (static manufacturer assigned hardware serial number per [17] or dynamic single-use USS assigned UUID [18]), but would necessitate several HIP enhancements (all with applicability beyond UAS RID); prototypes using DNS to reverse lookup UAS RID information from a broadcast HIT have been successfully flown. Any comprehensive approach should – * Verifiably identify all entities in the UTM ecosystem – UA, GCS [19], observer devices, registries, USS, et al – presumably using public key operations to: - prove ownership of the claimed ID; - authenticate other claims made via RID (e.g. location) as signed by the owner of that ID; and - provide observers [w/o Internet connectivity] locally verifiable proof that ID is in a known registry. * Enable all observers to use a received ID to look up minimal public information. * Enable only strongly authenticated, policy authorized observers to look up more extensive private information (including operator PII [20]) needed for legitimate (e.g. public safety or security) purposes in access controlled registries (e.g. as with Internet domain names [21]). Acronyms and references: [1] Civil Aviation Authority [2] Unmanned Aircraft System[s] [3] Remote Identification [4] United States Federal Aviation Administration [5] Notice of Proposed Rule-Making https://www.federalregister.gov/documents/2019/12/31/2019-28100/remote-identification-of-unmanned-aircraft-systems [6] ASTM International F38 Committee Work Item WK65041 “Standard Specification for UAS Remote ID and Tracking” https://www.astm.org/DATABASE.CART/WORKITEMS/WK65041.htm [7] Unmanned Aircraft [8] UAS Identification and Tracking Aviation Rulemaking Committee Recommendations Final Report 2017 SEP 30 https://www.faa.gov/regulations_policies/rulemaking/committees/documents/media/UAS%20ID%20ARC%20Final%20Report%20with%20Appendices.pdf [9] Standards Development Organizations including American National Standards Institute (ANSI), ASTM International (formerly American Society for Testing and Materials), Consumer Technology Association (CTA), International Civil Aviation Organization (ICAO), RTCA (formerly Radio Technical Commission for Aeronautics), et al [10] Extensible Provisioning Protocol [11] Registry Data Access Protocol [12] Domain Name System [13] Host Identity Protocol [14] Host Identity Tag [15] UAS Traffic Management [16] UAS Service Supplier[s] [17] ANSI/CTA-2063-A https://standards.cta.tech/apps/group_public/project/details.php?project_id=587 [18] Universally Unique Identifier, e.g. RFC 4122 [19] Ground Control Station[s] [20] Personally Identifiable Information [21] https://www.arin..net/resources/registry/whois/rdap/ [22] Hierarchical HIT [23] Overlay Routable Cryptographic Hash Identifier [24] Host Identity