IPv6 IoT / RPL — selected stack

6LoWPAN (RFC 4944/6282) / IPv6 / RPL (RFC 6550, non-storing downward routing with RFC 6554, OF0 RFC 6552) / UDP / DTLS 1.3 (RFC 9147). IEEE 802.15.4 link binding; endpoint leaf role, participant-operated RPL root and routers. Locally provisioned ULA prefix, numeric peer addresses, 6LoWPAN neighbor discovery RFC 6775. RPL unsecured mode on an access-controlled link; DTLS does not protect routing control. End-to-end DTLS with distinct locally provisioned pairwise external PSKs, psk_ke and TLS_AES_128_GCM_SHA256; no 0-RTT, tickets or application authentication overlay. Fresh PSK handshakes allowed; no forward-secrecy claim for this PSK-only choice. No DNS, public CA, cloud broker, CoAP or MQTT dependency. No DTLS-terminating gateway: the final peers hold the traffic keys. Documentary composition; complete executable integration and sleep/overhead behavior remain unqualified. C03 configuration: enable IEEE 802.15.4 AES-128-CCM link security at level 7 (ENC-MIC128) for all established data frames carrying 6LoWPAN, including RPL unicast and multicast control, on every observed adjacency. Provision link keys locally, including a key usable for multicast delivery, and maintain non-repeating frame counters. This credits a passive radio observer without link keys; MAC headers remain visible and authorized routers decrypt RPL controls. RPL remains in unsecured mode; final-pair DTLS keys stay separate.

Official project website · Logo credits · Methodology and limits