6TiSCH MR. Palattella, Ed.
Internet-Draft SnT/Univ. of Luxembourg
Intended status: Informational P. Thubert
Expires: July 12, 2015 cisco
T. Watteyne
Linear Technology / Dust Networks
Q. Wang
Univ. of Sci. and Tech. Beijing
January 8, 2015
Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e
draft-ietf-6tisch-terminology-03
Abstract
6TiSCH proposes an architecture for an IPv6 multi-link subnet that is
composed of a high speed powered backbone and a number of
IEEE802.15.4e TSCH wireless networks attached and synchronized by
backbone routers. This document extends existing terminology
documents available for Low-power and Lossy Networks to provide
additional terminology elements.
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 July 12, 2015.
Palattella, et al. Expires July 12, 2015 [Page 1]
Internet-Draft 6tisch-terminology January 2015
Copyright Notice
Copyright (c) 2015 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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1. Normative References . . . . . . . . . . . . . . . . . . 11
6.2. Informative References . . . . . . . . . . . . . . . . . 12
6.3. External Informative References . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
A new breed of Time Sensitive Networks is being developed to enable
traffic that is highly sensitive to jitter and quite sensitive to
latency. Such traffic is not limited to voice and video, but also
includes command and control operations such as in industrial
automation or in-vehicle sensors and actuators.
At IEEE802.1, the "Audio/Video Task Group", was renamed TSN for Time
Sensitive Networking. The IEEE802.15.4 Medium Access Control (MAC)
has evolved with IEEE802.15.4e which provides in particular the Time
Slotted Channel Hopping (TSCH) mode for industrial-type applications.
Both provide deterministic capabilities to the point that a packet
that pertains to a certain flow crosses the network from node to node
following a very precise schedule, like a train leaves intermediate
stations at precise times along its path.
This document provides additional terminology elements to cover terms
that are new to the context of TSCH wireless networks and other
deterministic networks.
Palattella, et al. Expires July 12, 2015 [Page 2]
Internet-Draft 6tisch-terminology January 2015
2. Terminology
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
reference.
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
IETF parlance.
This document adds the following terms:
6TiSCH: IPv6 over the Timeslotted Channel Hopping (TSCH) mode of
IEEE 802.15.4e. It defines the 6top sublayer and a set
of protocols (in particular, for setting up a schedule
with a centralized or distributed approach, managing the
resource allocation), as well as the architecture to bind
them together, for use in IPv6 TSCH based networks.
6F: IPv6 Forwarding. One of the three forwarding models
supported by 6TiSCH. Packets are routed at layer 3,
where Quality of Service (QoS) and Random Early Detection
(RED) [RFC2309] operations are expected to prioritize
flows with differentiated services.
6top: 6top is the adaptation sublayer between TSCH and upper
layers like 6LoWPAN and RPL. It is defined in
[I-D.wang-6tisch-6top-sublayer].
6top Data Convey Model: Model describing how the 6top adaptation
layer feeds the data flow coming from upper layers into
TSCH. It is composed by an I-MUX module, a MUX module, a
set of priority queues, and a PDU (Payload Data Unit).See
[I-D.wang-6tisch-6top-sublayer].
ARO: [RFC6775] defines a number of new Neighbor Discovery
options including the Address Registration Option (ARO).
ASN: Absolute Slot Number, the total number of timeslots that
has elapsed since the start of the network or an
arbitrary start time (i.e., a timeslot counter,
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
communication.
Palattella, et al. Expires July 12, 2015 [Page 3]
Internet-Draft 6tisch-terminology January 2015
BBR: Backbone Router. In the 6TiSCH architecture, it is an
LBR and also a IPv6 ND-efficiency-aware Router (NEAR)
[I-D.chakrabarti-nordmark-6man-efficient-nd]. It
performs ND proxy operations between registered devices
and classical ND devices that are located over the
backbone.
Broadcast cell: A scheduled cell used for broadcast transmission.
Bundle: A group of equivalent scheduled cells, i.e. cells
identified by different [slotOffset, channelOffset],
which are scheduled for a same purpose, with the same
neighbor, with the same flags, and the same slotframe.
The size of the bundle refers to the number of cells it
contains. Given the length of the slotframe, the size of
the bundle translates directly into bandwidth.
Cell: A single element in the TSCH schedule, identified by a
slotOffset, a channelOffset, a slotframeHandle. A cell
can be scheduled or unscheduled.
ChannelOffset: Identifies a row in the TSCH schedule. The number of
available channelOffsets is equal to the number of
available frequencies. The channelOffset translates into
a frequency when the communication takes place, resulting
in channel hopping, as detailed in
[I-D.ietf-6tisch-tsch].
Channel distribution/usage (CDU) matrix: : Matrix of height equal to
the number of available channels (i.e, ChannelOffsets),
representing the spectrum (channel) distribution among
the different (RPL parent) nodes in the networks. Every
single element of the matrix belongs to a specific chunk.
It has to be noticed that such 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
frequency, within a CDU matrix; a chunk represents a
portion of a CDU matrix that is globally known by all the
nodes in the network, with typically at most one cell per
slotOffset for single radio devices. Once appropriated,
a chunk can be managed separately by a single node within
its interference domain. A node may appropriate multiple
chunks, and use them according to a specific policy.
Chunks may overlap. They can be pre-programmed, or can
Palattella, et al. Expires July 12, 2015 [Page 4]
Internet-Draft 6tisch-terminology January 2015
be computed by an external entity at the network
bootstrap.
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
[RFC3444] of the state that is exchanged, and indicates:
the location of that state (e.g., centralized vs.
distributed, RESTful, etc.), the numbers of parties
(e.g., P2P vs. P2MP) and the relationship between parties
(e.g., master/slave vs. peers) at a high level of
protocol abstraction. Layer 5 client/server REST is a
typical communication paradigm, but industrial protocols
also use publish/subscribe which is P2MP and source/sink
which is MP2MP and primarily used for alarms and alerts
at the application layer. At layer 3, basic flooding,
P2P synchronization and path-marking (RSVP-like) are
commonly used paradigms, whereas at layer 2, master/slave
polling and peer-to-peer forwarding are classical
examples.
DAR/DAC: [RFC6775] defines the Duplicate Address Request (DAR) and
Duplicate Address Confirmation (DAC) options to turn the
multicast Duplicate Address Detection protocol into a
client/server process.
Dedicated Cell: A cell that is reserved for a given node to transmit
to a specific neighbor.
DevID: The secure DEVice IDentifier (DevID) defined in
[IEEE.802.1AR] is a device identifier that is
cryptographically bound to the device. It is composed of
the Secure Device Identifier Secret and the Secure Device
Identifier Credential.
Distributed cell reservation: A reservation of a cell done by one or
more in-network entities (typically a connection
endpoint).
Palattella, et al. Expires July 12, 2015 [Page 5]
Internet-Draft 6tisch-terminology January 2015
Distributed track reservation: A reservation of a track done by one
or more in-network entities (typically a connection
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
option to include some additional fields necessary to
distinguish duplicate addresses from nodes that have
moved networks when there are mulitple LLNs linked over a
backbone.
EB: Enhanced Beacon frame used by a node to announce the
presence of the network. It contains information about
the timeslot length, the current ASN value, the
slotframes and timeslots the beaconing mote is listening
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
forwarding models supported by 6TiSCH. The 6LoWPAN
Fragment is used as a label for switching at the 6LoWPAN
sublayer, as defined in
[I-D.thubert-roll-forwarding-frags].
GMPLS: Generalized Multi-Protocol Label Switching, a 2.5 layer
service that is used to forward packets based on the
concept of generalized labels.
Hard Cell: A scheduled cell which the 6top sublayer cannot
reallocate. See [I-D.wang-6tisch-6top-sublayer].
Hopping Sequence: Ordered sequence of frequencies, identified by a
Hopping_Sequence_ID, used for channel hopping, when
translating the channel offset value into a frequency
(i.e., PHY channel). See [IEEE802154e] and
[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
containers placed at the end of the MAC header, used to
Palattella, et al. Expires July 12, 2015 [Page 6]
Internet-Draft 6tisch-terminology January 2015
pass data between layers or devices. A small number of
types are defined by [IEEE802154e], but a range of types
is available for extensions, and thus, is exploitable by
6TiSCH. See [IEEE802154e].
I-MUX module: Inverse-Multiplexer, a classifier that receives
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
communication paradigm. Defined at a lower level of
abstraction, it includes protocol-specific details such
as a particular method (e.g., a REST GET) and a Data
Model for the state to be exchanged.
JCE: The Join Coordination Entity (JCE) is a central entity
like the Path Computation Engine (PCE), that is in charge
of authorization to join a network. The JCE provides
security credentials to joining devices.
JA: The Join Assistant (JA) is a constrained node near the
joining node that will act as its first 6LR, and will
relay traffic to/from the joining node.
JN: The Joining Node (JN) leverages the JA and the JCE to
learn or refresh its knowledge of the network operational
state and to obtain security material to participate to
the production network.
Join Protocol: The protocol which secures initial communication
between the JN 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)
is a Secure Device Identifier credential that is unique
in the local administrative domain in which the device is
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
communicate at the link layer, i.e., the layer
immediately below IP. Thus, the IETF parlance for the
Palattella, et al. Expires July 12, 2015 [Page 7]
Internet-Draft 6tisch-terminology January 2015
term "Link" is adopted, as opposed to the IEEE802.15.4e
terminology. In the context of the 6TiSCH architecture,
which applies to Low Power Lossy Networks (LLNs), an IPv6
subnet is usually not congruent to a single link and
techniques such as IPv6 Neighbor Discovery Proxying are
used to achieve reachability within the multilink subnet.
A link is distinct from a track. In fact, link local
addresses are not expected to be used over a track for
end to end communication. Finally, from the Layer 3
perspective (where the inner complexities of TSCH
operations are hidden to enable classical IP routing and
Forwarding), a single radio interface may be seen as a
number of Links with different capabilities for unicast
or multicast services.
Logical Cell: A cell that corresponds to granted bandwidth but is
only lazily associated to a physical cell, based on
usage.
MAC: Medium Access Control.
MUX module: Multiplexer, the entity that dequeues frames from
priority queues and associates them to a cell for
transmission. See [I-D.wang-6tisch-6top-sublayer].
NEAR: Energy Aware Default Router, as defined in
[I-D.chakrabarti-nordmark-6man-efficient-nd].
NME: Network Management Entity, the entity in the network
managing cells and other device resources. It may
cooperate with the PCE. It interacts with LLN nodes
through the backbone router.
Operational Network: A IEEE802.15.4e network whose encryption/
authentication keys are determined by some algorithms/
protocols. There may be network-wide group keys, or per-
link keys.
Operational Network Key: A Link-layer key known by all authorized
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
is responsible for building and maintaining the TSCH
schedule, when centralized scheduling is used.
Palattella, et al. Expires July 12, 2015 [Page 8]
Internet-Draft 6tisch-terminology January 2015
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.
(to) reallocate a cell: The action operated by the 6top sublayer of
changing the slotOffset and/or channelOffset of a soft
cell.
SA: Security Association.
(to) Schedule a cell: The action of turning an unscheduled cell into
a scheduled cell.
Scheduled cell: A cell which is assigned a neighbor MAC address
(broadcast address is also possible), and one or more of
the following flags: TX, RX, shared, timeskeeping. A
scheduled cell can be used by the IEEE802.15.4e TSCH
implementation to communicate. A scheduled cell can be a
hard cell or a soft cell.
Shared Cell: A cell marked with both the "TX" and "shared" flags.
This cell can be used by more than one transmitter node.
A backoff algorithm is used to resolve contention. See
[I-D.ietf-6tisch-tsch].
SlotOffset: Identifies a column in the TSCH schedule, i.e., the
number of timeslots since the beginning of the current
iteration of the slotframe.
Slotframe: A MAC-level abstraction that is internal to the node and
contains a series of timeslots of equal length and
priority. It is characterized by a slotframe_ID, and a
slotframe_size. Multiple slotframes can coexist in a
node's schedule, i.e., a node can have multiple
activities scheduled in different slotframes, based on
the priority of its packets/traffic flows. The timeslots
in the Slotframe are indexed by the SlotOffset; the first
timeslot is at SlotOffset 0.
Soft Cell: A scheduled cell which the 6top sublayer can reallocate,
as described in [I-D.wang-6tisch-6top-sublayer].
Palattella, et al. Expires July 12, 2015 [Page 9]
Internet-Draft 6tisch-terminology January 2015
TF: Track Forwarding. It is the simplest and fastest
forwarding model supported by 6TiSCH. It is a G-MPLS-
like forwarding model. The input cell characterizes the
flow and indicates the output cell.
Timeslot: A basic communication unit in TSCH which allows a
transmitter node to send a frame to a receiver neighbor,
and that receiver neighbor to optionally send back an
acknowledgment.
Time Source Neighbor: A neighbor a node uses as its time reference,
and to which it needs to keep its clock synchronized. A
node can have one or more time source neighbors.
Track: A determined sequence of cells along a multi-hop path.
It is typically the result of a reservation. The node
that initializes the process for establishing a track is
the owner of the track. The latter assigns a unique
identifier to the track, called TrackID.
TrackID: Unique identifier of a track, assigned by the owner of
the track.
TSCH: Time Slotted Channel Hopping, a medium access mode of the
[IEEE802154e] standard which uses time synchronization to
achieve ultra low-power operation and channel hopping to
enable high reliability.
TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset
and a channelOffset. The TSCH schedule contains all 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
matrix) is equal to the number of available frequencies.
unique join key: A key shared between a JN and the JCE. This key
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.
Palattella, et al. Expires July 12, 2015 [Page 10]
Internet-Draft 6tisch-terminology January 2015
3. IANA Considerations
This specification does not require IANA action.
4. Security Considerations
This specification is not found to introduce new security threats.
5. Acknowledgments
Thanks to the IoT6 European Project (STREP) of the 7th Framework
Program (Grant 288445).
6. References
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
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
Information Models and Data Models", RFC 3444, January
2003.
[RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A.
Yegin, "Protocol for Carrying Authentication for Network
Access (PANA)", RFC 5191, May 2008.
[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
Security Version 1.2", RFC 6347, January 2012.
[RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R.,
Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.
Alexander, "RPL: IPv6 Routing Protocol for Low-Power and
Lossy Networks", RFC 6550, March 2012.
[RFC6552] Thubert, P., "Objective Function Zero for the Routing
Protocol for Low-Power and Lossy Networks (RPL)", RFC
6552, March 2012.
Palattella, et al. Expires July 12, 2015 [Page 11]
Internet-Draft 6tisch-terminology January 2015
[RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann,
"Neighbor Discovery Optimization for IPv6 over Low-Power
Wireless Personal Area Networks (6LoWPANs)", RFC 6775,
November 2012.
[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
Application Protocol (CoAP)", RFC 7252, June 2014.
6.2. Informative References
[I-D.chakrabarti-nordmark-6man-efficient-nd]
Chakrabarti, S., Nordmark, E., Thubert, P., and M.
Wasserman, "IPv6 Neighbor Discovery Optimizations for
Wired and Wireless Networks", draft-chakrabarti-nordmark-
6man-efficient-nd-06 (work in progress), July 2014.
[I-D.ietf-6tisch-tsch]
Watteyne, T., Palattella, M., and L. Grieco, "Using
IEEE802.15.4e TSCH in an IoT context: Overview, Problem
Statement and Goals", draft-ietf-6tisch-tsch-04 (work in
progress), December 2014.
[I-D.ietf-roll-terminology]
Vasseur, J., "Terms used in Routing for Low power And
Lossy Networks", draft-ietf-roll-terminology-13 (work in
progress), October 2013.
[I-D.thubert-6lo-rfc6775-update-reqs]
Thubert, P., "Requirements for an update to 6LoWPAN ND",
draft-thubert-6lo-rfc6775-update-reqs-05 (work in
progress), October 2014.
[I-D.thubert-roll-forwarding-frags]
Thubert, P. and J. Hui, "LLN Fragment Forwarding and
Recovery", draft-thubert-roll-forwarding-frags-02 (work in
progress), September 2013.
[I-D.wang-6tisch-6top-sublayer]
Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH
Operation Sublayer (6top)", draft-wang-6tisch-6top-
sublayer-01 (work in progress), July 2014.
6.3. External Informative References
[IEEE.802.1AR]
IEEE standard for Information Technology, "802.1AR-2009 -
IEEE Standard for Local and metropolitan area networks -
Secure Device Identity", 2009.
Palattella, et al. Expires July 12, 2015 [Page 12]
Internet-Draft 6tisch-terminology January 2015
[IEEE802154e]
IEEE standard for Information Technology, "IEEE std.
802.15.4e, Part. 15.4: Low-Rate Wireless Personal Area
Networks (LR-WPANs) Amendment 1: MAC sublayer", April
2012.
Authors' Addresses
Maria Rita Palattella (editor)
University of Luxembourg
Interdisciplinary Centre for Security, Reliability and Trust
4, rue Alphonse Weicker
Luxembourg L-2721
Luxembourg
Phone: (+352) 46 66 44 5841
Email: maria-rita.palattella@uni.lu
Pascal Thubert
Cisco Systems, Inc
Village d'Entreprises Green Side
400, Avenue de Roumanille
Batiment T3
Biot - Sophia Antipolis 06410
France
Phone: +33 497 23 26 34
Email: pthubert@cisco.com
Thomas Watteyne
Linear Technology / Dust Networks
30695 Huntwood Avenue
Hayward, CA 94544
USA
Phone: +1 (510) 400-2978
Email: twatteyne@linear.com
Palattella, et al. Expires July 12, 2015 [Page 13]
Internet-Draft 6tisch-terminology January 2015
Qin Wang
Univ. of Sci. and Tech. Beijing
30 Xueyuan Road
Beijing, Hebei 100083
China
Phone: +86 (10) 6233 4781
Email: wangqin@ies.ustb.edu.cn
Palattella, et al. Expires July 12, 2015 [Page 14]