idnits 2.17.00 (12 Aug 2021) /tmp/idnits767/draft-ietf-6tisch-terminology-02.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 4, 2014) is 2878 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'IEEE802154e' is mentioned on line 499, but not defined == Unused Reference: 'I-D.ietf-6tisch-6top-interface' is defined on line 455, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-6tisch-architecture' is defined on line 460, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-6tisch-coap' is defined on line 466, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-6tisch-minimal' is defined on line 471, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2309 (Obsoleted by RFC 7567) == Outdated reference: A later version (-07) exists of draft-chakrabarti-nordmark-6man-efficient-nd-05 == Outdated reference: A later version (-04) exists of draft-ietf-6tisch-6top-interface-00 == Outdated reference: draft-ietf-6tisch-architecture has been published as RFC 9030 == Outdated reference: A later version (-03) exists of draft-ietf-6tisch-coap-00 == Outdated reference: draft-ietf-6tisch-minimal has been published as RFC 8180 == Outdated reference: draft-ietf-6tisch-tsch has been published as RFC 7554 == Outdated reference: draft-ietf-roll-terminology has been published as RFC 7102 == Outdated reference: A later version (-04) exists of draft-wang-6tisch-6top-sublayer-00 Summary: 1 error (**), 0 flaws (~~), 15 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 SnT/Univ. of Luxembourg 4 Intended status: Informational P. Thubert 5 Expires: January 5, 2015 cisco 6 T. Watteyne 7 Linear Technology / Dust Networks 8 Q. Wang 9 Univ. of Sci. and Tech. Beijing 10 July 4, 2014 12 Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e 13 draft-ietf-6tisch-terminology-02 15 Abstract 17 6TiSCH proposes an architecture for an IPv6 multi-link subnet that is 18 composed of a high speed powered backbone and a number of 19 IEEE802.15.4e TSCH wireless networks attached and synchronized by 20 backbone routers. This document extends existing terminology 21 documents available for Low-power and Lossy Networks to provide 22 additional terminology elements. 24 Requirements Language 26 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 27 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 28 "OPTIONAL" in this document are to be interpreted as described in RFC 29 2119 [RFC2119]. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at http://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on January 5, 2015. 48 Copyright Notice 50 Copyright (c) 2014 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 68 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 69 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 70 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 71 6.1. Normative References . . . . . . . . . . . . . . . . . . 9 72 6.2. Informative References . . . . . . . . . . . . . . . . . 10 73 6.3. External Informative References . . . . . . . . . . . . . 11 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 76 1. Introduction 78 A new breed of Time Sensitive Networks is being developed to enable 79 traffic that is highly sensitive to jitter and quite sensitive to 80 latency. Such traffic is not limited to voice and video, but also 81 includes command and control operations such as in industrial 82 automation or in-vehicle sensors and actuators. 84 At IEEE802.1, the "Audio/Video Task Group", was renamed TSN for Time 85 Sensitive Networking. The IEEE802.15.4 Medium Access Control (MAC) 86 has evolved with IEEE802.15.4e which provides in particular the Time 87 Slotted Channel Hopping (TSCH) mode for industrial-type applications. 88 Both provide deterministic capabilities to the point that a packet 89 that pertains to a certain flow crosses the network from node to node 90 following a very precise schedule, like a train leaves intermediate 91 stations at precise times along its path. 93 This document provides additional terminology elements to cover terms 94 that are new to the context of TSCH wireless networks and other 95 deterministic networks. 97 2. Terminology 99 The draft extends [I-D.ietf-roll-terminology] and use terms from RFC 100 6550 [RFC6550] and RFC 6552 [RFC6552], which are all included here by 101 reference. 103 The draft does not reuse terms from IEEE802.15.4e such as "path" or 104 "link" which bear a meaning that is quite different from classical 105 IETF parlance. 107 This document adds the following terms: 109 6TiSCH: IPv6 over the Timeslotted Channel Hopping (TSCH) mode of 110 IEEE 802.15.4e. It defines the 6top sublayer and a set 111 of protocols (in particular, for setting up a schedule 112 with a centralized or distributed approach, managing the 113 resource allocation), as well as the architecture to bind 114 them together, for use in IPv6 TSCH based networks. 116 6F: IPv6 Forwarding. One of the three forwarding models 117 supported by 6TiSCH. Packets are routed at layer 3, 118 where Quality of Service (QoS) and Random Early Detection 119 (RED) [RFC2309] operations are expected to prioritize 120 flows with differentiated services. 122 6top: 6top is the adaptation sublayer between TSCH and upper 123 layers like 6LoWPAN and RPL. It is defined in 124 [I-D.wang-6tisch-6top-sublayer]. 126 6top Data Convey Model: Model describing how the 6top adaptation 127 layer feeds the data flow coming from upper layers into 128 TSCH. It is composed by an I-MUX module, a MUX module, a 129 set of priority queues, and a PDU (Payload Data Unit).See 130 [I-D.wang-6tisch-6top-sublayer]. 132 ASN: Absolute Slot Number, the total number of timeslots that 133 has elapsed since the start of the network or an 134 arbitrary start time (i.e., a timeslot counter, 135 incremented by one at each timeslot). It is wide enough 136 to not roll over in practice. See [IEEE802154e]. 138 Blacklist: Set of frequencies which should not be used for 139 communication. 141 BBR: Backbone Router. In the 6TiSCH architecture, it is an 142 LBR and also a IPv6 ND-efficiency-aware Router (NEAR) 143 [I-D.chakrabarti-nordmark-6man-efficient-nd]. It 144 performs ND proxy operations between registered devices 145 and classical ND devices that are located over the 146 backbone. 148 Broadcast cell: A scheduled cell used for broadcast transmission. 150 Bundle: A group of equivalent scheduled cells, i.e. cells 151 identified by different [slotOffset, channelOffset], 152 which are scheduled for a same purpose, with the same 153 neighbor, with the same flags, and the same slotframe. 154 The size of the bundle refers to the number of cells it 155 contains. Given the length of the slotframe, the size of 156 the bundle translates directly into bandwidth. 158 Cell: A single element in the TSCH schedule, identified by a 159 slotOffset, a channelOffset, a slotframeHandle. A cell 160 can be scheduled or unscheduled. 162 ChannelOffset: Identifies a row in the TSCH slotframe. The number 163 of available channelOffsets is equal to the number of 164 available frequencies. The channelOffset translates into 165 a frequency when the communication takes place, resulting 166 in channel hopping, as detailed in 167 [I-D.ietf-6tisch-tsch]. 169 Channel distribution/usage (CDU) matrix: : Matrix of height equal to 170 the number of available channels (i.e, ChannelOffsets), 171 representing the spectrum (channel) distribution among 172 the different (RPL parent) nodes in the networks. Every 173 single element of the matrix belongs to a specific chunk. 174 It has to be noticed that such matrix, even though it 175 includes all the cells grouped in chunks, belonging to 176 different slotframes, is different from the TSCH 177 schedule. 179 Chunk: A well-known list of cells, well-distributed in time and 180 frequency, within a CDU matrix; a chunk represents a 181 portion of a CDU matrix that is globally known by all the 182 nodes in the network, with typically at most one cell per 183 slotOffset for single radio devices. Once appropriated, 184 a chunk can be managed separately by a single node within 185 its interference domain. A node may appropriate multiple 186 chunks, and use them according to a specific policy. 187 Chunks may overlap. They can be pre-programmed, or can 188 be computed by an external entity at the network 189 bootstrap. 191 Chunk ownership appropriation: The process by which an individual 192 node obtains a chunk to manage based on peer-to-peer 193 interaction with its neighbors. 195 Chunk ownership delegation: The process by which an individual node 196 obtains a chunk to manage based on point-to-point 197 interaction with an external entity. 199 Communication Paradigm: It is Associated with the Information Model 200 [RFC3444] of the state that is exchanged, and indicates: 201 the location of that state (e.g., centralized vs. 202 distributed, RESTful, etc.), the numbers of parties 203 (e.g., P2P vs. P2MP) and the relationship between parties 204 (e.g., master/slave vs. peers) at a high level of 205 protocol abstraction. Layer 5 client/server REST is a 206 typical communication paradigm, but industrial protocols 207 also use publish/subscribe which is P2MP and source/sink 208 which is MP2MP and primarily used for alarms and alerts 209 at the application layer. At layer 3, basic flooding, 210 P2P synchronization and path-marking (RSVP-like) are 211 commonly used paradigms, whereas at layer 2, master/slave 212 polling and peer-to-peer forwarding are classical 213 examples. 215 Dedicated Cell: A cell that is reserved for a given node to transmit 216 to a specific neighbor. 218 Distributed cell reservation: A reservation of a cell done by one or 219 more in-network entities (typically a connection 220 endpoint). 222 Distributed track reservation: A reservation of a track done by one 223 or more in-network entities (typically a connection 224 endpoint). 226 EB: Enhanced Beacon frame used by a node to announce the 227 presence of the network. It contains information about 228 the timeslot length, the current ASN value, the 229 slotframes and timeslots the beaconing mote is listening 230 on, and a 1-byte join priority (i.e., number of hops 231 separating the node sending the EB, and the PAN 232 coordinator). 234 FF: 6LoWPAN Fragment Forwarding. It is one of the three 235 forwarding models supported by 6TiSCH. The 6LoWPAN 236 Fragment is used as a label for switching at the 6LoWPAN 237 sublayer, as defined in 238 [I-D.thubert-roll-forwarding-frags]. 240 GMPLS: Generalized Multi-Protocol Label Switching, a 2.5 layer 241 service that is used to forward packets based on the 242 concept of generalized labels. 244 Hard Cell: A scheduled cell which the 6top sublayer cannot 245 reallocate. See [I-D.wang-6tisch-6top-sublayer]. 247 Hopping Sequence: Ordered sequence of frequencies, identified by a 248 Hopping_Sequence_ID, used for channel hopping, when 249 translating the channel offset value into a frequency 250 (i.e., PHY channel). See [IEEE802154e] and 251 [I-D.ietf-6tisch-tsch]. 253 IE: Information Elements, a list of Type-Length-Value 254 containers placed at the end of the MAC header, used to 255 pass data between layers or devices. A small number of 256 types are defined by [IEEE802154e], but a range of types 257 is available for extensions, and thus, is exploitable by 258 6TiSCH. See [IEEE802154e]. 260 I-MUX module: Inverse-Multiplexer, a classifier that receives 261 6LoWPAN frames and places them into priority queues. See 262 [I-D.wang-6tisch-6top-sublayer]. 264 Interaction Model: It is a particular way of implementing a 265 communication paradigm. Defined at a lower level of 266 abstraction, it includes protocol-specific details such 267 as a particular method (e.g., a REST GET) and a Data 268 Model for the state to be exchanged. 270 KMP: Key Managment Protocol. 272 LBR: LLN Border Router. It is an LLN device, usually powered, 273 that acts as a Border Router to the outside within the 274 6TiSCH architecture. 276 Link: A communication facility or medium over which nodes can 277 communicate at the link layer, i.e., the layer 278 immediately below IP. Thus, the IETF parlance for the 279 term "Link" is adopted, as opposed to the IEEE802.15.4e 280 terminology. In the context of the 6TiSCH architecture, 281 which applies to Low Power Lossy Networks (LLNs), an IPv6 282 subnet is usually not congruent to a single link and 283 techniques such as IPv6 Neighbor Discovery Proxying are 284 used to achieve reachability within the multilink subnet. 285 A link is distinct from a track. In fact, link local 286 addresses are not expected to be used over a track for 287 end to end communication. Finally, from the Layer 3 288 perspective (where the inner complexities of TSCH 289 operations are hidden to enable classical IP routing and 290 Forwarding), a single radio interface may be seen as a 291 number of Links with different capabilities for unicast 292 or multicast services. 294 Logical Cell: A cell that corresponds to granted bandwidth but is 295 only lazily associated to a physical cell, based on 296 usage. 298 MAC: Medium Access Control. 300 MUX module: Multiplexer, the entity that dequeues frames from 301 priority queues and associates them to a cell for 302 transmission. See [I-D.wang-6tisch-6top-sublayer]. 304 NEAR: Energy Aware Default Router, as defined in 305 [I-D.chakrabarti-nordmark-6man-efficient-nd]. 307 NME: Network Management Entity, the entity in the network 308 managing cells and other device resources. It may 309 cooperate with the PCE. It interacts with LLN nodes 310 through the backbone router. 312 PANA: Protocol for carrying Authentication for Network Access, 313 as defined in [RFC5191] . 315 PCE: Path Computation Element, the entity in the network which 316 is responsible for building and maintaining the TSCH 317 schedule, when centralized scheduling is used. 319 PCE cell reservation: The reservation of a cell done by the PCE. 321 PCE track reservation: The reservation of a track done by the PCE. 323 QoS: Quality of Service. 325 (to) reallocate a cell: The action operated by the 6top sublayer of 326 changing the slotOffset and/or channelOffset of a soft 327 cell. 329 SA: Security Association. 331 (to) Schedule a cell: The action of turning an unscheduled cell into 332 a scheduled cell. 334 Scheduled cell: A cell which is assigned a neighbor MAC address 335 (broadcast address is also possible), and one or more of 336 the following flags: TX, RX, shared, timeskeeping. A 337 scheduled cell can be used by the IEEE802.15.4e TSCH 338 implementation to communicate. A scheduled cell can be a 339 hard cell or a soft cell. 341 Shared Cell: A cell marked with both the "TX" and "shared" flags. 342 This cell can be used by more than one transmitter node. 343 A backoff algorithm is used to resolve contention. See 344 [I-D.ietf-6tisch-tsch]. 346 SlotOffset: Identifies a column in the TSCH schedule, i.e., the 347 number of timeslots since the beginning of the current 348 iteration of the slotframe. 350 Slotframe: A MAC-level abstraction that is internal to the node and 351 contains a series of timeslots of equal length and 352 priority. It is characterized by a slotframe_ID, and a 353 slotframe_size. Multiple slotframes can coexist in a 354 node's schedule, i.e., a node can have multiple 355 activities scheduled in different slotframes, based on 356 the priority of its packets/traffic flows. The timeslots 357 in the Slotframe are indexed by the SlotOffset; the first 358 timeslot is at SlotOffset 0. 360 Soft Cell: A scheduled cell which the 6top sublayer can reallocate, 361 as described in [I-D.wang-6tisch-6top-sublayer]. 363 TF: Track Forwarding. It is the simplest and fastest 364 forwarding model supported by 6TiSCH. It is a G-MPLS- 365 like forwarding model. The input cell characterizes the 366 flow and indicates the output cell. 368 Timeslot: A basic communication unit in TSCH which allows a 369 transmitter node to send a frame to a receiver neighbor, 370 and that receiver neighbor to optionally send back an 371 acknowledgment. 373 Time Source Neighbor: A neighbor a node uses as its time reference, 374 and to which it needs to keep its clock synchronized. A 375 node can have one or more time source neighbors. 377 Track: A determined sequence of cells along a multi-hop path. 378 It is typically the result of a reservation. The node 379 that initializes the process for establishing a track is 380 the owner of the track. The latter assigns a unique 381 identifier to the track, called TrackID. 383 TrackID: Unique identifier of a track, assigned by the owner of 384 the track. 386 TSCH: Time Slotted Channel Hopping, a medium access mode of the 387 [IEEE802154e] standard which uses time synchronization to 388 achieve ultra low-power operation and channel hopping to 389 enable high reliability. 391 TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset 392 and a channelOffset. The TSCH schedule contains all the 393 scheduled cells from all slotframes and is sufficient to 394 qualify the communication in the TSCH network. The 395 "width of the matrix is equal to the number of scheduled 396 timeslots in all the concurrent active slotframes. The 397 number of channelOffset values (the "height" of the 398 matrix) is equal to the number of available frequencies. 400 unscheduled cell: A cell which is not used by the IEEE802.15.4e TSCH 401 implementation. 403 3. IANA Considerations 405 This specification does not require IANA action. 407 4. Security Considerations 409 This specification is not found to introduce new security threats. 411 5. Acknowledgments 413 Thanks to the IoT6 European Project (STREP) of the 7th Framework 414 Program (Grant 288445). 416 6. References 418 6.1. Normative References 420 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 421 Requirement Levels", BCP 14, RFC 2119, March 1997. 423 [RFC2309] Braden, B., Clark, D., Crowcroft, J., Davie, B., Deering, 424 S., Estrin, D., Floyd, S., Jacobson, V., Minshall, G., 425 Partridge, C., Peterson, L., Ramakrishnan, K., Shenker, 426 S., Wroclawski, J., and L. Zhang, "Recommendations on 427 Queue Management and Congestion Avoidance in the 428 Internet", RFC 2309, April 1998. 430 [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between 431 Information Models and Data Models", RFC 3444, January 432 2003. 434 [RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A. 435 Yegin, "Protocol for Carrying Authentication for Network 436 Access (PANA)", RFC 5191, May 2008. 438 [RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R., 439 Levis, P., Pister, K., Struik, R., Vasseur, JP., and R. 440 Alexander, "RPL: IPv6 Routing Protocol for Low-Power and 441 Lossy Networks", RFC 6550, March 2012. 443 [RFC6552] Thubert, P., "Objective Function Zero for the Routing 444 Protocol for Low-Power and Lossy Networks (RPL)", RFC 445 6552, March 2012. 447 6.2. Informative References 449 [I-D.chakrabarti-nordmark-6man-efficient-nd] 450 Chakrabarti, S., Nordmark, E., Thubert, P., and M. 451 Wasserman, "IPv6 Neighbor Discovery Optimizations for 452 Wired and Wireless Networks", draft-chakrabarti-nordmark- 453 6man-efficient-nd-05 (work in progress), February 2014. 455 [I-D.ietf-6tisch-6top-interface] 456 Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH 457 Operation Sublayer (6top) Interface", draft-ietf-6tisch- 458 6top-interface-00 (work in progress), March 2014. 460 [I-D.ietf-6tisch-architecture] 461 Thubert, P., Watteyne, T., and R. Assimiti, "An 462 Architecture for IPv6 over the TSCH mode of IEEE 463 802.15.4e", draft-ietf-6tisch-architecture-02 (work in 464 progress), June 2014. 466 [I-D.ietf-6tisch-coap] 467 Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and 468 Interaction using CoAP", draft-ietf-6tisch-coap-00 (work 469 in progress), May 2014. 471 [I-D.ietf-6tisch-minimal] 472 Vilajosana, X. and K. Pister, "Minimal 6TiSCH 473 Configuration", draft-ietf-6tisch-minimal-01 (work in 474 progress), June 2014. 476 [I-D.ietf-6tisch-tsch] 477 Watteyne, T., Palattella, M., and L. Grieco, "Using 478 IEEE802.15.4e TSCH in an LLN context: Overview, Problem 479 Statement and Goals", draft-ietf-6tisch-tsch-00 (work in 480 progress), November 2013. 482 [I-D.ietf-roll-terminology] 483 Vasseur, J., "Terms used in Routing for Low power And 484 Lossy Networks", draft-ietf-roll-terminology-13 (work in 485 progress), October 2013. 487 [I-D.thubert-roll-forwarding-frags] 488 Thubert, P. and J. Hui, "LLN Fragment Forwarding and 489 Recovery", draft-thubert-roll-forwarding-frags-02 (work in 490 progress), September 2013. 492 [I-D.wang-6tisch-6top-sublayer] 493 Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH 494 Operation Sublayer (6top)", draft-wang-6tisch-6top- 495 sublayer-00 (work in progress), February 2014. 497 6.3. External Informative References 499 [IEEE802154e] 500 IEEE standard for Information Technology, "IEEE std. 501 802.15.4e, Part. 15.4: Low-Rate Wireless Personal Area 502 Networks (LR-WPANs) Amendment 1: MAC sublayer", April 503 2012. 505 Authors' Addresses 507 Maria Rita Palattella (editor) 508 University of Luxembourg 509 Interdisciplinary Centre for Security, Reliability and Trust 510 4, rue Alphonse Weicker 511 Luxembourg L-2721 512 Luxembourg 514 Phone: (+352) 46 66 44 5841 515 Email: maria-rita.palattella@uni.lu 516 Pascal Thubert 517 Cisco Systems, Inc 518 Village d'Entreprises Green Side 519 400, Avenue de Roumanille 520 Batiment T3 521 Biot - Sophia Antipolis 06410 522 France 524 Phone: +33 497 23 26 34 525 Email: pthubert@cisco.com 527 Thomas Watteyne 528 Linear Technology / Dust Networks 529 30695 Huntwood Avenue 530 Hayward, CA 94544 531 USA 533 Phone: +1 (510) 400-2978 534 Email: twatteyne@linear.com 536 Qin Wang 537 Univ. of Sci. and Tech. Beijing 538 30 Xueyuan Road 539 Beijing, Hebei 100083 540 China 542 Phone: +86 (10) 6233 4781 543 Email: wangqin@ies.ustb.edu.cn