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