< draft-ietf-6tisch-terminology-01.txt   draft-ietf-6tisch-terminology-02.txt >
6TiSCH MR. Palattella, Ed. 6TiSCH MR. Palattella, Ed.
Internet-Draft SnT/Univ. of Luxembourg Internet-Draft SnT/Univ. of Luxembourg
Intended status: Informational P. Thubert Intended status: Informational P. Thubert
Expires: August 17, 2014 cisco Expires: January 5, 2015 cisco
T. Watteyne T. Watteyne
Linear Technology / Dust Networks Linear Technology / Dust Networks
Q. Wang Q. Wang
Univ. of Sci. and Tech. Beijing Univ. of Sci. and Tech. Beijing
February 13, 2014 July 4, 2014
Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e
draft-ietf-6tisch-terminology-01 draft-ietf-6tisch-terminology-02
Abstract Abstract
6TiSCH proposes an architecture for an IPv6 multilink subnet that is 6TiSCH proposes an architecture for an IPv6 multi-link subnet that is
composed of a high speed powered backbone and a number of composed of a high speed powered backbone and a number of
IEEE802.15.4e TSCH wireless networks attached and synchronized by IEEE802.15.4e TSCH wireless networks attached and synchronized by
backbone routers. This document extends existing terminology backbone routers. This document extends existing terminology
documents available for Low-power and Lossy Networks to provide documents available for Low-power and Lossy Networks to provide
additional terminology elements. additional terminology elements.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
skipping to change at page 1, line 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 17, 2014. This Internet-Draft will expire on January 5, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 26 skipping to change at page 2, line 26
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. Normative References . . . . . . . . . . . . . . . . . . 9 6.1. Normative References . . . . . . . . . . . . . . . . . . 9
6.2. Informative References . . . . . . . . . . . . . . . . . 10 6.2. Informative References . . . . . . . . . . . . . . . . . 10
6.3. External Informative References . . . . . . . . . . . . . 11 6.3. External Informative References . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
A new breed of Time Sensitive Networks is being developed to enable A new breed of Time Sensitive Networks is being developed to enable
traffic that is highly sensitive to jitter and quite sensitive to traffic that is highly sensitive to jitter and quite sensitive to
skipping to change at page 3, line 18 skipping to change at page 3, line 18
6550 [RFC6550] and RFC 6552 [RFC6552], which are all included here by 6550 [RFC6550] and RFC 6552 [RFC6552], which are all included here by
reference. reference.
The draft does not reuse terms from IEEE802.15.4e such as "path" or The draft does not reuse terms from IEEE802.15.4e such as "path" or
"link" which bear a meaning that is quite different from classical "link" which bear a meaning that is quite different from classical
IETF parlance. IETF parlance.
This document adds the following terms: This document adds the following terms:
6TiSCH: IPv6 over the Timeslotted Channel Hopping (TSCH) mode of 6TiSCH: IPv6 over the Timeslotted Channel Hopping (TSCH) mode of
IEEE 802.15.4e. It defines a set of IETF sublayers and IEEE 802.15.4e. It defines the 6top sublayer and a set
protocols (in particular, for setting up a schedule with of protocols (in particular, for setting up a schedule
a centralized or distributed approach, managing the with a centralized or distributed approach, managing the
resource allocation), as well as the architecture to bind resource allocation), as well as the architecture to bind
them together, for use in IPv6 TSCH based networks. them together, for use in IPv6 TSCH based networks.
6F: IPv6 Forwarding. One of the three forwarding model 6F: IPv6 Forwarding. One of the three forwarding models
supported by 6TiSCH. Packets are routed at layer 3, supported by 6TiSCH. Packets are routed at layer 3,
where QoS and RED operations are expected to prioritize where Quality of Service (QoS) and Random Early Detection
(RED) [RFC2309] operations are expected to prioritize
flows with differentiated services. flows with differentiated services.
6top: 6top is the adaptation layer between TSCH and upper 6top: 6top is the adaptation sublayer between TSCH and upper
layers like 6LoWPAN and RPL. It is defined in layers like 6LoWPAN and RPL. It is defined in
[I-D.draft-wang-6tsch-6top]. [I-D.wang-6tisch-6top-sublayer].
6top Data Convey Model: Model describing how the 6top adaptation 6top Data Convey Model: Model describing how the 6top adaptation
layer feeds the data flow coming from upper layers into layer feeds the data flow coming from upper layers into
TSCH. It is composed by an I-MUX module, a MUX module, a TSCH. It is composed by an I-MUX module, a MUX module, a
set of priority queues, and a PDU (Payload Data Unit). set of priority queues, and a PDU (Payload Data Unit).See
[I-D.wang-6tisch-6top-sublayer].
ASN: Absolute Slot Number, the timeslot counter, incremented ASN: Absolute Slot Number, the total number of timeslots that
by one at each timeslot. It is wide enough to not roll has elapsed since the start of the network or an
over in practice. See arbitrary start time (i.e., a timeslot counter,
[I-D.watteyne-6tsch-tsch-lln-context]. incremented by one at each timeslot). It is wide enough
to not roll over in practice. See [IEEE802154e].
Blacklist: Set of frequencies which should not be used for Blacklist: Set of frequencies which should not be used for
communication. communication.
BBR: Backbone Router. In the 6TiSCH architecture, it is an BBR: Backbone Router. In the 6TiSCH architecture, it is an
LBR and also a NEAR. It performs ND proxy operations LBR and also a IPv6 ND-efficiency-aware Router (NEAR)
between registered devices and classical ND devices that [I-D.chakrabarti-nordmark-6man-efficient-nd]. It
are located over the backbone. performs ND proxy operations between registered devices
and classical ND devices that are located over the
backbone.
Broadcast cell: A scheduled cell whose neighbor MAC address is set Broadcast cell: A scheduled cell used for broadcast transmission.
to the broadcast address.
Bundle: A group of equivalent scheduled cells, i.e. cells Bundle: A group of equivalent scheduled cells, i.e. cells
identified by different [slotOffset, channelOffset], identified by different [slotOffset, channelOffset],
which are scheduled for a same purpose, with the same which are scheduled for a same purpose, with the same
neighbor, with the same flags, and the same slotframe. neighbor, with the same flags, and the same slotframe.
The size of the bundle refers to the number of cells it The size of the bundle refers to the number of cells it
contains. Given the length of the slotframe, the size of contains. Given the length of the slotframe, the size of
the bundle translates directly into bandwidth, either the bundle translates directly into bandwidth.
logical, or physical.
Cell: A single element in the TSCH schedule, identified by a Cell: A single element in the TSCH schedule, identified by a
slotOffset, a channelOffset, a slotframeHandle. A cell slotOffset, a channelOffset, a slotframeHandle. A cell
can be scheduled or unscheduled. can be scheduled or unscheduled.
ChannelOffset: Identifies a row in the TSCH slotframe. The number ChannelOffset: Identifies a row in the TSCH slotframe. The number
of available channelOffsets is equal to the number of of available channelOffsets is equal to the number of
available frequencies. The channelOffset translates into available frequencies. The channelOffset translates into
a frequency when the communication takes place, resulting a frequency when the communication takes place, resulting
in channel hopping, as detailed in in channel hopping, as detailed in
[I-D.watteyne-6tsch-tsch-lln-context]. [I-D.ietf-6tisch-tsch].
Channel distribution/usage (CDU) matrix: : Matrix of height equal to Channel distribution/usage (CDU) matrix: : Matrix of height equal to
the number of available channels (i.e, ChannelOffsets), the number of available channels (i.e, ChannelOffsets),
representing the spectrum(channel) distribution among the representing the spectrum (channel) distribution among
different (RPL parent) nodes in the networks. Every the different (RPL parent) nodes in the networks. Every
single element of the matrix belongs to a specific chunk. single element of the matrix belongs to a specific chunk.
It has to be noticed that such matrix, even though it It has to be noticed that such matrix, even though it
includes all the cells grouped in chunks, belonging to includes all the cells grouped in chunks, belonging to
different slotframes, is different from the TSCH different slotframes, is different from the TSCH
schedule. schedule.
Chunk: A well-known list of cells, well-distributed in time and Chunk: A well-known list of cells, well-distributed in time and
frequency, within a slotframe; a chunk represents a frequency, within a CDU matrix; a chunk represents a
portion of a slotframe that is globally known by all the portion of a CDU matrix that is globally known by all the
nodes in the network, but it can be managed separately by nodes in the network, with typically at most one cell per
a single node. A node can have multiple chunks, and use slotOffset for single radio devices. Once appropriated,
them according to a specific policy. Chunks may overlap. a chunk can be managed separately by a single node within
They can be pre-programmed, or can be computed by an its interference domain. A node may appropriate multiple
external entity at the network bootstrap. chunks, and use them according to a specific policy.
Chunks may overlap. They can be pre-programmed, or can
be computed by an external entity at the network
bootstrap.
Chunk ownership appropriation: The process by which an individual Chunk ownership appropriation: The process by which an individual
node obtains a chunk to manage based on peer-to-peer node obtains a chunk to manage based on peer-to-peer
interaction with its neighbors. interaction with its neighbors.
Chunk ownership delegation: The process by which an individual node Chunk ownership delegation: The process by which an individual node
obtains a chunk to manage based on point-to-point obtains a chunk to manage based on point-to-point
interaction with an external entity. interaction with an external entity.
Communication Paradigm: It is Associated with the Information Model Communication Paradigm: It is Associated with the Information Model
skipping to change at page 5, line 32 skipping to change at page 5, line 40
to a specific neighbor. to a specific neighbor.
Distributed cell reservation: A reservation of a cell done by one or Distributed cell reservation: A reservation of a cell done by one or
more in-network entities (typically a connection more in-network entities (typically a connection
endpoint). endpoint).
Distributed track reservation: A reservation of a track done by one Distributed track reservation: A reservation of a track done by one
or more in-network entities (typically a connection or more in-network entities (typically a connection
endpoint). endpoint).
EB: Enhanced Beacon frame used by an advertising node to EB: Enhanced Beacon frame used by a node to announce the
announce the presence of the network. It contains presence of the network. It contains information about
information about the timeslot length, the current ASN the timeslot length, the current ASN value, the
value, the slotframes and timeslots the beaconing mote is slotframes and timeslots the beaconing mote is listening
listening on, and a 1-byte join priority (i.e., number of on, and a 1-byte join priority (i.e., number of hops
hops separating the node sending the EB, and the PAN separating the node sending the EB, and the PAN
coordinator). coordinator).
FF: 6LoWPAN Fragment Forwarding. It is one of the three FF: 6LoWPAN Fragment Forwarding. It is one of the three
forwarding model supported by 6TiSCH. The 6LoWPAN forwarding models supported by 6TiSCH. The 6LoWPAN
Fragment is used as a label for switching at the 6LoWPAN Fragment is used as a label for switching at the 6LoWPAN
sublayer, as defined in sublayer, as defined in
[I-D.thubert-roll-forwarding-frags]. [I-D.thubert-roll-forwarding-frags].
GMPLS: Generalized Multi-Protocol Label Switching, a 2.5 layer GMPLS: Generalized Multi-Protocol Label Switching, a 2.5 layer
service that is used to forward packets based on the service that is used to forward packets based on the
concept of generalized labels. concept of generalized labels.
Hard Cell: A scheduled cell which the 6top sublayer cannot Hard Cell: A scheduled cell which the 6top sublayer cannot
reallocate. See [I-D.draft-wang-6tsch-6top]. reallocate. See [I-D.wang-6tisch-6top-sublayer].
Hopping Sequence: Sequence of frequencies, identified by a Hopping Sequence: Ordered sequence of frequencies, identified by a
Hopping_Sequence_ID, used for channel hopping, when Hopping_Sequence_ID, used for channel hopping, when
translating the channel offset value into a frequency translating the channel offset value into a frequency
(i.e., PHY channel). See (i.e., PHY channel). See [IEEE802154e] and
[I-D.watteyne-6tsch-tsch-lln-context]. [I-D.ietf-6tisch-tsch].
IE: Information Elements, a list of Type-Length-Value IE: Information Elements, a list of Type-Length-Value
containers placed at the end of the MAC header, used to containers placed at the end of the MAC header, used to
pass data between layers or devices. A small number of pass data between layers or devices. A small number of
types are defined by TSCH, but a range of types is types are defined by [IEEE802154e], but a range of types
available for extensions, and thus, is exploitable by is available for extensions, and thus, is exploitable by
6TiSCH. See [I-D.watteyne-6tsch-tsch-lln-context]. 6TiSCH. See [IEEE802154e].
I-MUX module: Inverse-Multiplexer, a classifier that receives I-MUX module: Inverse-Multiplexer, a classifier that receives
6LoWPAN frames and places them into priority queues. 6LoWPAN frames and places them into priority queues. See
[I-D.wang-6tisch-6top-sublayer].
Interaction Model: It is a particular way of implementing a Interaction Model: It is a particular way of implementing a
communication paradigm. Defined at a lower level of communication paradigm. Defined at a lower level of
abstraction, it includes protocol-specific details such abstraction, it includes protocol-specific details such
as a particular method (e.g., a REST GET) and a Data as a particular method (e.g., a REST GET) and a Data
Model for the state to be exchanged. Model for the state to be exchanged.
KMP: Key Managment Protocol. KMP: Key Managment Protocol.
LBR: LLN Border Router. It is an LLN device, usually powered, LBR: LLN Border Router. It is an LLN device, usually powered,
that acts as a Border Router to the outside within the that acts as a Border Router to the outside within the
6TiSCH architecture. 6TiSCH architecture.
Link: A communication facility or medium over which nodes can Link: A communication facility or medium over which nodes can
communicate at the link layer, i.e., the layer communicate at the link layer, i.e., the layer
immediately below IP. Thus, the IETF parlance for the immediately below IP. Thus, the IETF parlance for the
term "Link" is adopted, as opposed to the incompatible term "Link" is adopted, as opposed to the IEEE802.15.4e
IEEE802.15.4e terminology. In the context of the 6TiSCH terminology. In the context of the 6TiSCH architecture,
architecture, which applies to Low Power Lossy Networks which applies to Low Power Lossy Networks (LLNs), an IPv6
(LLNs), an IPv6 subnet is usually not congruent to a subnet is usually not congruent to a single link and
single link and techniques such as IPv6 Neighbor techniques such as IPv6 Neighbor Discovery Proxying are
Discovery Proxying and Routing Over LLNs are required to used to achieve reachability within the multilink subnet.
achieve reachability within the multilink subnet. A link A link is distinct from a track. In fact, link local
is distinct from a track. In fact, link local addresses addresses are not expected to be used over a track for
are not expected to be used over a track for end to end end to end communication. Finally, from the Layer 3
communication. Finally, from the Layer 3 perspective perspective (where the inner complexities of TSCH
(where the inner complexities of TSCH operations are operations are hidden to enable classical IP routing and
hidden to enable classical IP routing and Forwarding), a Forwarding), a single radio interface may be seen as a
single radio interface may be seen as a number of Links number of Links with different capabilities for unicast
with different capabilities for unicast or multicast or multicast services.
services.
Logical Cell: A cell that corresponds to granted bandwidth but is Logical Cell: A cell that corresponds to granted bandwidth but is
only lazily associated to a physical cell, based on only lazily associated to a physical cell, based on
usage. usage.
MAC: Medium Access Control. MAC: Medium Access Control.
MUX module: Multiplexer, the entity that dequeues frames from MUX module: Multiplexer, the entity that dequeues frames from
priority queues and associates them to a cell for priority queues and associates them to a cell for
transmission. transmission. See [I-D.wang-6tisch-6top-sublayer].
NEAR: Energy Aware Default Router, as defined in NEAR: Energy Aware Default Router, as defined in
[I-D.chakrabarti-nordmark-6man-efficient-nd]. [I-D.chakrabarti-nordmark-6man-efficient-nd].
NME: Network Management Entity, the entity in the network NME: Network Management Entity, the entity in the network
managing cells and other device resources. It may managing cells and other device resources. It may
cooperate with the PCE. It interacts with LLN nodes cooperate with the PCE. It interacts with LLN nodes
through the backbone router. through the backbone router.
PANA: Protocol for carrying Authentication for Network Access, PANA: Protocol for carrying Authentication for Network Access,
as defined in [RFC5191] . It is the protocol used in the as defined in [RFC5191] .
6TiSCH architecture for handling authentication during
the join process.
PCE: Path Computation Element, the entity in the network which PCE: Path Computation Element, the entity in the network which
is responsible for building and maintaining the TSCH is responsible for building and maintaining the TSCH
schedule, when centralized scheduling is used. schedule, when centralized scheduling is used.
PCE cell reservation: The reservation of a cell done by the PCE. PCE cell reservation: The reservation of a cell done by the PCE.
PCE track reservation: The reservation of a track done by the PCE. PCE track reservation: The reservation of a track done by the PCE.
QoS: Quality of Service. QoS: Quality of Service.
skipping to change at page 8, line 5 skipping to change at page 8, line 9
(to) Schedule a cell: The action of turning an unscheduled cell into (to) Schedule a cell: The action of turning an unscheduled cell into
a scheduled cell. a scheduled cell.
Scheduled cell: A cell which is assigned a neighbor MAC address Scheduled cell: A cell which is assigned a neighbor MAC address
(broadcast address is also possible), and one or more of (broadcast address is also possible), and one or more of
the following flags: TX, RX, shared, timeskeeping. A the following flags: TX, RX, shared, timeskeeping. A
scheduled cell can be used by the IEEE802.15.4e TSCH scheduled cell can be used by the IEEE802.15.4e TSCH
implementation to communicate. A scheduled cell can be a implementation to communicate. A scheduled cell can be a
hard cell or a soft cell. hard cell or a soft cell.
Shared Cell: A cell that is used by more than one transmitter nodes Shared Cell: A cell marked with both the "TX" and "shared" flags.
at the same time and on the same channelOffset. Only This cell can be used by more than one transmitter node.
cells with TX flag can be marked as "shared". A backoff A backoff algorithm is used to resolve contention. See
algorithm is used to resolve contention. [I-D.ietf-6tisch-tsch].
SlotOffset: Identifies a column in the TSCH schedule, i.e., the SlotOffset: Identifies a column in the TSCH schedule, i.e., the
number of timeslots since the beginning of the current number of timeslots since the beginning of the current
iteration of the slotframe. iteration of the slotframe.
Slotframe: A MAC-level abstraction that is internal to the node and Slotframe: A MAC-level abstraction that is internal to the node and
contains a series of timeslots of equal length and contains a series of timeslots of equal length and
priority. It is characterized by a slotframe_ID, and a priority. It is characterized by a slotframe_ID, and a
slotframe_size. Multiple slotframes can coexist in a slotframe_size. Multiple slotframes can coexist in a
node's schedule, i.e., a node can have multiple node's schedule, i.e., a node can have multiple
activities scheduled in different slotframes, based on activities scheduled in different slotframes, based on
the priority of its packets/traffic flows. The timeslots the priority of its packets/traffic flows. The timeslots
in the Slotframe are indexed by the SlotOffset; the first in the Slotframe are indexed by the SlotOffset; the first
timeslot is at SlotOffset 0. timeslot is at SlotOffset 0.
Soft Cell: A scheduled cell which the 6top sublayer can reallocate, Soft Cell: A scheduled cell which the 6top sublayer can reallocate,
as described in [I-D.draft-wang-6tsch-6top]. as described in [I-D.wang-6tisch-6top-sublayer].
TF: Track Forwarding. It is the simplest and fastest TF: Track Forwarding. It is the simplest and fastest
forwarding model supported by 6TiSCH. It is a G-MPLS- forwarding model supported by 6TiSCH. It is a G-MPLS-
like forwarding model. The input cell characterises the like forwarding model. The input cell characterizes the
flow and indicates the output cell. flow and indicates the output cell.
Timeslot: A basic communication unit in TSCH which allows a Timeslot: A basic communication unit in TSCH which allows a
transmitter node to send a frame to a receiver neighbor, transmitter node to send a frame to a receiver neighbor,
and that receiver neighbor to optionally send back an and that receiver neighbor to optionally send back an
acknowledgment. The length of the timeslot determines acknowledgment.
the maximum size of the frame that can be exchanged.
Time Source Neighbor: A neighbor a node uses as its time reference, Time Source Neighbor: A neighbor a node uses as its time reference,
and to which it needs to keep its clock synchronized. A and to which it needs to keep its clock synchronized. A
node can have one or more time source neighbors. node can have one or more time source neighbors.
Track: A determined sequence of cells along a multi-hop path. Track: A determined sequence of cells along a multi-hop path.
It is typically the result of a reservation. The node It is typically the result of a reservation. The node
that initializes the process for establishing a track is that initializes the process for establishing a track is
the owner of the track. The latter assigns a unique the owner of the track. The latter assigns a unique
identifier to the track, called TrackID. identifier to the track, called TrackID.
TrackID: Unique identifier of a track, assigned by the owner of TrackID: Unique identifier of a track, assigned by the owner of
the track. the track.
TSCH: Time Slotted Channel Hopping, a medium access mode of the TSCH: Time Slotted Channel Hopping, a medium access mode of the
[IEEE802154e] standard which uses time synchronization to [IEEE802154e] standard which uses time synchronization to
achieve ultra low-power operation and channel hopping to achieve ultra low-power operation and channel hopping to
enable high reliability. enable high reliability.
TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset
and a channelOffset. The slotframe size (the "width" of and a channelOffset. The TSCH schedule contains all the
the matrix) is the number of timeslots it contains. The scheduled cells from all slotframes and is sufficient to
qualify the communication in the TSCH network. The
"width of the matrix is equal to the number of scheduled
timeslots in all the concurrent active slotframes. The
number of channelOffset values (the "height" of the number of channelOffset values (the "height" of the
matrix) is equal to the number of available frequencies. matrix) is equal to the number of available frequencies.
The TSCH schedule contains all the scheduled cells from
all slotframes and is sufficient to qualify the
communication in the TSCH network.
unscheduled cell: A cell which is not used by the IEEE802.15.4e TSCH unscheduled cell: A cell which is not used by the IEEE802.15.4e TSCH
implementation. implementation.
3. IANA Considerations 3. IANA Considerations
This specification does not require IANA action. This specification does not require IANA action.
4. Security Considerations 4. Security Considerations
This specification is not found to introduce new security threat. This specification is not found to introduce new security threats.
5. Acknowledgements 5. Acknowledgments
Thanks to the IoT6 European Project (STREP) of the 7th Framework Thanks to the IoT6 European Project (STREP) of the 7th Framework
Program (Grant 288445). Program (Grant 288445).
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2309] Braden, B., Clark, D., Crowcroft, J., Davie, B., Deering,
S., Estrin, D., Floyd, S., Jacobson, V., Minshall, G.,
Partridge, C., Peterson, L., Ramakrishnan, K., Shenker,
S., Wroclawski, J., and L. Zhang, "Recommendations on
Queue Management and Congestion Avoidance in the
Internet", RFC 2309, April 1998.
[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
Information Models and Data Models", RFC 3444, January Information Models and Data Models", RFC 3444, January
2003. 2003.
[RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A. [RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A.
Yegin, "Protocol for Carrying Authentication for Network Yegin, "Protocol for Carrying Authentication for Network
Access (PANA)", RFC 5191, May 2008. Access (PANA)", RFC 5191, May 2008.
[RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R., [RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R.,
Levis, P., Pister, K., Struik, R., Vasseur, JP., and R. Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.
skipping to change at page 10, line 13 skipping to change at page 10, line 26
Lossy Networks", RFC 6550, March 2012. Lossy Networks", RFC 6550, March 2012.
[RFC6552] Thubert, P., "Objective Function Zero for the Routing [RFC6552] Thubert, P., "Objective Function Zero for the Routing
Protocol for Low-Power and Lossy Networks (RPL)", RFC Protocol for Low-Power and Lossy Networks (RPL)", RFC
6552, March 2012. 6552, March 2012.
6.2. Informative References 6.2. Informative References
[I-D.chakrabarti-nordmark-6man-efficient-nd] [I-D.chakrabarti-nordmark-6man-efficient-nd]
Chakrabarti, S., Nordmark, E., Thubert, P., and M. Chakrabarti, S., Nordmark, E., Thubert, P., and M.
Wasserman, "Wired and Wireless IPv6 Neighbor Discovery Wasserman, "IPv6 Neighbor Discovery Optimizations for
Optimizations", draft-chakrabarti-nordmark-6man-efficient- Wired and Wireless Networks", draft-chakrabarti-nordmark-
nd-04 (work in progress), October 2013. 6man-efficient-nd-05 (work in progress), February 2014.
[I-D.draft-sudhaakar-6tisch-coap] [I-D.ietf-6tisch-6top-interface]
Sudhaakar, R., Ed. and P. Zand, "6TiSCH Data Model for Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH
CoAP-00 (work in progress)", October 2013. Operation Sublayer (6top) Interface", draft-ietf-6tisch-
6top-interface-00 (work in progress), March 2014.
[I-D.draft-wang-6tsch-6top] [I-D.ietf-6tisch-architecture]
Wang, Q., Ed., Vilajosana, X., and T. Watteyne, "6TiSCH Thubert, P., Watteyne, T., and R. Assimiti, "An
Operation Sublayer (6top). draft-wang-6tisch-6top-00 (work Architecture for IPv6 over the TSCH mode of IEEE
in progress)", October 2013. 802.15.4e", draft-ietf-6tisch-architecture-02 (work in
progress), June 2014.
[I-D.ietf-6tisch-coap]
Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and
Interaction using CoAP", draft-ietf-6tisch-coap-00 (work
in progress), May 2014.
[I-D.ietf-6tisch-minimal]
Vilajosana, X. and K. Pister, "Minimal 6TiSCH
Configuration", draft-ietf-6tisch-minimal-01 (work in
progress), June 2014.
[I-D.ietf-6tisch-tsch]
Watteyne, T., Palattella, M., and L. Grieco, "Using
IEEE802.15.4e TSCH in an LLN context: Overview, Problem
Statement and Goals", draft-ietf-6tisch-tsch-00 (work in
progress), November 2013.
[I-D.ietf-roll-terminology] [I-D.ietf-roll-terminology]
Vasseur, J., "Terms used in Routing for Low power And Vasseur, J., "Terms used in Routing for Low power And
Lossy Networks", draft-ietf-roll-terminology-13 (work in Lossy Networks", draft-ietf-roll-terminology-13 (work in
progress), October 2013. progress), October 2013.
[I-D.ohba-6tsch-security]
Chasko, S., Das, S., Lopez, R., Ohba, Y., Thubert, P., and
A. Yegin, "Security Framework and Key Management Protocol
Requirements for 6TSCH", draft-ohba-6tsch-security-01
(work in progress), July 2013.
[I-D.thubert-6tisch-architecture]
Thubert, P., Watteyne, T., and R. Assimiti, "An
Architecture for IPv6 over the TSCH mode of IEEE
802.15.4e", draft-thubert-6tisch-architecture-01 (work in
progress), October 2013.
[I-D.thubert-roll-forwarding-frags] [I-D.thubert-roll-forwarding-frags]
Thubert, P. and J. Hui, "LLN Fragment Forwarding and Thubert, P. and J. Hui, "LLN Fragment Forwarding and
Recovery", draft-thubert-roll-forwarding-frags-02 (work in Recovery", draft-thubert-roll-forwarding-frags-02 (work in
progress), September 2013. progress), September 2013.
[I-D.vilajosana-6tisch-minimal] [I-D.wang-6tisch-6top-sublayer]
Vilajosana, X. and K. Pister, "Minimal 6TiSCH Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH
Configuration", draft-vilajosana-6tisch-minimal-00 (work Operation Sublayer (6top)", draft-wang-6tisch-6top-
in progress), October 2013. sublayer-00 (work in progress), February 2014.
[I-D.watteyne-6tsch-tsch-lln-context]
Watteyne, T., Palattella, M., and L. Grieco, "Using
IEEE802.15.4e TSCH in an LLN context: Overview, Problem
Statement and Goals", draft-watteyne-6tsch-tsch-lln-
context-02 (work in progress), May 2013.
6.3. External Informative References 6.3. External Informative References
[IEEE802154e] [IEEE802154e]
IEEE standard for Information Technology, "IEEE std. IEEE standard for Information Technology, "IEEE std.
802.15.4e, Part. 15.4: Low-Rate Wireless Personal Area 802.15.4e, Part. 15.4: Low-Rate Wireless Personal Area
Networks (LR-WPANs) Amendament 1: MAC sublayer", April Networks (LR-WPANs) Amendment 1: MAC sublayer", April
2012. 2012.
Authors' Addresses Authors' Addresses
Maria Rita Palattella (editor) Maria Rita Palattella (editor)
University of Luxembourg University of Luxembourg
Interdisciplinary Centre for Security, Reliability and Trust Interdisciplinary Centre for Security, Reliability and Trust
4, rue Alphonse Weicker 4, rue Alphonse Weicker
Luxembourg L-2721 Luxembourg L-2721
LUXEMBOURG Luxembourg
Phone: (+352) 46 66 44 5841 Phone: (+352) 46 66 44 5841
Email: maria-rita.palattella@uni.lu Email: maria-rita.palattella@uni.lu
Pascal Thubert Pascal Thubert
Cisco Systems, Inc Cisco Systems, Inc
Village d'Entreprises Green Side Village d'Entreprises Green Side
400, Avenue de Roumanille 400, Avenue de Roumanille
Batiment T3 Batiment T3
Biot - Sophia Antipolis 06410 Biot - Sophia Antipolis 06410
FRANCE France
Phone: +33 497 23 26 34 Phone: +33 497 23 26 34
Email: pthubert@cisco.com Email: pthubert@cisco.com
Thomas Watteyne Thomas Watteyne
Linear Technology / Dust Networks Linear Technology / Dust Networks
30695 Huntwood Avenue 30695 Huntwood Avenue
Hayward, CA 94544 Hayward, CA 94544
USA USA
 End of changes. 47 change blocks. 
120 lines changed or deleted 129 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/