Propose a new Ockam Transport implementation

[mrinalwadhwa]

Connected machines and devices communicate amongst each other by exchanging messages over a variety of transport protocols like TCP, UDP, Bluetooth, ZigBee, LoRaWAN etc.

Ockam includes a set of secure communication protocols, like secure channels that provide their functionality in a way that is agnostic to the underlying means of transporting messages. Such higher level protocols need a simple consistent mechanism, to send and receive messages, that only loosely couples them with the underlying transport protocol. This loose coupling is achieved using an abstract Transport interface.

So far we've implemented TCP and UDP and are thinking about adding the following.
https://github.com/ockam-network/ockam/issues?q=is%3Aissue+is%3Aopen+label%3A%22Component%3A+Transport%22

Which other transport protocols should we consider?

[mrinalwadhwa]

I think even simple mediums like QR codes, Webhooks, Push Notifications, email etc. can potentially be transports

[akramIOT]

Connected machines and devices communicate amongst each other by exchanging messages over a variety of transport protocols like TCP, UDP, Bluetooth, ZigBee, LoRaWAN etc.

Ockam includes a set of secure communication protocols, like secure channels that provide their functionality in a way that is agnostic to the underlying means of transporting messages. Such higher level protocols need a simple consistent mechanism, to send and receive messages, that only loosely couples them with the underlying transport protocol. This loose coupling is achieved using an abstract Transport interface.

So far we've implemented TCP and UDP and are thinking about adding the following.
https://github.com/ockam-network/ockam/issues?q=is%3Aissue+is%3Aopen+label%3A%22Component%3A+Transport%22

Which other transport protocols should we consider?

Mrinal,
I think you can also explore an abstract Transport interface with Secured channels for OpenThread wireless Protocol.

How different is this Ockham IOT Security tooling software with "secured channels" different from techniques like IOTSafe which GSMA supports widely with chipset OEM Partnerships ?

https://bics.com/iot-safe-robust-iot-security-at-scale/
https://semiengineering.com/isim-with-iot-safe-for-seamless-authentication-from-chip-to-cloud/

IoTsafe which decouples security from core IoT applications, making security independent from the firmware libraries and IoT software. It is based on stand-alone SSH protocol embodiments instead of integrating TLS into the IoT software

[mrinalwadhwa]

Hey @akramIOT, Thread is a great suggestion for a transport 👍thank you.

I'm not deeply familiar with IOTSafe, I'll try to find some time to read about it over the next few days. Thank you for pointing me to it.

[akramIOT]

@mrinalwadhwa : check this one on "IOTSafe" on the decoupling of Transport layer protocols in a secured way for IOT device firmware.
https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8649577&tag=1

[codeadict]

What about MQTT and COAP (the most popular IoT protocols out there), they fail into the TCP and UDP protocols but the packets are rather specific and need some specific connection semantics. Would those be accepted as transports or prefer to leave the TCP and UDP ones and let the implementer "format" the packets somehow to not have such higher-level transports?

[akramIOT]

What about MQTT and COAP (the most popular IoT protocols out there), they fail into the TCP and UDP protocols but the packets are rather specific and need some specific connection semantics. Would those be accepted as transports or prefer to leave the TCP and UDP ones and let the implementer "format" the packets somehow to not have such higher-level transports?

MQTT and COAP are IOT Application layer Protocols with TLS over TCP and DTLS over UDP support correspondingly. So the existing de-coupling done via 'abstract transport interface' still holds good for this TCP and UDP based IOT protocols.

[rogeriob2br]

Other alternatives:
gRPC(HTTP2 -tonic is a great crate for this), QUIC(HTTP3), i2c( for IoTs), FIX(Financial Information eXchange protocol used for trading)