Standards
OASA adopts or extends existing standards (MAVLink, Cursor-on-Target (CoT), DroneCAN, ROS 2, Meshtastic) before writing new ones. Where no good standard exists, OASA publishes its own open spec. Standards use proven encryption methods; OASA defines how to apply them to drone links, not new encryption math.
Stages
Section titled “Stages”- Idea: the Technical council accepts the proposal.
- Draft: at least one working prototype.
- Candidate: two independent implementations that work together.
- Security review: passes red team and Security council review.
- Stable.
- Deprecated: a migration path is published.
Every standard includes
Section titled “Every standard includes”Purpose and scope, the spec, a security section, an open reference implementation, a test suite, and a version and change log.
Versioning
Section titled “Versioning”Major versions are breaking. Minor versions add compatible features. Old majors stay supported for a set period.
People
Section titled “People”A standard editor and a working group. The Technical council approves stages, and the Security council signs off before Stable. Anyone can comment on drafts. Members write them.
Planned standards
Section titled “Planned standards”| Standard | Covers |
|---|---|
| OASA-SEC | Encryption, pairing, keys |
| OASA-MAP | How systems appear on TAK |
| OASA-NET | Mesh networking and routing |
| OASA-PAY | Payload interface |
| OASA-LOG | Logs and black box data |
| OASA-TIME | Time sync |
| OASA-VID | On-demand video over mesh |
| OASA-DOCK | Dock, landing and charging |
| OASA-RF | Antenna and radio test procedures |
| OASA-SENSE | Low-power sensor nodes |
Build order for the first six: SEC, MAP, NET, PAY, LOG, TIME.
Certification
Section titled “Certification”- OASA Compatible: passes the test suite. The product may be proprietary.
- OASA Open: passes the test suite and is fully open.
Testing is free. Integration help from OASA is paid work through OASA Engineering.