< draft-ietf-6tisch-terminology-03.txt   draft-ietf-6tisch-terminology-04.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: July 12, 2015 cisco Expires: September 24, 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
January 8, 2015 March 23, 2015
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-03 draft-ietf-6tisch-terminology-04
Abstract Abstract
6TiSCH proposes an architecture for an IPv6 multi-link 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.
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 July 12, 2015. This Internet-Draft will expire on September 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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 . . . . . . . . . . . . . . . . . . . . . 11 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Normative References . . . . . . . . . . . . . . . . . . 11 6.1. Normative References . . . . . . . . . . . . . . . . . . 10
6.2. Informative References . . . . . . . . . . . . . . . . . 12 6.2. Informative References . . . . . . . . . . . . . . . . . 11
6.3. External Informative References . . . . . . . . . . . . . 12 6.3. External Informative References . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
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
latency. Such traffic is not limited to voice and video, but also latency. Such traffic is not limited to voice and video, but also
includes command and control operations such as in industrial includes command and control operations such as in industrial
automation or in-vehicle sensors and actuators. automation or in-vehicle sensors and actuators.
At IEEE802.1, the "Audio/Video Task Group", was renamed TSN for Time The IEEE802.15.4 Medium Access Control (MAC) has evolved with
Sensitive Networking. The IEEE802.15.4 Medium Access Control (MAC) IEEE802.15.4e which provides in particular the Time Slotted Channel
has evolved with IEEE802.15.4e which provides in particular the Time Hopping (TSCH) mode for industrial-type applications. It provides
Slotted Channel Hopping (TSCH) mode for industrial-type applications. deterministic capabilities to the point that a packet that pertains
Both provide deterministic capabilities to the point that a packet to a certain flow crosses the network from node to node following a
that pertains to a certain flow crosses the network from node to node very precise schedule, like a train leaves intermediate stations at
following a very precise schedule, like a train leaves intermediate precise times along its path.
stations at precise times along its path.
This document provides additional terminology elements to cover terms This document provides additional terminology elements to cover terms
that are new to the context of TSCH wireless networks and other that are new to the context of TSCH wireless networks and other
deterministic networks. deterministic networks.
2. Terminology 2. Terminology
The draft extends [I-D.ietf-roll-terminology] and use terms from RFC The draft extends [I-D.ietf-roll-terminology] and use terms from RFC
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 the 6top sublayer and a set IEEE 802.15.4e. It defines the 6top sublayer and a set
of protocols (in particular, for setting up a schedule of protocols (in particular, for setting up a TSCH
with a centralized or distributed approach, managing the schedule with a centralized or distributed approach,
resource allocation), as well as the architecture to bind managing the resource allocation), as well as the
them together, for use in IPv6 TSCH based networks. architecture to bind them together, for use in IPv6 TSCH
based networks.
6F: IPv6 Forwarding. One of the three forwarding models 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 Quality of Service (QoS) and Random Early Detection where Quality of Service (QoS) and Active Queue
(RED) [RFC2309] operations are expected to prioritize Management (e.g., Random Early Detection, RED, [RFC2309])
flows with differentiated services. operations are expected to prioritize flows with
differentiated services.
6top: 6top is the adaptation sublayer 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 IPv6 over Low-Power Wireless Personal Area
Networks (6LoWPANs) and IPv6 Routing Protocol for Low-
Power and Lossy Networks (RPL). It is defined in
[I-D.wang-6tisch-6top-sublayer]. [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).See set of priority queues, and a PDU (Payload Data Unit).See
[I-D.wang-6tisch-6top-sublayer]. [I-D.wang-6tisch-6top-sublayer].
ARO: [RFC6775] defines a number of new Neighbor Discovery ARO: [RFC6775] defines a number of new Neighbor Discovery
options including the Address Registration Option (ARO). options including the Address Registration Option (ARO).
ASN: Absolute Slot Number, the total number of timeslots that ASN: Absolute Slot Number, the total number of timeslots that
has elapsed since the start of the network or an has elapsed since the PAN coordinator has started the
arbitrary start time (i.e., a timeslot counter, TSCH network. It is incremented by one at each timeslot.
incremented by one at each timeslot). It is wide enough It is wide enough to not roll over in practice. See
to not roll over in practice. See [IEEE802154e]. [IEEE802154e].
Blacklist: Set of frequencies which should not be used for Blacklist of Frequencies: Simply defined Blacklist in [IEEE802154e],
it is the 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 IPv6 ND-efficiency-aware Router (NEAR) LBR and also a IPv6 ND-efficiency-aware Router (NEAR)
[I-D.chakrabarti-nordmark-6man-efficient-nd]. It [I-D.chakrabarti-nordmark-6man-efficient-nd]. It
performs ND proxy operations between registered devices performs ND proxy operations between registered devices
and classical ND devices that are located over the and classical ND devices that are located over the
backbone. backbone.
Broadcast cell: A scheduled cell used for broadcast transmission. Broadcast Cell: A scheduled cell used for broadcast transmission.
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. the bundle translates directly into bandwidth.
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.
Centralized Cell Reservation: A reservation of a cell done by a
centralized entity (e.g., a PCE) in the network.
Centralized Track Reservation: A reservation of a track done by a
centralized entity (e.g., a PCE) in the network.
ChannelOffset: Identifies a row in the TSCH schedule. The number of ChannelOffset: Identifies a row in the TSCH schedule. The number of
available channelOffsets is equal to the number 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.ietf-6tisch-tsch]. [I-D.ietf-6tisch-tsch].
Channel distribution/usage (CDU) matrix: : Matrix of height equal to Channel Distribution/Usage (CDU) matrix: : Matrix of cells (i,j)
the number of available channels (i.e, ChannelOffsets),
representing the spectrum (channel) distribution among representing the spectrum (channel) distribution among
the different (RPL parent) nodes in the networks. Every the different nodes in the 6TiSCH network. The CDU
single element of the matrix belongs to a specific chunk. matrix has width in timeslots, equal to the period of the
It has to be noticed that such matrix, even though it network scheduling operation, and height equal to the
includes all the cells grouped in chunks, belonging to number of available channels. Every cell (i,j) in the
different slotframes, is different from the TSCH CDU, identified by (slotOffset, channelOffset), belongs
schedule. to a specific chunk. It has to be noticed that such a
matrix, even though it includes all the cells grouped in
chunks, belonging to different slotframes, is different
from the TSCH schedule.
Chunk: A well-known list of cells, well-distributed in time and Chunk: A well-known list of cells, distributed in time and
frequency, within a CDU matrix; a chunk represents a frequency, within a CDU matrix; a chunk represents a
portion of a CDU matrix that is globally known by all the portion of a CDU matrix. The partition of the CDU in
nodes in the network, with typically at most one cell per chunks is globally known by all the nodes in the network
slotOffset for single radio devices. Once appropriated, to support the appropriation process, which is a
a chunk can be managed separately by a single node within negotiation between nodes within an interference domain.
its interference domain. A node may appropriate multiple A node that manages to appropriate a chunk gets to decide
chunks, and use them according to a specific policy. which transmissions will occur over the cells in the
Chunks may overlap. They can be pre-programmed, or can chunk within its interference domain (i.e., a parent node
be computed by an external entity at the network will decide when the cells within the appropriated chunk
bootstrap. are used and by which node, among its children.
Chunk ownership appropriation: The process by which an individual
node obtains a chunk to manage based on peer-to-peer
interaction with its neighbors.
Chunk ownership delegation: The process by which an individual node
obtains a chunk to manage based on point-to-point
interaction with an external entity.
CoAP: The Constrained Application Protocol (CoAP), defined in
[RFC7252] is an HTTP-like resource access protocol. CoAP
runs over UDP.
Communication Paradigm: It is Associated with the Information Model Communication Paradigm: It is Associated with the Information Model
[RFC3444] of the state that is exchanged, and indicates: [RFC3444] of the state that is exchanged, and indicates:
the location of that state (e.g., centralized vs. the location of that state (e.g., centralized vs.
distributed, RESTful, etc.), the numbers of parties distributed, RESTful, etc.), the numbers of parties
(e.g., P2P vs. P2MP) and the relationship between parties (e.g., point to point, P2P, vs. point to multi-point,
(e.g., master/slave vs. peers) at a high level of P2MP) and the relationship between parties (e.g., master/
protocol abstraction. Layer 5 client/server REST is a slave vs. peers) at a high level of protocol abstraction.
typical communication paradigm, but industrial protocols Layer 5 client/server REST is a typical communication
also use publish/subscribe which is P2MP and source/sink paradigm, but industrial protocols also use publish/
which is MP2MP and primarily used for alarms and alerts subscribe which is P2MP and source/sink which is multi-
at the application layer. At layer 3, basic flooding, point to multi-point (MP2MP) and primarily used for
P2P synchronization and path-marking (RSVP-like) are alarms and alerts at the application layer. At layer 3,
commonly used paradigms, whereas at layer 2, master/slave basic flooding, P2P synchronization and path-marking
polling and peer-to-peer forwarding are classical (RSVP-like) are commonly used paradigms, whereas at layer
examples. 2, master/slave polling and peer-to-peer forwarding are
classical examples.
DAR/DAC: [RFC6775] defines the Duplicate Address Request (DAR) and DAR/DAC: [RFC6775] defines the Duplicate Address Request (DAR) and
Duplicate Address Confirmation (DAC) options to turn the Duplicate Address Confirmation (DAC) options to turn the
multicast Duplicate Address Detection protocol into a multicast Duplicate Address Detection protocol into a
client/server process. unicast-based multi-hop process between routers and the
backbone router.
Dedicated Cell: A cell that is reserved for a given node to transmit Dedicated Cell: A cell that is reserved for a given node to transmit
to a specific neighbor. to a specific neighbor.
DevID: The secure DEVice IDentifier (DevID) defined in Deterministic Network: A Deterministic Network supports traffic
[IEEE.802.1AR] is a device identifier that is flows with communication patterns that are known a
cryptographically bound to the device. It is composed of priori. Thus, routing paths and communication schedules
the Secure Device Identifier Secret and the Secure Device can be computed in advance, in a fashion similar to a
Identifier Credential. railway system, to avoid losses due to packet collisions,
and to perform global optimizations across multiple
flows. A deterministic network can allocates the
required resources (buffers, processors, medium access)
along the multi-hop routing path at the precise moment
the resources are needed.
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).
DTLS: The datagram version of the Transport Layer Security
(TLS) Protocol, defined in [RFC6347], and which can be
used to secure CoAP in the same way that TLS secures
HTTP.
EARO: [I-D.thubert-6lo-rfc6775-update-reqs]extends the ARO EARO: [I-D.thubert-6lo-rfc6775-update-reqs]extends the ARO
option to include some additional fields necessary to option to include some additional fields necessary to
distinguish duplicate addresses from nodes that have distinguish duplicate addresses from nodes that have
moved networks when there are mulitple LLNs linked over a moved networks when there are mulitple LLNs linked over a
backbone. backbone.
EB: Enhanced Beacon frame used by a node to announce the EB: Enhanced Beacon frame used by a node to announce the
presence of the network. It contains information about presence of the network. It contains useful information
the timeslot length, the current ASN value, the (see [IEEE802154e] for details) that allow a new node to
slotframes and timeslots the beaconing mote is listening synhronize and join the network.
on, and a 1-byte join priority (i.e., number of hops
separating the node sending the EB, and the PAN
coordinator).
FF: 6LoWPAN Fragment Forwarding. It is one of the three FF: 6LoWPAN Fragment Forwarding. It is one of the three
forwarding models 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.wang-6tisch-6top-sublayer]. reallocate. See [I-D.wang-6tisch-6top-sublayer].
Hopping Sequence: Ordered 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 [IEEE802154e] and (i.e., PHY channel). See [IEEE802154e] and
[I-D.ietf-6tisch-tsch]. [I-D.ietf-6tisch-tsch].
IDevID: The Initial secure DEVice IDentifier (IDevID) is the
Device Identifier which was installed on the device by
the manufacturer.
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 [IEEE802154e], but a range of types types are defined by [IEEE802154e], but a range of types
is available for extensions, and thus, is exploitable by is available for extensions, and thus, is exploitable by
6TiSCH. See [IEEE802154e]. 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. See 6LoWPAN frames and places them into priority queues. See
[I-D.wang-6tisch-6top-sublayer]. [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.
JCE: The Join Coordination Entity (JCE) is a central entity Interference Domain: The Interference Domain of a given
like the Path Computation Engine (PCE), that is in charge (transmitter) node A includes all the nodes in its
of authorization to join a network. The JCE provides neighbourhood that can generate interference at its
security credentials to joining devices. receiver B, when transmitting on the same channel (i.e.,
using the same frequency).
JA: The Join Assistant (JA) is a constrained node near the JCE: The Join Coordination Entity (JCE) is a central entity
joining node that will act as its first 6LR, and will like the Path Computation Engine (PCE), that may assist
relay traffic to/from the joining node. in several aspects of the join protocol, such as
authentication, authorization, and configuration.
JN: The Joining Node (JN) leverages the JA and the JCE to JA: The Join Assistant (JA) is a one-hop neighbor of a
learn or refresh its knowledge of the network operational joining node that may facilitate it to become meaningful
state and to obtain security material to participate to part of the network (e.g., by serving as a local
the production network. connectivity point to the remainder of the network).
Join Protocol: The protocol which secures initial communication Join Protocol: The protocol which secures initial communication
between the JN and the JCE. between a joining node and the JCE.
KMP: Key Management Protocol.
LBR: LLN Border Router. It is an LLN device, usually powered,
that acts as a Border Router to the outside within the
6TiSCH architecture.
LDevID: A Locally significant secure DEVice IDentifiers (LDevID) LBR: Low-power Lossy Network (LLN) Border Router. It is an
is a Secure Device Identifier credential that is unique LLN device, usually powered, that acts as a Border Router
in the local administrative domain in which the device is to the outside within the 6TiSCH architecture.
used. The LDevID is usually a new certificate
provisioned by some local means, such as the 6top
sublayer [I-D.wang-6tisch-6top-sublayer].
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 IEEE802.15.4e term "Link" is adopted, as opposed to the IEEE802.15.4e
terminology. In the context of the 6TiSCH architecture, terminology. In the context of the 6TiSCH architecture,
which applies to Low Power Lossy Networks (LLNs), an IPv6 which applies to Low Power Lossy Networks (LLNs), an IPv6
subnet is usually not congruent to a single link and subnet is usually not congruent to a single link and
techniques such as IPv6 Neighbor Discovery Proxying are techniques such as IPv6 Neighbor Discovery Proxying are
used to achieve reachability within the multilink subnet. used to achieve reachability within the multilink subnet.
skipping to change at page 8, line 25 skipping to change at page 8, line 13
Forwarding), a single radio interface may be seen as a Forwarding), a single radio interface may be seen as a
number of Links with different capabilities for unicast number of Links with different capabilities for unicast
or multicast services. or multicast 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. See [I-D.wang-6tisch-6top-sublayer]. transmission. See [I-D.wang-6tisch-6top-sublayer].
NEAR: Energy Aware Default Router, as defined in NEAR: IPv6 ND-efficiency-aware 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.
Operational Network: A IEEE802.15.4e network whose encryption/ Operational Network: A IEEE802.15.4e network whose encryption/
authentication keys are determined by some algorithms/ authentication keys are determined by some algorithms/
protocols. There may be network-wide group keys, or per- protocols. There may be network-wide group keys, or per-
link keys. link keys.
Operational Network Key: A Link-layer key known by all authorized Operational Network Key: A Link-layer key known by all authorized
nodes, used for multicast messages. nodes, used for multicast messages.
PANA: Protocol for carrying Authentication for Network Access,
as defined in [RFC5191] .
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 track reservation: The reservation of a track done by the PCE.
Per-Peer L2 Key: A key that results from an exchange (such as MLE)
that creates a pair-wise link-layer key which is known
only to the two nodes involved.
QoS: Quality of Service. QoS: Quality of Service.
(to) reallocate a cell: The action operated by the 6top sublayer of (to) Reallocate a Cell: The action operated by the 6top sublayer of
changing the slotOffset and/or channelOffset of a soft changing the slotOffset and/or channelOffset of a soft
cell. cell.
SA: Security Association. (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 marked with both the "TX" and "shared" flags. Shared Cell: A cell marked with both the "TX" and "shared" flags.
skipping to change at page 10, line 6 skipping to change at page 9, line 28
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.wang-6tisch-6top-sublayer]. 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 GMPLS-like
like forwarding model. The input cell characterizes the forwarding model. The input cell characterizes the flow
flow and indicates the output cell. 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. acknowledgment.
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 track reservation. The
that initializes the process for establishing a track is node that initializes the process for establishing a
the owner of the track. The latter assigns a unique track is the owner of the track. The latter assigns a
identifier to the track, called TrackID. unique 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 TSCH schedule contains all the and a channelOffset. The TSCH schedule contains all the
scheduled cells from all slotframes and is sufficient to scheduled cells from all slotframes and is sufficient to
qualify the communication in the TSCH network. The qualify the communication in the TSCH network. The
"width of the matrix is equal to the number of scheduled "width of the matrix is equal to the number of scheduled
timeslots in all the concurrent active slotframes. The 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.
unique join key: A key shared between a JN and the JCE. This key Unscheduled Cell: A cell which is not used by the IEEE802.15.4e TSCH
supports smaller installations for which asymmetric
methods are considered too large.
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 threats. This specification is not found to introduce new security threats.
skipping to change at page 12, line 19 skipping to change at page 11, line 35
[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
Application Protocol (CoAP)", RFC 7252, June 2014. Application Protocol (CoAP)", RFC 7252, June 2014.
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, "IPv6 Neighbor Discovery Optimizations for Wasserman, "IPv6 Neighbor Discovery Optimizations for
Wired and Wireless Networks", draft-chakrabarti-nordmark- Wired and Wireless Networks", draft-chakrabarti-nordmark-
6man-efficient-nd-06 (work in progress), July 2014. 6man-efficient-nd-07 (work in progress), February 2015.
[I-D.ietf-6tisch-tsch] [I-D.ietf-6tisch-tsch]
Watteyne, T., Palattella, M., and L. Grieco, "Using Watteyne, T., Palattella, M., and L. Grieco, "Using
IEEE802.15.4e TSCH in an IoT context: Overview, Problem IEEE802.15.4e TSCH in an IoT context: Overview, Problem
Statement and Goals", draft-ietf-6tisch-tsch-04 (work in Statement and Goals", draft-ietf-6tisch-tsch-06 (work in
progress), December 2014. progress), March 2015.
[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.thubert-6lo-rfc6775-update-reqs] [I-D.thubert-6lo-rfc6775-update-reqs]
Thubert, P., "Requirements for an update to 6LoWPAN ND", Thubert, P. and P. Stok, "Requirements for an update to
draft-thubert-6lo-rfc6775-update-reqs-05 (work in 6LoWPAN ND", draft-thubert-6lo-rfc6775-update-reqs-06
progress), October 2014. (work in progress), January 2015.
[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.wang-6tisch-6top-sublayer] [I-D.wang-6tisch-6top-sublayer]
Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH
Operation Sublayer (6top)", draft-wang-6tisch-6top- Operation Sublayer (6top)", draft-wang-6tisch-6top-
sublayer-01 (work in progress), July 2014. sublayer-01 (work in progress), July 2014.
skipping to change at page 13, line 33 skipping to change at page 13, line 4
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
Phone: +1 (510) 400-2978 Phone: +1 (510) 400-2978
Email: twatteyne@linear.com Email: twatteyne@linear.com
Qin Wang Qin Wang
Univ. of Sci. and Tech. Beijing Univ. of Sci. and Tech. Beijing
30 Xueyuan Road 30 Xueyuan Road
Beijing, Hebei 100083 Beijing 100083
China China
Phone: +86 (10) 6233 4781 Phone: +86 (10) 6233 4781
Email: wangqin@ies.ustb.edu.cn Email: wangqin@ies.ustb.edu.cn
 End of changes. 46 change blocks. 
158 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/