Subject: [6lo] FW: New Version Notification for draft-thubert-6lo-forwarding-fragments-07.txt

From: "Pascal Thubert (pthubert)" <[email-masked]>
Date: Mon, 24 Jul 2017 11:02:15 +0000

This version addresses comments by Thomas and them Michael. Thank you both!

Pascal

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: lundi 24 juillet 2017 12:59
To: Pascal Thubert (pthubert) <[email-masked]>; Jonathan W. Hui <[email-masked]>; Jonathan Hui <[email-masked]>
Subject: New Version Notification for draft-thubert-6lo-forwarding-fragments-07.txt

A new version of I-D, draft-thubert-6lo-forwarding-fragments-07.txt
has been successfully submitted by Pascal Thubert and posted to the IETF repository.

Name:		draft-thubert-6lo-forwarding-fragments
Revision:	07
Title:		LLN Fragment Forwarding and Recovery
Document date:	2017-07-24
Group:		Individual Submission
Pages:		19
URL:            https://www.ietf.org/internet-drafts/draft-thubert-6lo-forwarding-fragments-07.txt
Status:         https://datatracker.ietf.org/doc/draft-thubert-6lo-forwarding-fragments/
Htmlized:       https://tools.ietf.org/html/draft-thubert-6lo-forwarding-fragments-07
Htmlized:       https://datatracker.ietf.org/doc/html/draft-thubert-6lo-forwarding-fragments-07
Diff:           https://www.ietf.org/rfcdiff?url2=draft-thubert-6lo-forwarding-fragments-07

Abstract:
   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.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat