LLN Fragment Forwarding and Recovery
draft-thubert-roll-forwarding-frags-02

Document Type Expired Internet-Draft (individual)
Last updated 2014-03-13 (latest revision 2013-09-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-thubert-roll-forwarding-frags-02.txt

Abstract

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.

Authors

Pascal Thubert (pthubert@cisco.com)
Jonathan Hui (johui@cisco.com)

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