20191127 Dev Meeting

Agenda

General:

RomanLigocki - Discuss possibility of integrating authentication/encryption into MAVLink 2
- Essentially adding support for public key infrastructure, and packet-payload level encryption.
- Lorenz queried proposal - what sort of timeframes looking at.
- PX4/Firmware#13538: Secure communication in PX4 (Diploma thesis) - proposal from Roman - team to read to see if there is synergy.
Microservices proposal.
- JamesP concerned that proposed mechanism is overly complex/intrusive to toolchain, and that similar result can be achieved using proper MAVLink versioning and existing mechanisms, possibly with better management of service-level XML.
- General discussion on how this might work. At the end:
  - HamishW does not understand how mavlink versioning can deliver what microservices versioning does
  - JamesP still not convinced there "isn't a better way"
  - Lorenz very open to other way that achieves same goals. Happy to meet with JamesP to discuss further.
- ACTION: HamishW to think about this further and raise further options with James next week.
#1176 COMPONENT_INFORMATION - brief diversion into this. Explained that it is a generic way of getting high-level component information and dynamically generating configuration UI. Orthogonal to microservices versioning.

Did not cover

#1264 More support for ICE monitoring
- Asked poster to take PR. As a point of interest, what is trigger to accept vs update dialect message?
#929 No way to transmit airspeed reference
- Propose to close - see comment.
#1234 Add messages for power regulation and temperature status reporting
- FYI, Edwin no longer working on this. Do we close, or wait to see if gets picked up?
Common Flight Modes Microservices
- Action on Lorenz to do first evolution of spec/requirements.
JulianOes discuss "MAVLink connection semantics
#1216 SET_POSITION_HOME: Add frame for local coordinates

See above!