| < draft-ietf-6tisch-terminology-04.txt | draft-ietf-6tisch-terminology-05.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: September 24, 2015 cisco | Expires: January 7, 2016 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 | |||
| March 23, 2015 | July 6, 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-04 | draft-ietf-6tisch-terminology-05 | |||
| 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 September 24, 2015. | This Internet-Draft will expire on January 7, 2016. | |||
| 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 . . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 | 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 | |||
| 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 | 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 | |||
| 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 | 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 | |||
| 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 | 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 | |||
| 6.1. Normative References . . . . . . . . . . . . . . . . . . 10 | 6.1. Normative References . . . . . . . . . . . . . . . . . . 10 | |||
| 6.2. Informative References . . . . . . . . . . . . . . . . . 11 | 6.2. Informative References . . . . . . . . . . . . . . . . . 11 | |||
| 6.3. External Informative References . . . . . . . . . . . . . 12 | 6.3. External Informative References . . . . . . . . . . . . . 12 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 | |||
| 1. Introduction | 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. | ||||
| The IEEE802.15.4 Medium Access Control (MAC) has evolved with | The IEEE802.15.4 Medium Access Control (MAC) has evolved with | |||
| IEEE802.15.4e which provides in particular the Time Slotted Channel | IEEE802.15.4e which provides in particular the Time Slotted Channel | |||
| Hopping (TSCH) mode for industrial-type applications. It provides | Hopping (TSCH) mode for industrial-type applications. It provides | |||
| deterministic capabilities to the point that a packet that pertains | deterministic capabilities to the point that a packet that pertains | |||
| to a certain flow crosses the network from node to node following a | to a certain flow crosses the network from node to node following a | |||
| very precise schedule, like a train leaves intermediate stations at | very precise schedule, like a train leaves intermediate stations at | |||
| precise times along its path. | 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 | |||
| skipping to change at page 3, line 18 ¶ | skipping to change at page 3, line 12 ¶ | |||
| 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 | IEEE802.15.4e. It defines (i)the 6top sublayer; (ii) a | |||
| of protocols (in particular, for setting up a TSCH | set of protocols for setting up a TSCH schedule with a | |||
| schedule with a centralized or distributed approach, | centralized and/or distributed approach, for managing the | |||
| managing the resource allocation), as well as the | allocation of resources; and (iii) the architecture to | |||
| architecture to bind them together, for use in IPv6 TSCH | bind them together, for use in IPv6 TSCH based networks. | |||
| 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 Active Queue | where Quality of Service (QoS) and Active Queue | |||
| Management (e.g., Random Early Detection, RED, [RFC2309]) | Management (e.g., Random Early Detection, RED, [RFC2309]) | |||
| operations are expected to prioritize flows with | operations are expected to prioritize flows with | |||
| differentiated services. | differentiated services. | |||
| 6top: 6top is the adaptation sublayer between TSCH and upper | 6top: 6top is the adaptation sublayer between TSCH and upper | |||
| layers like IPv6 over Low-Power Wireless Personal Area | layers like IPv6 over Low-Power Wireless Personal Area | |||
| Networks (6LoWPANs) and IPv6 Routing Protocol for Low- | Networks (6LoWPANs) and IPv6 Routing Protocol for Low- | |||
| Power and Lossy Networks (RPL). It is defined in | 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). | |||
| [I-D.wang-6tisch-6top-sublayer]. | See [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 PAN coordinator has started the | has elapsed since the PAN coordinator has started the | |||
| TSCH network. It is incremented by one at each timeslot. | TSCH network. It is incremented by one at each timeslot. | |||
| It is wide enough to not roll over in practice. See | It is wide enough to not roll over in practice. See | |||
| [IEEE802154e]. | [IEEE802154e]. | |||
| Blacklist of Frequencies: Simply defined Blacklist in [IEEE802154e], | Blacklist of Frequencies: Simply defined Blacklist in [IEEE802154e], | |||
| it is the set of frequencies which should not be used for | it is the set of frequencies among the 16 available ones, | |||
| communication. | which should not be used for 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. A bundle | |||
| represents a half-duplex link between nodes, one | ||||
| transmitter and one or more receivers, with a bandwidth | ||||
| that amount to the sum of the cells in the bundle. A | ||||
| bundle is globally identified by (source MAC, destination | ||||
| MAC, TrackID). At Layer 3 a pair of bundles forms a | ||||
| link. By usining a well-known constant, NULLT, as | ||||
| TrackId for a L3 link, the IP link between adjacent nodes | ||||
| A and B comprises 2 bundles: (macA, macB, NULLT) and | ||||
| (macB, macA, NULLT). At L2 a pair of bundles forms a | ||||
| switching state. Considered a segment A-B-C along a | ||||
| track, there are two bundles in node B, one incoming = | ||||
| (macA, macB, trackId) and one outgoing = (macB, macC, | ||||
| trackId). | ||||
| 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 Cell Reservation: A reservation of a cell done by a | |||
| centralized entity (e.g., a PCE) in the network. | centralized entity (e.g., a PCE) in the network. | |||
| Centralized Track Reservation: A reservation of a track done by a | Centralized Track Reservation: A reservation of a track done by a | |||
| centralized entity (e.g., a PCE) in the network. | 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 [RFC7554]. | |||
| [I-D.ietf-6tisch-tsch]. | ||||
| Channel Distribution/Usage (CDU) matrix: : Matrix of cells (i,j) | Channel Distribution/Usage (CDU) matrix: : Matrix of cells (i,j) | |||
| representing the spectrum (channel) distribution among | representing the spectrum (channel) distribution among | |||
| the different nodes in the 6TiSCH network. The CDU | the different nodes in the 6TiSCH network. The CDU | |||
| matrix has width in timeslots, equal to the period of the | matrix has width in timeslots, equal to the period of the | |||
| network scheduling operation, and height equal to the | network scheduling operation, and height equal to the | |||
| number of available channels. Every cell (i,j) in the | number of available channels. Every cell (i,j) in the | |||
| CDU, identified by (slotOffset, channelOffset), belongs | CDU, identified by (slotOffset, channelOffset), belongs | |||
| to a specific chunk. It has to be noticed that such a | to a specific chunk. It has to be noticed that such a | |||
| matrix, even though it includes all the cells grouped in | matrix which includes all the cells grouped in chunks, | |||
| chunks, belonging to different slotframes, is different | belonging to different slotframes, is different from the | |||
| from the TSCH schedule. | TSCH schedule. | |||
| Chunk: A well-known list of cells, 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. The partition of the CDU in | portion of a CDU matrix. The partition of the CDU in | |||
| chunks is globally known by all the nodes in the network | chunks is globally known by all the nodes in the network | |||
| to support the appropriation process, which is a | to support the appropriation process, which is a | |||
| negotiation between nodes within an interference domain. | negotiation between nodes within an interference domain. | |||
| A node that manages to appropriate a chunk gets to decide | A node that manages to appropriate a chunk gets to decide | |||
| which transmissions will occur over the cells in the | which transmissions will occur over the cells in the | |||
| chunk within its interference domain (i.e., a parent node | chunk within its interference domain (i.e., a parent node | |||
| skipping to change at page 6, line 16 ¶ | skipping to change at page 6, line 20 ¶ | |||
| the resources are needed. | 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). | |||
| 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 useful information | presence of the network. It contains useful information | |||
| (see [IEEE802154e] for details) that allow a new node to | (see [IEEE802154e] for details) that allow a new node to | |||
| synhronize and join the network. | synhronize and join the network. | |||
| skipping to change at page 6, line 43 ¶ | skipping to change at page 6, line 47 ¶ | |||
| 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 [RFC7554]. | |||
| [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 [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 | |||
| skipping to change at page 7, line 22 ¶ | skipping to change at page 7, line 25 ¶ | |||
| 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. | |||
| Interference Domain: The Interference Domain of a given | Interference Domain: The Interference Domain of a given | |||
| (transmitter) node A includes all the nodes in its | (transmitter) node A includes all the nodes in its | |||
| neighbourhood that can generate interference at its | neighbourhood that can generate interference at its | |||
| receiver B, when transmitting on the same channel (i.e., | receiver B, when transmitting on the same channel (i.e., | |||
| using the same frequency). | using the same frequency). | |||
| JCE: The Join Coordination Entity (JCE) is a central entity | JCE: The Join Coordination Entity (JCE) is a central entity | |||
| like the Path Computation Engine (PCE), that may assist | like the Path Computation Element (PCE), that may assist | |||
| in several aspects of the join protocol, such as | in several aspects of the join protocol, such as | |||
| authentication, authorization, and configuration. | authentication, authorization, and configuration. | |||
| JA: The Join Assistant (JA) is a one-hop neighbor of a | JA: The Join Assistant (JA) is a one-hop neighbor of a | |||
| joining node that may facilitate it to become meaningful | joining node that may facilitate it to become meaningful | |||
| part of the network (e.g., by serving as a local | part of the network (e.g., by serving as a local | |||
| connectivity point to the remainder of the 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 a joining node and the JCE. | between a joining node and the JCE. | |||
| skipping to change at page 7, line 52 ¶ | skipping to change at page 8, line 7 ¶ | |||
| 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. | |||
| A link is distinct from a track. In fact, link local | A link is distinct from a track. In fact, link local | |||
| addresses are not expected to be used over a track for | addresses are not expected to be used over a track for | |||
| end to end communication. Finally, from the Layer 3 | end to end communication. Finally, from the Layer 3 | |||
| perspective (where the inner complexities of TSCH | perspective (where the inner complexities of TSCH | |||
| operations are hidden to enable classical IP routing and | operations are hidden to enable classical IP routing and | |||
| 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 | ||||
| only lazily associated to a physical cell, based on | ||||
| 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: IPv6 ND-efficiency-aware 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 | |||
| skipping to change at page 8, line 50 ¶ | skipping to change at page 8, line 50 ¶ | |||
| changing the slotOffset and/or channelOffset of a soft | changing the slotOffset and/or channelOffset of a soft | |||
| cell. | cell. | |||
| (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 | |||
| hard cell or a soft cell. | either a hard 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. | |||
| This cell can be used by more than one transmitter node. | This cell can be used by more than one transmitter node. | |||
| A backoff algorithm is used to resolve contention. See | A backoff algorithm is used to resolve contention. See | |||
| [I-D.ietf-6tisch-tsch]. | [RFC7554]. | |||
| 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.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 GMPLS-like | forwarding model supported by 6TiSCH. It is a GMPLS-like | |||
| forwarding model. The input cell characterizes the flow | forwarding model. The incoming bundle (and thus, the | |||
| and indicates the output cell. | input cell) characterizes the flow and indicates the | |||
| outgoing bundle (and 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 that a node uses as its time | |||
| and to which it needs to keep its clock synchronized. A | reference, and to which it needs to keep its clock | |||
| node can have one or more time source neighbors. | synchronized. A 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 track reservation. The | It is typically the result of a track reservation. The | |||
| node that initializes the process for establishing a | node that initializes the process for establishing a | |||
| track is the owner of the track. The latter assigns a | track is the owner of the track. The latter assigns a | |||
| unique 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. | |||
| skipping to change at page 11, line 29 ¶ | skipping to change at page 11, line 29 ¶ | |||
| 6552, March 2012. | 6552, March 2012. | |||
| [RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann, | [RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann, | |||
| "Neighbor Discovery Optimization for IPv6 over Low-Power | "Neighbor Discovery Optimization for IPv6 over Low-Power | |||
| Wireless Personal Area Networks (6LoWPANs)", RFC 6775, | Wireless Personal Area Networks (6LoWPANs)", RFC 6775, | |||
| November 2012. | November 2012. | |||
| [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. | |||
| [RFC7554] Watteyne, T., Palattella, M., and L. Grieco, "Using IEEE | ||||
| 802.15.4e Time-Slotted Channel Hopping (TSCH) in the | ||||
| Internet of Things (IoT): Problem Statement", RFC 7554, | ||||
| May 2015. | ||||
| 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-07 (work in progress), February 2015. | 6man-efficient-nd-07 (work in progress), February 2015. | |||
| [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-06 (work in | ||||
| 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. and P. Stok, "Requirements for an update to | Thubert, P. and P. Stok, "Requirements for an update to | |||
| 6LoWPAN ND", draft-thubert-6lo-rfc6775-update-reqs-06 | 6LoWPAN ND", draft-thubert-6lo-rfc6775-update-reqs-06 | |||
| (work in progress), January 2015. | (work in progress), January 2015. | |||
| skipping to change at page 12, line 17 ¶ | skipping to change at page 12, line 17 ¶ | |||
| 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. | |||
| 6.3. External Informative References | 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. | ||||
| [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) Amendment 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 | |||
| End of changes. 24 change blocks. | ||||
| 55 lines changed or deleted | 51 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/ | ||||