Skip to main content

LLN Fragment Forwarding and Recovery

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Pascal Thubert , Jonathan Hui
Last updated 2018-01-16
Replaced by draft-thubert-6lo-fragment-recovery
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-thubert-6lo-fragment-recovery
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Considering that an LLN frame can have a MAC payload below 100 bytes, an IPv6 packet might be fragmented into more than 10 fragments at the 6LoWPAN layer. In a 6LoWPAN mesh-under network, the fragments can be forwarded individually across the mesh, whereas a route-over mesh network, a fragmented 6LoWPAN packet must be reassembled at every hop, which causes latency and congestion. This draft introduces a simple protocol to forward individual fragments across a route-over mesh network, and, regardless of the type of mesh, recover the loss of individual fragments across the mesh and protect the network against bloat with a minimal flow control.


Pascal Thubert
Jonathan Hui

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)