6LoWPAN Selective Fragment Recovery
draft-thubert-6lo-fragment-recovery-01
6lo P. Thubert, Ed.
Internet-Draft Cisco Systems
Updates: 4944 (if approved) June 27, 2018
Intended status: Standards Track
Expires: December 29, 2018
6LoWPAN Selective Fragment Recovery
draft-thubert-6lo-fragment-recovery-01
Abstract
This draft updates RFC 4944 with a simple protocol to recover
individual fragments across a route-over mesh network, with a minimal
flow control to protect the network against bloat.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 29, 2018.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Thubert Expires December 29, 2018 [Page 1]
Internet-Draft 6LoWPAN Selective Fragment Recovery June 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Updating RFC 4944 . . . . . . . . . . . . . . . . . . . . . . 3
3. Updating draft-watteyne-6lo-minimal-fragment . . . . . . . . 4
4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. BCP 14 . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. References . . . . . . . . . . . . . . . . . . . . . . . 4
4.3. 6LoWPAN Acronyms . . . . . . . . . . . . . . . . . . . . 4
4.4. Referenced Work . . . . . . . . . . . . . . . . . . . . . 5
4.5. New Terms . . . . . . . . . . . . . . . . . . . . . . . . 6
5. New Dispatch types and headers . . . . . . . . . . . . . . . 6
5.1. Recoverable Fragment Dispatch type and Header . . . . . . 7
5.2. RFRAG Acknowledgment Dispatch type and Header . . . . . . 9
6. Fragments Recovery . . . . . . . . . . . . . . . . . . . . . 10
7. Forwarding Fragments . . . . . . . . . . . . . . . . . . . . 12
7.1. Upon the first fragment . . . . . . . . . . . . . . . . . 12
7.2. Upon the next fragments . . . . . . . . . . . . . . . . . 13
7.3. Upon the RFRAG Acknowledgments . . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
11.1. Normative References . . . . . . . . . . . . . . . . . . 14
11.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. Rationale . . . . . . . . . . . . . . . . . . . . . 17
Appendix B. Requirements . . . . . . . . . . . . . . . . . . . . 18
Appendix C. Considerations On Flow Control . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction
In most Low Power and Lossy Network (LLN) applications, the bulk of
the traffic consists of small chunks of data (in the order few bytes
to a few tens of bytes) at a time. Given that an IEEE Std. 802.15.4
[IEEE.802.15.4] frame can carry 74 bytes or more in all cases,
fragmentation is usually not required. However, and though this
happens only occasionally, a number of mission critical applications
do require the capability to transfer larger chunks of data, for
instance to support a firmware upgrades of the LLN nodes or an
extraction of logs from LLN nodes. In the former case, the large
chunk of data is transferred to the LLN node, whereas in the latter,
the large chunk flows away from the LLN node. In both cases, the
size can be on the order of 10Kbytes or more and an end-to-end
Show full document text