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