idnits 2.17.1 draft-schoenw-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 (November 7, 2013) is 3816 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 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: May 11, 2014 T. Tsou 6 Huawei Technologies (USA) 7 C. Zhou 8 Huawei Technologies 9 November 7, 2013 11 Definition of Managed Objects for IPv6 over Low-Power Wireless Personal 12 Area Networks (6LoWPANs) 13 draft-schoenw-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 May 11, 2014. 39 Copyright Notice 41 Copyright (c) 2013 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 . . . . . . . . . . . . . . 6 61 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 62 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 63 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 64 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 65 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 66 10.1. Normative References . . . . . . . . . . . . . . . . . . 15 67 10.2. Informative References . . . . . . . . . . . . . . . . . 16 68 Appendix A. JSON Representation . . . . . . . . . . . . . . . . . 17 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 object identifier registration tree has the following structure: 104 --lowpanMIB(1.3.6.1.2.1.XXXX) 105 +--lowpanNotifications(0) 106 +--lowpanObjects(1) 107 | +-- r-n Unsigned32 lowpanReasmTimeout(1) 108 | +-- r-n Counter32 lowpanInReceives(2) 109 | +-- r-n Counter32 lowpanInHdrErrors(3) 110 | +-- r-n Counter32 lowpanInMeshReceives(4) 111 | +-- r-n Counter32 lowpanInMeshForwds(5) 112 | +-- r-n Counter32 lowpanInMeshDelivers(6) 113 | +-- r-n Counter32 lowpanInReasmReqds(7) 114 | +-- r-n Counter32 lowpanInReasmFails(8) 115 | +-- r-n Counter32 lowpanInReasmOKs(9) 116 | +-- r-n Counter32 lowpanInCompReqds(10) 117 | +-- r-n Counter32 lowpanInCompFails(11) 118 | +-- r-n Counter32 lowpanInCompOKs(12) 119 | +-- r-n Counter32 lowpanInDiscards(13) 120 | +-- r-n Counter32 lowpanInDelivers(14) 121 | +-- r-n Counter32 lowpanOutRequests(15) 122 | +-- r-n Counter32 lowpanOutCompReqds(16) 123 | +-- r-n Counter32 lowpanOutCompFails(17) 124 | +-- r-n Counter32 lowpanOutCompOKs(18) 125 | +-- r-n Counter32 lowpanOutFragReqds(19) 126 | +-- r-n Counter32 lowpanOutFragFails(20) 127 | +-- r-n Counter32 lowpanOutFragOKs(21) 128 | +-- r-n Counter32 lowpanOutFragCreates(22) 129 | +-- r-n Counter32 lowpanOutMeshHopLimitExceeds(23) 130 | +-- r-n Counter32 lowpanOutMeshNoRoutes(24) 131 | +-- r-n Counter32 lowpanOutMeshRequests(25) 132 | +-- r-n Counter32 lowpanOutMeshForwds(26) 133 | +-- r-n Counter32 lowpanOutMeshTransmits(27) 134 | +-- r-n Counter32 lowpanOutDiscards(28) 135 | +-- r-n Counter32 lowpanOutTransmits(29) 136 +--lowpanConformance(2) 137 +--lowpanGroups(1) 138 | +--lowpanCoreGroup(1) 139 | +--lowpanMeshGroup(2) 140 +--lowpanCompliances(2) 141 +--lowpanCompliance(1) 143 The counters defined in the LOWPAN-MIB module provide information 144 about the 6LoWPAN datagrams received and transmitted and how they are 145 processed in the 6LoWPAN layer. For link-layers that use the 6LoWPAN 146 dispatch byte as defined in [RFC4944] (e.g., IEEE 802.15.4), a 147 6LoWPAN datagram is a datagram with a dispatch byte matching the bit 148 patterns 01xxxxxx, 10xxxxxx, or 11xxxxxx. Datagrams with a dispatch 149 byte matching the bit pattern 00xxxxxx (NALP - not a LoWPAN frame) 150 are not considered to be 6LoWPAN datagram by this specification. 151 Other radio technologies may use different mechanisms to identify 152 6LoWPAN datagrams (e.g., the BLUETOOTH Low Energy Logical Link 153 Control and Adaptation Protocol uses Channel Identifiers 154 [I-D.ietf-6lowpan-btle]). 156 The following diagram illustrates the conceptual relationships 157 between the counters. 159 IPv6 layer 160 ^ v 161 InDelivers -+- -+- OutRequests 162 | | 163 InDiscards <--+ | 164 | | 165 InCompOKs .-->| |-->. OutCompReqds 166 InCompFails <--| | | +--> OutCompFails 167 InCompReqds `<--+ +<--' OutCompOKs 168 | | 169 | +-->. OutFragReqds 170 InReasmOKs .-->| | +--> OutFragFails 171 InReasmFails <--| | | -+- OutFragOKs 172 InReasmReqds `<--+ +<--' OutFragCreates 173 | | 174 | | 175 InMeshDelivers |<--. | 176 InMeshForwds | |-->. | 177 InMeshReceives +-->' | | 178 | +--> | OutMeshHopLimitExceeds 179 | +--> | OutMeshNoRoutes 180 | | | 181 | | .<--+ OutMeshRequests 182 | `-->| | OutMeshForwds 183 | `-->| OutMeshTransmits 184 | | 185 InHdrErrors <--+ +--> OutDiscards 186 | | 187 InReceives -+- -+- OutTransmits 188 ^ v 189 interface layer 191 The fragmentation related counters have been modeled after the 192 fragmentation related counters of the IP-MIB [RFC4293]. The discard 193 counters have been placed at the end of the input and output chains 194 but they can be bumped any time if a datagram is discarded for a 195 reason not covered by the other counters. 197 The compression related counters provide insights into compression 198 requests and in particular also compression related failures. Note 199 that the diagram is conceptual in the sense that compression happens 200 after reassembly for incoming 6LoWPAN datagrams and compression 201 happens before fragmentation for outgoing 6LoWPAN datagrams. 202 Implementations may choose to implement things slightly differently. 203 For example, implementations may decompress FRAG1 fragments as soon 204 as they are received, not waiting for reassembly to complete. 206 The mesh header processing related counters do not have an explicit 207 discard counter. Implementations that do not support mesh forwarding 208 MUST count the number of received 6LoWPAN datagrams with a MESH 209 header (lowpanInMeshReceives) but they MUST NOT increment the 210 lowpanInMeshReceives and lowpanInMeshDelivers counters if these 211 6LoWPAN datagrams are dropped. 213 5. Relationship to Other MIB Modules 215 The MIB module IMPORTS definitions from SNMPv2-SMI [RFC2578] and 216 SNMPv2-CONF [RFC2580]. 218 6. Definitions 220 LOWPAN-MIB DEFINITIONS ::= BEGIN 222 IMPORTS 223 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2 224 FROM SNMPv2-SMI -- RFC 2578 225 OBJECT-GROUP, MODULE-COMPLIANCE 226 FROM SNMPv2-CONF; -- RFC 2580 228 lowpanMIB MODULE-IDENTITY 229 LAST-UPDATED "201311070000Z" 230 ORGANIZATION 231 "Jacobs University Bremen" 232 CONTACT-INFO 233 "Juergen Schoenwaelder 234 Jacobs University Bremen 235 Email: j.schoenwaelder@jacobs-university.de 237 Anuj Sehgal 238 Jacobs University Bremen 239 Email: s.anuj@jacobs-university.de 241 Tina Tsou 242 Huawei Technologies 243 Email: tina.tsou.zouting@huawei.com 245 Cathy Zhou 246 Huawei Technologies 247 Email: cathyzhou@huawei.com" 248 DESCRIPTION 249 "The MIB module for monitoring nodes implementing the IPv6 250 over Low-Power Wireless Personal Area Networks (6LoWPAN) 251 protocol. 253 Copyright (c) 2013 IETF Trust and the persons identified as 254 authors of the code. All rights reserved. 256 Redistribution and use in source and binary forms, with or 257 without modification, is permitted pursuant to, and subject 258 to the license terms contained in, the Simplified BSD 259 License set forth in Section 4.c of the IETF Trust's 260 Legal Provisions Relating to IETF Documents 261 (http://trustee.ietf.org/license-info)." 263 REVISION "201311070000Z" 264 DESCRIPTION 265 "Initial version, published as RFC XXXX." 266 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 268 ::= { mib-2 XXXX } 270 -- object definitions 272 lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 } 273 lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 } 274 lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 } 276 lowpanReasmTimeout OBJECT-TYPE 277 SYNTAX Unsigned32 278 UNITS "seconds" 279 MAX-ACCESS read-only 280 STATUS current 281 DESCRIPTION 282 "The maximum number of seconds that received fragments are 283 held while they are awaiting reassembly at this entity." 284 ::= { lowpanObjects 1 } 286 lowpanInReceives OBJECT-TYPE 287 SYNTAX Counter32 288 MAX-ACCESS read-only 289 STATUS current 290 DESCRIPTION 291 "The total number of 6LoWPAN datagrams received, including 292 those received in error." 293 ::= { lowpanObjects 2 } 295 lowpanInHdrErrors OBJECT-TYPE 296 SYNTAX Counter32 297 MAX-ACCESS read-only 298 STATUS current 299 DESCRIPTION 300 "The number of received 6LoWPAN datagrams discarded due to 301 errors in their headers, including unknown dispatch values." 302 ::= { lowpanObjects 3 } 304 lowpanInMeshReceives OBJECT-TYPE 305 SYNTAX Counter32 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "The number of received 6LoWPAN datagrams with a MESH header." 310 ::= { lowpanObjects 4 } 312 lowpanInMeshForwds OBJECT-TYPE 313 SYNTAX Counter32 314 MAX-ACCESS read-only 315 STATUS current 316 DESCRIPTION 317 "The number of received 6LoWPAN datagrams requiring MESH 318 forwarding." 319 ::= { lowpanObjects 5 } 321 lowpanInMeshDelivers OBJECT-TYPE 322 SYNTAX Counter32 323 MAX-ACCESS read-only 324 STATUS current 325 DESCRIPTION 326 "The number of received 6LoWPAN datagrams with a MESH header 327 delivered to the local system." 328 ::= { lowpanObjects 6 } 330 lowpanInReasmReqds OBJECT-TYPE 331 SYNTAX Counter32 332 MAX-ACCESS read-only 333 STATUS current 334 DESCRIPTION 335 "The number of received 6LoWPAN fragments that needed to 336 be reassembled. This includes both FRAG1 and FRAGN 6LoWPAN 337 datagrams." 338 ::= { lowpanObjects 7 } 340 lowpanInReasmFails OBJECT-TYPE 341 SYNTAX Counter32 342 MAX-ACCESS read-only 343 STATUS current 344 DESCRIPTION 345 "The number of failures detected by the re-assembly algorithm 346 (e.g., timeouts). Note that this is not necessarily a count of 347 discarded 6LoWPAN fragments since implementations can lose 348 track of the number of fragments by combining them as 349 received." 350 ::= { lowpanObjects 8 } 352 lowpanInReasmOKs OBJECT-TYPE 353 SYNTAX Counter32 354 MAX-ACCESS read-only 355 STATUS current 356 DESCRIPTION 357 "The number of IPv6 packets successfully reassembled." 358 ::= { lowpanObjects 9 } 360 lowpanInCompReqds OBJECT-TYPE 361 SYNTAX Counter32 362 MAX-ACCESS read-only 363 STATUS current 364 DESCRIPTION 365 "The number of 6LoWPAN datagrams requiring header 366 decompression." 367 ::= { lowpanObjects 10 } 369 lowpanInCompFails OBJECT-TYPE 370 SYNTAX Counter32 371 MAX-ACCESS read-only 372 STATUS current 373 DESCRIPTION 374 "The number of 6LoWPAN datagrams where header decompression 375 failed (e.g., because the necessary context information was 376 not available)." 377 ::= { lowpanObjects 11 } 379 lowpanInCompOKs OBJECT-TYPE 380 SYNTAX Counter32 381 MAX-ACCESS read-only 382 STATUS current 383 DESCRIPTION 384 "The number of 6LoWPAN datagrams where header decompression 385 was successful." 386 ::= { lowpanObjects 12 } 388 lowpanInDiscards OBJECT-TYPE 389 SYNTAX Counter32 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The number of received 6LoWPAN datagrams for which no 394 problems were encountered to prevent their continued 395 processing, but were discarded (e.g., for lack of buffer 396 space). Note that this counter does not include any 397 datagrams discarded due to a reassembly failure or a 398 compression failure." 399 ::= { lowpanObjects 13 } 401 lowpanInDelivers OBJECT-TYPE 402 SYNTAX Counter32 403 MAX-ACCESS read-only 404 STATUS current 405 DESCRIPTION 406 "The total number of IPv6 packets successfully delivered 407 to the IPv6 layer." 408 ::= { lowpanObjects 14 } 410 lowpanOutRequests OBJECT-TYPE 411 SYNTAX Counter32 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION 415 "The total number of IPv6 packets supplied by the IPv6 layer." 416 ::= { lowpanObjects 15 } 418 lowpanOutCompReqds OBJECT-TYPE 419 SYNTAX Counter32 420 MAX-ACCESS read-only 421 STATUS current 422 DESCRIPTION 423 "The total number of IPv6 packets for which header compression 424 was attempted." 425 ::= { lowpanObjects 16 } 427 lowpanOutCompFails OBJECT-TYPE 428 SYNTAX Counter32 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION 432 "The total number of IPv6 packets for which header compression 433 failed." 434 ::= { lowpanObjects 17 } 436 lowpanOutCompOKs OBJECT-TYPE 437 SYNTAX Counter32 438 MAX-ACCESS read-only 439 STATUS current 440 DESCRIPTION 441 "The total number of IPv6 packets for which header compression 442 was successful." 443 ::= { lowpanObjects 18 } 445 lowpanOutFragReqds OBJECT-TYPE 446 SYNTAX Counter32 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The number of IPv6 packets that required fragmentation 451 in order to be transmitted." 452 ::= { lowpanObjects 19 } 454 lowpanOutFragFails OBJECT-TYPE 455 SYNTAX Counter32 456 MAX-ACCESS read-only 457 STATUS current 458 DESCRIPTION 459 "The number of IPv6 packets that have been discarded because 460 fragmentation failed." 461 ::= { lowpanObjects 20 } 463 lowpanOutFragOKs OBJECT-TYPE 464 SYNTAX Counter32 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The number of IPv6 packets that have been successfully 469 fragmented." 470 ::= { lowpanObjects 21 } 472 lowpanOutFragCreates OBJECT-TYPE 473 SYNTAX Counter32 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "The number of 6LoWPAN fragments that have been 478 generated as a result of fragmentation. This includes 479 both FRAG1 and FRAGN 6LoWPAN datagrams." 480 ::= { lowpanObjects 22 } 482 lowpanOutMeshHopLimitExceeds OBJECT-TYPE 483 SYNTAX Counter32 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "The number of 6LoWPAN datagrams with a MESH header that 488 were dropped because the hop limit has been exceeded." 489 ::= { lowpanObjects 23 } 491 lowpanOutMeshNoRoutes OBJECT-TYPE 492 SYNTAX Counter32 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "The number of 6LoWPAN datagrams with a MESH header that 497 were dropped because there was no forwarding information 498 available." 499 ::= { lowpanObjects 24 } 501 lowpanOutMeshRequests OBJECT-TYPE 502 SYNTAX Counter32 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION 506 "The number of 6LoWPAN datagrams requiring MESH header 507 encapsulation." 508 ::= { lowpanObjects 25 } 510 lowpanOutMeshForwds OBJECT-TYPE 511 SYNTAX Counter32 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The number of 6LoWPAN datagrams with a MESH header for 516 which suitable forwarding information was available." 517 ::= { lowpanObjects 26 } 519 lowpanOutMeshTransmits OBJECT-TYPE 520 SYNTAX Counter32 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The number of 6LoWPAN datagrams with a MESH header 525 created." 526 ::= { lowpanObjects 27 } 528 lowpanOutDiscards OBJECT-TYPE 529 SYNTAX Counter32 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION 533 "The number of IPv6 packets for which no problem was 534 encountered to prevent their transmission to their 535 destination, but were discarded (e.g., for lack of 536 buffer space)." 537 ::= { lowpanObjects 28 } 539 lowpanOutTransmits OBJECT-TYPE 540 SYNTAX Counter32 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 "The total number of 6LoWPAN datagram that this entity 545 supplied to the lower layers for transmission." 546 ::= { lowpanObjects 29 } 548 -- conformance definitions 550 lowpanGroups OBJECT IDENTIFIER ::= { lowpanConformance 1 } 551 lowpanCompliances OBJECT IDENTIFIER ::= { lowpanConformance 2 } 553 lowpanCompliance MODULE-COMPLIANCE 554 STATUS current 555 DESCRIPTION 556 "Compliance statement for systems that implement 6LoWPAN." 557 MODULE -- this module 558 MANDATORY-GROUPS { 559 lowpanCoreGroup 560 } 561 GROUP lowpanMeshGroup 562 DESCRIPTION 563 "This group is mandatory for implementations that process 564 or forward 6LoWPAN datagrams with mesh headers." 565 ::= { lowpanCompliances 1 } 567 lowpanCoreGroup OBJECT-GROUP 568 OBJECTS { 569 lowpanReasmTimeout, 570 lowpanInReceives, 571 lowpanInHdrErrors, 572 lowpanInMeshReceives, 573 lowpanInReasmReqds, 574 lowpanInReasmFails, 575 lowpanInReasmOKs, 576 lowpanInCompReqds, 577 lowpanInCompFails, 578 lowpanInCompOKs, 579 lowpanInDiscards, 580 lowpanInDelivers, 581 lowpanOutRequests, 582 lowpanOutCompReqds, 583 lowpanOutCompFails, 584 lowpanOutCompOKs, 585 lowpanOutFragReqds, 586 lowpanOutFragFails, 587 lowpanOutFragOKs, 588 lowpanOutFragCreates, 589 lowpanOutDiscards, 590 lowpanOutTransmits 591 } 592 STATUS current 593 DESCRIPTION 594 "A collection of objects providing information and 595 statistics about the processing of 6LoWPAN datagrams, 596 excluding counters covering the processing of datagrams 597 with a mesh headers." 598 ::= { lowpanGroups 1 } 600 lowpanMeshGroup OBJECT-GROUP 601 OBJECTS { 602 lowpanInMeshForwds, 603 lowpanInMeshDelivers, 604 lowpanOutMeshHopLimitExceeds, 605 lowpanOutMeshNoRoutes, 606 lowpanOutMeshRequests, 607 lowpanOutMeshForwds, 608 lowpanOutMeshTransmits 609 } 610 STATUS current 611 DESCRIPTION 612 "A collection of objects providing information and 613 statistics about the processing of 6LoWPAN datagrams 614 with a 6LoWPAN mesh header." 615 ::= { lowpanGroups 2 } 617 END 619 7. Security Considerations 621 Some of the readable objects in this MIB module (i.e., objects with a 622 MAX-ACCESS other than not-accessible) may be considered sensitive or 623 vulnerable in some network environments. It is thus important to 624 control even GET and/or NOTIFY access to these objects and possibly 625 to even encrypt the values of these objects when sending them over 626 the network via SNMP. These are the tables and objects and their 627 sensitivity/vulnerability: 629 The read-only counters provide insights into the amount of 6LoWPAN 630 traffic a node is receiving or transmitting. This might provide 631 information whether a device is regularly exchanging information with 632 other devices or whether a device is mostly not participating in any 633 communication (e.g., the device might be "easier" to take away 634 unnoticed). The reassembly counters could be used to direct denial 635 of service attacks on the reassembly mechanism. 637 SNMP versions prior to SNMPv3 did not include adequate security. 638 Even if the network itself is secure (for example by using IPsec), 639 even then, there is no control as to who on the secure network is 640 allowed to access and GET/SET (read/change/create/delete) the objects 641 in this MIB module. 643 It is RECOMMENDED that implementers consider the security features as 644 provided by the SNMPv3 framework (see [RFC3410], section 8), 645 including full support for the SNMPv3 cryptographic mechanisms (for 646 authentication and privacy). 648 Further, deployment of SNMP versions prior to SNMPv3 is NOT 649 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 650 enable cryptographic security. It is then a customer/operator 651 responsibility to ensure that the SNMP entity giving access to an 652 instance of this MIB module is properly configured to give access to 653 the objects only to those principals (users) that have legitimate 654 rights to indeed GET or SET (change/create/delete) them. 656 8. IANA Considerations 658 IANA is requested to assign a value for "XXXX" under the 'mib-2' 659 subtree and to record the assignment in the SMI Numbers registry. 660 When the assignment has been made, the RFC Editor is asked to replace 661 "XXXX" (here and in the MIB module) with the assigned value and to 662 remove this note. 664 9. Acknowledgements 666 This specification borrows heavily from the IP-MIB defined in 667 [RFC4293]. 669 Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo, 670 a Network of Excellence project (ICT-318488) supported by the 671 European Commission under its Seventh Framework Programme. 673 10. References 675 10.1. Normative References 677 [RFC2119] Bradner, S., "Key words for use in 678 RFCs to Indicate Requirement Levels", 679 BCP 14, RFC 2119, March 1997. 681 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 682 and J. Schoenwaelder, Ed., "Structure 683 of Management Information Version 2 684 (SMIv2)", STD 58, RFC 2578, 685 April 1999. 687 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 688 and J. Schoenwaelder, Ed., "Textual 689 Conventions for SMIv2", STD 58, 690 RFC 2579, April 1999. 692 [RFC2580] McCloghrie, K., Perkins, D., and J. 693 Schoenwaelder, "Conformance Statements 694 for SMIv2", STD 58, RFC 2580, 695 April 1999. 697 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, 698 J., and D. Culler, "Transmission of 699 IPv6 Packets over IEEE 802.15.4 700 Networks", RFC 4944, September 2007. 702 [I-D.ietf-6lowpan-btle] Nieminen, J., Savolainen, T., Isomaki, 703 M., Patil, B., Shelby, Z., and C. 704 Gomez, "Transmission of IPv6 Packets 705 over BLUETOOTH Low Energy", 706 draft-ietf-6lowpan-btle-12 (work in 707 progress), February 2013. 709 10.2. Informative References 711 [RFC3410] Case, J., Mundy, R., Partain, D., and 712 B. Stewart, "Introduction and 713 Applicability Statements for Internet- 714 Standard Management Framework", 715 RFC 3410, December 2002. 717 [RFC4293] Routhier, S., "Management Information 718 Base for the Internet Protocol (IP)", 719 RFC 4293, April 2006. 721 [RFC6643] Schoenwaelder, J., "Translation of 722 Structure of Management Information 723 Version 2 (SMIv2) MIB Modules to YANG 724 Modules", RFC 6643, July 2012. 726 [I-D.lhotka-netmod-yang-json] Lhotka, L., "Modeling JSON Text with 727 YANG", 728 draft-lhotka-netmod-yang-json-02 (work 729 in progress), September 2013. 731 Appendix A. JSON Representation 733 Using the translation algorithm defined in [RFC6643], the SMIv2 734 module can be translated to YANG. Using the JSON representation of 735 data modeled in YANG defined in [I-D.lhotka-netmod-yang-json], the 736 objects defined in the MIB module can be represented in JSON as shown 737 below. The compact representation without any white space uses 468 738 octets. (Of course, this number depends on the number of octets 739 needed for the counter values.) 741 { 742 "LOWPAN-MIB:LOWPAN-MIB": { 743 "lowpanReasmTimeout": 20, 744 "lowpanInReceives": 42, 745 "lowpanInHdrErrors": 0, 746 "lowpanInMeshReceives": 8, 747 "lowpanInMeshForwds": 0, 748 "lowpanInMeshDelivers": 0, 749 "lowpanInReasmReqds": 22, 750 "lowpanInReasmFails": 2, 751 "lowpanInReasmOKs": 20, 752 "lowpanInCompReqds": 16, 753 "lowpanInCompFails": 2, 754 "lowpanInCompOKs": 14, 755 "lowpanInDiscards": 1, 756 "lowpanInDelivers": 12, 757 "lowpanOutRequests": 12, 758 "lowpanOutCompReqds": 0, 759 "lowpanOutCompFails": 0, 760 "lowpanOutCompOKs": 0, 761 "lowpanOutFragReqds": 5, 762 "lowpanOutFragFails": 0, 763 "lowpanOutFragOKs": 5, 764 "lowpanOutFragCreates": 8, 765 "lowpanOutMeshHopLimitExceeds": 0, 766 "lowpanOutMeshNoRoutes": 0, 767 "lowpanOutMeshRequests": 0, 768 "lowpanOutMeshForwds": 0, 769 "lowpanOutMeshTransmits": 0, 770 "lowpanOutDiscards": 0, 771 "lowpanOutTransmits": 15 772 } 773 } 775 Authors' Addresses 777 Juergen Schoenwaelder 778 Jacobs University 779 Campus Ring 1 780 Bremen 28759 781 Germany 783 EMail: j.schoenwaelder@jacobs-university.de 785 Anuj Sehgal 786 Jacobs University 787 Campus Ring 1 788 Bremen 28759 789 Germany 791 EMail: s.anuj@jacobs-university.de 793 Tina Tsou 794 Huawei Technologies (USA) 795 2330 Central Expressway 796 Santa Clara CA 95050 797 USA 799 EMail: tina.tsou.zouting@huawei.com 801 Cathy Zhou 802 Huawei Technologies 803 Bantian, Longgang District 804 Shenzhen 518129 805 P.R. China 807 EMail: cathyzhou@huawei.com