Sign in
Version 5.13.0, 2015-03-25
Report a bug

LLN Fragment Forwarding and Recovery

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-03-13 (latest revision 2013-09-09)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


In order to be routed, a fragmented packet must be reassembled at every hop of a multihop link where lower layer fragmentation occurs. Considering that the IPv6 minimum MTU is 1280 bytes and that an an 802.15.4 frame can have a payload limited to 74 bytes in the worst case, a packet might end up fragmented into as many as 18 fragments at the 6LoWPAN shim layer. If a single one of those fragments is lost in transmission, all fragments must be resent, further contributing to the congestion that might have caused the initial packet loss. This draft introduces a simple protocol to forward and recover individual fragments that might be lost over multiple hops between 6LoWPAN endpoints.


Pascal Thubert <>
Jonathan Hui <>

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