idnits 2.17.00 (12 Aug 2021) /tmp/idnits61474/draft-ietf-6tisch-terminology-04.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 (March 23, 2015) is 2616 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'IEEE802154e' is mentioned on line 543, but not defined == Missing Reference: 'IEEE.802.1AR' is mentioned on line 538, but not defined == Unused Reference: 'RFC5191' is defined on line 478, but no explicit reference was found in the text == Unused Reference: 'RFC6347' is defined on line 482, but no explicit reference was found in the text == Unused Reference: 'RFC7252' is defined on line 499, but no explicit reference was found in the text == Unused Reference: 'I-D.thubert-6lo-rfc6775-update-reqs' is defined on line 521, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2309 (Obsoleted by RFC 7567) ** Obsolete normative reference: RFC 6347 (Obsoleted by RFC 9147) == 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 (-07) exists of draft-thubert-6lo-rfc6775-update-reqs-06 == Outdated reference: A later version (-04) exists of draft-wang-6tisch-6top-sublayer-01 Summary: 2 errors (**), 0 flaws (~~), 12 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: September 24, 2015 cisco 6 T. Watteyne 7 Linear Technology / Dust Networks 8 Q. Wang 9 Univ. of Sci. and Tech. Beijing 10 March 23, 2015 12 Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e 13 draft-ietf-6tisch-terminology-04 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 September 24, 2015. 48 Copyright Notice 50 Copyright (c) 2015 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 . . . . . . . . . . . . . . . . . . . . . 10 68 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 69 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 70 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 71 6.1. Normative References . . . . . . . . . . . . . . . . . . 10 72 6.2. Informative References . . . . . . . . . . . . . . . . . 11 73 6.3. External Informative References . . . . . . . . . . . . . 12 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 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 The IEEE802.15.4 Medium Access Control (MAC) has evolved with 85 IEEE802.15.4e which provides in particular the Time Slotted Channel 86 Hopping (TSCH) mode for industrial-type applications. It provides 87 deterministic capabilities to the point that a packet that pertains 88 to a certain flow crosses the network from node to node following a 89 very precise schedule, like a train leaves intermediate stations at 90 precise times along its path. 92 This document provides additional terminology elements to cover terms 93 that are new to the context of TSCH wireless networks and other 94 deterministic networks. 96 2. Terminology 98 The draft extends [I-D.ietf-roll-terminology] and use terms from RFC 99 6550 [RFC6550] and RFC 6552 [RFC6552], which are all included here by 100 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 6TiSCH: IPv6 over the Timeslotted Channel Hopping (TSCH) mode of 109 IEEE 802.15.4e. It defines the 6top sublayer and a set 110 of protocols (in particular, for setting up a TSCH 111 schedule with a centralized or distributed approach, 112 managing the resource allocation), as well as the 113 architecture to bind them together, for use in IPv6 TSCH 114 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 Active Queue 119 Management (e.g., Random Early Detection, RED, [RFC2309]) 120 operations are expected to prioritize flows with 121 differentiated services. 123 6top: 6top is the adaptation sublayer between TSCH and upper 124 layers like IPv6 over Low-Power Wireless Personal Area 125 Networks (6LoWPANs) and IPv6 Routing Protocol for Low- 126 Power and Lossy Networks (RPL). It is defined in 127 [I-D.wang-6tisch-6top-sublayer]. 129 6top Data Convey Model: Model describing how the 6top adaptation 130 layer feeds the data flow coming from upper layers into 131 TSCH. It is composed by an I-MUX module, a MUX module, a 132 set of priority queues, and a PDU (Payload Data Unit).See 133 [I-D.wang-6tisch-6top-sublayer]. 135 ARO: [RFC6775] defines a number of new Neighbor Discovery 136 options including the Address Registration Option (ARO). 138 ASN: Absolute Slot Number, the total number of timeslots that 139 has elapsed since the PAN coordinator has started the 140 TSCH network. It is incremented by one at each timeslot. 141 It is wide enough to not roll over in practice. See 142 [IEEE802154e]. 144 Blacklist of Frequencies: Simply defined Blacklist in [IEEE802154e], 145 it is the set of frequencies which should not be used for 146 communication. 148 BBR: Backbone Router. In the 6TiSCH architecture, it is an 149 LBR and also a IPv6 ND-efficiency-aware Router (NEAR) 150 [I-D.chakrabarti-nordmark-6man-efficient-nd]. It 151 performs ND proxy operations between registered devices 152 and classical ND devices that are located over the 153 backbone. 155 Broadcast Cell: A scheduled cell used for broadcast transmission. 157 Bundle: A group of equivalent scheduled cells, i.e. cells 158 identified by different [slotOffset, channelOffset], 159 which are scheduled for a same purpose, with the same 160 neighbor, with the same flags, and the same slotframe. 161 The size of the bundle refers to the number of cells it 162 contains. Given the length of the slotframe, the size of 163 the bundle translates directly into bandwidth. 165 Cell: A single element in the TSCH schedule, identified by a 166 slotOffset, a channelOffset, a slotframeHandle. A cell 167 can be scheduled or unscheduled. 169 Centralized Cell Reservation: A reservation of a cell done by a 170 centralized entity (e.g., a PCE) in the network. 172 Centralized Track Reservation: A reservation of a track done by a 173 centralized entity (e.g., a PCE) in the network. 175 ChannelOffset: Identifies a row in the TSCH schedule. The number of 176 available channelOffsets is equal to the number of 177 available frequencies. The channelOffset translates into 178 a frequency when the communication takes place, resulting 179 in channel hopping, as detailed in 180 [I-D.ietf-6tisch-tsch]. 182 Channel Distribution/Usage (CDU) matrix: : Matrix of cells (i,j) 183 representing the spectrum (channel) distribution among 184 the different nodes in the 6TiSCH network. The CDU 185 matrix has width in timeslots, equal to the period of the 186 network scheduling operation, and height equal to the 187 number of available channels. Every cell (i,j) in the 188 CDU, identified by (slotOffset, channelOffset), belongs 189 to a specific chunk. It has to be noticed that such a 190 matrix, even though it includes all the cells grouped in 191 chunks, belonging to different slotframes, is different 192 from the TSCH schedule. 194 Chunk: A well-known list of cells, distributed in time and 195 frequency, within a CDU matrix; a chunk represents a 196 portion of a CDU matrix. The partition of the CDU in 197 chunks is globally known by all the nodes in the network 198 to support the appropriation process, which is a 199 negotiation between nodes within an interference domain. 200 A node that manages to appropriate a chunk gets to decide 201 which transmissions will occur over the cells in the 202 chunk within its interference domain (i.e., a parent node 203 will decide when the cells within the appropriated chunk 204 are used and by which node, among its children. 206 Communication Paradigm: It is Associated with the Information Model 207 [RFC3444] of the state that is exchanged, and indicates: 208 the location of that state (e.g., centralized vs. 209 distributed, RESTful, etc.), the numbers of parties 210 (e.g., point to point, P2P, vs. point to multi-point, 211 P2MP) and the relationship between parties (e.g., master/ 212 slave vs. peers) at a high level of protocol abstraction. 213 Layer 5 client/server REST is a typical communication 214 paradigm, but industrial protocols also use publish/ 215 subscribe which is P2MP and source/sink which is multi- 216 point to multi-point (MP2MP) and primarily used for 217 alarms and alerts at the application layer. At layer 3, 218 basic flooding, P2P synchronization and path-marking 219 (RSVP-like) are commonly used paradigms, whereas at layer 220 2, master/slave polling and peer-to-peer forwarding are 221 classical examples. 223 DAR/DAC: [RFC6775] defines the Duplicate Address Request (DAR) and 224 Duplicate Address Confirmation (DAC) options to turn the 225 multicast Duplicate Address Detection protocol into a 226 unicast-based multi-hop process between routers and the 227 backbone router. 229 Dedicated Cell: A cell that is reserved for a given node to transmit 230 to a specific neighbor. 232 Deterministic Network: A Deterministic Network supports traffic 233 flows with communication patterns that are known a 234 priori. Thus, routing paths and communication schedules 235 can be computed in advance, in a fashion similar to a 236 railway system, to avoid losses due to packet collisions, 237 and to perform global optimizations across multiple 238 flows. A deterministic network can allocates the 239 required resources (buffers, processors, medium access) 240 along the multi-hop routing path at the precise moment 241 the resources are needed. 243 Distributed Cell Reservation: A reservation of a cell done by one or 244 more in-network entities (typically a connection 245 endpoint). 247 Distributed Track Reservation: A reservation of a track done by one 248 or more in-network entities (typically a connection 249 endpoint). 251 EARO: [I-D.thubert-6lo-rfc6775-update-reqs]extends the ARO 252 option to include some additional fields necessary to 253 distinguish duplicate addresses from nodes that have 254 moved networks when there are mulitple LLNs linked over a 255 backbone. 257 EB: Enhanced Beacon frame used by a node to announce the 258 presence of the network. It contains useful information 259 (see [IEEE802154e] for details) that allow a new node to 260 synhronize and join the network. 262 FF: 6LoWPAN Fragment Forwarding. It is one of the three 263 forwarding models supported by 6TiSCH. The 6LoWPAN 264 Fragment is used as a label for switching at the 6LoWPAN 265 sublayer, as defined in 266 [I-D.thubert-roll-forwarding-frags]. 268 GMPLS: Generalized Multi-Protocol Label Switching, a 2.5 layer 269 service that is used to forward packets based on the 270 concept of generalized labels. 272 Hard Cell: A scheduled cell which the 6top sublayer cannot 273 reallocate. See [I-D.wang-6tisch-6top-sublayer]. 275 Hopping Sequence: Ordered sequence of frequencies, identified by a 276 Hopping_Sequence_ID, used for channel hopping, when 277 translating the channel offset value into a frequency 278 (i.e., PHY channel). See [IEEE802154e] and 279 [I-D.ietf-6tisch-tsch]. 281 IE: Information Elements, a list of Type-Length-Value 282 containers placed at the end of the MAC header, used to 283 pass data between layers or devices. A small number of 284 types are defined by [IEEE802154e], but a range of types 285 is available for extensions, and thus, is exploitable by 286 6TiSCH. See [IEEE802154e]. 288 I-MUX module: Inverse-Multiplexer, a classifier that receives 289 6LoWPAN frames and places them into priority queues. See 290 [I-D.wang-6tisch-6top-sublayer]. 292 Interaction Model: It is a particular way of implementing a 293 communication paradigm. Defined at a lower level of 294 abstraction, it includes protocol-specific details such 295 as a particular method (e.g., a REST GET) and a Data 296 Model for the state to be exchanged. 298 Interference Domain: The Interference Domain of a given 299 (transmitter) node A includes all the nodes in its 300 neighbourhood that can generate interference at its 301 receiver B, when transmitting on the same channel (i.e., 302 using the same frequency). 304 JCE: The Join Coordination Entity (JCE) is a central entity 305 like the Path Computation Engine (PCE), that may assist 306 in several aspects of the join protocol, such as 307 authentication, authorization, and configuration. 309 JA: The Join Assistant (JA) is a one-hop neighbor of a 310 joining node that may facilitate it to become meaningful 311 part of the network (e.g., by serving as a local 312 connectivity point to the remainder of the network). 314 Join Protocol: The protocol which secures initial communication 315 between a joining node and the JCE. 317 LBR: Low-power Lossy Network (LLN) Border Router. It is an 318 LLN device, usually powered, that acts as a Border Router 319 to the outside within the 6TiSCH architecture. 321 Link: A communication facility or medium over which nodes can 322 communicate at the link layer, i.e., the layer 323 immediately below IP. Thus, the IETF parlance for the 324 term "Link" is adopted, as opposed to the IEEE802.15.4e 325 terminology. In the context of the 6TiSCH architecture, 326 which applies to Low Power Lossy Networks (LLNs), an IPv6 327 subnet is usually not congruent to a single link and 328 techniques such as IPv6 Neighbor Discovery Proxying are 329 used to achieve reachability within the multilink subnet. 330 A link is distinct from a track. In fact, link local 331 addresses are not expected to be used over a track for 332 end to end communication. Finally, from the Layer 3 333 perspective (where the inner complexities of TSCH 334 operations are hidden to enable classical IP routing and 335 Forwarding), a single radio interface may be seen as a 336 number of Links with different capabilities for unicast 337 or multicast services. 339 Logical Cell: A cell that corresponds to granted bandwidth but is 340 only lazily associated to a physical cell, based on 341 usage. 343 MAC: Medium Access Control. 345 MUX Module: Multiplexer, the entity that dequeues frames from 346 priority queues and associates them to a cell for 347 transmission. See [I-D.wang-6tisch-6top-sublayer]. 349 NEAR: IPv6 ND-efficiency-aware Router, as defined in 350 [I-D.chakrabarti-nordmark-6man-efficient-nd]. 352 NME: Network Management Entity, the entity in the network 353 managing cells and other device resources. It may 354 cooperate with the PCE. It interacts with LLN nodes 355 through the backbone router. 357 Operational Network: A IEEE802.15.4e network whose encryption/ 358 authentication keys are determined by some algorithms/ 359 protocols. There may be network-wide group keys, or per- 360 link keys. 362 Operational Network Key: A Link-layer key known by all authorized 363 nodes, used for multicast messages. 365 PCE: Path Computation Element, the entity in the network which 366 is responsible for building and maintaining the TSCH 367 schedule, when centralized scheduling is used. 369 QoS: Quality of Service. 371 (to) Reallocate a Cell: The action operated by the 6top sublayer of 372 changing the slotOffset and/or channelOffset of a soft 373 cell. 375 (to) Schedule a Cell: The action of turning an unscheduled cell into 376 a scheduled cell. 378 Scheduled cell: A cell which is assigned a neighbor MAC address 379 (broadcast address is also possible), and one or more of 380 the following flags: TX, RX, shared, timeskeeping. A 381 scheduled cell can be used by the IEEE802.15.4e TSCH 382 implementation to communicate. A scheduled cell can be a 383 hard cell or a soft cell. 385 Shared Cell: A cell marked with both the "TX" and "shared" flags. 386 This cell can be used by more than one transmitter node. 387 A backoff algorithm is used to resolve contention. See 388 [I-D.ietf-6tisch-tsch]. 390 SlotOffset: Identifies a column in the TSCH schedule, i.e., the 391 number of timeslots since the beginning of the current 392 iteration of the slotframe. 394 Slotframe: A MAC-level abstraction that is internal to the node and 395 contains a series of timeslots of equal length and 396 priority. It is characterized by a slotframe_ID, and a 397 slotframe_size. Multiple slotframes can coexist in a 398 node's schedule, i.e., a node can have multiple 399 activities scheduled in different slotframes, based on 400 the priority of its packets/traffic flows. The timeslots 401 in the Slotframe are indexed by the SlotOffset; the first 402 timeslot is at SlotOffset 0. 404 Soft Cell: A scheduled cell which the 6top sublayer can reallocate, 405 as described in [I-D.wang-6tisch-6top-sublayer]. 407 TF: Track Forwarding. It is the simplest and fastest 408 forwarding model supported by 6TiSCH. It is a GMPLS-like 409 forwarding model. The input cell characterizes the flow 410 and indicates the output cell. 412 Timeslot: A basic communication unit in TSCH which allows a 413 transmitter node to send a frame to a receiver neighbor, 414 and that receiver neighbor to optionally send back an 415 acknowledgment. 417 Time Source Neighbor: A neighbor a node uses as its time reference, 418 and to which it needs to keep its clock synchronized. A 419 node can have one or more time source neighbors. 421 Track: A determined sequence of cells along a multi-hop path. 422 It is typically the result of a track reservation. The 423 node that initializes the process for establishing a 424 track is the owner of the track. The latter assigns a 425 unique identifier to the track, called TrackID. 427 TrackID: Unique identifier of a track, assigned by the owner of 428 the track. 430 TSCH: Time Slotted Channel Hopping, a medium access mode of the 431 [IEEE802154e] standard which uses time synchronization to 432 achieve ultra low-power operation and channel hopping to 433 enable high reliability. 435 TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset 436 and a channelOffset. The TSCH schedule contains all the 437 scheduled cells from all slotframes and is sufficient to 438 qualify the communication in the TSCH network. The 439 "width of the matrix is equal to the number of scheduled 440 timeslots in all the concurrent active slotframes. The 441 number of channelOffset values (the "height" of the 442 matrix) is equal to the number of available frequencies. 444 Unscheduled Cell: A cell which is not used by the IEEE802.15.4e TSCH 445 implementation. 447 3. IANA Considerations 449 This specification does not require IANA action. 451 4. Security Considerations 453 This specification is not found to introduce new security threats. 455 5. Acknowledgments 457 Thanks to the IoT6 European Project (STREP) of the 7th Framework 458 Program (Grant 288445). 460 6. References 462 6.1. Normative References 464 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 465 Requirement Levels", BCP 14, RFC 2119, March 1997. 467 [RFC2309] Braden, B., Clark, D., Crowcroft, J., Davie, B., Deering, 468 S., Estrin, D., Floyd, S., Jacobson, V., Minshall, G., 469 Partridge, C., Peterson, L., Ramakrishnan, K., Shenker, 470 S., Wroclawski, J., and L. Zhang, "Recommendations on 471 Queue Management and Congestion Avoidance in the 472 Internet", RFC 2309, April 1998. 474 [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between 475 Information Models and Data Models", RFC 3444, January 476 2003. 478 [RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A. 479 Yegin, "Protocol for Carrying Authentication for Network 480 Access (PANA)", RFC 5191, May 2008. 482 [RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer 483 Security Version 1.2", RFC 6347, January 2012. 485 [RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R., 486 Levis, P., Pister, K., Struik, R., Vasseur, JP., and R. 487 Alexander, "RPL: IPv6 Routing Protocol for Low-Power and 488 Lossy Networks", RFC 6550, March 2012. 490 [RFC6552] Thubert, P., "Objective Function Zero for the Routing 491 Protocol for Low-Power and Lossy Networks (RPL)", RFC 492 6552, March 2012. 494 [RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann, 495 "Neighbor Discovery Optimization for IPv6 over Low-Power 496 Wireless Personal Area Networks (6LoWPANs)", RFC 6775, 497 November 2012. 499 [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained 500 Application Protocol (CoAP)", RFC 7252, June 2014. 502 6.2. Informative References 504 [I-D.chakrabarti-nordmark-6man-efficient-nd] 505 Chakrabarti, S., Nordmark, E., Thubert, P., and M. 506 Wasserman, "IPv6 Neighbor Discovery Optimizations for 507 Wired and Wireless Networks", draft-chakrabarti-nordmark- 508 6man-efficient-nd-07 (work in progress), February 2015. 510 [I-D.ietf-6tisch-tsch] 511 Watteyne, T., Palattella, M., and L. Grieco, "Using 512 IEEE802.15.4e TSCH in an IoT context: Overview, Problem 513 Statement and Goals", draft-ietf-6tisch-tsch-06 (work in 514 progress), March 2015. 516 [I-D.ietf-roll-terminology] 517 Vasseur, J., "Terms used in Routing for Low power And 518 Lossy Networks", draft-ietf-roll-terminology-13 (work in 519 progress), October 2013. 521 [I-D.thubert-6lo-rfc6775-update-reqs] 522 Thubert, P. and P. Stok, "Requirements for an update to 523 6LoWPAN ND", draft-thubert-6lo-rfc6775-update-reqs-06 524 (work in progress), January 2015. 526 [I-D.thubert-roll-forwarding-frags] 527 Thubert, P. and J. Hui, "LLN Fragment Forwarding and 528 Recovery", draft-thubert-roll-forwarding-frags-02 (work in 529 progress), September 2013. 531 [I-D.wang-6tisch-6top-sublayer] 532 Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH 533 Operation Sublayer (6top)", draft-wang-6tisch-6top- 534 sublayer-01 (work in progress), July 2014. 536 6.3. External Informative References 538 [IEEE.802.1AR] 539 IEEE standard for Information Technology, "802.1AR-2009 - 540 IEEE Standard for Local and metropolitan area networks - 541 Secure Device Identity", 2009. 543 [IEEE802154e] 544 IEEE standard for Information Technology, "IEEE std. 545 802.15.4e, Part. 15.4: Low-Rate Wireless Personal Area 546 Networks (LR-WPANs) Amendment 1: MAC sublayer", April 547 2012. 549 Authors' Addresses 551 Maria Rita Palattella (editor) 552 University of Luxembourg 553 Interdisciplinary Centre for Security, Reliability and Trust 554 4, rue Alphonse Weicker 555 Luxembourg L-2721 556 Luxembourg 558 Phone: (+352) 46 66 44 5841 559 Email: maria-rita.palattella@uni.lu 561 Pascal Thubert 562 Cisco Systems, Inc 563 Village d'Entreprises Green Side 564 400, Avenue de Roumanille 565 Batiment T3 566 Biot - Sophia Antipolis 06410 567 France 569 Phone: +33 497 23 26 34 570 Email: pthubert@cisco.com 571 Thomas Watteyne 572 Linear Technology / Dust Networks 573 30695 Huntwood Avenue 574 Hayward, CA 94544 575 USA 577 Phone: +1 (510) 400-2978 578 Email: twatteyne@linear.com 580 Qin Wang 581 Univ. of Sci. and Tech. Beijing 582 30 Xueyuan Road 583 Beijing 100083 584 China 586 Phone: +86 (10) 6233 4781 587 Email: wangqin@ies.ustb.edu.cn