IPv6 for IoT and constrained networks
Explain 6LoWPAN adaptation and header compression (RFC 4944, RFC 6282). Explain ND optimisation and registration for low-power networks (RFC 6775, RFC 8505). Describe RPL routing for low-power and lossy networks (RFC 6550).
Take the quiz · pass mark 70% · 9 questions
Explanation
IPv6's 128-bit addresses and 1280-byte minimum MTU look impossible on a radio that sends 127-byte frames to battery-powered nodes. The 6LoWPAN family makes IPv6 fit anyway — which is why IPv6 is the native protocol of modern IoT (Thread, many industrial meshes).
Adaptation over IEEE 802.15.4 (RFC 4944)
RFC 4944 defines carrying IPv6 over IEEE 802.15.4. The link's maximum frame is only 127 bytes, far below IPv6's 1280-byte minimum MTU, so the adaptation layer adds fragmentation and reassembly to carry a 1280-byte IPv6 packet across many tiny frames, plus a mesh header for mesh-under forwarding. The point: IPv6 still guarantees a 1280-byte MTU to the upper layers; 6LoWPAN hides the fragmentation underneath.
Header compression (RFC 6282)
A 40-byte IPv6 header is unacceptable overhead on a 127-byte frame. RFC 6282 (IPHC) compresses it aggressively: fields that can be derived from the link (e.g. a link-local prefix, or an interface identifier equal to the L2 address) are elided, so the IPv6 header can shrink to as few as 2 bytes in the best case, with further NHC compression of UDP. This is what makes IPv6-over-radio practical.
ND optimisation and registration (RFC 6775, RFC 8505)
Classic Neighbor Discovery is multicast-heavy (Level 1) — fatal for sleepy, battery nodes. RFC 6775 optimises ND for low-power networks: instead of multicast DAD and gratuitous NS, a node registers its address with a router (the 6LoWPAN Border Router) using a unicast Address Registration Option, so there is no periodic multicast. RFC 8505 extends this registration (routing registration, better DAD, support for RPL), and is the modern basis for ND in constrained networks.
RPL routing (RFC 6550)
Within the mesh, RPL (RFC 6550) is the routing protocol for low-power and lossy networks. It builds a DODAG (a destination-oriented directed acyclic graph) rooted at the border router, chosen by an objective function (e.g. expected transmissions), so traffic flows up to the root and down to nodes with minimal control overhead. RPL is designed for thousands of constrained nodes with lossy links, not for a data-centre fabric.
ictNetworks scenario
ictNetworks' smart-metering pilot runs IPv6 over 802.15.4 with IPHC compression (RFC 6282), RFC 8505 registration-based ND so meters can sleep without multicast, and RPL (RFC 6550) up to a 6LoWPAN Border Router that bridges the mesh to the campus IPv6 network. The meters get documentation-prefix addresses in the lab, and the border router enforces the same first-hop and perimeter policy (Level 5) as any other segment.
Drawing diagram…
Worked examples
Example 1: The tiny frame
IEEE 802.15.4 frames are at most 127 bytes, so 6LoWPAN (RFC 4944) must fragment a full IPv6 packet across several frames and compress headers to make anything fit.
Example 2: The MTU it must still offer
Despite 127-byte frames, the 6LoWPAN adaptation layer must still present the IPv6 minimum MTU of 1280 bytes to the layers above, which it achieves with fragmentation and reassembly.
Example 3: How small the header gets
RFC 6282 IPHC can compress the 40-byte IPv6 header to as few as 2 bytes in the best case (link-local, elided addresses), which is the difference between IPv6 being impractical and practical on a radio.
Lab
Goal: Build a simulated 6LoWPAN network and ping a node from the LAN.
You need: the Contiki-NG Cooja simulator (or Linux mac802154_hwsim), a 6LoWPAN Border Router bridging to an IPv6 LAN, and several mote nodes. (6LoWPAN/RPL support and syntax vary by stack and version — check the docs.)
- Build a small 6LoWPAN mesh with a border router and several nodes; confirm they form an RPL DODAG.
- Observe IPHC header compression and fragmentation on the radio frames (a capture of the 127-byte frames).
- Confirm nodes use registration-based ND (RFC 6775/8505) rather than multicast DAD.
- From a host on the IPv6 LAN, ping a node through the border router and back.
- Break a link and watch RPL reconverge the DODAG; note the delivery recovery.
What to submit: the topology, the RPL DODAG, a radio-frame capture showing IPHC/fragmentation, the LAN-to-node ping, and the reconvergence observation.
Summary
- 6LoWPAN (RFC 4944) carries IPv6 over 127-byte 802.15.4 frames with fragmentation, still offering the 1280-byte MTU.
- IPHC (RFC 6282) compresses the 40-byte IPv6 header to as few as 2 bytes.
- Registration-based ND (RFC 6775, RFC 8505) removes multicast so battery nodes can sleep.
- RPL (RFC 6550) routes the low-power lossy mesh as a DODAG rooted at the border router.
- Next lesson (L8.04): prefix translation and advanced multihoming.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.