idnits 2.17.1 draft-ietf-6tisch-terminology-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 2, 2018) is 2246 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'IEEE802154-2015' is mentioned on line 360, but not defined == Outdated reference: A later version (-13) exists of draft-ietf-detnet-architecture-04 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6TiSCH MR. Palattella, Ed. 3 Internet-Draft LIST 4 Intended status: Informational P. Thubert 5 Expires: September 3, 2018 cisco 6 T. Watteyne 7 Analog Devices 8 Q. Wang 9 Univ. of Sci. and Tech. Beijing 10 March 2, 2018 12 Terms Used in IPv6 over the TSCH mode of IEEE 802.15.4e 13 draft-ietf-6tisch-terminology-10 15 Abstract 17 This document provides a glossary of terminology used in IPv6 over 18 the TSCH mode of IEEE 802.15.4e (6TiSCH). This document extends 19 existing terminology documents for Low-power and Lossy Networks. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on September 3, 2018. 38 Copyright Notice 40 Copyright (c) 2018 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 57 3. Security Considerations . . . . . . . . . . . . . . . . . . . 7 58 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 59 4.1. Normative References . . . . . . . . . . . . . . . . . . 7 60 4.2. Informative References . . . . . . . . . . . . . . . . . 8 61 4.3. External Informative References . . . . . . . . . . . . . 8 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 64 1. Introduction 66 The IEEE802.15.4 Medium Access Control (MAC) has evolved with the 67 Time Slotted Channel Hopping (TSCH) mode for industrial-type 68 applications. 70 This document provides additional terminology elements to cover terms 71 that are new to the context of TSCH wireless networks and other 72 deterministic networks. 74 2. Terminology 76 The draft extends [RFC7102] and use terms from [RFC6550] and 77 [RFC6552], which are all included here by reference. 79 The draft does not reuse terms from IEEE802.15.4 such as "path" or 80 "link" which bear a meaning that is quite different from classical 81 IETF parlance. 83 This document adds the following terms: 85 6TiSCH (IPv6 over the TSCH mode of IEEE 802.15.4e): It defines the 86 6top sublayer, a set of protocols for setting up a TSCH 87 schedule in distributed approach, and a security 88 solution. 90 6top (6TiSCH Operation Sublayer): The next highest layer of the 91 IEEE802.15.4 TSCH medium access control layer. It 92 implements and terminates 6P, and contains at least one 93 SF. 95 6P (6top Protocol): Allows neighbor nodes to communicate to add/ 96 delete cells to one another in their TSCH schedule. 98 6P Transaction: Part of 6P, the action of two neighbors exchanging a 99 6P request message and the corresponding 6P response 100 message. 102 ASN (Absolute Slot Number): The total number of timeslots that have 103 elapsed since the PAN coordinator has started the TSCH 104 network. Incremented by one at each timeslot. It is 105 wide enough to not roll over in practice. 107 BBR (Backbone Router): An LBR and also a IPv6 ND-efficiency-aware 108 Router (NEAR) 109 [I-D.chakrabarti-nordmark-6man-efficient-nd]. Performs 110 ND proxy operations between registered devices and 111 classical ND devices that are located on the backbone. 113 blacklist of frequencies: A set of frequencies which should not be 114 used for communication. 116 broadcast cell: A scheduled cell used for broadcast transmission. 118 bundle: A group of equivalent scheduled cells, i.e. cells 119 identified by different [slotOffset, channelOffset], 120 which are scheduled for a same purpose, with the same 121 neighbor, with the same flags, and the same slotframe. 122 The size of the bundle refers to the number of cells it 123 contains. For a given slotframe length, the size of the 124 bundle translates directly into bandwidth. A bundle is a 125 local abstraction that represents a half-duplex link for 126 either sending or receiving, with bandwidth that amounts 127 to the sum of the cells in the bundle. 129 CCA (Clear Channel Assessment): Mechanism defined in 130 [IEEE802154-2015], section 6.2.5.2. In a TSCH network, 131 CCA can be used to detect other radio networks in 132 vicinity. Nodes listen the channel before sending, to 133 detect other ongoing transmissions. Because the network 134 is synchronized, CCA cannot be used to detect colliding 135 transmission within the same network. 137 cell: A single element in the TSCH schedule, identified by a 138 slotOffset, a channelOffset, a slotframeHandle. A cell 139 can be scheduled or unscheduled. 141 centralized cell reservation: A reservation of a cell done by a 142 centralized entity (e.g., a PCE) in the network. 144 centralized track reservation: A reservation of a track done by a 145 centralized entity (e.g., a PCE) in the network. 147 Channel Distribution/Usage (CDU) matrix: : Matrix of cells (i,j) 148 representing the spectrum (channel) distribution among 149 the different nodes in the 6TiSCH network. The CDU 150 matrix has width in timeslots, equal to the period of the 151 network scheduling operation, and height equal to the 152 number of available channels. Every cell (i,j) in the 153 CDU, identified by (slotOffset, channelOffset), belongs 154 to a specific chunk. It has to be noticed that such a 155 matrix which includes all the cells grouped in chunks, 156 belonging to different slotframes, is different from the 157 TSCH schedule. 159 channelOffset: Identifies a row in the TSCH schedule. The number of 160 available channelOffset values is equal to the number of 161 available frequencies. The channelOffset translates into 162 a frequency when the communication takes place, resulting 163 in channel hopping. 165 chunk: A well-known list of cells, distributed in time and 166 frequency, within a CDU matrix. A chunk represents a 167 portion of a CDU matrix. The partition of the CDU matrix 168 in chunks is globally known by all the nodes in the 169 network to support the appropriation process, which is a 170 negotiation between nodes within an interference domain. 171 A node that manages to appropriate a chunk gets to decide 172 which transmissions will occur over the cells in the 173 chunk within its interference domain (i.e., a parent node 174 will decide when the cells within the appropriated chunk 175 are used and by which node, among its children. 177 dedicated cell: A cell that is reserved for a given node to transmit 178 to a specific neighbor. 180 deterministic network: The generic concept of deterministic network 181 is defined in [I-D.ietf-detnet-architecture]. When 182 applied to 6TiSCH, it refers to the reservation of tracks 183 which guarantee an end-to-end latency and optimize the 184 PDR for well-characterized flows. 186 distributed cell reservation: A reservation of a cell done by one or 187 more in-network entities. 189 distributed track reservation: A reservation of a track done by one 190 or more in-network entities. 192 EB (Enhanced Beacon): A special frame defined used by a node, 193 including the JP, to announce the presence of the 194 network. It contains enough information for a pledge to 195 synchronize to the network. 197 hard cell: A scheduled cell which the 6top sublayer cannot relocate. 199 hopping sequence: Ordered sequence of frequencies, identified by a 200 Hopping_Sequence_ID, used for channel hopping when 201 translating the channel offset value into a frequency. 203 IE (Information Element): Type-Length-Value containers placed at the 204 end of the MAC header, used to pass data between layers 205 or devices. Some IE identifiers are managed by the IEEE 206 [IEEE802154-2015]. Some IE identifiers are managed by 207 the IETF [I-D.kivinen-802-15-ie]. 209 join process: The overall process that includes the discovery of the 210 network by pledge(s) and the execution of the join 211 protocol. 213 join protocol: The protocol that allows the pledge to join the 214 network. The join protocol encompasses authentication, 215 authorization and parameter distribution. The join 216 protocol is executed between the pledge and the JRC. 218 joined node: The new device, after having completed the join 219 process, often just called a node. 221 JP (Join Proxy): Node already part of the 6TiSCH network that serves 222 as a relay to provide connectivity between the pledge and 223 the JRC. The JP announces the presence of the network by 224 regularly sending EB frames. 226 JRC (Join Registrar/Coordinator): Central entity responsible for the 227 authentication, authorization and configuration of the 228 pledge. 230 LBR: Low-power Lossy Network (LLN) Border Router. It is an 231 LLN device, usually powered, that acts as a Border Router 232 to the outside within the 6TiSCH architecture. 234 link: A communication facility or medium over which nodes can 235 communicate at the link layer, the layer immediately 236 below IP. The IETF parlance for the term "Link" is 237 adopted, as opposed to the IEEE802.15.4 terminology. 239 pledge: A new device that attempts to join a 6TiSCH network. 241 (to) relocate a cell: The action operated by the 6top sublayer of 242 changing the slotOffset and/or channelOffset of a soft 243 cell. 245 (to) schedule a cell: The action of turning an unscheduled cell into 246 a scheduled cell. 248 scheduled cell: A cell which is assigned a neighbor MAC address 249 (broadcast address is also possible), and one or more of 250 the following flags: TX, RX, shared, timeskeeping. A 251 scheduled cell can be used by the IEEE802.15.4 TSCH 252 implementation to communicate. A scheduled cell can 253 either be a hard or a soft cell. 255 SF (6top Scheduling Function): The cell management entity that adds 256 or deletes cells dynamically based on application 257 networking requirements. The cell negotiation with a 258 neighbor is done using 6P. 260 SFID (6top Scheduling Function Identifier): A 4-bit field 261 identifying an SF. 263 shared cell: A cell marked with both the "TX" and "shared" flags. 264 This cell can be used by more than one transmitter node. 265 A back-off algorithm is used to resolve contention. 267 slotframe: A collection of timeslots repeating in time, analogous to 268 a superframe in that it defines periods of communication 269 opportunities. It is characterized by a slotframe_ID, 270 and a slotframe_size. Multiple slotframes can coexist in 271 a node's schedule, i.e., a node can have multiple 272 activities scheduled in different slotframes, based on 273 the priority of its packets/traffic flows. The timeslots 274 in the Slotframe are indexed by the SlotOffset; the first 275 timeslot is at SlotOffset 0. 277 slotOffset: A column in the TSCH schedule, i.e. the number of 278 timeslots since the beginning of the current iteration of 279 the slotframe. 281 soft cell: A scheduled cell which the 6top sublayer can relocate. 283 time source neighbor: A neighbor that a node uses as its time 284 reference, and to which it needs to keep its clock 285 synchronized. 287 timeslot: A basic communication unit in TSCH which allows a 288 transmitter node to send a frame to a receiver neighbor, 289 and that receiver neighbor to optionally send back an 290 acknowledgment. 292 track: A determined sequence of cells along a multi-hop path. 293 It is typically the result of a track reservation. The 294 node that initializes the process of establishing a track 295 is the owner of the track. The latter assigns a unique 296 identifier to the track, called TrackID. 298 TrackID: Unique identifier of a track. 300 TSCH (6top Scheduling Function Identifier): A medium access mode of 301 the [IEEE802154-2015] standard which uses time 302 synchronization to achieve ultra low-power operation, and 303 channel hopping to enable high reliability. 305 TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset 306 and a channelOffset. The TSCH schedule contains all the 307 scheduled cells from all slotframes and is sufficient to 308 qualify the communication in the TSCH network. The 309 number of channelOffset values (the "height" of the 310 matrix) is equal to the number of available frequencies. 312 Unscheduled Cell: A cell which is not used by the IEEE802.15.4 TSCH 313 implementation. 315 3. Security Considerations 317 Since this document specifies terminology and does not specify new 318 procedures or protocols, it raises no new security issues. 320 4. References 322 4.1. Normative References 324 [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., 325 Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, 326 JP., and R. Alexander, "RPL: IPv6 Routing Protocol for 327 Low-Power and Lossy Networks", RFC 6550, 328 DOI 10.17487/RFC6550, March 2012, 329 . 331 [RFC6552] Thubert, P., Ed., "Objective Function Zero for the Routing 332 Protocol for Low-Power and Lossy Networks (RPL)", 333 RFC 6552, DOI 10.17487/RFC6552, March 2012, 334 . 336 [RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and 337 Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January 338 2014, . 340 4.2. Informative References 342 [I-D.chakrabarti-nordmark-6man-efficient-nd] 343 Chakrabarti, S., Nordmark, E., Thubert, P., and M. 344 Wasserman, "IPv6 Neighbor Discovery Optimizations for 345 Wired and Wireless Networks", draft-chakrabarti-nordmark- 346 6man-efficient-nd-07 (work in progress), February 2015. 348 [I-D.ietf-detnet-architecture] 349 Finn, N., Thubert, P., Varga, B., and J. Farkas, 350 "Deterministic Networking Architecture", draft-ietf- 351 detnet-architecture-04 (work in progress), October 2017. 353 [I-D.kivinen-802-15-ie] 354 Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information 355 Element for IETF", draft-kivinen-802-15-ie-06 (work in 356 progress), March 2017. 358 4.3. External Informative References 360 [IEEE802154-2015] 361 IEEE standard for Information Technology, "IEEE Std 362 802.15.4-2015 Standard for Low-Rate Wireless Personal Area 363 Networks (WPANs)", December 2015. 365 Authors' Addresses 367 Maria Rita Palattella (editor) 368 Luxembourg Institute of Science and Technology 369 Department 'Environmental Research and Innovation' (ERIN) 370 41, rue du Brill 371 Belvaux L-4422 372 Luxembourg 374 Phone: (+352) 275 888-5055 375 Email: mariarita.palattella@list.lu 376 Pascal Thubert 377 Cisco Systems, Inc 378 Village d'Entreprises Green Side 379 400, Avenue de Roumanille 380 Batiment T3 381 Biot - Sophia Antipolis 06410 382 France 384 Phone: +33 497 23 26 34 385 Email: pthubert@cisco.com 387 Thomas Watteyne 388 Analog Devices 389 32990 Alvarado-Niles Road, Suite 910 390 Union City, CA 94587 391 USA 393 Email: thomas.watteyne@analog.com 395 Qin Wang 396 Univ. of Sci. and Tech. Beijing 397 30 Xueyuan Road 398 Beijing 100083 399 China 401 Phone: +86 (10) 6233 4781 402 Email: wangqin@ies.ustb.edu.cn