1 of 4

Eclipse Californium

RFC9146

IoT WG

2 of 4

Overview

​

RFC9146

​

Challenge: Mobile IoT devices in the wild are frequently

- lose connections

- faced unaware IP-address changes

- faced IP-address changes on wake-up after Power Sleeping Mode

- While UDP is resilent against lost and retained connections, IP-address changes are hard to handle. IP-tunnels may be a solution, but it

- Ends up in too frequent handshakes, with data- and energy consumption.

- RFC 9146 replaces the device IP-address by an assigned Connection ID, which doesn’t change unaware nor on wake-up.

- Enables, data- and energy-efficient communication.

3 of 4

RFC9146 – Eclipse IoT

Californium – Java – Server and Client:

  • Implementation started end of 2018
  • Promising first results Q1/2019
  • Add features as UDP-CID-LoadBalancer

​

TinyDTLS – C – (currently) Feature-Branch, Client only

  • Implememtation started Q3/2021
  • Porting to zephyr Q1/2022
  • Used with mobile prototyping Platform “Thingy 91”

​

PoC: runs stable from battery using LTE-M over weeks against the Eclipse Californium Sandbox. (LTE-M, offerings starting at 1 MB per week for 10 Euro for 10 years (1 Euro/year).)

4 of 4

RFC9146 – Demonstration

Thingy!91

https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91

​

TinyDtls

https://github.com/eclipse/tinydtls/tree/feature/connection_id

​

Zephyr (to be)

https://github.com/zephyrproject-rtos/zephyr/discussions/43650

​

Californium - Cloud:

https://github.com/eclipse/californium/tree/master/demo-apps/cf-unix-setup#installation-on-exoscale-cloud

​