Find a replacement for sourceGUID

hrishiballal commented 6 years ago

Originally reported by Hrishikesh Ballal (Bitbucket: hrishiballal, GitHub: hrishiballal)

There are a few open questions around sourceGUID, How will sourceGUID will be managed?

Most sensors have a MAC address that gives it uniqueness and therefore
- How to accommodate sensors without MAC addresses?
16-bytes gives you a lot of sources, are they enough?
GUID has to be sent with every transmission
- Is the tradeoff worth it? With very large UVIN?
Some of these sensors will be in the air.
- GUID + Lat + Lon is a good unique stamp.
We leave GUID as it is as a start, need to keep a eye on it.

Bitbucket: https://bitbucket.org/hrishiballal/airtraffic-data-protocol-development/issue/1

overlandla commented 5 years ago

Maybe aggregate sourceGUID-collections that come from some trusted/known source?

hrishiballal commented 5 years ago

@overlandla Thank you for your message, yes that is a good idea, but how to know which source should be trusted? Maybe its possible in a InterUSS environment but how about otherwise?

gutma-org / airtraffic-data-protocol-development

Find a replacement for sourceGUID #1