Download IP Optimization for IoT Networks and more Slides Computer Science in PDF only on Docsity!
Optimizing IP for Constrained Environments
IoT deployments introduce constraints that mandate optimization across the IP stack.
Constrained Nodes
Devices with limited CPU, memory, and power — some transmit only a few bytes infrequently with minimal security capabilities.
Constrained Networks
Low-power, lossy links (few kbps to hundreds of kbps) with high latency and packet loss.
IP Version Transition
The IETF's 20+ year IPv4-to-IPv transition requires tunneling and translation for IoT interoperability.
6LoWPAN: Adapting IPv6 for Constrained
Networks
The IETF 6LoWPAN working group defined an adaptation layer to carry IPv6 over IEEE 802.15.4 and similar
constrained links. RFC 4944 is foundational, enabling three key optimizations.
Header Compression
Compresses the 40-byte IPv6 +
8-byte UDP headers down to as
little as 6 bytes combined.
IPv4 is not supported.
Fragmentation
IPv6 requires 1280-byte MTU;
IEEE 802.15.4 supports only 127
bytes. 6LoWPAN fragments large
packets across multiple frames
using datagram size, tag, and
offset fields.
Mesh Addressing
Enables multi-hop forwarding
with hop limit, source address,
and destination address fields —
analogous to IPv6 hop limit.
RPL: Routing for Low-Power Lossy Networks The IETF RoLL working group developed RPL (RFC 6550), a distance-vector routing protocol for constrained IPv6 networks. Each node acts as a router, forwarding at the IP layer without MAC-layer dependency. DODAG Discovery Nodes exchange DIOs to find root and rank Packet Forwarding IPv6 routed hop-by- hop storing or non- storing Route Establishment Nodes pick parents via ETX, latency, energy RPL builds a Destination-Oriented DAG rooted at a border router. In Storing Mode , all nodes maintain full routing tables; in Non-Storing Mode , only the roo reducing memory overhead.
Security for Constrained Environments
CoAP + DTLS: The Security Stack
Constrained nodes implement an optimized IP stack: CoAP at the application layer over UDP at transport, secured by DTLS.
- (^) ACE standardizes authentication and authorization for resource- constrained servers
- (^) DICE profiles DTLS for low-memory, low-power devices
- (^) Both enable secure RESTful access (GET, PUT, POST, DELETE) over constrained links
