Tm-rid -- Drone Remote Identification Protocol | |
|
|
About Tm-rid | |
DRIP’s goal is to specify how RID can be made trustworthy and available in both Internet and local-only connected scenarios, especially in emergency situations. Some UAS operate in environments where the network or the devices or both are severely constrained in terms of processing, bandwidth (e.g., Bluetooth 4 beacon payload is 25 bytes long), or battery life, and DRIP aims to function in these environments. The specifications produced by the WG will need to balance public safety authorities’ need to know trustworthy information with UAS operators’ and other involved parties’ privacy. To see the collection of prior postings to the list, visit the Tm-rid Archives. |
|
Using Tm-rid | |
To post a message to all the list members, send email to
tm-rid@ietf.org.
You can subscribe to the list, or change your existing subscription, in the sections below. |
|
Subscribing to Tm-rid | |
Subscribe to Tm-rid by filling out the following form. You will be sent email requesting confirmation, to prevent others from gratuitously subscribing you. This is a private list, which means that the list of members is not available to non-members. | |
Tm-rid Subscribers | |
|
![]() version 2.1.39 |
![]() |
![]() |