idnits 2.17.1 draft-sehgal-roll-rpl-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 : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 127 has weird spacing: '...eration rpl...' == Line 135 has weird spacing: '...ference rpl...' == Line 141 has weird spacing: '...rolSize rpl...' == Line 146 has weird spacing: '...ceIndex rplDo...' == 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 (March 12, 2012) is 4428 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 7 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force K. Korte 3 Internet-Draft J. Schoenwaelder 4 Intended status: Standards Track A. Sehgal 5 Expires: September 13, 2012 Jacobs University 6 T. Tsou 7 Huawei Technologies (USA) 8 C. Zhou 9 Huawei Technologies 10 March 12, 2012 12 Definition of Managed Objects for the IPv6 Routing Protocol for Low 13 Power and Lossy Networks (RPL) 14 draft-sehgal-roll-rpl-mib-03 16 Abstract 18 This memo defines a portion of the Management Information Base (MIB) 19 for use with network management protocols in the Internet community. 20 In particular, it defines objects for managing the IPv6 Routing 21 Protocol for Low Power and Lossy Networks (RPL). 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on September 13, 2012. 40 Copyright Notice 42 Copyright (c) 2012 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. The Internet-Standard Management Framework . . . . . . . . . . 3 59 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 62 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 7. Security Considerations . . . . . . . . . . . . . . . . . . . 26 64 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 65 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27 66 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 67 10.1. Normative References . . . . . . . . . . . . . . . . . . 27 68 10.2. Informative References . . . . . . . . . . . . . . . . . 28 69 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 28 71 1. Introduction 73 This memo defines a portion of the Management Information Base (MIB) 74 for use with network management protocols. In particular it defines 75 objects for managing the IPv6 Routing Protocol for Low Power and 76 Lossy Networks (RPL) [I-D.ietf-roll-rpl]. It also provides 77 management access to the Trickle [RFC6206] parameters as they are 78 used by RPL. 80 2. The Internet-Standard Management Framework 82 For a detailed overview of the documents that describe the current 83 Internet-Standard Management Framework, please refer to section 7 of 84 RFC 3410 [RFC3410]. 86 Managed objects are accessed via a virtual information store, termed 87 the Management Information Base or MIB. MIB objects are generally 88 accessed through the Simple Network Management Protocol (SNMP). 89 Objects in the MIB are defined using the mechanisms defined in the 90 Structure of Management Information (SMI). This memo specifies a MIB 91 module that is compliant to the SMIv2, which is described in STD 58, 92 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 93 [RFC2580]. 95 3. Conventions 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in RFC 2119 [RFC2119]. 101 4. Overview 103 The MIB module is organized into a group of scalars and tables. 105 # RPL-MIB registration tree (generated by smidump 0.4.8) 107 -rplMib(1.3.6.1.2.1.XXXX) 108 +-rplNotifications(0) 109 +-rplObjects(1) 110 +-rplGeneral(1) 111 | +- rwn RplDISMode rplDefaultDISMode(1) 112 +-rplActive(2) 113 | +- rwn RplInstanceID rplActiveInstance(1) 114 | +- rwn InetAddressIPv6 rplActiveDodag(2) 115 | +- r-n Unsigned32 rplActiveDodagDAOSequence(3) 116 | +- rwn Unsigned32 rplActiveDodagTriggerSequence(4) 117 +-rplOCPTable(3) 118 | +-rplOCPEntry(1) [rplOCPCodepoint] 119 | +- --- RplObjectiveCodePoint rplOCPCodepoint(1) 120 | +- rwn TruthValue rplOCPEnabled(2) 121 +-rplRPLInstanceTable(4) 122 | +-rplRPLInstanceEntry(1) [rplRPLInstanceID] 123 | +- --- RplInstanceID rplRPLInstanceID(1) 124 | +- rwn RplObjectiveCodePoint rplRPLInstanceOCP(2) 125 | +- rwn RplDISMode rplRPLInstanceDisMode(3) 126 | +- rwn Enumeration rplRPLInstanceDAOAcknowledgement(4) 127 | +- rwn RplModeOfOperation rplRPLInstanceModeOfOperation(5) 128 +-rplDodagTable(5) 129 | +-rplDodagEntry(1) [rplRPLInstanceID,rplDodagRoot] 130 | +- --- InetAddressIPv6 rplDodagRoot(1) 131 | +- r-n RplDodagVersionNumber rplDodagVersion(2) 132 | +- r-n RplRank rplDodagRank(3) 133 | +- r-n Enumeration rplDodagState(4) 134 | +- r-n RplDAODelay rplDodagDAODelay(5) 135 | +- r-n RplDodagPreference rplDodagPreference(6) 136 | +- r-n RplMinHopRankIncrease rplDodagMinHopRankIncrease(7) 137 | +- r-n Unsigned32 rplDodagMaxRankIncrease(8) 138 | +- rwn Unsigned32 rplDodagIntervalDoublings(9) 139 | +- rwn Unsigned32 rplDodagIntervalMin(10) 140 | +- rwn Unsigned32 rplDodagRedundancyConstant(11) 141 | +- r-n RplPathControlSize rplDodagPathControlSize(12) 142 +-rplDodagParentTable(6) 143 | +-rplDodagParentEntry(1) [rplRPLInstanceID,rplDodagRoot, 144 | | rplDodagParentID] 145 | +- --- InetAddressIPv6 rplDodagParentID(1) 146 | +- r-n InterfaceIndex rplDodagParentIf(2) 147 +-rplDodagChildTable(7) 148 | +-rplDodagChildEntry(1) [rplRPLInstanceID,rplDodagRoot, 149 | | rplDodagChildID] 150 | +- r-n InetAddressIPv6 rplDodagChildID(1) 151 +-rplDodagPrefixTable(8) 152 | +-rplDodagPrefixEntry(1) [rplRPLInstanceID,rplDodagRoot, 153 | | rplDodagPrefixIpv6Prefix, 154 | | rplDodagPrefixIpv6PrefixLength] 155 | +- r-n InetAddressIPv6 rplDodagPrefixIpv6Prefix(1) 156 | +- r-n InetAddressPrefixLength 157 | rplDodagPrefixIpv6PrefixLength(2) 158 +-rplStats(9) 159 | +- r-n Counter32 rplMemOverflows(1) 160 | +- r-n Counter32 rplParseErrors(2) 161 | +- r-n Counter32 rplUnknownMsgTypes(3) 162 | +- r-n Counter32 rplSecurityPolicyViolations(4) 163 | +- r-n Counter32 rplIntegrityCheckFailures(5) 164 | +- r-n Counter32 rplReplayProtectionFailures(6) 165 | +- r-n Counter32 rplValidParentFailures(7) 166 | +- r-n Counter32 rplNoInstanceIDs(8) 167 | +- r-n Counter32 rplTriggeredLocalRepairs(9) 168 | +- r-n Counter32 rplTriggeredGlobalRepairs(10) 169 | +- r-n Counter32 rplNoParentSecs(11) 170 | +- r-n Counter32 rplActiveNoParentSecs(12) 171 | +- r-n Counter32 rplOBitSetDownwards(13) 172 | +- r-n Counter32 rplOBitClearedUpwards(14) 173 | +- r-n Counter32 rplFBitSet(15) 174 | +- r-n Counter32 rplRBitSet(16) 175 | +- r-n Counter32 rplTrickleTimerResets(17) 176 +-rplMsgStatsTable(10) 177 +-rplMsgStatsEntry(1) [rplMsgStatsType] 178 +- --- RplMessageType rplMsgStatsType(1) 179 +- r-n Counter32 rplMsgStatsInMsgs(2) 180 +- r-n Counter32 rplMsgStatsOutMsgs(3) 182 5. Relationship to Other MIB Modules 184 The MIB module IMPORTS definitions from SNMPv2-SMI [RFC2578], 185 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and the 186 INET-ADDRESS-MIB [RFC4001]. 188 The IPv6 routing table should be exposed via the inetCidrRouteTable 189 defined in the IP-FORWARD-MIB [RFC4292]. XXX: We need to clarify 190 whether the inetCidrRoutePolicy can / should point to the DODAG 191 instance. 193 6. Definitions 195 RPL-MIB DEFINITIONS ::= BEGIN 197 IMPORTS 198 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2 199 FROM SNMPv2-SMI -- RFC 2578 200 TEXTUAL-CONVENTION, TruthValue 201 FROM SNMPv2-TC -- RFC 2579 202 OBJECT-GROUP, MODULE-COMPLIANCE 203 FROM SNMPv2-CONF -- RFC 2580 204 InterfaceIndex 205 FROM IF-MIB -- RFC 2863 206 InetAddressIPv6, InetAddressPrefixLength 207 FROM INET-ADDRESS-MIB; -- RFC 4001 209 rplMib MODULE-IDENTITY 210 LAST-UPDATED "201110310000Z" 211 ORGANIZATION 212 "Jacobs University Bremen" 213 CONTACT-INFO 214 "Kevin Dominik Korte 215 Jacobs University Bremen 216 Email: k.korte@jacobs-university.de 218 Anuj Sehgal 219 Jacobs University Bremen 220 Email: s.anuj@jacobs-university.de 222 Juergen Schoenwaelder 223 Jacobs University Bremen 224 Email: j.schoenwaelder@jacobs-university.de 226 Tina Tsou 227 Huawei Technologies 228 Email: tena@huawei.com 230 Cathy Zhou 231 Huawei Technologies 232 Email: cathyzhou@huawei.com" 233 DESCRIPTION 234 "The MIB module for monitoring nodes implementing the IPv6 235 routing protocol for low power and lossy networks (RPL). 237 Copyright (c) 2011 IETF Trust and the persons identified as 238 authors of the code. All rights reserved. 240 Redistribution and use in source and binary forms, with or 241 without modification, is permitted pursuant to, and subject 242 to the license terms contained in, the Simplified BSD 243 License set forth in Section 4.c of the IETF Trust's 244 Legal Provisions Relating to IETF Documents 245 (http://trustee.ietf.org/license-info)." 247 REVISION "201110310000Z" 248 DESCRIPTION 249 "Initial version, published as RFC XXXX." 250 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 252 ::= { mib-2 XXXX } 254 -- XXX: Do we keep all types (textual conventions) defined below or 255 -- XXX do we inline those that only get used once? 257 RplMessageType ::= TEXTUAL-CONVENTION 258 DISPLAY-HINT "d" 259 STATUS current 260 DESCRIPTION 261 "The type of an RPL control message." 262 REFERENCE 263 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs as defined in 264 Section 6 of RFC YYYY." 265 SYNTAX Unsigned32 (0..255) 267 RplInstanceID ::= TEXTUAL-CONVENTION 268 DISPLAY-HINT "d" 269 STATUS current 270 DESCRIPTION 271 "A global or local RPLinstanceID as defined in Section 5.1. of 272 RFC YYYY." 273 REFERENCE 274 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 275 SYNTAX Unsigned32 (0..255) 277 RplDodagVersionNumber ::= TEXTUAL-CONVENTION 278 DISPLAY-HINT "d" 279 STATUS current 280 DESCRIPTION 281 "The version number of a DODAG as defined in Section 6.3 of 282 RFC YYYY." 283 REFERENCE 284 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 285 SYNTAX Unsigned32 (0..255) 287 RplRank ::= TEXTUAL-CONVENTION 288 DISPLAY-HINT "d" 289 STATUS current 290 DESCRIPTION 291 "The rank of a node within a DODAG as defined in Section 6.3 292 of RFC YYYY." 293 REFERENCE 294 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 295 SYNTAX Unsigned32 (0..65535) 297 RplObjectiveCodePoint ::= TEXTUAL-CONVENTION 298 DISPLAY-HINT "d" 299 STATUS current 300 DESCRIPTION 301 "The Objective Code Point of a DODAG as defined in 302 Section 6.7.6 of RFC YYYY." 303 REFERENCE 304 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 305 SYNTAX Unsigned32 (0..65535) 307 RplDISMode ::= TEXTUAL-CONVENTION 308 STATUS current 309 DESCRIPTION 310 "Determines whether a DIS message is send upon boot-up 311 or not as defined in Section 17.2.1.1 of RFC YYYY: 313 silent(1) do not send DIS messages 314 send(2) send DIS messages" 315 REFERENCE 316 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 317 SYNTAX INTEGER { 318 silent(1), 319 send(2) 320 } 322 RplModeOfOperation ::= TEXTUAL-CONVENTION 323 STATUS current 324 DESCRIPTION 325 "Determines the mode of operation." 326 REFERENCE 327 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 328 SYNTAX INTEGER { 329 noDownwardRoutes(0), 330 nonStoringMode(1), 331 storingWithoutMulticastSupport(2), 332 storingWithMulticastSupport(3) 333 } 335 RplDAODelay ::= TEXTUAL-CONVENTION 336 DISPLAY-HINT "d" 337 STATUS current 338 DESCRIPTION 339 "The delay time used for aggregation before a DAO message 340 is send." 341 REFERENCE 342 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 343 SYNTAX Unsigned32 345 RplDodagPreference ::= TEXTUAL-CONVENTION 346 DISPLAY-HINT "d" 347 STATUS current 348 DESCRIPTION 349 "The preference of a DODAG compared to another DODAG of the 350 same instance as defined in Section 6.3 of RFC YYYY." 351 REFERENCE 352 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 353 SYNTAX Unsigned32 (0..7) 355 RplMinHopRankIncrease ::= TEXTUAL-CONVENTION 356 DISPLAY-HINT "d" 357 STATUS current 358 DESCRIPTION 359 "The minimal incerease of a rank within a single hop as 360 defined in Section 6.7.6 of RFC YYYY." 361 REFERENCE 362 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 363 SYNTAX Unsigned32 (0..131071) 365 RplPathControlSize ::= TEXTUAL-CONVENTION 366 DISPLAY-HINT "d" 367 STATUS current 368 DESCRIPTION 369 "The Path Control Size within a DODAG as defined in 370 Section 6.7.6 of RFC YYYY." 371 REFERENCE 372 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 373 SYNTAX Unsigned32 (0..7) 375 -- object definitions 377 rplNotifications OBJECT IDENTIFIER ::= { rplMib 0 } 378 rplObjects OBJECT IDENTIFIER ::= { rplMib 1 } 379 rplConformance OBJECT IDENTIFIER ::= { rplMib 2 } 381 rplGeneral OBJECT IDENTIFIER ::= { rplObjects 1 } 383 rplDefaultDISMode OBJECT-TYPE 384 SYNTAX RplDISMode 385 MAX-ACCESS read-write 386 STATUS current 387 DESCRIPTION 388 "Determines whether a DIS message is send upon boot-up. 389 Changes to this value may not persist across restarts." 390 ::= { rplGeneral 1 } 391 -- XXX should be able to configure the number of DIS messages 392 -- XXX and related timer, see 18.2.1.1. 394 -- XXX Should there be more objects to configure default timers 395 -- XXX etc that are applied to all DODAGs etc? 397 rplActive OBJECT IDENTIFIER ::= { rplObjects 2 } 399 rplActiveInstance OBJECT-TYPE 400 SYNTAX RplInstanceID 401 MAX-ACCESS read-write 402 STATUS current 403 DESCRIPTION 404 "The currently active RPL Instance. Changes to this value 405 may not persist across restarts." 406 ::= { rplActive 1 } 408 rplActiveDodag OBJECT-TYPE 409 SYNTAX InetAddressIPv6 410 MAX-ACCESS read-write 411 STATUS current 412 DESCRIPTION 413 "The currently active RPL DODAG in the active RPL Instance. 414 Changes to this value may not persist across restarts." 415 ::= { rplActive 2 } 417 rplActiveDodagDAOSequence OBJECT-TYPE 418 SYNTAX Unsigned32 (0..255) 419 MAX-ACCESS read-only 420 STATUS current 421 DESCRIPTION 422 "The DAO message sequence number (DAOSequence) of the active 423 DODAG as defined in Section 6.5.1 of RFC YYYY." 424 REFERENCE 425 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 426 ::= { rplActive 3 } 428 rplActiveDodagTriggerSequence OBJECT-TYPE 429 SYNTAX Unsigned32 (0..255) 430 MAX-ACCESS read-write 431 STATUS current 432 DESCRIPTION 433 "The DAO Trigger Sequence Number (DTSN) of the active 434 DODAG as defined in Section 6.3.1 of RFC YYYY. Changes to 435 this value may not persist across restarts." 436 REFERENCE 437 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 438 ::= { rplActive 4 } 440 rplOCPTable OBJECT-TYPE 441 SYNTAX SEQUENCE OF RplOCPEntry 442 MAX-ACCESS not-accessible 443 STATUS current 444 DESCRIPTION 445 "The table of all supported Objective Code Points (OCPs)." 446 ::= { rplObjects 3 } 448 rplOCPEntry OBJECT-TYPE 449 SYNTAX RplOCPEntry 450 MAX-ACCESS not-accessible 451 STATUS current 452 DESCRIPTION 453 "An entry representing a supported Objective Code Point." 454 INDEX { rplOCPCodepoint } 455 ::= { rplOCPTable 1 } 457 RplOCPEntry ::= SEQUENCE { 458 rplOCPCodepoint RplObjectiveCodePoint, 459 rplOCPEnabled TruthValue 460 } 462 rplOCPCodepoint OBJECT-TYPE 463 SYNTAX RplObjectiveCodePoint 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "A supported Objective Code Point." 468 ::= { rplOCPEntry 1 } 470 rplOCPEnabled OBJECT-TYPE 471 SYNTAX TruthValue 472 MAX-ACCESS read-write 473 STATUS current 474 DESCRIPTION 475 "Enables the usage of this Objective Code Point. Changes to 476 this value may not persist across restarts." 477 ::= { rplOCPEntry 2 } 479 rplRPLInstanceTable OBJECT-TYPE 480 SYNTAX SEQUENCE OF RplRPLInstanceEntry 481 MAX-ACCESS not-accessible 482 STATUS current 483 DESCRIPTION 484 "The table represents information about all known 485 RPL Instances." 486 ::= { rplObjects 4 } 488 rplRPLInstanceEntry OBJECT-TYPE 489 SYNTAX RplRPLInstanceEntry 490 MAX-ACCESS not-accessible 491 STATUS current 492 DESCRIPTION 493 "An entry representing information about a RPL Instance." 494 INDEX { rplRPLInstanceID } 495 ::= { rplRPLInstanceTable 1 } 496 -- XXX This should likely be a read-create table. 498 RplRPLInstanceEntry ::= SEQUENCE { 499 rplRPLInstanceID RplInstanceID, 500 rplRPLInstanceOCP RplObjectiveCodePoint, 501 rplRPLInstanceDisMode RplDISMode, 502 rplRPLInstanceDAOAcknowledgement INTEGER, 503 rplRPLInstanceModeOfOperation RplModeOfOperation 504 } 505 rplRPLInstanceID OBJECT-TYPE 506 SYNTAX RplInstanceID 507 MAX-ACCESS not-accessible 508 STATUS current 509 DESCRIPTION 510 "The InstanceID of this RPL Instance." 511 ::= { rplRPLInstanceEntry 1 } 513 rplRPLInstanceOCP OBJECT-TYPE 514 SYNTAX RplObjectiveCodePoint 515 MAX-ACCESS read-write 516 STATUS current 517 DESCRIPTION 518 "The Objective Code Point of this RPL Instance. Changes to 519 this value may not persist across restarts." 520 ::= { rplRPLInstanceEntry 2 } 522 rplRPLInstanceDisMode OBJECT-TYPE 523 SYNTAX RplDISMode 524 MAX-ACCESS read-write 525 STATUS current 526 DESCRIPTION 527 "Determines whether a DIS message is send for this instance 528 upon boot-up. Changes to this value may not persist across 529 restarts." 530 ::= { rplRPLInstanceEntry 3 } 531 -- XXX Check how this works together with the global toggle. 532 -- XXX should we allow per instance parameters such as the number 533 -- XXX of DIS messages and related timer, see 17.2.1.1? 535 rplRPLInstanceDAOAcknowledgement OBJECT-TYPE 536 SYNTAX INTEGER { 537 nope(1) 538 } 539 MAX-ACCESS read-write 540 STATUS current 541 DESCRIPTION 542 "The mode of Operation of the RPL instance. Changes to this 543 value may not persist across restarts." 544 ::= { rplRPLInstanceEntry 4 } 545 -- XXX What is this? Kevin? 547 rplRPLInstanceModeOfOperation OBJECT-TYPE 548 SYNTAX RplModeOfOperation 549 MAX-ACCESS read-write 550 STATUS current 551 DESCRIPTION 552 "The mode of Operation of the RPL instance. Changes to this 553 value may not persist across restarts." 554 ::= { rplRPLInstanceEntry 5 } 556 rplDodagTable OBJECT-TYPE 557 SYNTAX SEQUENCE OF RplDodagEntry 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION 561 "The table represents information about all locally known 562 DODAGs." 563 ::= { rplObjects 5 } 564 -- XXX The root needs a bit(?) config, where does that go? 566 rplDodagEntry OBJECT-TYPE 567 SYNTAX RplDodagEntry 568 MAX-ACCESS not-accessible 569 STATUS current 570 DESCRIPTION 571 "An entry representing information about a DODAG." 572 INDEX { rplRPLInstanceID, rplDodagRoot } 573 ::= { rplDodagTable 1 } 575 RplDodagEntry ::= SEQUENCE { 576 rplDodagRoot InetAddressIPv6, 577 rplDodagVersion RplDodagVersionNumber, 578 rplDodagRank RplRank, 579 rplDodagState INTEGER, 580 rplDodagDAODelay RplDAODelay, 581 rplDodagPreference RplDodagPreference, 582 rplDodagMinHopRankIncrease RplMinHopRankIncrease, 583 rplDodagMaxRankIncrease Unsigned32, 584 rplDodagIntervalDoublings Unsigned32, 585 rplDodagIntervalMin Unsigned32, 586 rplDodagRedundancyConstant Unsigned32, 587 rplDodagPathControlSize RplPathControlSize 588 } 590 rplDodagRoot OBJECT-TYPE 591 SYNTAX InetAddressIPv6 592 MAX-ACCESS not-accessible 593 STATUS current 594 DESCRIPTION 595 "The identifier of a DODAG root (DODAGID) of this RPL 596 instance. The root of the DODAG reports its own IPv6 597 address as the DODAG root." 598 ::= { rplDodagEntry 1 } 600 rplDodagVersion OBJECT-TYPE 601 SYNTAX RplDodagVersionNumber 602 MAX-ACCESS read-only 603 STATUS current 604 DESCRIPTION 605 "The version of the DODAG in this RPL instance." 606 ::= { rplDodagEntry 2 } 608 rplDodagRank OBJECT-TYPE 609 SYNTAX RplRank 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The rank of the node within the DODAG." 614 ::= { rplDodagEntry 3 } 616 rplDodagState OBJECT-TYPE 617 SYNTAX INTEGER { 618 other(0), 619 associated(1), 620 grounded(2), 621 floating(3) 622 } 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "The status of the DODAG: 628 other(0) An unknown state. 630 associated(1) A node is associated with the RPL instance. 632 grounded(2) The DODAG is grounded. 634 floating(3) The DODAG is floating (not grounded). 635 " 636 ::= { rplDodagEntry 4 } 638 rplDodagDAODelay OBJECT-TYPE 639 SYNTAX RplDAODelay 640 UNITS "milliseconds" 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "The delay for aggregations before a DAO is send." 645 ::= { rplDodagEntry 5 } 646 -- XXX should this be configuration? If so we should add a default 647 -- clause to define the default value to be 1 second. 649 rplDodagPreference OBJECT-TYPE 650 SYNTAX RplDodagPreference 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "How preferred this DODAG is compared to other DODAGs 655 within the same instance." 656 ::= { rplDodagEntry 6 } 658 rplDodagMinHopRankIncrease OBJECT-TYPE 659 SYNTAX RplMinHopRankIncrease 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 663 "The minimum increase of the rank in a single hop." 664 ::= { rplDodagEntry 7 } 665 -- XXX should this be writable at the root? If so we should add a 666 -- defval clause to define the default value to be 256. 668 rplDodagMaxRankIncrease OBJECT-TYPE 669 SYNTAX Unsigned32 (0..65535) 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "The maximum allowable increase in rank in support of local 674 repair. If DAGMaxRankIncrease is 0 then this mechanism is 675 disabled." 676 ::= { rplDodagEntry 8 } 678 rplDodagIntervalDoublings OBJECT-TYPE 679 SYNTAX Unsigned32 (0..255) 680 MAX-ACCESS read-write 681 STATUS current 682 DESCRIPTION 683 "The configured Imax of the DIO trickle timer. This is 684 typically only writable at the root. Changes to this value 685 may not persist across restarts." 686 REFERENCE 687 "RFC 6206: The Trickle Algorithm" 688 DEFVAL { 20 } 689 ::= { rplDodagEntry 9 } 691 rplDodagIntervalMin OBJECT-TYPE 692 SYNTAX Unsigned32 (0..255) 693 MAX-ACCESS read-write 694 STATUS current 695 DESCRIPTION 696 "The configured Imin of the DIO trickle timer. Changes to this 697 value may not persist across restarts." 698 REFERENCE 699 "RFC 6206: The Trickle Algorithm" 700 DEFVAL { 3 } 701 ::= { rplDodagEntry 10 } 703 rplDodagRedundancyConstant OBJECT-TYPE 704 SYNTAX Unsigned32 (0..255) 705 MAX-ACCESS read-write 706 STATUS current 707 DESCRIPTION 708 "The configured k of the DIO trickle timer. Changes to this 709 value may not persist across restarts." 710 REFERENCE 711 "RFC 6206: The Trickle Algorithm" 712 DEFVAL { 10 } 713 ::= { rplDodagEntry 11 } 715 rplDodagPathControlSize OBJECT-TYPE 716 SYNTAX RplPathControlSize 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "The Path Control Size of this DODAG." 721 ::= { rplDodagEntry 12 } 723 rplDodagParentTable OBJECT-TYPE 724 SYNTAX SEQUENCE OF RplDodagParentEntry 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "The list of parents for a DODAG." 729 ::= { rplObjects 6 } 731 rplDodagParentEntry OBJECT-TYPE 732 SYNTAX RplDodagParentEntry 733 MAX-ACCESS not-accessible 734 STATUS current 735 DESCRIPTION 736 "Information about a known DODAG parent." 737 INDEX { rplRPLInstanceID, rplDodagRoot, rplDodagParentID } 738 ::= { rplDodagParentTable 1 } 740 RplDodagParentEntry ::= SEQUENCE { 741 rplDodagParentID InetAddressIPv6, 742 rplDodagParentIf InterfaceIndex 743 } 744 rplDodagParentID OBJECT-TYPE 745 SYNTAX InetAddressIPv6 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "An RPL parent associated with this DODAG." 750 ::= { rplDodagParentEntry 1 } 752 rplDodagParentIf OBJECT-TYPE 753 SYNTAX InterfaceIndex 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "The interface over which the parent can be reached." 758 ::= { rplDodagParentEntry 2 } 760 rplDodagChildTable OBJECT-TYPE 761 SYNTAX SEQUENCE OF RplDodagChildEntry 762 MAX-ACCESS not-accessible 763 STATUS current 764 DESCRIPTION 765 "The list of children for a DODAG." 766 ::= { rplObjects 7 } 768 rplDodagChildEntry OBJECT-TYPE 769 SYNTAX RplDodagChildEntry 770 MAX-ACCESS not-accessible 771 STATUS current 772 DESCRIPTION 773 "Information about a known DODAG child." 774 INDEX { rplRPLInstanceID, rplDodagRoot, rplDodagChildID } 775 ::= { rplDodagChildTable 1 } 777 RplDodagChildEntry ::= SEQUENCE { 778 rplDodagChildID InetAddressIPv6 779 } 781 rplDodagChildID OBJECT-TYPE 782 SYNTAX InetAddressIPv6 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION 786 "An RPL child associated with this DODAG." 787 ::= { rplDodagChildEntry 1 } 789 rplDodagPrefixTable OBJECT-TYPE 790 SYNTAX SEQUENCE OF RplDodagPrefixEntry 791 MAX-ACCESS not-accessible 792 STATUS current 793 DESCRIPTION 794 "List of prefixes associated with a DODAG." 795 ::= { rplObjects 8 } 796 -- XXX Explain how this relates to the ipAddressPrefixTable in 797 -- XXX the IP-MIB 799 rplDodagPrefixEntry OBJECT-TYPE 800 SYNTAX RplDodagPrefixEntry 801 MAX-ACCESS not-accessible 802 STATUS current 803 DESCRIPTION 804 "Information about a prefix associated with a DODAG." 805 INDEX { rplRPLInstanceID, rplDodagRoot, 806 rplDodagPrefixIpv6Prefix, rplDodagPrefixIpv6PrefixLength } 807 ::= { rplDodagPrefixTable 1 } 809 RplDodagPrefixEntry ::= SEQUENCE { 810 rplDodagPrefixIpv6Prefix InetAddressIPv6, 811 rplDodagPrefixIpv6PrefixLength InetAddressPrefixLength 812 } 814 rplDodagPrefixIpv6Prefix OBJECT-TYPE 815 SYNTAX InetAddressIPv6 816 MAX-ACCESS read-only 817 STATUS current 818 DESCRIPTION 819 "The IPv6 address forming the IPv6 prefix." 820 ::= { rplDodagPrefixEntry 1 } 822 rplDodagPrefixIpv6PrefixLength OBJECT-TYPE 823 SYNTAX InetAddressPrefixLength 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "The length of the IPv6 prefix." 828 ::= { rplDodagPrefixEntry 2 } 830 rplStats OBJECT IDENTIFIER ::= { rplObjects 9 } 832 rplMemOverflows OBJECT-TYPE 833 SYNTAX Counter32 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "The number of memory allocation failures (e.g., routing table 838 overflows)." 839 ::= { rplStats 1 } 841 rplParseErrors OBJECT-TYPE 842 SYNTAX Counter32 843 MAX-ACCESS read-only 844 STATUS current 845 DESCRIPTION 846 "The number of received malformed messages." 847 ::= { rplStats 2 } 849 rplUnknownMsgTypes OBJECT-TYPE 850 SYNTAX Counter32 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The number of received RPL messages that we dropped because 855 the message type is not recognized by the implementation." 856 ::= { rplStats 3 } 858 rplSecurityPolicyViolations OBJECT-TYPE 859 SYNTAX Counter32 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 "The number of messages discarded because the described level 864 of security for the message type and originator is unknown or 865 does not meet locally maintained security policies as defined 866 in Section 10.7. of RFC YYYY." 867 ::= { rplStats 4 } 869 rplIntegrityCheckFailures OBJECT-TYPE 870 SYNTAX Counter32 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "The number of messages discarded because the integrity 875 check failed against the received message authentication 876 code (MAC) as defined in Section 10.7. of RFC YYYY." 877 ::= { rplStats 5 } 879 rplReplayProtectionFailures OBJECT-TYPE 880 SYNTAX Counter32 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION 884 "The number of messages discarded because the received 885 message Counter value is non-zero and less than the 886 maintained incoming Counter watermark or because the 887 received Timestamp Counter value indicates a message 888 transmission time that is earlier than the Current time 889 less the acceptable packet delay as defined in Section 890 10.7. of RFC YYYY. This counter is also incremented if the 891 temporal consistency check of the message fails as defined 892 in Section 10.7.1." 893 ::= { rplStats 6 } 895 rplValidParentFailures OBJECT-TYPE 896 SYNTAX Counter32 897 MAX-ACCESS read-only 898 STATUS current 899 DESCRIPTION 900 "The number of times a packet could not be sent to a DODAG 901 parent flagged as valid." 902 ::= { rplStats 7 } 904 rplNoInstanceIDs OBJECT-TYPE 905 SYNTAX Counter32 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "The number of times a packet could not be sent because of 910 a missing RPLInstanceID." 911 ::= { rplStats 8 } 913 rplTriggeredLocalRepairs OBJECT-TYPE 914 SYNTAX Counter32 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "The number of times a local repair procedure was triggered." 919 ::= { rplStats 9 } 921 rplTriggeredGlobalRepairs OBJECT-TYPE 922 SYNTAX Counter32 923 MAX-ACCESS read-only 924 STATUS current 925 DESCRIPTION 926 "The number of times a global repair procedure was triggered." 927 ::= { rplStats 10 } 929 rplNoParentSecs OBJECT-TYPE 930 SYNTAX Counter32 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "The number of seconds without a next hop (DODAG parent)." 935 ::= { rplStats 11 } 937 rplActiveNoParentSecs OBJECT-TYPE 938 SYNTAX Counter32 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "The number of seconds with packets to forward without a 943 next hop (DODAG parent)." 944 ::= { rplStats 12 } 946 rplOBitSetDownwards OBJECT-TYPE 947 SYNTAX Counter32 948 MAX-ACCESS read-only 949 STATUS current 950 DESCRIPTION 951 "Number of packets received with the 'O' bit set from 952 a node with a higher rank as defined in Section 18.3.2 953 of RFC YYYY." 954 ::= { rplStats 13 } 956 rplOBitClearedUpwards OBJECT-TYPE 957 SYNTAX Counter32 958 MAX-ACCESS read-only 959 STATUS current 960 DESCRIPTION 961 "Number of packets received with the 'O' bit cleared 962 from a node with a lower rank as defined in Section 18.3.2 963 of RFC YYYY." 964 ::= { rplStats 14 } 966 rplFBitSet OBJECT-TYPE 967 SYNTAX Counter32 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "Number of packets received with the 'F' bit set as 972 defined in Section 18.3.2 of RFC YYYY." 973 ::= { rplStats 15 } 975 rplRBitSet OBJECT-TYPE 976 SYNTAX Counter32 977 MAX-ACCESS read-only 978 STATUS current 979 DESCRIPTION 980 "Number of packets received with the 'R' bit set as 981 defined in Section 18.3.2 of RFC YYYY." 982 ::= { rplStats 16 } 984 rplTrickleTimerResets OBJECT-TYPE 985 SYNTAX Counter32 986 MAX-ACCESS read-only 987 STATUS current 988 DESCRIPTION 989 "The number of trickle timer resets." 990 ::= { rplStats 17 } 992 rplMsgStatsTable OBJECT-TYPE 993 SYNTAX SEQUENCE OF RplMsgStatsEntry 994 MAX-ACCESS not-accessible 995 STATUS current 996 DESCRIPTION 997 "Basic RPL message statistics by message type." 998 ::= { rplObjects 10 } 1000 rplMsgStatsEntry OBJECT-TYPE 1001 SYNTAX RplMsgStatsEntry 1002 MAX-ACCESS not-accessible 1003 STATUS current 1004 DESCRIPTION 1005 "Statistics for a specific RPL message type." 1006 INDEX { rplMsgStatsType } 1007 ::= { rplMsgStatsTable 1 } 1009 RplMsgStatsEntry ::= SEQUENCE { 1010 rplMsgStatsType RplMessageType, 1011 rplMsgStatsInMsgs Counter32, 1012 rplMsgStatsOutMsgs Counter32 1013 } 1015 rplMsgStatsType OBJECT-TYPE 1016 SYNTAX RplMessageType 1017 MAX-ACCESS not-accessible 1018 STATUS current 1019 DESCRIPTION 1020 "The RPL message type being counted by this row." 1021 ::= { rplMsgStatsEntry 1 } 1023 rplMsgStatsInMsgs OBJECT-TYPE 1024 SYNTAX Counter32 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "The number of RPL messages received of this type." 1029 ::= { rplMsgStatsEntry 2 } 1031 rplMsgStatsOutMsgs OBJECT-TYPE 1032 SYNTAX Counter32 1033 MAX-ACCESS read-only 1034 STATUS current 1035 DESCRIPTION 1036 "The number of RPL messages sent of this type." 1037 ::= { rplMsgStatsEntry 3 } 1039 rplGroups OBJECT IDENTIFIER ::= { rplConformance 1 } 1040 rplCompliances OBJECT IDENTIFIER ::= { rplConformance 2 } 1042 rplFullCompliance MODULE-COMPLIANCE 1043 STATUS current 1044 DESCRIPTION 1045 "Compliance statement for implementations supporting 1046 read/write access, according to the object definitions." 1047 MODULE -- this module 1048 MANDATORY-GROUPS { 1049 rplGeneralGroup, 1050 rplInstanceGroup, 1051 rplStatsGroup 1052 } 1053 ::= { rplCompliances 1 } 1055 rplReadOnlyCompliance MODULE-COMPLIANCE 1056 STATUS current 1057 DESCRIPTION 1058 "Compliance statement for implementations supporting 1059 only readonly access." 1060 MODULE -- this module 1061 MANDATORY-GROUPS { 1062 rplGeneralGroup, 1063 rplInstanceGroup, 1064 rplStatsGroup 1065 } 1067 OBJECT rplDefaultDISMode 1068 MIN-ACCESS read-only 1069 DESCRIPTION 1070 "Write access is not required." 1072 OBJECT rplActiveInstance 1073 MIN-ACCESS read-only 1074 DESCRIPTION 1075 "Write access is not required." 1077 OBJECT rplActiveDodag 1078 MIN-ACCESS read-only 1079 DESCRIPTION 1080 "Write access is not required." 1082 OBJECT rplActiveDodagTriggerSequence 1083 MIN-ACCESS read-only 1084 DESCRIPTION 1085 "Write access is not required." 1087 OBJECT rplOCPEnabled 1088 MIN-ACCESS read-only 1089 DESCRIPTION 1090 "Write access is not required." 1092 OBJECT rplRPLInstanceOCP 1093 MIN-ACCESS read-only 1094 DESCRIPTION 1095 "Write access is not required." 1097 OBJECT rplRPLInstanceDisMode 1098 MIN-ACCESS read-only 1099 DESCRIPTION 1100 "Write access is not required." 1102 OBJECT rplRPLInstanceDAOAcknowledgement 1103 MIN-ACCESS read-only 1104 DESCRIPTION 1105 "Write access is not required." 1107 OBJECT rplRPLInstanceModeOfOperation 1108 MIN-ACCESS read-only 1109 DESCRIPTION 1110 "Write access is not required." 1112 OBJECT rplDodagIntervalDoublings 1113 MIN-ACCESS read-only 1114 DESCRIPTION 1115 "Write access is not required." 1117 OBJECT rplDodagIntervalMin 1118 MIN-ACCESS read-only 1119 DESCRIPTION 1120 "Write access is not required." 1122 OBJECT rplDodagRedundancyConstant 1123 MIN-ACCESS read-only 1124 DESCRIPTION 1125 "Write access is not required." 1127 ::= { rplCompliances 2 } 1129 rplGeneralGroup OBJECT-GROUP 1130 OBJECTS { 1131 rplDefaultDISMode, 1132 rplActiveInstance, 1133 rplActiveDodag, 1134 rplActiveDodagDAOSequence, 1135 rplActiveDodagTriggerSequence, 1136 -- rplOCPCodepoint, 1137 rplOCPEnabled 1138 } 1139 STATUS current 1140 DESCRIPTION 1141 "A collection of objects providing general information about 1142 the RPL implementation." 1143 ::= { rplGroups 1 } 1145 rplInstanceGroup OBJECT-GROUP 1146 OBJECTS { 1147 -- rplRPLInstanceID, 1148 rplRPLInstanceOCP, 1149 rplRPLInstanceDisMode, 1150 rplRPLInstanceDAOAcknowledgement, 1151 rplRPLInstanceModeOfOperation, 1152 -- rplDodagRoot, 1153 rplDodagVersion, 1154 rplDodagRank, 1155 rplDodagState, 1156 rplDodagDAODelay, 1157 rplDodagPreference, 1158 rplDodagMinHopRankIncrease, 1159 rplDodagMaxRankIncrease, 1160 rplDodagIntervalDoublings, 1161 rplDodagIntervalMin, 1162 rplDodagRedundancyConstant, 1163 rplDodagPathControlSize, 1164 -- rplDodagParentID, 1165 rplDodagParentIf, 1166 rplDodagChildID, 1167 rplDodagPrefixIpv6Prefix, 1168 rplDodagPrefixIpv6PrefixLength 1169 } 1170 STATUS current 1171 DESCRIPTION 1172 "A collection of objects providing insight into the RPL 1173 Instances and the DODAGs." 1174 ::= { rplGroups 2 } 1176 rplStatsGroup OBJECT-GROUP 1177 OBJECTS { 1178 rplMemOverflows, 1179 rplParseErrors, 1180 rplUnknownMsgTypes, 1181 rplSecurityPolicyViolations, 1182 rplIntegrityCheckFailures, 1183 rplReplayProtectionFailures, 1184 rplValidParentFailures, 1185 rplNoInstanceIDs, 1186 rplTriggeredLocalRepairs, 1187 rplTriggeredGlobalRepairs, 1188 rplNoParentSecs, 1189 rplActiveNoParentSecs, 1190 rplOBitSetDownwards, 1191 rplOBitClearedUpwards, 1192 rplFBitSet, 1193 rplRBitSet, 1194 rplTrickleTimerResets, 1195 -- rplMsgStatsType, 1196 rplMsgStatsInMsgs, 1197 rplMsgStatsOutMsgs 1198 } 1199 STATUS current 1200 DESCRIPTION 1201 "A collection of objects providing statistics about the 1202 RPL implementation." 1203 ::= { rplGroups 3 } 1205 END 1207 7. Security Considerations 1209 There are a number of management objects defined in this MIB module 1210 with a MAX-ACCESS clause of read-write and/or read-create. Such 1211 objects may be considered sensitive or vulnerable in some network 1212 environments. The support for SET operations in a non-secure 1213 environment without proper protection can have a negative effect on 1214 network operations. These are the tables and objects and their 1215 sensitivity/vulnerability: 1217 o rplActiveInstance: [ TBD ] explain sensitivity 1219 Some of the readable objects in this MIB module (i.e., objects with a 1220 MAX-ACCESS other than not-accessible) may be considered sensitive or 1221 vulnerable in some network environments. It is thus important to 1222 control even GET and/or NOTIFY access to these objects and possibly 1223 to even encrypt the values of these objects when sending them over 1224 the network via SNMP. These are the tables and objects and their 1225 sensitivity/vulnerability: 1227 [TODO: Need to describe vulnerabilities here.] 1229 SNMP versions prior to SNMPv3 did not include adequate security. 1230 Even if the network itself is secure (for example by using IPsec), 1231 even then, there is no control as to who on the secure network is 1232 allowed to access and GET/SET (read/change/create/delete) the objects 1233 in this MIB module. 1235 It is RECOMMENDED that implementers consider the security features as 1236 provided by the SNMPv3 framework (see [RFC3410], section 8), 1237 including full support for the SNMPv3 cryptographic mechanisms (for 1238 authentication and privacy). 1240 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1241 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1242 enable cryptographic security. It is then a customer/operator 1243 responsibility to ensure that the SNMP entity giving access to an 1244 instance of this MIB module is properly configured to give access to 1245 the objects only to those principals (users) that have legitimate 1246 rights to indeed GET or SET (change/create/delete) them. 1248 8. IANA Considerations 1250 IANA is requested to assign a value for "XXXX" under the 'mib-2' 1251 subtree and to record the assignment in the SMI Numbers registry. 1252 When the assignment has been made, the RFC Editor is asked to replace 1253 "XXXX" (here and in the MIB module) with the assigned value and to 1254 remove this note. 1256 IANA has allocated a number for RPL in the IANAipRouteProtocol 1257 textual convention of the IANA-RTPROTO-MIB. 1259 9. Acknowledgements 1261 Thanks to Michael Richardson for helpful comments during the 1262 development of this specification. 1264 10. References 1266 10.1. Normative References 1268 [RFC2119] Bradner, S., "Key words for use in RFCs to 1269 Indicate Requirement Levels", BCP 14, RFC 2119, 1270 March 1997. 1272 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1273 Schoenwaelder, Ed., "Structure of Management 1274 Information Version 2 (SMIv2)", STD 58, 1275 RFC 2578, April 1999. 1277 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1278 Schoenwaelder, Ed., "Textual Conventions for 1279 SMIv2", STD 58, RFC 2579, April 1999. 1281 [RFC2580] McCloghrie, K., Perkins, D., and J. 1282 Schoenwaelder, "Conformance Statements for 1283 SMIv2", STD 58, RFC 2580, April 1999. 1285 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1286 Interfaces Group MIB", RFC 2863, June 2000. 1288 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1289 Schoenwaelder, "Textual Conventions for Internet 1290 Network Addresses", RFC 4001, February 2005. 1292 [RFC4292] Haberman, B., "IP Forwarding Table MIB", 1293 RFC 4292, April 2006. 1295 [RFC6206] Levis, P., Clausen, T., Hui, J., Gnawali, O., 1296 and J. Ko, "The Trickle Algorithm", RFC 6206, 1297 March 2011. 1299 [I-D.ietf-roll-rpl] Brandt, A., Vasseur, J., Hui, J., Pister, K., 1300 Thubert, P., Levis, P., Struik, R., Kelsey, R., 1301 Clausen, T., and T. Winter, "RPL: IPv6 Routing 1302 Protocol for Low power and Lossy Networks", 1303 draft-ietf-roll-rpl-19 (work in progress), 1304 March 2011. 1306 10.2. Informative References 1308 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 1309 Stewart, "Introduction and Applicability 1310 Statements for Internet-Standard Management 1311 Framework", RFC 3410, December 2002. 1313 Appendix A. Open Issues 1315 Should we model objective functions, e.g. by introducing a table 1316 that includes things such as MinHopRankIncrease and 1317 MaxRankIncrease 1319 Authors' Addresses 1321 Kevin Korte 1322 Jacobs University 1323 Campus Ring 1 1324 Bremen 28759 1325 Germany 1327 EMail: k.korte@jacobs-university.de 1329 Juergen Schoenwaelder 1330 Jacobs University 1331 Campus Ring 1 1332 Bremen 28759 1333 Germany 1335 EMail: j.schoenwaelder@jacobs-university.de 1337 Anuj Sehgal 1338 Jacobs University 1339 Campus Ring 1 1340 Bremen 28759 1341 Germany 1343 EMail: s.anuj@jacobs-university.de 1345 Tina Tsou 1346 Huawei Technologies (USA) 1347 2330 Central Expressway 1348 Santa Clara CA 95050 1349 USA 1351 EMail: tina.tsou.zouting@huawei.com 1353 Cathy Zhou 1354 Huawei Technologies 1355 Bantian, Longgang District 1356 Shenzhen 518129 1357 P.R. China 1359 EMail: cathyzhou@huawei.com