Dear 6lowpanners; This is parallel work to enable to protect and forward 6lowpan fragments. Since the HC draft is mostly complete and last call has timed out, there might be room for this work.
Changes in this version: - offsets are expressed on the compressed form of the packets. So the fragmentation sublayer is cleanly sitting below the compression sublayer. - details are given on how the datagram id can be used as a label to correlate fragments of a same packet and switched as fragment progresses. Cheers, Pascal -----Original Message----- From: IETF I-D Submission Tool [mailto:[email protected]] Sent: Friday, June 04, 2010 6:12 PM To: Pascal Thubert (pthubert) Cc: [email protected] Subject: New Version Notification for draft-thubert-6lowpan-simple-fragment-recovery-07 A new version of I-D, draft-thubert-6lowpan-simple-fragment-recovery-07.txt has been successfully submitted by Pascal Thubert and posted to the IETF repository. Filename: draft-thubert-6lowpan-simple-fragment-recovery Revision: 07 Title: LoWPAN fragment Forwarding and Recovery Creation_date: 2010-06-04 WG ID: Independent Submission Number_of_pages: 16 Abstract: 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. The IETF Secretariat. _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
