idnits 2.17.1 draft-ietf-6lo-lowpan-mib-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 seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (July 25, 2014) is 3563 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFCXXXX' is mentioned on line 122, but not defined -- Obsolete informational reference (is this intentional?): RFC 2013 (Obsoleted by RFC 4113) == Outdated reference: A later version (-17) exists of draft-ietf-6lo-btle-02 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Schoenwaelder 3 Internet-Draft A. Sehgal 4 Intended status: Standards Track Jacobs University 5 Expires: January 26, 2015 T. Tsou 6 Huawei Technologies (USA) 7 C. Zhou 8 Huawei Technologies 9 July 25, 2014 11 Definition of Managed Objects for IPv6 over Low-Power Wireless Personal 12 Area Networks (6LoWPANs) 13 draft-ietf-6lo-lowpan-mib-02 15 Abstract 17 This memo defines a portion of the Management Information Base (MIB) 18 for use with network management protocols in the Internet community. 19 In particular, it defines objects for managing IPv6 over Low-Power 20 Wireless Personal Area Networks (6LoWPANs). 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on January 26, 2015. 39 Copyright Notice 41 Copyright (c) 2014 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. The Internet-Standard Management Framework . . . . . . . . . 2 58 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 61 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 62 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 63 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 64 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 65 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 66 10.1. Normative References . . . . . . . . . . . . . . . . . . 25 67 10.2. Informative References . . . . . . . . . . . . . . . . . 25 69 1. Introduction 71 This memo defines a portion of the Management Information Base (MIB) 72 for use with network management protocols. In particular it defines 73 objects for managing IPv6 over Low-Power Wireless Personal Area 74 Networks (6LoWPANs) [RFC4944]. 76 While a MIB module provides a direct binding for accessing data via 77 the Simple Network Management Protocol (SNMP) [RFC3410], supporting 78 SNMP may not always be affordable on constrained devices. Other 79 protocols to access data modeled in MIB modules are possible and 80 proposals have been made recently to provide bindings to the 81 Constrained Application Protocol (CoAP) [RFC7252]. 83 2. The Internet-Standard Management Framework 85 For a detailed overview of the documents that describe the current 86 Internet-Standard Management Framework, please refer to section 7 of 87 RFC 3410 [RFC3410]. 89 Managed objects are accessed via a virtual information store, termed 90 the Management Information Base or MIB. MIB objects are generally 91 accessed through the Simple Network Management Protocol (SNMP). 92 Objects in the MIB are defined using the mechanisms defined in the 93 Structure of Management Information (SMI). This memo specifies a MIB 94 module that is compliant to the SMIv2, which is described in STD 58, 95 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 96 [RFC2580]. 98 3. Conventions 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC 2119 [RFC2119]. 104 4. Overview 106 The left part of Figure 1 provides an overview of the protocols 107 typically used on constrained devices. The right part lists the MIB 108 modules providing monitoring and troubleshooting support ([RFC2013], 109 [RFC4292], [RFC4293], [RFC2863]). The LOWPAN-MIB defined in this 110 document fills a hole by providing monitoring and troubleshooting 111 support for the 6LoWPAN layer. 113 Protocol Layer MIB Modules 114 +---------------+ 115 | CoAP | 116 +---------------+ +--------------------------+ 117 | UDP | | UDP-MIB [RFC2013] | 118 +---------------+ +--------------------------+ 119 | IPv6 | | IP-MIB [RFC4293] | 120 | ICMPv6 | | IP-FORWARD-MIB [RFC4292] | 121 +---------------+ +--------------------------+ 122 | 6LoWPAN | | LOWPAN-MIB [RFCXXXX] | 123 +---------------+ +--------------------------+ 124 | IF-MIB [RFC2863] | 125 +---------------+ +--------------------------+ 126 | IEEE 802.15.4 | 127 +---------------+ 129 Figure 1: Protocol Layers and MIB Modules 131 The LOWPAN-MIB module is primarily a collection of counters that 132 reflect how 6LoWPAN datagrams are processed by the 6LoWPAN layer. 133 The objects are defined twice, once to report the global statistics 134 as seen by the 6LoWPAN layer and once to report per interface 6LoWPAN 135 layer statistics. The per interface statistics are optional to 136 implement. The object identifier registration tree has the following 137 structure: 139 ---- lowpanMIB(1.3.6.1.2.1.XXXX) 140 +---- lowpanNotifications(0) 141 +---- lowpanObjects(1) 142 | +---- lowpanStats(1) 143 | | +--r- lowpanReasmTimeout(1) Unsigned32 144 | | +--r- lowpanInReceives(2) Counter32 145 | | +--r- lowpanInHdrErrors(3) Counter32 146 | | +--r- lowpanInMeshReceives(4) Counter32 147 | | +--r- lowpanInMeshForwds(5) Counter32 148 | | +--r- lowpanInMeshDelivers(6) Counter32 149 | | +--r- lowpanInReasmReqds(7) Counter32 150 | | +--r- lowpanInReasmFails(8) Counter32 151 | | +--r- lowpanInReasmOKs(9) Counter32 152 | | +--r- lowpanInCompReqds(10) Counter32 153 | | +--r- lowpanInCompFails(11) Counter32 154 | | +--r- lowpanInCompOKs(12) Counter32 155 | | +--r- lowpanInDiscards(13) Counter32 156 | | +--r- lowpanInDelivers(14) Counter32 157 | | +--r- lowpanOutRequests(15) Counter32 158 | | +--r- lowpanOutCompReqds(16) Counter32 159 | | +--r- lowpanOutCompFails(17) Counter32 160 | | +--r- lowpanOutCompOKs(18) Counter32 161 | | +--r- lowpanOutFragReqds(19) Counter32 162 | | +--r- lowpanOutFragFails(20) Counter32 163 | | +--r- lowpanOutFragOKs(21) Counter32 164 | | +--r- lowpanOutFragCreates(22) Counter32 165 | | +--r- lowpanOutMeshHopLimitExceeds(23) Counter32 166 | | +--r- lowpanOutMeshNoRoutes(24) Counter32 167 | | +--r- lowpanOutMeshRequests(25) Counter32 168 | | +--r- lowpanOutMeshForwds(26) Counter32 169 | | +--r- lowpanOutMeshTransmits(27) Counter32 170 | | +--r- lowpanOutDiscards(28) Counter32 171 | | +--r- lowpanOutTransmits(29) Counter32 172 | +---- lowpanIfStatsTable(2) 173 | +---- lowpanIfStatsEntry(1) [ifIndex] 174 | +--r- lowpanIfReasmTimeout(1) Unsigned32 175 | +--r- lowpanIfInReceives(2) Counter32 176 | +--r- lowpanIfInHdrErrors(3) Counter32 177 | +--r- lowpanIfInMeshReceives(4) Counter32 178 | +--r- lowpanIfInMeshForwds(5) Counter32 179 | +--r- lowpanIfInMeshDelivers(6) Counter32 180 | +--r- lowpanIfInReasmReqds(7) Counter32 181 | +--r- lowpanIfInReasmFails(8) Counter32 182 | +--r- lowpanIfInReasmOKs(9) Counter32 183 | +--r- lowpanIfInCompReqds(10) Counter32 184 | +--r- lowpanIfInCompFails(11) Counter32 185 | +--r- lowpanIfInCompOKs(12) Counter32 186 | +--r- lowpanIfInDiscards(13) Counter32 187 | +--r- lowpanIfInDelivers(14) Counter32 188 | +--r- lowpanIfOutRequests(15) Counter32 189 | +--r- lowpanIfOutCompReqds(16) Counter32 190 | +--r- lowpanIfOutCompFails(17) Counter32 191 | +--r- lowpanIfOutCompOKs(18) Counter32 192 | +--r- lowpanIfOutFragReqds(19) Counter32 193 | +--r- lowpanIfOutFragFails(20) Counter32 194 | +--r- lowpanIfOutFragOKs(21) Counter32 195 | +--r- lowpanIfOutFragCreates(22) Counter32 196 | +--r- lowpanIfOutMeshHopLimitExceeds(23) Counter32 197 | +--r- lowpanIfOutMeshNoRoutes(24) Counter32 198 | +--r- lowpanIfOutMeshRequests(25) Counter32 199 | +--r- lowpanIfOutMeshForwds(26) Counter32 200 | +--r- lowpanIfOutMeshTransmits(27) Counter32 201 | +--r- lowpanIfOutDiscards(28) Counter32 202 | +--r- lowpanIfOutTransmits(29) Counter32 203 +---- lowpanConformance(2) 204 +---- lowpanGroups(1) 205 | +---- lowpanStatsGroup(1) 206 | +---- lowpanStatsMeshGroup(2) 207 | +---- lowpanIfStatsGroup(3) 208 | +---- lowpanIfStatsMeshGroup(4) 209 +---- lowpanCompliances(2) 210 +---- lowpanCompliance(1) 212 The counters defined in the LOWPAN-MIB module provide information 213 about the 6LoWPAN datagrams received and transmitted and how they are 214 processed in the 6LoWPAN layer. For link-layers that use the 6LoWPAN 215 dispatch byte as defined in [RFC4944] (e.g., IEEE 802.15.4), a 216 6LoWPAN datagram is a datagram with a dispatch byte matching the bit 217 patterns 01xxxxxx, 10xxxxxx, or 11xxxxxx. Datagrams with a dispatch 218 byte matching the bit pattern 00xxxxxx (NALP - not a LoWPAN frame) 219 are not considered to be 6LoWPAN datagram by this specification. 220 Other radio technologies may use different mechanisms to identify 221 6LoWPAN datagrams (e.g., the BLUETOOTH Low Energy Logical Link 222 Control and Adaptation Protocol uses Channel Identifiers 223 [I-D.ietf-6lo-btle]). 225 Figure 2 illustrates the conceptual relationships between the 226 counters. Implementations may choose to implement the processing of 227 6LoWPAN datagrams in a different order. 229 The generic InDiscards and OutDiscards counters can be incremented 230 anytime when 6LoWPAN datagrams are discarded due to reasons not 231 covered by the other more specific counters. For example, an 232 implementation discarding 6LoWPAN datagrams while all buffers are 233 used for ongoing packet reassemblies will increment the relevant 234 InDiscards counters for each discarded 6LoWPAN datagram. 236 IPv6 layer 237 ^ v 238 InDelivers -+- -+- OutRequests 239 | | 240 InDiscards <--+ | 241 | | 242 InCompOKs .-->| |-->. OutCompReqds 243 InCompFails <--| | | +--> OutCompFails 244 InCompReqds `<--+ +<--' OutCompOKs 245 | | 246 | +-->. OutFragReqds 247 InReasmOKs .-->| | +--> OutFragFails 248 InReasmFails <--| | | -+- OutFragOKs 249 InReasmReqds `<--+ +<--' OutFragCreates 250 | | 251 | | 252 InMeshDelivers |<--. | 253 InMeshForwds | |-->. | 254 InMeshReceives +-->' | | 255 | +--> | OutMeshHopLimitExceeds 256 | +--> | OutMeshNoRoutes 257 | | | 258 | | .<--+ OutMeshRequests 259 | `-->| | OutMeshForwds 260 | `-->| OutMeshTransmits 261 | | 262 InHdrErrors <--+ +--> OutDiscards 263 | | 264 InReceives -+- -+- OutTransmits 265 ^ v 266 interface layer 268 Figure 2: Conceptual Relationship between LOWPAN-MIB Counters 270 The fragmentation related counters have been modeled after the 271 fragmentation related counters of the IP-MIB [RFC4293]. The discard 272 counters have been placed at the end of the input and output chains 273 but they can be bumped any time if a datagram is discarded for a 274 reason not covered by the other counters. 276 The compression related counters provide insights into compression 277 requests and in particular also compression related failures. Note 278 that the diagram is conceptual in the sense that compression happens 279 after reassembly for incoming 6LoWPAN datagrams and compression 280 happens before fragmentation for outgoing 6LoWPAN datagrams. 281 Implementations may choose to implement things slightly differently. 282 For example, implementations may decompress FRAG1 fragments as soon 283 as they are received, not waiting for reassembly to complete. 285 The mesh header processing related counters do not have an explicit 286 discard counter. Implementations that do not support mesh forwarding 287 MUST count the number of received 6LoWPAN datagrams with a MESH 288 header (lowpanInMeshReceives) but they MUST NOT increment the 289 lowpanInMeshReceives and lowpanInMeshDelivers counters if these 290 6LoWPAN datagrams are dropped. 292 5. Relationship to Other MIB Modules 294 The MIB module IMPORTS definitions from SNMPv2-SMI [RFC2578], 295 SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863]. 297 6. Definitions 299 LOWPAN-MIB DEFINITIONS ::= BEGIN 301 IMPORTS 302 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2 303 FROM SNMPv2-SMI -- RFC 2578 304 OBJECT-GROUP, MODULE-COMPLIANCE 305 FROM SNMPv2-CONF -- RFC 2580 306 ifIndex FROM IF-MIB; -- RFC 2863 308 lowpanMIB MODULE-IDENTITY 309 LAST-UPDATED "201407250000Z" 310 ORGANIZATION 311 "Jacobs University Bremen" 312 CONTACT-INFO 313 "Juergen Schoenwaelder 314 Jacobs University Bremen 315 Email: j.schoenwaelder@jacobs-university.de 317 Anuj Sehgal 318 Jacobs University Bremen 319 Email: s.anuj@jacobs-university.de 321 Tina Tsou 322 Huawei Technologies 323 Email: tina.tsou.zouting@huawei.com 325 Cathy Zhou 326 Huawei Technologies 327 Email: cathyzhou@huawei.com" 328 DESCRIPTION 329 "The MIB module for monitoring nodes implementing the IPv6 330 over Low-Power Wireless Personal Area Networks (6LoWPAN) 331 protocol. 333 Copyright (c) 2014 IETF Trust and the persons identified as 334 authors of the code. All rights reserved. 336 Redistribution and use in source and binary forms, with or 337 without modification, is permitted pursuant to, and subject 338 to the license terms contained in, the Simplified BSD 339 License set forth in Section 4.c of the IETF Trust's 340 Legal Provisions Relating to IETF Documents 341 (http://trustee.ietf.org/license-info)." 343 REVISION "201407250000Z" 344 DESCRIPTION 345 "Initial version, published as RFC XXXX." 346 -- RFC Ed.: replace XXXX with RFC number and remove this note 348 ::= { mib-2 XXXX } 350 -- object definitions 352 lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 } 353 lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 } 354 lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 } 356 lowpanStats OBJECT IDENTIFIER ::= { lowpanObjects 1 } 358 lowpanReasmTimeout OBJECT-TYPE 359 SYNTAX Unsigned32 360 UNITS "seconds" 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The maximum number of seconds that received fragments are 365 held while they are awaiting reassembly at this entity." 366 ::= { lowpanStats 1 } 368 lowpanInReceives OBJECT-TYPE 369 SYNTAX Counter32 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The total number of 6LoWPAN datagrams received, including 374 those received in error." 375 ::= { lowpanStats 2 } 377 lowpanInHdrErrors OBJECT-TYPE 378 SYNTAX Counter32 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The number of received 6LoWPAN datagrams discarded due to 383 errors in their headers, including unknown dispatch values." 384 ::= { lowpanStats 3 } 386 lowpanInMeshReceives OBJECT-TYPE 387 SYNTAX Counter32 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "The number of received 6LoWPAN datagrams with a MESH 392 header." 393 ::= { lowpanStats 4 } 395 lowpanInMeshForwds OBJECT-TYPE 396 SYNTAX Counter32 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The number of received 6LoWPAN datagrams requiring MESH 401 forwarding." 402 ::= { lowpanStats 5 } 404 lowpanInMeshDelivers OBJECT-TYPE 405 SYNTAX Counter32 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "The number of received 6LoWPAN datagrams with a MESH header 410 delivered to the local system." 411 ::= { lowpanStats 6 } 413 lowpanInReasmReqds OBJECT-TYPE 414 SYNTAX Counter32 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION 418 "The number of received 6LoWPAN fragments that needed to 419 be reassembled. This includes both FRAG1 and FRAGN 6LoWPAN 420 datagrams." 421 ::= { lowpanStats 7 } 423 lowpanInReasmFails OBJECT-TYPE 424 SYNTAX Counter32 425 MAX-ACCESS read-only 426 STATUS current 427 DESCRIPTION 428 "The number of failures detected by the re-assembly 429 algorithm (e.g., timeouts). Note that this is not 430 necessarily a count of discarded 6LoWPAN fragments 431 since implementations can lose track of the number 432 of fragments by combining them as received." 433 ::= { lowpanStats 8 } 435 lowpanInReasmOKs OBJECT-TYPE 436 SYNTAX Counter32 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "The number of IPv6 packets successfully reassembled." 441 ::= { lowpanStats 9 } 443 lowpanInCompReqds OBJECT-TYPE 444 SYNTAX Counter32 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "The number of 6LoWPAN datagrams requiring header 449 decompression." 450 ::= { lowpanStats 10 } 452 lowpanInCompFails OBJECT-TYPE 453 SYNTAX Counter32 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "The number of 6LoWPAN datagrams where header decompression 458 failed (e.g., because the necessary context information was 459 not available)." 460 ::= { lowpanStats 11 } 462 lowpanInCompOKs OBJECT-TYPE 463 SYNTAX Counter32 464 MAX-ACCESS read-only 465 STATUS current 466 DESCRIPTION 467 "The number of 6LoWPAN datagrams where header decompression 468 was successful." 469 ::= { lowpanStats 12 } 471 lowpanInDiscards OBJECT-TYPE 472 SYNTAX Counter32 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The number of received 6LoWPAN datagrams for which no 477 problems were encountered to prevent their continued 478 processing, but were discarded (e.g., for lack of buffer 479 space). Note that this counter does not include any 480 datagrams discarded due to a reassembly failure or a 481 compression failure." 482 ::= { lowpanStats 13 } 484 lowpanInDelivers OBJECT-TYPE 485 SYNTAX Counter32 486 MAX-ACCESS read-only 487 STATUS current 488 DESCRIPTION 489 "The total number of IPv6 packets successfully delivered 490 to the IPv6 layer." 491 ::= { lowpanStats 14 } 493 lowpanOutRequests OBJECT-TYPE 494 SYNTAX Counter32 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "The total number of IPv6 packets supplied by the IPv6 499 layer." 500 ::= { lowpanStats 15 } 502 lowpanOutCompReqds OBJECT-TYPE 503 SYNTAX Counter32 504 MAX-ACCESS read-only 505 STATUS current 506 DESCRIPTION 507 "The total number of IPv6 packets for which header 508 compression was attempted." 509 ::= { lowpanStats 16 } 511 lowpanOutCompFails OBJECT-TYPE 512 SYNTAX Counter32 513 MAX-ACCESS read-only 514 STATUS current 515 DESCRIPTION 516 "The total number of IPv6 packets for which header 517 compression failed." 518 ::= { lowpanStats 17 } 520 lowpanOutCompOKs OBJECT-TYPE 521 SYNTAX Counter32 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "The total number of IPv6 packets for which header 526 compression was successful." 527 ::= { lowpanStats 18 } 529 lowpanOutFragReqds OBJECT-TYPE 530 SYNTAX Counter32 531 MAX-ACCESS read-only 532 STATUS current 533 DESCRIPTION 534 "The number of IPv6 packets that required fragmentation 535 in order to be transmitted." 536 ::= { lowpanStats 19 } 538 lowpanOutFragFails OBJECT-TYPE 539 SYNTAX Counter32 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "The number of IPv6 packets that have been discarded because 544 fragmentation failed." 545 ::= { lowpanStats 20 } 547 lowpanOutFragOKs OBJECT-TYPE 548 SYNTAX Counter32 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "The number of IPv6 packets that have been successfully 553 fragmented." 554 ::= { lowpanStats 21 } 556 lowpanOutFragCreates OBJECT-TYPE 557 SYNTAX Counter32 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "The number of 6LoWPAN fragments that have been 562 generated as a result of fragmentation. This includes 563 both FRAG1 and FRAGN 6LoWPAN datagrams." 564 ::= { lowpanStats 22 } 566 lowpanOutMeshHopLimitExceeds OBJECT-TYPE 567 SYNTAX Counter32 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "The number of 6LoWPAN datagrams with a MESH header that 572 were dropped because the hop limit has been exceeded." 574 ::= { lowpanStats 23 } 576 lowpanOutMeshNoRoutes OBJECT-TYPE 577 SYNTAX Counter32 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "The number of 6LoWPAN datagrams with a MESH header that 582 were dropped because there was no forwarding information 583 available." 584 ::= { lowpanStats 24 } 586 lowpanOutMeshRequests OBJECT-TYPE 587 SYNTAX Counter32 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "The number of 6LoWPAN datagrams requiring MESH header 592 encapsulation." 593 ::= { lowpanStats 25 } 595 lowpanOutMeshForwds OBJECT-TYPE 596 SYNTAX Counter32 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "The number of 6LoWPAN datagrams with a MESH header for 601 which suitable forwarding information was available." 602 ::= { lowpanStats 26 } 604 lowpanOutMeshTransmits OBJECT-TYPE 605 SYNTAX Counter32 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "The number of 6LoWPAN datagrams with a MESH header 610 created." 611 ::= { lowpanStats 27 } 613 lowpanOutDiscards OBJECT-TYPE 614 SYNTAX Counter32 615 MAX-ACCESS read-only 616 STATUS current 617 DESCRIPTION 618 "The number of IPv6 packets for which no problem was 619 encountered to prevent their transmission to their 620 destination, but were discarded (e.g., for lack of 621 buffer space)." 623 ::= { lowpanStats 28 } 625 lowpanOutTransmits OBJECT-TYPE 626 SYNTAX Counter32 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "The total number of 6LoWPAN datagram that this entity 631 supplied to the lower layers for transmission." 632 ::= { lowpanStats 29 } 634 lowpanIfStatsTable OBJECT-TYPE 635 SYNTAX SEQUENCE OF LowpanIfStatsEntry 636 MAX-ACCESS not-accessible 637 STATUS current 638 DESCRIPTION 639 "A table providing per interface statistics." 640 ::= { lowpanObjects 2 } 642 lowpanIfStatsEntry OBJECT-TYPE 643 SYNTAX LowpanIfStatsEntry 644 MAX-ACCESS not-accessible 645 STATUS current 646 DESCRIPTION 647 "An entry providing statistics for a specific interface." 648 INDEX { ifIndex } 649 ::= { lowpanIfStatsTable 1 } 651 LowpanIfStatsEntry ::= SEQUENCE { 652 lowpanIfReasmTimeout Unsigned32, 653 lowpanIfInReceives Counter32, 654 lowpanIfInHdrErrors Counter32, 655 lowpanIfInMeshReceives Counter32, 656 lowpanIfInMeshForwds Counter32, 657 lowpanIfInMeshDelivers Counter32, 658 lowpanIfInReasmReqds Counter32, 659 lowpanIfInReasmFails Counter32, 660 lowpanIfInReasmOKs Counter32, 661 lowpanIfInCompReqds Counter32, 662 lowpanIfInCompFails Counter32, 663 lowpanIfInCompOKs Counter32, 664 lowpanIfInDiscards Counter32, 665 lowpanIfInDelivers Counter32, 666 lowpanIfOutRequests Counter32, 667 lowpanIfOutCompReqds Counter32, 668 lowpanIfOutCompFails Counter32, 669 lowpanIfOutCompOKs Counter32, 670 lowpanIfOutFragReqds Counter32, 671 lowpanIfOutFragFails Counter32, 672 lowpanIfOutFragOKs Counter32, 673 lowpanIfOutFragCreates Counter32, 674 lowpanIfOutMeshHopLimitExceeds Counter32, 675 lowpanIfOutMeshNoRoutes Counter32, 676 lowpanIfOutMeshRequests Counter32, 677 lowpanIfOutMeshForwds Counter32, 678 lowpanIfOutMeshTransmits Counter32, 679 lowpanIfOutDiscards Counter32, 680 lowpanIfOutTransmits Counter32 681 } 683 lowpanIfReasmTimeout OBJECT-TYPE 684 SYNTAX Unsigned32 685 UNITS "seconds" 686 MAX-ACCESS read-only 687 STATUS current 688 DESCRIPTION 689 "The maximum number of seconds that received fragments are 690 held while they are awaiting reassembly at this interface." 691 ::= { lowpanIfStatsEntry 1 } 693 lowpanIfInReceives OBJECT-TYPE 694 SYNTAX Counter32 695 MAX-ACCESS read-only 696 STATUS current 697 DESCRIPTION 698 "The total number of 6LoWPAN datagrams received on this 699 interface, including those received in error." 700 ::= { lowpanIfStatsEntry 2 } 702 lowpanIfInHdrErrors OBJECT-TYPE 703 SYNTAX Counter32 704 MAX-ACCESS read-only 705 STATUS current 706 DESCRIPTION 707 "The number of 6LoWPAN datagrams received on this 708 interface that were discarded due to errors in 709 their headers, including unknown dispatch values." 710 ::= { lowpanIfStatsEntry 3 } 712 lowpanIfInMeshReceives OBJECT-TYPE 713 SYNTAX Counter32 714 MAX-ACCESS read-only 715 STATUS current 716 DESCRIPTION 717 "The number of 6LoWPAN datagrams reveived on this 718 interface with a MESH header." 720 ::= { lowpanIfStatsEntry 4 } 722 lowpanIfInMeshForwds OBJECT-TYPE 723 SYNTAX Counter32 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "The number of 6LoWPAN datagrams received on this 728 interface requiring MESH forwarding." 729 ::= { lowpanIfStatsEntry 5 } 731 lowpanIfInMeshDelivers OBJECT-TYPE 732 SYNTAX Counter32 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "The number of 6LoWPAN datagrams received on this 737 interface with a MESH header delivered to the local 738 system." 739 ::= { lowpanIfStatsEntry 6 } 741 lowpanIfInReasmReqds OBJECT-TYPE 742 SYNTAX Counter32 743 MAX-ACCESS read-only 744 STATUS current 745 DESCRIPTION 746 "The number of 6LoWPAN fragments received on this 747 interface that needed to be reassembled. This 748 includes both FRAG1 and FRAGN 6LoWPAN datagrams." 749 ::= { lowpanIfStatsEntry 7 } 751 lowpanIfInReasmFails OBJECT-TYPE 752 SYNTAX Counter32 753 MAX-ACCESS read-only 754 STATUS current 755 DESCRIPTION 756 "The number of failures detected by the re-assembly 757 algorithm (e.g., timeouts) for datagrams received 758 on this interface. Note that this is not necessarily 759 a count of discarded 6LoWPAN fragments since 760 implementations can lose track of the number 761 of fragments by combining them as received." 762 ::= { lowpanIfStatsEntry 8 } 764 lowpanIfInReasmOKs OBJECT-TYPE 765 SYNTAX Counter32 766 MAX-ACCESS read-only 767 STATUS current 768 DESCRIPTION 769 "The number of IPv6 packets successfully reassembled 770 from fragments received on this interface." 771 ::= { lowpanIfStatsEntry 9 } 773 lowpanIfInCompReqds OBJECT-TYPE 774 SYNTAX Counter32 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "The number of 6LoWPAN datagrams received on this 779 interface requiring header decompression." 780 ::= { lowpanIfStatsEntry 10 } 782 lowpanIfInCompFails OBJECT-TYPE 783 SYNTAX Counter32 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "The number of 6LoWPAN datagrams received on this 788 interface where header decompression failed (e.g., 789 because the necessary context information was 790 not available)." 791 ::= { lowpanIfStatsEntry 11 } 793 lowpanIfInCompOKs OBJECT-TYPE 794 SYNTAX Counter32 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "The number of 6LoWPAN datagrams received on this 799 interface where header decompression was successful." 800 ::= { lowpanIfStatsEntry 12 } 802 lowpanIfInDiscards OBJECT-TYPE 803 SYNTAX Counter32 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "The number of 6LoWPAN datagrams received on this 808 interface for which no problems were encountered to 809 prevent their continued processing, but were discarded 810 (e.g., for lack of buffer space). Note that this 811 counter does not include any datagrams discarded due 812 to a reassembly failure or a compression failure." 813 ::= { lowpanIfStatsEntry 13 } 815 lowpanIfInDelivers OBJECT-TYPE 816 SYNTAX Counter32 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "The total number of IPv6 packets received on this 821 interface that were successfully delivered to the 822 IPv6 layer." 823 ::= { lowpanIfStatsEntry 14 } 825 lowpanIfOutRequests OBJECT-TYPE 826 SYNTAX Counter32 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "The total number of IPv6 packets supplied by the IPv6 831 layer to be sent over this interface." 832 ::= { lowpanIfStatsEntry 15 } 834 lowpanIfOutCompReqds OBJECT-TYPE 835 SYNTAX Counter32 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The total number of IPv6 packets to be sent over 840 this interface for which header compression was 841 attempted." 842 ::= { lowpanIfStatsEntry 16 } 844 lowpanIfOutCompFails OBJECT-TYPE 845 SYNTAX Counter32 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "The total number of IPv6 packets to be sent over 850 this interface for which header compression failed." 851 ::= { lowpanIfStatsEntry 17 } 853 lowpanIfOutCompOKs OBJECT-TYPE 854 SYNTAX Counter32 855 MAX-ACCESS read-only 856 STATUS current 857 DESCRIPTION 858 "The total number of IPv6 packets to be sent over 859 this interface for which header compression was 860 successful." 861 ::= { lowpanIfStatsEntry 18 } 863 lowpanIfOutFragReqds OBJECT-TYPE 864 SYNTAX Counter32 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "The number of IPv6 packets to be sent over this 869 interface that required fragmentation in order 870 to be transmitted." 871 ::= { lowpanIfStatsEntry 19 } 873 lowpanIfOutFragFails OBJECT-TYPE 874 SYNTAX Counter32 875 MAX-ACCESS read-only 876 STATUS current 877 DESCRIPTION 878 "The number of IPv6 packets to be sent over this 879 interface that have been discarded because 880 fragmentation failed." 881 ::= { lowpanIfStatsEntry 20 } 883 lowpanIfOutFragOKs OBJECT-TYPE 884 SYNTAX Counter32 885 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 888 "The number of IPv6 packets to be sent over this 889 interface that have been successfully fragmented." 890 ::= { lowpanIfStatsEntry 21 } 892 lowpanIfOutFragCreates OBJECT-TYPE 893 SYNTAX Counter32 894 MAX-ACCESS read-only 895 STATUS current 896 DESCRIPTION 897 "The number of 6LoWPAN fragments that have been 898 generated on this interface as a result of 899 fragmentation. This includes both FRAG1 and FRAGN 900 6LoWPAN datagrams." 901 ::= { lowpanIfStatsEntry 22 } 903 lowpanIfOutMeshHopLimitExceeds OBJECT-TYPE 904 SYNTAX Counter32 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "The number of 6LoWPAN datagrams to be sent on this 909 interface with a MESH header that were dropped 910 because the hop limit has been exceeded." 911 ::= { lowpanIfStatsEntry 23 } 913 lowpanIfOutMeshNoRoutes OBJECT-TYPE 914 SYNTAX Counter32 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "The number of 6LoWPAN datagrams to be sent on this 919 interface with a MESH header that were dropped 920 because there was no forwarding information available." 921 ::= { lowpanIfStatsEntry 24 } 923 lowpanIfOutMeshRequests OBJECT-TYPE 924 SYNTAX Counter32 925 MAX-ACCESS read-only 926 STATUS current 927 DESCRIPTION 928 "The number of 6LoWPAN datagrams to be sent on this 929 interface requiring MESH header encapsulation." 930 ::= { lowpanIfStatsEntry 25 } 932 lowpanIfOutMeshForwds OBJECT-TYPE 933 SYNTAX Counter32 934 MAX-ACCESS read-only 935 STATUS current 936 DESCRIPTION 937 "The number of 6LoWPAN datagrams to be sent on this 938 interface with a MESH header for which suitable 939 forwarding information was available." 940 ::= { lowpanIfStatsEntry 26 } 942 lowpanIfOutMeshTransmits OBJECT-TYPE 943 SYNTAX Counter32 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION 947 "The number of 6LoWPAN datagrams to be send on this 948 interface with a MESH header created." 949 ::= { lowpanIfStatsEntry 27 } 951 lowpanIfOutDiscards OBJECT-TYPE 952 SYNTAX Counter32 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "The number of IPv6 packets to be sent over this 957 interface for which no problem was encountered to 958 prevent their transmission to their destination, but 959 were discarded (e.g., for lack of buffer space)." 960 ::= { lowpanIfStatsEntry 28 } 962 lowpanIfOutTransmits OBJECT-TYPE 963 SYNTAX Counter32 964 MAX-ACCESS read-only 965 STATUS current 966 DESCRIPTION 967 "The total number of 6LoWPAN datagrams to be sent on 968 this interface that this entity supplied to the lower 969 layers for transmission." 970 ::= { lowpanIfStatsEntry 29 } 972 -- conformance definitions 974 lowpanGroups OBJECT IDENTIFIER ::= { lowpanConformance 1 } 975 lowpanCompliances OBJECT IDENTIFIER ::= { lowpanConformance 2 } 977 lowpanCompliance MODULE-COMPLIANCE 978 STATUS current 979 DESCRIPTION 980 "Compliance statement for systems that implement 6LoWPAN." 981 MODULE -- this module 982 MANDATORY-GROUPS { 983 lowpanStatsGroup 984 } 985 GROUP lowpanStatsMeshGroup 986 DESCRIPTION 987 "This group is mandatory for implementations that process 988 or forward 6LoWPAN datagrams with mesh headers." 989 GROUP lowpanIfStatsGroup 990 DESCRIPTION 991 "This group is mandatory for implementations that expose 992 per interface statistics." 993 GROUP lowpanIfStatsMeshGroup 994 DESCRIPTION 995 "This group is mandatory for implementations that expose 996 per interface statistics and that process or forward 997 6LoWPAN datagrams with mesh headers." 998 ::= { lowpanCompliances 1 } 1000 lowpanStatsGroup OBJECT-GROUP 1001 OBJECTS { 1002 lowpanReasmTimeout, 1003 lowpanInReceives, 1004 lowpanInHdrErrors, 1005 lowpanInMeshReceives, 1006 lowpanInReasmReqds, 1007 lowpanInReasmFails, 1008 lowpanInReasmOKs, 1009 lowpanInCompReqds, 1010 lowpanInCompFails, 1011 lowpanInCompOKs, 1012 lowpanInDiscards, 1013 lowpanInDelivers, 1014 lowpanOutRequests, 1015 lowpanOutCompReqds, 1016 lowpanOutCompFails, 1017 lowpanOutCompOKs, 1018 lowpanOutFragReqds, 1019 lowpanOutFragFails, 1020 lowpanOutFragOKs, 1021 lowpanOutFragCreates, 1022 lowpanOutDiscards, 1023 lowpanOutTransmits 1024 } 1025 STATUS current 1026 DESCRIPTION 1027 "A collection of objects providing information and 1028 statistics about the processing of 6LoWPAN datagrams, 1029 excluding counters covering the processing of datagrams 1030 with a mesh headers." 1031 ::= { lowpanGroups 1 } 1033 lowpanStatsMeshGroup OBJECT-GROUP 1034 OBJECTS { 1035 lowpanInMeshForwds, 1036 lowpanInMeshDelivers, 1037 lowpanOutMeshHopLimitExceeds, 1038 lowpanOutMeshNoRoutes, 1039 lowpanOutMeshRequests, 1040 lowpanOutMeshForwds, 1041 lowpanOutMeshTransmits 1042 } 1043 STATUS current 1044 DESCRIPTION 1045 "A collection of objects providing information and 1046 statistics about the processing of 6LoWPAN datagrams 1047 with a 6LoWPAN mesh header." 1048 ::= { lowpanGroups 2 } 1050 lowpanIfStatsGroup OBJECT-GROUP 1051 OBJECTS { 1052 lowpanIfReasmTimeout, 1053 lowpanIfInReceives, 1054 lowpanIfInHdrErrors, 1055 lowpanIfInMeshReceives, 1056 lowpanIfInReasmReqds, 1057 lowpanIfInReasmFails, 1058 lowpanIfInReasmOKs, 1059 lowpanIfInCompReqds, 1060 lowpanIfInCompFails, 1061 lowpanIfInCompOKs, 1062 lowpanIfInDiscards, 1063 lowpanIfInDelivers, 1064 lowpanIfOutRequests, 1065 lowpanIfOutCompReqds, 1066 lowpanIfOutCompFails, 1067 lowpanIfOutCompOKs, 1068 lowpanIfOutFragReqds, 1069 lowpanIfOutFragFails, 1070 lowpanIfOutFragOKs, 1071 lowpanIfOutFragCreates, 1072 lowpanIfOutDiscards, 1073 lowpanIfOutTransmits 1074 } 1075 STATUS current 1076 DESCRIPTION 1077 "A collection of objects providing per interface 1078 information and statistics about the processing 1079 of 6LoWPAN datagrams, excluding counters covering 1080 the processing of datagrams with a mesh headers." 1081 ::= { lowpanGroups 3 } 1083 lowpanIfStatsMeshGroup OBJECT-GROUP 1084 OBJECTS { 1085 lowpanIfInMeshForwds, 1086 lowpanIfInMeshDelivers, 1087 lowpanIfOutMeshHopLimitExceeds, 1088 lowpanIfOutMeshNoRoutes, 1089 lowpanIfOutMeshRequests, 1090 lowpanIfOutMeshForwds, 1091 lowpanIfOutMeshTransmits 1092 } 1093 STATUS current 1094 DESCRIPTION 1095 "A collection of objects providing per interface 1096 information and statistics about the processing 1097 of 6LoWPAN datagrams with a 6LoWPAN mesh header." 1098 ::= { lowpanGroups 4 } 1100 END 1102 7. Security Considerations 1104 Some of the readable objects in this MIB module (i.e., objects with a 1105 MAX-ACCESS other than not-accessible) may be considered sensitive or 1106 vulnerable in some network environments. It is thus important to 1107 control even GET and/or NOTIFY access to these objects and possibly 1108 to even encrypt the values of these objects when sending them over 1109 the network via SNMP. These are the tables and objects and their 1110 sensitivity/vulnerability: 1112 The read-only counters provide insights into the amount of 6LoWPAN 1113 traffic a node is receiving or transmitting. This might provide 1114 information whether a device is regularly exchanging information with 1115 other devices or whether a device is mostly not participating in any 1116 communication (e.g., the device might be "easier" to take away 1117 unnoticed). The reassembly counters could be used to direct denial 1118 of service attacks on the reassembly mechanism. 1120 SNMP versions prior to SNMPv3 did not include adequate security. 1121 Even if the network itself is secure (for example by using IPsec), 1122 even then, there is no control as to who on the secure network is 1123 allowed to access and GET/SET (read/change/create/delete) the objects 1124 in this MIB module. 1126 It is RECOMMENDED that implementers consider the security features as 1127 provided by the SNMPv3 framework (see [RFC3410], section 8), 1128 including full support for the SNMPv3 cryptographic mechanisms (for 1129 authentication and privacy). 1131 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1132 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1133 enable cryptographic security. It is then a customer/operator 1134 responsibility to ensure that the SNMP entity giving access to an 1135 instance of this MIB module is properly configured to give access to 1136 the objects only to those principals (users) that have legitimate 1137 rights to indeed GET or SET (change/create/delete) them. 1139 8. IANA Considerations 1141 IANA is requested to assign a value for "XXXX" under the 'mib-2' 1142 subtree and to record the assignment in the SMI Numbers registry. 1143 When the assignment has been made, the RFC Editor is asked to replace 1144 "XXXX" (here and in the MIB module) with the assigned value and to 1145 remove this note. 1147 9. Acknowledgements 1149 This specification borrows heavily from the IP-MIB defined in 1150 [RFC4293]. 1152 Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo, 1153 a Network of Excellence project (ICT-318488) supported by the 1154 European Commission under its Seventh Framework Programme. 1156 10. References 1158 10.1. Normative References 1160 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1161 Requirement Levels", BCP 14, RFC 2119, March 1997. 1163 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1164 Schoenwaelder, Ed., "Structure of Management Information 1165 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1167 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1168 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 1169 58, RFC 2579, April 1999. 1171 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1172 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1173 April 1999. 1175 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 1176 "Transmission of IPv6 Packets over IEEE 802.15.4 1177 Networks", RFC 4944, September 2007. 1179 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1180 MIB", RFC 2863, June 2000. 1182 10.2. Informative References 1184 [RFC2013] McCloghrie, K., "SNMPv2 Management Information Base for 1185 the User Datagram Protocol using SMIv2", RFC 2013, 1186 November 1996. 1188 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1189 "Introduction and Applicability Statements for Internet- 1190 Standard Management Framework", RFC 3410, December 2002. 1192 [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April 1193 2006. 1195 [RFC4293] Routhier, S., "Management Information Base for the 1196 Internet Protocol (IP)", RFC 4293, April 2006. 1198 [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained 1199 Application Protocol (CoAP)", RFC 7252, June 2014. 1201 [I-D.ietf-6lo-btle] 1202 Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., 1203 Shelby, Z., and C. Gomez, "Transmission of IPv6 Packets 1204 over BLUETOOTH(R) Low Energy", draft-ietf-6lo-btle-02 1205 (work in progress), June 2014. 1207 Authors' Addresses 1209 Juergen Schoenwaelder 1210 Jacobs University 1211 Campus Ring 1 1212 Bremen 28759 1213 Germany 1215 EMail: j.schoenwaelder@jacobs-university.de 1217 Anuj Sehgal 1218 Jacobs University 1219 Campus Ring 1 1220 Bremen 28759 1221 Germany 1223 EMail: s.anuj@jacobs-university.de 1225 Tina Tsou 1226 Huawei Technologies (USA) 1227 2330 Central Expressway 1228 Santa Clara CA 95050 1229 USA 1231 EMail: tina.tsou.zouting@huawei.com 1233 Cathy Zhou 1234 Huawei Technologies 1235 Bantian, Longgang District 1236 Shenzhen 518129 1237 P.R. China 1239 EMail: cathyzhou@huawei.com