idnits 2.17.1 draft-ietf-6tisch-terminology-08.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 (December 16, 2016) is 2659 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'IEEE802154-2015' is mentioned on line 456, but not defined == Unused Reference: 'RFC2309' is defined on line 364, but no explicit reference was found in the text == Unused Reference: 'RFC3444' is defined on line 372, but no explicit reference was found in the text == Unused Reference: 'RFC6775' is defined on line 389, but no explicit reference was found in the text == Unused Reference: 'I-D.thubert-6lo-rfc6775-update-reqs' is defined on line 444, but no explicit reference was found in the text == Unused Reference: 'I-D.thubert-roll-forwarding-frags' is defined on line 449, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2309 (Obsoleted by RFC 7567) == Outdated reference: A later version (-12) exists of draft-ietf-6tisch-6top-protocol-03 == Outdated reference: A later version (-01) exists of draft-ietf-6tisch-dtsecurity-secure-join-00 == Outdated reference: A later version (-21) exists of draft-ietf-6tisch-minimal-17 == Outdated reference: A later version (-15) exists of draft-ietf-6tisch-minimal-security-00 == Outdated reference: A later version (-13) exists of draft-ietf-detnet-architecture-00 == Outdated reference: A later version (-06) exists of draft-kivinen-802-15-ie-04 Summary: 2 errors (**), 0 flaws (~~), 13 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: June 19, 2017 cisco 6 T. Watteyne 7 Linear Technology / Dust Networks 8 Q. Wang 9 Univ. of Sci. and Tech. Beijing 10 December 16, 2016 12 Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e 13 draft-ietf-6tisch-terminology-08 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 http://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 June 19, 2017. 38 Copyright Notice 40 Copyright (c) 2016 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 (http://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 . . . . . . . . . . . . . . . . . . . 8 58 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 59 4.1. Normative References . . . . . . . . . . . . . . . . . . 8 60 4.2. Informative References . . . . . . . . . . . . . . . . . 9 61 4.3. External Informative References . . . . . . . . . . . . . 10 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 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. It provides deterministic capabilities to the point 69 that a packet that pertains to a certain flow crosses the network 70 from node to node following a very precise schedule, like a train 71 leaves intermediate stations at precise times along its path. 73 This document provides additional terminology elements to cover terms 74 that are new to the context of TSCH wireless networks and other 75 deterministic networks. 77 2. Terminology 79 The draft extends [RFC7102] and use terms from [RFC6550] and 80 [RFC6552], which are all included here by reference. 82 The draft does not reuse terms from IEEE802.15.4e such as "path" or 83 "link" which bear a meaning that is quite different from classical 84 IETF parlance. 86 This document adds the following terms: 88 6TiSCH: IPv6 over the Timeslotted Channel Hopping (TSCH) mode of 89 IEEE802.15.4e. It defines (i) the 6top sublayer; (ii) a 90 set of protocols for setting up a TSCH schedule in 91 distributed approach, for managing the allocation of 92 resources; and (iii) the architecture to bind them 93 together, for use in IPv6 TSCH based networks. 95 6top: The "6TiSCH Operation Sublayer" (6top) is the next 96 highest layer of the IEEE802.15.4e TSCH medium access 97 control layer. It implements and terminates the "6top 98 Protocol" (6P), and contains a "6top Scheduling Function" 99 (SF). 101 SF: The "6top Scheduling Function" (SF) "is the cell 102 management entity that add or delete cells dynamically 103 based on its allocation policy in order to fulfill cell 104 requirements. The cell negotiation with a neighbor is 105 done using 6P. General guidelines for designing a SF are 106 provided in [I-D.ietf-6tisch-6top-protocol]. 108 SFID: The "6top Scheduling Function Identifier" (SFID) is a 109 4-bit field identifying a SF. Defined in 110 [I-D.ietf-6tisch-6top-protocol]. 112 6P: The "6top Protocol" (6P) allows neighbor nodes to 113 communicate to add/delete cells to one another in their 114 TSCH schedule. Defined in 115 [I-D.ietf-6tisch-6top-protocol]. 117 6P Transaction: Part of the "6top Protocol" (6P), the action of two 118 neighbors exchanging a 6P request message and the 119 corresponding 6P response message. Defined in 120 [I-D.ietf-6tisch-6top-protocol]. 122 ASN: Absolute Slot Number, the total number of timeslots that 123 have elapsed since the PAN coordinator has started the 124 TSCH network. Incremented by one at each timeslot. It 125 is wide enough to not roll over in practice. See 126 [IEEE802154-2015] and [RFC7554]. 128 Blacklist of Frequencies: A set of frequencies which should not be 129 used for communication. See [IEEE802154-2015] and 130 [RFC7554]. 132 BBR: Backbone Router. In the 6TiSCH architecture, an LBR and 133 also a IPv6 ND-efficiency-aware Router (NEAR) 134 [I-D.chakrabarti-nordmark-6man-efficient-nd]. Performs 135 ND proxy operations between registered devices and 136 classical ND devices that are located over the backbone. 138 Broadcast Cell: A scheduled cell used for broadcast transmission. 140 Bundle: A group of equivalent scheduled cells, i.e. cells 141 identified by different [slotOffset, channelOffset], 142 which are scheduled for a same purpose, with the same 143 neighbor, with the same flags, and the same slotframe. 144 The size of the bundle refers to the number of cells it 145 contains. For a given slotframe length, the size of the 146 bundle translates directly into bandwidth. A bundle is a 147 local abstraction thar represents a half-duplex link for 148 either sending or receiving, with bandwidth that amounts 149 to the sum of the cells in the bundle. A bundle is 150 globally identified by (source MAC, destination MAC, 151 TrackID). At Layer 3, a pair of bundles forms a link. 152 By using a well-known constant, NULLT, as TrackId for a 153 L3 link, the IP link between adjacent nodes A and B 154 comprises 2 bundles: (macA, macB, NULLT) and (macB, macA, 155 NULLT). At Layer 2, a pair of bundles forms a switching 156 state. Considered a segment A-B-C along a track, there 157 are two bundles in node B, one incoming = (macA, macB, 158 trackId) and one outgoing = (macB, macC, trackId). 160 CCA: Clear Channel Assessment. Mechanism defined in 161 [IEEE802154-2015], section 6.2.5.2. In a TSCH network, 162 CCA can be used to detect other radio networks in 163 vicinity. Nodes listen the channel before sending, to 164 detect other ongoing transmissions. Because the network 165 is synchronized, CCA cannot be used to detect colliding 166 transmission within the same network. CCA is necessary 167 for the 6TiSCH minimal configuration 168 [I-D.ietf-6tisch-minimal] in shared slots, and in 169 presence of multiple instances of 6TiSCH networks. 171 Cell: A single element in the TSCH schedule, identified by a 172 slotOffset, a channelOffset, a slotframeHandle. A cell 173 can be scheduled or unscheduled. 175 Centralized Cell Reservation: A reservation of a cell done by a 176 centralized entity (e.g., a PCE) in the network. 178 Centralized Track Reservation: A reservation of a track done by a 179 centralized entity (e.g., a PCE) in the network. 181 ChannelOffset: Identifies a row in the TSCH schedule. The number of 182 available channelOffset values is equal to the number of 183 available frequencies. The channelOffset translates into 184 a frequency when the communication takes place, resulting 185 in channel hopping. See [RFC7554]. 187 Channel Distribution/Usage (CDU) matrix: : Matrix of cells (i,j) 188 representing the spectrum (channel) distribution among 189 the different nodes in the 6TiSCH network. The CDU 190 matrix has width in timeslots, equal to the period of the 191 network scheduling operation, and height equal to the 192 number of available channels. Every cell (i,j) in the 193 CDU, identified by (slotOffset, channelOffset), belongs 194 to a specific chunk. It has to be noticed that such a 195 matrix which includes all the cells grouped in chunks, 196 belonging to different slotframes, is different from the 197 TSCH schedule. 199 Chunk: A well-known list of cells, distributed in time and 200 frequency, within a CDU matrix; a chunk represents a 201 portion of a CDU matrix. The partition of the CDU in 202 chunks is globally known by all the nodes in the network 203 to support the appropriation process, which is a 204 negotiation between nodes within an interference domain. 205 A node that manages to appropriate a chunk gets to decide 206 which transmissions will occur over the cells in the 207 chunk within its interference domain (i.e., a parent node 208 will decide when the cells within the appropriated chunk 209 are used and by which node, among its children. 211 Dedicated Cell: A cell that is reserved for a given node to transmit 212 to a specific neighbor. 214 Deterministic Network: The generic concept of deterministic network 215 is defined in [I-D.ietf-detnet-architecture]. When 216 applied to 6TiSCH it refers to the reservation of tracks 217 which guarantee an end to end latency and optimize the 218 PDR for well-characterized flows. 220 Distributed Cell Reservation: A reservation of a cell done by one or 221 more in-network entities (typically a connection 222 endpoint). 224 Distributed Track Reservation: A reservation of a track done by one 225 or more in-network entities (typically a connection 226 endpoint). 228 EB: Enhanced Beacon frame used by a node to announce the 229 presence of the network. It contains enough information 230 for a joining node to synchronize to the network. See 231 [IEEE802154-2015] and [RFC7554]. 233 Hard Cell: A scheduled cell which the 6top sublayer cannot relocate. 235 Hopping Sequence: Ordered sequence of frequencies, identified by a 236 Hopping_Sequence_ID, used for channel hopping, when 237 translating the channel offset value into a frequency 238 (i.e., PHY channel). See [IEEE802154-2015] and 239 [RFC7554]. 241 IE: Information Element, a Type-Length-Value containers 242 placed at the end of the MAC header, used to pass data 243 between layers or devices. Some IE identifiers are 244 managed by the IEEE [IEEE802154-2015]. Some IE 245 identifiers are managed by the IETF 246 [I-D.kivinen-802-15-ie]. 248 JCE: The Join Coordination Entity (JCE) is a central entity 249 that coordinates the joining of new nodes in the network. 250 See [I-D.ietf-6tisch-minimal-security] and 251 [I-D.ietf-6tisch-dtsecurity-secure-join]. 253 JA: The Join Assistant (JA) is a one-hop neighbor of a 254 joining node that may facilitate it to become meaningful 255 part of the network (e.g., by serving as a local 256 connectivity point to the remainder of the network). JA 257 emits EBs, used by JNs to synchronize to the network. 258 See [I-D.ietf-6tisch-minimal-security] and 259 [I-D.ietf-6tisch-dtsecurity-secure-join]. 261 JN: The Joining Node (JN) is a device attempting to join a 262 particular 6TiSCH network. See 263 [I-D.ietf-6tisch-minimal-security]. 265 Join Protocol: The protocol which secures initial communication 266 between a joining node and the JCE. 268 LBR: Low-power Lossy Network (LLN) Border Router. It is an 269 LLN device, usually powered, that acts as a Border Router 270 to the outside within the 6TiSCH architecture. 272 Link: A communication facility or medium over which nodes can 273 communicate at the link layer, i.e., the layer 274 immediately below IP. Thus, the IETF parlance for the 275 term "Link" is adopted, as opposed to the IEEE802.15.4e 276 terminology. 278 Operational Network: A IEEE802.15.4e network whose encryption/ 279 authentication keys are determined by some algorithms/ 280 protocols. There may be network-wide group keys, or per- 281 link keys. 283 (to) Relocate a Cell: The action operated by the 6top sublayer of 284 changing the slotOffset and/or channelOffset of a soft 285 cell. 287 (to) Schedule a Cell: The action of turning an unscheduled cell into 288 a scheduled cell. 290 Scheduled cell: A cell which is assigned a neighbor MAC address 291 (broadcast address is also possible), and one or more of 292 the following flags: TX, RX, shared, timeskeeping. A 293 scheduled cell can be used by the IEEE802.15.4e TSCH 294 implementation to communicate. A scheduled cell can be 295 either a hard or a soft cell. 297 Shared Cell: A cell marked with both the "TX" and "shared" flags. 298 This cell can be used by more than one transmitter node. 299 A back-off algorithm is used to resolve contention. See 300 [IEEE802154-2015] and [RFC7554]. 302 SlotOffset: Identifies a column in the TSCH schedule, i.e., the 303 number of timeslots since the beginning of the current 304 iteration of the slotframe. See [IEEE802154-2015] and 305 [RFC7554]. 307 Slotframe: A collection of timeslots repeating in time, analogous to 308 a superframe in that it defines periods of communication 309 opportunities. It is characterized by a slotframe_ID, 310 and a slotframe_size. Multiple slotframes can coexist in 311 a node's schedule, i.e., a node can have multiple 312 activities scheduled in different slotframes, based on 313 the priority of its packets/traffic flows. The timeslots 314 in the Slotframe are indexed by the SlotOffset; the first 315 timeslot is at SlotOffset 0. See [IEEE802154-2015] and 316 [RFC7554]. 318 Soft Cell: A scheduled cell which the 6top sublayer can relocate. 320 Timeslot: A basic communication unit in TSCH which allows a 321 transmitter node to send a frame to a receiver neighbor, 322 and that receiver neighbor to optionally send back an 323 acknowledgment. See [IEEE802154-2015] and [RFC7554]. 325 Time Source Neighbor: A neighbor that a node uses as its time 326 reference, and to which it needs to keep its clock 327 synchronized. See [IEEE802154-2015] and [RFC7554]. 329 Track: A determined sequence of cells along a multi-hop path. 330 It is typically the result of a track reservation. The 331 node that initializes the process of establishing a track 332 is the owner of the track. The latter assigns a unique 333 identifier to the track, called TrackID. 335 TrackID: Unique identifier of a track, assigned by the owner of 336 the track. 338 TSCH: Time Slotted Channel Hopping, a medium access mode of the 339 [IEEE802154-2015] standard which uses time 340 synchronization to achieve ultra low-power operation and 341 channel hopping to enable high reliability. See 342 [IEEE802154-2015] and [RFC7554]. 344 TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset 345 and a channelOffset. The TSCH schedule contains all the 346 scheduled cells from all slotframes and is sufficient to 347 qualify the communication in the TSCH network. The 348 number of channelOffset values (the "height" of the 349 matrix) is equal to the number of available frequencies. 350 See [IEEE802154-2015] and [RFC7554]. 352 Unscheduled Cell: A cell which is not used by the IEEE802.15.4e TSCH 353 implementation. See [IEEE802154-2015] and [RFC7554]. 355 3. Security Considerations 357 Since this document specifies terminology and does not specify new 358 procedures or protocols, it raises no new security issues. 360 4. References 362 4.1. Normative References 364 [RFC2309] Braden, B., Clark, D., Crowcroft, J., Davie, B., Deering, 365 S., Estrin, D., Floyd, S., Jacobson, V., Minshall, G., 366 Partridge, C., Peterson, L., Ramakrishnan, K., Shenker, 367 S., Wroclawski, J., and L. Zhang, "Recommendations on 368 Queue Management and Congestion Avoidance in the 369 Internet", RFC 2309, DOI 10.17487/RFC2309, April 1998, 370 . 372 [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between 373 Information Models and Data Models", RFC 3444, 374 DOI 10.17487/RFC3444, January 2003, 375 . 377 [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., 378 Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, 379 JP., and R. Alexander, "RPL: IPv6 Routing Protocol for 380 Low-Power and Lossy Networks", RFC 6550, 381 DOI 10.17487/RFC6550, March 2012, 382 . 384 [RFC6552] Thubert, P., Ed., "Objective Function Zero for the Routing 385 Protocol for Low-Power and Lossy Networks (RPL)", 386 RFC 6552, DOI 10.17487/RFC6552, March 2012, 387 . 389 [RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C. 390 Bormann, "Neighbor Discovery Optimization for IPv6 over 391 Low-Power Wireless Personal Area Networks (6LoWPANs)", 392 RFC 6775, DOI 10.17487/RFC6775, November 2012, 393 . 395 [RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and 396 Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January 397 2014, . 399 [RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using 400 IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the 401 Internet of Things (IoT): Problem Statement", RFC 7554, 402 DOI 10.17487/RFC7554, May 2015, 403 . 405 4.2. Informative References 407 [I-D.chakrabarti-nordmark-6man-efficient-nd] 408 Chakrabarti, S., Nordmark, E., Thubert, P., and M. 409 Wasserman, "IPv6 Neighbor Discovery Optimizations for 410 Wired and Wireless Networks", draft-chakrabarti-nordmark- 411 6man-efficient-nd-07 (work in progress), February 2015. 413 [I-D.ietf-6tisch-6top-protocol] 414 Wang, Q. and X. Vilajosana, "6top Protocol (6P)", draft- 415 ietf-6tisch-6top-protocol-03 (work in progress), October 416 2016. 418 [I-D.ietf-6tisch-dtsecurity-secure-join] 419 Richardson, M., "6tisch Secure Join protocol", draft-ietf- 420 6tisch-dtsecurity-secure-join-00 (work in progress), 421 December 2016. 423 [I-D.ietf-6tisch-minimal] 424 Vilajosana, X. and K. Pister, "Minimal 6TiSCH 425 Configuration", draft-ietf-6tisch-minimal-17 (work in 426 progress), November 2016. 428 [I-D.ietf-6tisch-minimal-security] 429 malisa.vucinic@st.com, m., Simon, J., and K. Pister, 430 "Minimal Security Framework for 6TiSCH", draft-ietf- 431 6tisch-minimal-security-00 (work in progress), December 432 2016. 434 [I-D.ietf-detnet-architecture] 435 Finn, N. and P. Thubert, "Deterministic Networking 436 Architecture", draft-ietf-detnet-architecture-00 (work in 437 progress), September 2016. 439 [I-D.kivinen-802-15-ie] 440 Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information 441 Element for IETF", draft-kivinen-802-15-ie-04 (work in 442 progress), October 2016. 444 [I-D.thubert-6lo-rfc6775-update-reqs] 445 Thubert, P. and P. Stok, "Requirements for an update to 446 6LoWPAN ND", draft-thubert-6lo-rfc6775-update-reqs-07 447 (work in progress), April 2016. 449 [I-D.thubert-roll-forwarding-frags] 450 Thubert, P. and J. Hui, "LLN Fragment Forwarding and 451 Recovery", draft-thubert-roll-forwarding-frags-02 (work in 452 progress), September 2013. 454 4.3. External Informative References 456 [IEEE802154-2015] 457 IEEE standard for Information Technology, "IEEE Std 458 802.15.4-2015 Standard for Low-Rate Wireless Personal Area 459 Networks (WPANs)", December 2015. 461 Authors' Addresses 463 Maria Rita Palattella (editor) 464 Luxembourg Institute of Science and Technology 465 Department 'Environmental Research and Innovation' (ERIN) 466 41, rue du Brill 467 Belvaux L-4422 468 Luxembourg 470 Phone: (+352) 275 888-5055 471 Email: mariarita.palattella@list.lu 472 Pascal Thubert 473 Cisco Systems, Inc 474 Village d'Entreprises Green Side 475 400, Avenue de Roumanille 476 Batiment T3 477 Biot - Sophia Antipolis 06410 478 France 480 Phone: +33 497 23 26 34 481 Email: pthubert@cisco.com 483 Thomas Watteyne 484 Linear Technology / Dust Networks 485 30695 Huntwood Avenue 486 Hayward, CA 94544 487 USA 489 Phone: +1 (510) 400-2978 490 Email: twatteyne@linear.com 492 Qin Wang 493 Univ. of Sci. and Tech. Beijing 494 30 Xueyuan Road 495 Beijing 100083 496 China 498 Phone: +86 (10) 6233 4781 499 Email: wangqin@ies.ustb.edu.cn