Page History

Wednesday 2021-02-10

MQTT (and general design) discussion

• SSL/TLS setup between MQTT server and MQTT client could have bi-directional authentication (checking also client certificate)
• Authentication method for the initial CONNECT can be any one that client+server both support. 
• One approach is to allow any client to get any MQTT topic, but the data itself is encrypted and then only those who can decrypt have access to the data in practice.
• Another (VISS and other) consider applying filters on the signals (MQTT:topics) that you can actually request.    E.g. Vehicle/Cabin/Temperature.  E.g. Mosquitto plugins can be used for this.
• VSS Layer (<link) a possibility to define permissions groups (for any of the technology choices or approaches above).
• Bosch proposes the use of the SSI approach: https://en.wikipedia.org/wiki/Self-sovereign_identity
  • ... but SSL/TLS is also required in some environments e.g. across internet

Open areas for getting started on implementation

• Mapping VSS to popular cloud/infrastructure technologies Apache Kafka/Spark/NiFi etc. 
• What about VSSo?
• Which existing technologies do VSSo fit into?
  • VSSo maps well to GraphQL (or SPARQL of course).  Web-of-things ← is there an obvious implementation/framework to use in implementing?
    • For GraphQL there is Apollo, Neo4j, maybe others.
  • Protege / Webprotege  ← development/analysis of ontology/data?
    
    

Action:  Collect more information from more companies about preferred technologies/implementations.

Wednesday 2021-02-03

US friendly time 17:00 CET

...