draft-ietf-6tisch-terminology-00.txt   draft-ietf-6tisch-terminology-01.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: April 14, 2014 cisco Expires: August 17, 2014 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
November 18, 2013 February 13, 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-00 draft-ietf-6tisch-terminology-01
Abstract Abstract
6TiSCH proposes an architecture for an IPv6 multilink subnet that is 6TiSCH proposes an architecture for an IPv6 multilink 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 April 14, 2014. This Internet-Draft will expire on August 17, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
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 . . . . . . . . . . . . . . . . . . . . . 8 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. Normative References . . . . . . . . . . . . . . . . . . 8 6.1. Normative References . . . . . . . . . . . . . . . . . . 9
6.2. Informative References . . . . . . . . . . . . . . . . . 9 6.2. Informative References . . . . . . . . . . . . . . . . . 10
6.3. External Informative References . . . . . . . . . . . . . 10 6.3. External Informative References . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 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
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 At IEEE802.1, the "Audio/Video Task Group", was renamed TSN for Time
skipping to change at page 3, line 51 skipping to change at page 3, line 51
[I-D.watteyne-6tsch-tsch-lln-context]. [I-D.watteyne-6tsch-tsch-lln-context].
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 NEAR. It performs ND proxy operations
between registered devices and classical ND devices that between registered devices and classical ND devices that
are located over the backbone. are located over the backbone.
Broadcast cell: A scheduled cell whose neighbor MAC address is set
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, either
logical, or physical. logical, or physical.
Cell: A single element in the TSCH sloframe, identified by a Cell: A single element in the TSCH schedule, identified by a
slotOffset value, a channelOffset value, a slotframe_ID slotOffset, a channelOffset, a slotframeHandle. A cell
and Hopping_Sequence_ID. A cell can be scheduled or can be scheduled or unscheduled.
unscheduled. During an unscheduled cell, the node does
not communicate. When a cell is scheduled, it is
assigned a MAC-layer slotframe identifier, a neighbor MAC
address (which can be the broadcast address), and one or
more of the following flags: TX, RX, shared,
timeskeeping, hard. A broadcast cell is an alias for "a
scheduled cell with neighbor address the broadcast
address".
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.watteyne-6tsch-tsch-lln-context].
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 slotframe; a chunk represents a
portion of a slotframe that is globally known by all the
nodes in the network, but it can be managed separately by
a single node. A node can have multiple 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
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.
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., P2P vs. P2MP) and the relationship between parties
(e.g., master/slave vs. peers) at a high level of (e.g., master/slave vs. peers) at a high level of
protocol abstraction. Layer 5 client/server REST is a protocol abstraction. Layer 5 client/server REST is a
typical communication paradigm, but industrial protocols typical communication paradigm, but industrial protocols
also use publish/subscribe which is P2MP and source/sink also use publish/subscribe which is P2MP and source/sink
which is MP2MP and primarily used for alarms and alerts which is MP2MP and primarily used for alarms and alerts
skipping to change at page 5, line 27 skipping to change at page 5, line 50
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 model 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 that is locked, i.e., it cannot be moved Hard Cell: A scheduled cell which the 6top sublayer cannot
by 6top in the schedule. See reallocate. See [I-D.draft-wang-6tsch-6top].
[I-D.draft-wang-6tsch-6top].
Hopping Sequence: Sequence of frequencies, identified by a Hopping Sequence: 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
[I-D.watteyne-6tsch-tsch-lln-context]. [I-D.watteyne-6tsch-tsch-lln-context].
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
skipping to change at page 7, line 15 skipping to change at page 7, line 38
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.
(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. 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 that is used by more than one transmitter nodes Shared Cell: A cell that is used by more than one transmitter nodes
at the same time and on the same channelOffset. Only at the same time and on the same channelOffset. Only
cells with TX flag can be marked as "shared". A backoff cells with TX flag can be marked as "shared". A backoff
algorithm is used to resolve contention. algorithm is used to resolve contention.
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 that is not locked, i.e., it may be Soft Cell: A scheduled cell which the 6top sublayer can reallocate,
moved in the schedule within a same slotframe by 6top, as as described in [I-D.draft-wang-6tsch-6top].
described in [I-D.draft-wang-6tsch-6top].
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 characterises 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 length of the timeslot determines
skipping to change at page 8, line 32 skipping to change at page 9, line 16
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 slotframe size (the "width" of
the matrix) is the number of timeslots it contains. The the matrix) is the number of timeslots it contains. 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 The TSCH schedule contains all the scheduled cells from
all slotframes and is sufficient to qualify the all slotframes and is sufficient to qualify the
communication in the TSCH network. communication in the TSCH network.
unscheduled cell: A cell which is not used by the IEEE802.15.4e TSCH
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 threat.
5. Acknowledgements 5. Acknowledgements
skipping to change at page 9, line 26 skipping to change at page 10, line 13
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, "Efficiency aware IPv6 Neighbor Discovery Wasserman, "Wired and Wireless IPv6 Neighbor Discovery
Optimizations", draft-chakrabarti-nordmark-6man-efficient- Optimizations", draft-chakrabarti-nordmark-6man-efficient-
nd-02 (work in progress), July 2013. nd-04 (work in progress), October 2013.
[I-D.draft-sudhaakar-6tisch-coap] [I-D.draft-sudhaakar-6tisch-coap]
Sudhaakar, R., Ed. and P. Zand, "6TiSCH Data Model for Sudhaakar, R., Ed. and P. Zand, "6TiSCH Data Model for
CoAP-00 (work in progress) ", October 2013. CoAP-00 (work in progress)", October 2013.
[I-D.draft-wang-6tsch-6top] [I-D.draft-wang-6tsch-6top]
Wang, Q., Ed., Vilajosana, X., and T. Watteyne, "6TiSCH Wang, Q., Ed., Vilajosana, X., and T. Watteyne, "6TiSCH
Operation Sublayer (6top). draft-wang-6tisch-6top-00 (work Operation Sublayer (6top). draft-wang-6tisch-6top-00 (work
in progress) ", October 2013. in progress)", October 2013.
[I-D.ietf-roll-terminology] [I-D.ietf-roll-terminology]
Vasseur, J., "Terms used in Ruting for Low power And Lossy Vasseur, J., "Terms used in Routing for Low power And
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] [I-D.ohba-6tsch-security]
Chasko, S., Das, S., Lopez, R., Ohba, Y., Thubert, P., and Chasko, S., Das, S., Lopez, R., Ohba, Y., Thubert, P., and
A. Yegin, "Security Framework and Key Management Protocol A. Yegin, "Security Framework and Key Management Protocol
Requirements for 6TSCH", draft-ohba-6tsch-security-01 Requirements for 6TSCH", draft-ohba-6tsch-security-01
(work in progress), July 2013. (work in progress), July 2013.
[I-D.thubert-6tisch-architecture] [I-D.thubert-6tisch-architecture]
Thubert, P., Assimiti, R., and T. Watteyne, "An Thubert, P., Watteyne, T., and R. Assimiti, "An
Architecture for IPv6 over the TSCH mode of IEEE Architecture for IPv6 over the TSCH mode of IEEE
IEEE802.15.4e", draft-thubert-6tisch-architecture-00 (work 802.15.4e", draft-thubert-6tisch-architecture-01 (work in
in progress), October 2013. 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.vilajosana-6tisch-minimal]
Vilajosana, X. and K. Pister, "Minimal 6TiSCH Vilajosana, X. and K. Pister, "Minimal 6TiSCH
Configuration", draft-vilajosana-6tisch-minimal-00 (work Configuration", draft-vilajosana-6tisch-minimal-00 (work
in progress), October 2013. in progress), October 2013.
 End of changes. 21 change blocks. 
39 lines changed or deleted 76 lines changed or added

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