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