idnits 2.17.1 draft-palattella-6tsch-terminology-01.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 15, 2013) is 3910 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'IEEE802154e' is mentioned on line 407, but not defined == Unused Reference: 'I-D.ohba-6tsch-security' is defined on line 377, but no explicit reference was found in the text == Unused Reference: 'I-D.thubert-6tsch-architecture' is defined on line 383, but no explicit reference was found in the text == Unused Reference: 'I-D.vilajosana-6tsch-basic' is defined on line 394, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-chakrabarti-nordmark-6man-efficient-nd-01 == Outdated reference: A later version (-13) exists of draft-ietf-roll-terminology-12 == Outdated reference: A later version (-02) exists of draft-thubert-6tsch-architecture-01 == Outdated reference: A later version (-02) exists of draft-thubert-roll-forwarding-frags-01 Summary: 0 errors (**), 0 flaws (~~), 10 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6TSCH MR. Palattella, Ed. 3 Internet-Draft SnT/Univ. of Luxembourg 4 Intended status: Informational P. Thubert 5 Expires: January 16, 2014 cisco 6 T. Watteyne 7 Linear Technology / Dust Networks 8 Q. Wang 9 Univ. of Sci. and Tech. Beijing 10 July 15, 2013 12 Terminology in IPv6 over Timeslotted Channel Hopping 13 draft-palattella-6tsch-terminology-01 15 Abstract 17 6TSCH proposes an architecture for an IPv6 multilink 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 16, 2014. 48 Copyright Notice 50 Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . 8 68 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 69 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 70 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 71 6.1. Normative References . . . . . . . . . . . . . . . . . . 8 72 6.2. Informative References . . . . . . . . . . . . . . . . . 8 73 6.3. External Informative References . . . . . . . . . . . . . 9 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 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] which is included here 100 by reference. 102 The draft does not reuse terms from IEEE802.15.4e such as "path" or 103 "link" which bear a meaning that is quite different from classical 104 IETF parlance. 106 This document adds the following terms: 108 6TSCH: IPv6 over Time Slotted Channel Hopping (pronounced 109 "sixtus"). It defines a set of IETF sublayers and 110 protocols (in particular, for setting up a schedule with 111 a centralized or distributed approach, managing the 112 resource allocation), as well as the architecture to bind 113 them together, for use in IPv6 TSCH based networks. 115 6F: IPv6 Forwarding. One of the three forwarding model 116 supported by 6TSCH. Packets are routed at layer 3, where 117 QoS and RED operations are expected to prioritize flows 118 with differentiated services. 120 6top: 6top is the adaptation layer between TSCH and upper 121 layers like 6LoWPAN and RPL. It is defined in 122 [I-D.draft-wang-6tsch-6top]. 124 6top Data Convey Model: Model describing how the 6top adaptation 125 layer feeds the data flow coming from upper layers into 126 TSCH. It is composed by an I-MUX module, a MUX module, a 127 set of priority queues, and a PDU (Payload Data Unit). 129 ASN: Absolute Slot Number, the timeslot counter, incremented 130 by one at each timeslot. It is wide enough to not roll 131 over in practice. See 132 [I-D.watteyne-6tsch-tsch-lln-context]. 134 Blacklist: Set of frequencies which should not be used for 135 communication. 137 BBR: Backbone Router. In the 6TSCH architecture, it is an LBR 138 and also a NEAR. It performs ND proxy operations between 139 registered devices and classical ND devices that are 140 located over the backbone. 142 Bundle: A group of equivalent scheduled cells, i.e. cells 143 identified by different [slotOffset, channelOffset], 144 which are scheduled for a same purpose, with the same 145 neighbor, with the same flags, and the same slotframe. 146 The size of the bundle refers to the number of cells it 147 contains. Given the length of the slotframe, the size of 148 the bundle translates directly into bandwidth, either 149 logical, or physical. 151 Cell: A single element in the TSCH sloframe, identified by a 152 slotOffset value, a channelOffset value, a slotframe_ID 153 and Hopping_Sequence_ID. A cell can be scheduled or 154 unscheduled. During an unscheduled cell, the node does 155 not communicate. When a cell is scheduled, it is 156 assigned a MAC-layer slotframe identifier, a neighbor MAC 157 address (which can be the broadcast address), and one or 158 more of the following flags: TX, RX, shared, 159 timeskeeping, hard. A broadcast cell is an alias for "a 160 scheduled cell with neighbor address the broadcast 161 address". 163 ChannelOffset: Identifies a row in the TSCH slotframe. The number 164 of available channelOffsets is equal to the number of 165 available frequencies. The channelOffset translates into 166 a frequency when the communication takes place, resulting 167 in channel hopping, as detailed in 168 [I-D.watteyne-6tsch-tsch-lln-context]. 170 Dedicated Cell: A cell that is reserved for a given node to transmit 171 to a specific neighbor. 173 Distributed cell reservation: A reservation of a cell done by one or 174 more in-network entities (typically a connection 175 endpoint). 177 Distributed track reservation: A reservation of a track done by one 178 or more in-network entities (typically a connection 179 endpoint). 181 EB: Enhanced Beacon frame used by an advertising node to 182 announce the presence of the network. It contains 183 information about the timeslot length, the current ASN 184 value, the slotframes and timeslots the beaconing mote is 185 listening on, and a 1-byte join priority (i.e., number of 186 hops separating the node sending the EB, and the PAN 187 coordinator). 189 FF: 6LoWPAN Fragment Forwarding. It is one of the three 190 forwarding model supported by 6TSCH. The 6LoWPAN 191 Fragment is used as a label for switching at the 6LoWPAN 192 sublayer, as defined in 193 [I-D.thubert-roll-forwarding-frags]. 195 GMPLS: Generalized Multi-Protocol Label Switching, a 2.5 layer 196 service that is used to forward packets based on the 197 concept of generalized labels. 199 Hard Cell: A scheduled cell that is locked, i.e., it cannot be moved 200 by 6top in the schedule. See 201 [I-D.draft-wang-6tsch-6top]. 203 Hopping Sequence: Sequence of frequencies, identified by a 204 Hopping_Sequence_ID, used for channel hopping, when 205 translating the channel offset value into a frequency 206 (i.e., PHY channel). See 207 [I-D.watteyne-6tsch-tsch-lln-context]. 209 IE: Information Elements, a list of Type-Length-Value 210 containers placed at the end of the MAC header, used to 211 pass data between layers or devices. A small number of 212 types are defined by TSCH, but a range of types is 213 available for extensions, and thus, is exploitable by 214 6TSCH. See [I-D.watteyne-6tsch-tsch-lln-context]. 216 I-MUX module: Inverse-Multiplexer, a classifier that receives 217 6LoWPAN frames and places them into priority queues. 219 KMP: Key Managment Protocol. 221 LBR: LLN Border Router. It is an LLN device, usually powered, 222 that acts as a Border Router to the outside within the 223 6TSCH architecture. 225 Link: A communication facility or medium over which nodes can 226 communicate at the link layer, i.e., the layer 227 immediately below IP. Thus, the IETF parlance for the 228 term "Link" is adopted, as opposed to the incompatible 229 IEEE802.15.4e terminology. In the context of the 6TSCH 230 architecture, which applies to Low Power Lossy Networks 231 (LLNs), an IPv6 subnet is usually not congruent to a 232 single link and techniques such as IPv6 Neighbor 233 Discovery Proxying and Routing Over LLNs are required to 234 achieve reachability within the multilink subnet. A link 235 is distinct from a track. In fact, link local addresses 236 are not expected to be used over a track for end to end 237 communication. Finally, from the Layer 3 perspective 238 (where the inner complexities of TSCH operations are 239 hidden to enable classical IP routing and Forwarding), a 240 single radio interface may be seen as a number of Links 241 with different capabilities for unicast or multicast 242 services. 244 Logical Cell: A cell that corresponds to granted bandwidth but is 245 only lazily associated to a physical cell, based on 246 usage. 248 MAC: Medium Access Control. 250 MUX module: Multiplexer, the entity that dequeues frames from 251 priority queues and associates them to a cell for 252 transmission. 254 NEAR: Energy Aware Default Router, as defined in 255 [I-D.chakrabarti-nordmark-6man-efficient-nd]. 257 PANA: Protocol for carrying Authentication for Network Access, 258 as defined in [RFC5191] . It is the protocol used in the 259 6TSCH architecture for handling authentication during the 260 join process. 262 PCE: Path Computation Element, the entity in the network which 263 is responsible for building and maintaining the TSCH 264 schedule, when centralized scheduling is used. 266 PCE cell reservation: The reservation of a cell done by the PCE. 268 PCE track reservation: The reservation of a track done by the PCE. 270 QoS: Quality of Service. 272 SA: Security Association. 274 Shared Cell: A cell that is used by more than one transmitter nodes 275 at the same time and on the same channelOffset. Only 276 cells with TX flag can be marked as "shared". A backoff 277 algorithm is used to resolve contention. 279 SlotOffset: Identifies a column in the TSCH schedule, i.e., the 280 number of timeslots since the beginning of the current 281 iteration of the slotframe. 283 Slotframe: A MAC-level abstraction that is internal to the node and 284 contains a series of timeslots of equal length and 285 priority. It is characterized by a slotframe_ID, and a 286 slotframe_size. Multiple slotframes can coexist in a 287 node's schedule, i.e., a node can have multiple 288 activities scheduled in different slotframes, based on 289 the priority of its packets/traffic flows. The timeslots 290 in the Slotframe are indexed by the SlotOffset; the first 291 timeslot is at SlotOffset 0. 293 Soft Cell: A scheduled cell that is not locked, i.e., it may be 294 moved in the schedule within a same slotframe by 6top, as 295 described in [I-D.draft-wang-6tsch-6top]. 297 TF: Track Forwarding. It is the simplest and fastest 298 forwarding model supported by 6TSCH. It is a G-MPLS-like 299 forwarding model. The input cell characterises the flow 300 and indicates the output cell. 302 Timeslot: A basic communication unit in TSCH which allows a 303 transmitter node to send a frame to a receiver neighbor, 304 and that receiver neighbor to optionally send back an 305 acknowledgment. The length of the timeslot determines 306 the maximum size of the frame that can be exchanged. 308 Time Source Neighbor: A neighbor a node uses as its time reference, 309 and to which it needs to keep its clock synchronized. A 310 node can have one or more time source neighbors. 312 Track: A determined sequence of cells along a multi-hop path. 313 It is typically the result of a reservation. The node 314 that initializes the process for establishing a track is 315 the owner of the track. The latter assigns a unique 316 identifier to the track, called TrackID. 318 TrackID: Unique identifier of a track, assigned by the owner of 319 the track. 321 TSCH: Time Slotted Channel Hopping, a medium access mode of the 322 [IEEE802154e] standard which uses time synchronization to 323 achieve ultra low-power operation and channel hopping to 324 enable high reliability. 326 TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset 327 and a channelOffset. The slotframe size (the "width" of 328 the matrix) is the number of timeslots it contains. The 329 number of channelOffset values (the "height" of the 330 matrix) is equal to the number of available frequencies. 331 The TSCH schedule contains all the scheduled cells from 332 all slotframes and is sufficient to qualify the 333 communication in the TSCH network. 335 3. IANA Considerations 337 This specification does not require IANA action. 339 4. Security Considerations 341 This specification is not found to introduce new security threat. 343 5. Acknowledgements 345 Thanks to the IoT6 European Project (STREP) of the 7th Framework 346 Program (Grant 288445). 348 6. References 350 6.1. Normative References 352 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 353 Requirement Levels", BCP 14, RFC 2119, March 1997. 355 [RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A. 356 Yegin, "Protocol for Carrying Authentication for Network 357 Access (PANA)", RFC 5191, May 2008. 359 6.2. Informative References 361 [I-D.chakrabarti-nordmark-6man-efficient-nd] 362 Chakrabarti, S., Nordmark, E., and M. Wasserman, 363 "Efficiency aware IPv6 Neighbor Discovery Optimizations", 364 draft-chakrabarti-nordmark-6man-efficient-nd-01 (work in 365 progress), November 2012. 367 [I-D.draft-wang-6tsch-6top] 368 Wang, Q., Ed., Vilajosana, X., and T. Watteyne, "6TSCH 369 Operation Sublayer (6top). draft-wang-6tsch-6top-00 (work 370 in progress) ", July 2013. 372 [I-D.ietf-roll-terminology] 373 Vasseur, J., "Terminology in Low power And Lossy 374 Networks", draft-ietf-roll-terminology-12 (work in 375 progress), March 2013. 377 [I-D.ohba-6tsch-security] 378 Chasko, S., Das, S., Lopez, R., Ohba, Y., Thubert, P., and 379 A. Yegin, "Security Framework and Key Management Protocol 380 Requirements for 6TSCH", draft-ohba-6tsch-security-01 381 (work in progress), July 2013. 383 [I-D.thubert-6tsch-architecture] 384 Thubert, P., Assimiti, R., and T. Watteyne, "An 385 Architecture for IPv6 over Time Slotted Channel Hopping", 386 draft-thubert-6tsch-architecture-01 (work in progress), 387 April 2013. 389 [I-D.thubert-roll-forwarding-frags] 390 Thubert, P. and J. Hui, "LLN Fragment Forwarding and 391 Recovery", draft-thubert-roll-forwarding-frags-01 (work in 392 progress), February 2013. 394 [I-D.vilajosana-6tsch-basic] 395 Vilajosana, X. and K. Pister, "Minimal 6TSCH 396 Configuration", draft-vilajosana-6tsch-basic-01 (work in 397 progress), July 2013. 399 [I-D.watteyne-6tsch-tsch-lln-context] 400 Watteyne, T., Palattella, M., and L. Grieco, "Using 401 IEEE802.15.4e TSCH in an LLN context: Overview, Problem 402 Statement and Goals", draft-watteyne-6tsch-tsch-lln- 403 context-02 (work in progress), May 2013. 405 6.3. External Informative References 407 [IEEE802154e] 408 IEEE standard for Information Technology, "IEEE std. 409 802.15.4e, Part. 15.4: Low-Rate Wireless Personal Area 410 Networks (LR-WPANs) Amendament 1: MAC sublayer", April 411 2012. 413 Authors' Addresses 414 Maria Rita Palattella (editor) 415 University of Luxembourg 416 Interdisciplinary Centre for Security, Reliability and Trust 417 4, rue Alphonse Weicker 418 Luxembourg L-2721 419 LUXEMBOURG 421 Phone: (+352) 46 66 44 5841 422 Email: maria-rita.palattella@uni.lu 424 Pascal Thubert 425 Cisco Systems, Inc 426 Village d'Entreprises Green Side 427 400, Avenue de Roumanille 428 Batiment T3 429 Biot - Sophia Antipolis 06410 430 FRANCE 432 Phone: +33 497 23 26 34 433 Email: pthubert@cisco.com 435 Thomas Watteyne 436 Linear Technology / Dust Networks 437 30695 Huntwood Avenue 438 Hayward, CA 94544 439 USA 441 Phone: +1 (510) 400-2978 442 Email: twatteyne@linear.com 444 Qin Wang 445 Univ. of Sci. and Tech. Beijing 446 30 Xueyuan Road 447 Beijing, Hebei 100083 448 China 450 Phone: +86 (10) 6233 4781 451 Email: wangqin@ies.ustb.edu.cn