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