6TiSCH Autonomous Scheduling Function (ASF)
draft-duquennoy-6tisch-asf-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-07-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
6TiSCH S. Duquennoy, Ed.
Internet-Draft Inria
Intended status: Standards Track X. Vilajosana
Expires: January 4, 2018 Universitat Oberta de Catalunya
T. Watteyne
Inria
July 3, 2017
6TiSCH Autonomous Scheduling Function (ASF)
draft-duquennoy-6tisch-asf-00
Abstract
This document defines a Scheduling Function called "ASF": the 6TiSCH
Autoonomous Scheduling Function. With ASF, nodes maintain their TSCH
schedule based on local neighborhood knowledge, without any
signaling. Hashes of the nodes' MAC address are used to
deterministically derive the [slotOffset,channelOffset] location of
cells in the TSCH schedule. The MAC, control, and application
traffic planes are assigned to distinct slotframes, for isolation and
flexible dimensioning. This approach provides over-provisioned
schedules with low maintenance, in pursuit for simplicity rather than
optimality.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119].
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 http://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 January 4, 2018.
Duquennoy, et al. Expires January 4, 2018 [Page 1]
Internet-Draft 6TiSCH Autonomous Scheduling Function (ASF) July 2017
Copyright Notice
Copyright (c) 2017 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
(http://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.
Table of Contents
1. TEMPORARY EDITORIAL NOTES . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Application Domains . . . . . . . . . . . . . . . . . . . 3
3. General Operation . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Types of Slotframes . . . . . . . . . . . . . . . . . . . 4
3.2. Cell Coordinates . . . . . . . . . . . . . . . . . . . . 4
3.3. Slotframes Definition . . . . . . . . . . . . . . . . . . 5
4. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Scheduling Function Identifier . . . . . . . . . . . . . . . 6
6. Rules for Adding/Deleting Cells . . . . . . . . . . . . . . . 6
7. Rules for CellList . . . . . . . . . . . . . . . . . . . . . 7
8. 6P Timeout Value . . . . . . . . . . . . . . . . . . . . . . 7
9. Rule for Ordering Cells . . . . . . . . . . . . . . . . . . . 7
10. Meaning of the Metadata Field . . . . . . . . . . . . . . . . 7
11. Node Behavior at Boot . . . . . . . . . . . . . . . . . . . . 8
12. 6P Error Handling . . . . . . . . . . . . . . . . . . . . . . 8
13. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 8
14. Implementation Status . . . . . . . . . . . . . . . . . . . . 8
15. Security Considerations . . . . . . . . . . . . . . . . . . . 9
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
16.1. 6P Scheduling Function Identifiers 'ASF' . . . . . . . . 9
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
Show full document text