idnits 2.17.1 draft-sehgal-roll-rpl-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 == Line 124 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 (October 15, 2010) is 4941 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'TBD' is mentioned on line 582, but not defined == Outdated reference: A later version (-19) exists of draft-ietf-roll-rpl-12 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). 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: April 18, 2011 Jacobs University 6 October 15, 2010 8 Definition of Managed Objects for the IPv6 Routing Protocol for Low 9 power and Lossy Networks (RPL) 10 draft-sehgal-roll-rpl-mib-00 12 Abstract 14 This memo defines a portion of the Management Information Base (MIB) 15 for use with network management protocols in the Internet community. 16 In particular, it defines objects for managing the IPv6 Routing 17 Protocol for Low power and Lossy Networks (RPL). 19 Status of This Memo 21 This Internet-Draft is submitted to IETF in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 This Internet-Draft will expire on April 18, 2011. 42 Copyright Notice 44 Copyright (c) 2010 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. The Internet-Standard Management Framework . . . . . . . . . . 3 61 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 4 64 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 66 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 67 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 68 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 69 9.2. Informative References . . . . . . . . . . . . . . . . . . 15 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) [ID-RPL]. 78 2. The Internet-Standard Management Framework 80 For a detailed overview of the documents that describe the current 81 Internet-Standard Management Framework, please refer to section 7 of 82 RFC 3410 [RFC3410]. 84 Managed objects are accessed via a virtual information store, termed 85 the Management Information Base or MIB. MIB objects are generally 86 accessed through the Simple Network Management Protocol (SNMP). 87 Objects in the MIB are defined using the mechanisms defined in the 88 Structure of Management Information (SMI). This memo specifies a MIB 89 module that is compliant to the SMIv2, which is described in STD 58, 90 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 91 [RFC2580]. 93 3. Conventions 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 97 document are to be interpreted as described in RFC 2119 [RFC2119]. 99 4. Overview 101 The MIB module is organized into a group of scalars and tables. 103 +--rplObjects(1) 104 | 105 +-- rwn RplInstanceID rplActiveInstance(1) 106 | 107 +--rplDodagTable(2) 108 | | 109 | +--rplDodagEntry(1) [rplDodagInstanceID] 110 | | 111 | +-- --- RplInstanceID rplDodagInstanceID(1) 112 | +-- r-n InetAddressIPv6 rplDodagRoot(2) 113 | +-- r-n RplDodagVersionNumber rplDodagVersion(3) 114 | +-- r-n RplRank rplDodagRank(4) 115 | +-- r-n RplObjectiveCodePoint rplDodagOCP(5) 116 | +-- r-n InetAddressIPv6 rplDodagParent(6) 117 | +-- r-n Enumeration rplDodagState(7) 118 | 119 +--rplDodagParentTable(3) 120 | | 121 | +--rplDodagParentEntry(1) [rplDodagInstanceID,rplDodagParentID] 122 | | 123 | +-- r-n InetAddressIPv6 rplDodagParentID(1) 124 | +-- r-n InterfaceIndex rplDodagParentIf(2) 125 | 126 +--rplDodagChildTable(4) 127 | | 128 | +--rplDodagChildEntry(1) [rplDodagInstanceID,rplDodagChildID] 129 | | 130 | +-- r-n InetAddressIPv6 rplDodagChildID(1) 131 | 132 +--rplStats(5) 133 | 134 +-- r-n Counter32 rplStatsMemOverflows(1) 135 +-- r-n Counter32 rplStatsValidParentFailures(2) 136 +-- r-n Counter32 rplStatsNoInstanceIDs(3) 137 +-- r-n Counter32 rplStatsTriggeredLocalRepairs(4) 138 +-- r-n Counter32 rplStatsTriggeredGlobalRepairs(5) 139 +-- r-n Counter32 rplStatsParseErrors(6) 140 +-- r-n Counter32 rplStatsNoParentSecs(7) 141 +-- r-n Counter32 rplStatsActiveNoParentSecs(8) 143 5. Relationship to Other MIB Modules 145 The MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-TC 146 [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and the INET- 147 ADDRESS-MIB [RFC4001]. 149 6. Definitions 150 RPL-MIB DEFINITIONS ::= BEGIN 152 IMPORTS 153 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2 154 FROM SNMPv2-SMI -- RFC 2578 155 TEXTUAL-CONVENTION 156 FROM SNMPv2-TC -- RFC 2579 157 OBJECT-GROUP, MODULE-COMPLIANCE 158 FROM SNMPv2-CONF -- RFC 2580 159 InterfaceIndex 160 FROM IF-MIB -- RFC 2863 161 InetAddressIPv6 162 FROM INET-ADDRESS-MIB; -- RFC 4001 164 rplMib MODULE-IDENTITY 165 LAST-UPDATED "201010151600Z" 166 ORGANIZATION 167 "Jacobs University Bremen" 168 CONTACT-INFO 169 "Kevin Dominik Korte 170 Jacobs University Bremen 171 Email: k.korte@jacobs-university.de 173 Anuj Sehgal 174 Jacobs University Bremen 175 Email: s.anuj@jacobs-university.de 177 Juergen Schoenwaelder 178 Jacobs University Bremen 179 Email: j.schoenwaelder@jacobs-university.de" 180 DESCRIPTION 181 "The MIB module for monitoring nodes implementing the IPv6 182 routing protocol for low power and lossy networks (RPL). 184 Copyright (c) 2010 IETF Trust and the persons identified as 185 authors of the code. All rights reserved. 187 Redistribution and use in source and binary forms, with or 188 without modification, is permitted pursuant to, and subject 189 to the license terms contained in, the Simplified BSD 190 License set forth in Section 4.c of the IETF Trust's 191 Legal Provisions Relating to IETF Documents 192 (http://trustee.ietf.org/license-info)." 194 REVISION "201010151600Z" 195 DESCRIPTION 196 "Initial version, published as RFC XXXX." 197 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 198 ::= { mib-2 XXXX } 200 RplInstanceID ::= TEXTUAL-CONVENTION 201 DISPLAY-HINT "d" 202 STATUS current 203 DESCRIPTION 204 "A global or local RPLinstanceID as defined in Section 5.1. of 205 RFC YYYY." 206 REFERENCE 207 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 208 SYNTAX Unsigned32 (0..255) 210 RplDodagVersionNumber ::= TEXTUAL-CONVENTION 211 DISPLAY-HINT "d" 212 STATUS current 213 DESCRIPTION 214 "The version number of a DODAG." 215 REFERENCE 216 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 217 SYNTAX Unsigned32 (0..255) 219 RplRank ::= TEXTUAL-CONVENTION 220 DISPLAY-HINT "d" 221 STATUS current 222 DESCRIPTION 223 "The rank of a node within a DODAG." 224 REFERENCE 225 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 226 SYNTAX Unsigned32 (0..65535) 228 RplObjectiveCodePoint ::= TEXTUAL-CONVENTION 229 DISPLAY-HINT "d" 230 STATUS current 231 DESCRIPTION 232 "The Objective Code Point of a DODAG." 233 REFERENCE 234 "RFC YYYY: RPL: IPv6 Routing Protocol for LLNs" 235 SYNTAX Unsigned32 (0..65535) 237 -- object definitions 239 rplNotifications OBJECT IDENTIFIER ::= { rplMib 0 } 240 rplObjects OBJECT IDENTIFIER ::= { rplMib 1 } 241 rplConformance OBJECT IDENTIFIER ::= { rplMib 2 } 243 rplActiveInstance OBJECT-TYPE 244 SYNTAX RplInstanceID 245 MAX-ACCESS read-write 246 STATUS current 247 DESCRIPTION 248 "The currently active RPL Instance." 249 ::= { rplObjects 1 } 251 rplDodagTable OBJECT-TYPE 252 SYNTAX SEQUENCE OF RplDodagEntry 253 MAX-ACCESS not-accessible 254 STATUS current 255 DESCRIPTION 256 "The table represents information about all locally known 257 DODAGs." 258 ::= { rplObjects 2 } 260 rplDodagEntry OBJECT-TYPE 261 SYNTAX RplDodagEntry 262 MAX-ACCESS not-accessible 263 STATUS current 264 DESCRIPTION 265 "An entry representing information about a DODAG." 266 INDEX { rplDodagInstanceID } 267 ::= { rplDodagTable 1 } 269 RplDodagEntry ::= SEQUENCE { 270 rplDodagInstanceID RplInstanceID, 271 rplDodagRoot InetAddressIPv6, 272 rplDodagVersion RplDodagVersionNumber, 273 rplDodagRank RplRank, 274 rplDodagOCP RplObjectiveCodePoint, 275 rplDodagState INTEGER 276 } 278 rplDodagInstanceID OBJECT-TYPE 279 SYNTAX RplInstanceID 280 MAX-ACCESS not-accessible 281 STATUS current 282 DESCRIPTION 283 "The InstanceID of this RPL Instance." 284 ::= { rplDodagEntry 1 } 286 rplDodagRoot OBJECT-TYPE 287 SYNTAX InetAddressIPv6 288 MAX-ACCESS read-only 289 STATUS current 290 DESCRIPTION 291 "The DODAGID in the currently active RPL instance. The 292 root of the DODAG reports its own IPv6 address as the 293 DODAG root." 295 ::= { rplDodagEntry 2 } 297 rplDodagVersion OBJECT-TYPE 298 SYNTAX RplDodagVersionNumber 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "The version of the DODAG in this RPL instance." 303 ::= { rplDodagEntry 3 } 305 rplDodagRank OBJECT-TYPE 306 SYNTAX RplRank 307 MAX-ACCESS read-only 308 STATUS current 309 DESCRIPTION 310 "The rank of the node within the DODAG." 311 ::= { rplDodagEntry 4 } 313 rplDodagOCP OBJECT-TYPE 314 SYNTAX RplObjectiveCodePoint 315 MAX-ACCESS read-only 316 STATUS current 317 DESCRIPTION 318 "The Objective Code Point used by this DODAG." 319 ::= { rplDodagEntry 5 } 321 rplDodagState OBJECT-TYPE 322 SYNTAX INTEGER { 323 other(0), 324 associated(1), 325 grounded(2), 326 floating(3) 327 } 328 MAX-ACCESS read-only 329 STATUS current 330 DESCRIPTION 331 "The status of the DODAG: 333 other(0) An unknown state. 335 associated(1) A node is associated with the RPL instance. 337 grounded(2) The DODAG is grounded. 339 floating(3) The DODAG is floating (not grounded). 340 " 341 ::= { rplDodagEntry 6 } 343 rplDodagParentTable OBJECT-TYPE 344 SYNTAX SEQUENCE OF RplDodagParentEntry 345 MAX-ACCESS not-accessible 346 STATUS current 347 DESCRIPTION 348 "The list of parents for a DODAG." 349 ::= { rplObjects 3 } 351 rplDodagParentEntry OBJECT-TYPE 352 SYNTAX RplDodagParentEntry 353 MAX-ACCESS not-accessible 354 STATUS current 355 DESCRIPTION 356 "Information about a known DODAG parent." 357 INDEX { rplDodagInstanceID, rplDodagParentID } 358 ::= { rplDodagParentTable 1 } 360 RplDodagParentEntry ::= SEQUENCE { 361 rplDodagParentID InetAddressIPv6, 362 rplDodagParentIf InterfaceIndex 363 } 365 rplDodagParentID OBJECT-TYPE 366 SYNTAX InetAddressIPv6 367 MAX-ACCESS read-only 368 STATUS current 369 DESCRIPTION 370 "An RPL parent associated with this RPL node." 371 ::= { rplDodagParentEntry 1 } 373 rplDodagParentIf OBJECT-TYPE 374 SYNTAX InterfaceIndex 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The interface over which the parent can be reached." 379 ::= { rplDodagParentEntry 2 } 381 rplDodagChildTable OBJECT-TYPE 382 SYNTAX SEQUENCE OF RplDodagChildEntry 383 MAX-ACCESS not-accessible 384 STATUS current 385 DESCRIPTION 386 "" 387 ::= { rplObjects 4 } 389 rplDodagChildEntry OBJECT-TYPE 390 SYNTAX RplDodagChildEntry 391 MAX-ACCESS not-accessible 392 STATUS current 393 DESCRIPTION 394 "" 395 INDEX { rplDodagInstanceID, rplDodagChildID } 396 ::= { rplDodagChildTable 1 } 398 RplDodagChildEntry ::= SEQUENCE { 399 rplDodagChildID InetAddressIPv6 400 } 402 rplDodagChildID OBJECT-TYPE 403 SYNTAX InetAddressIPv6 404 MAX-ACCESS read-only 405 STATUS current 406 DESCRIPTION 407 "An RPL child associated with this RPL node." 408 ::= { rplDodagChildEntry 1 } 410 rplStats OBJECT IDENTIFIER ::= { rplObjects 5 } 412 rplStatsMemOverflows OBJECT-TYPE 413 SYNTAX Counter32 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The number of memory allocation failures (e.g., routing table 418 overflows)." 419 ::= { rplStats 1 } 421 rplStatsValidParentFailures OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The number of times a packet could not be sent to a DODAG 427 parent flagged as valid." 428 ::= { rplStats 2 } 430 rplStatsNoInstanceIDs OBJECT-TYPE 431 SYNTAX Counter32 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The number of times a packet could not be sent because of 436 a missing RPLInstanceID." 437 ::= { rplStats 3 } 439 rplStatsTriggeredLocalRepairs OBJECT-TYPE 440 SYNTAX Counter32 441 MAX-ACCESS read-only 442 STATUS current 443 DESCRIPTION 444 "The number of times a local repair procedure was triggered." 445 ::= { rplStats 4 } 447 rplStatsTriggeredGlobalRepairs OBJECT-TYPE 448 SYNTAX Counter32 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The number of times a global repair procedure was triggered." 453 ::= { rplStats 5 } 455 rplStatsParseErrors OBJECT-TYPE 456 SYNTAX Counter32 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The number of received malformed messages." 461 ::= { rplStats 6 } 463 rplStatsNoParentSecs OBJECT-TYPE 464 SYNTAX Counter32 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The number of seconds without a next hop (DODAG parent)." 469 ::= { rplStats 7 } 471 rplStatsActiveNoParentSecs OBJECT-TYPE 472 SYNTAX Counter32 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The number of seconds with packets to forward without a 477 next hop (DODAG parent)." 478 ::= { rplStats 8 } 480 rplGroups OBJECT IDENTIFIER ::= { rplConformance 1 } 481 rplCompliances OBJECT IDENTIFIER ::= { rplConformance 2 } 483 rplCompliance MODULE-COMPLIANCE 484 STATUS current 485 DESCRIPTION 486 "" 488 MODULE -- this module 489 MANDATORY-GROUPS { 490 rplDodagGroup, 491 rplStatsGroup 492 } 493 ::= { rplCompliances 1 } 495 rplDodagGroup OBJECT-GROUP 496 OBJECTS { 497 rplActiveInstance, 498 -- rplDodagInstanceID 499 rplDodagRoot, 500 rplDodagVersion, 501 rplDodagRank, 502 rplDodagOCP, 503 rplDodagState, 504 rplDodagParentID, 505 rplDodagParentIf, 506 rplDodagChildID 507 } 508 STATUS current 509 DESCRIPTION 510 "A collection of objects providing insight into the DODAGs 511 known to the implementation." 512 ::= { rplGroups 1 } 514 rplStatsGroup OBJECT-GROUP 515 OBJECTS { 516 rplStatsMemOverflows, 517 rplStatsValidParentFailures, 518 rplStatsNoInstanceIDs, 519 rplStatsTriggeredLocalRepairs, 520 rplStatsTriggeredGlobalRepairs, 521 rplStatsParseErrors, 522 rplStatsNoParentSecs, 523 rplStatsActiveNoParentSecs 524 } 525 STATUS current 526 DESCRIPTION 527 "A collection of objects providing statistics about the 528 RPL implementation." 529 ::= { rplGroups 2 } 531 END 533 7. Security Considerations 535 There are a number of management objects defined in this MIB module 536 with a MAX-ACCESS clause of read-write and/or read-create. Such 537 objects may be considered sensitive or vulnerable in some network 538 environments. The support for SET operations in a non-secure 539 environment without proper protection can have a negative effect on 540 network operations. These are the tables and objects and their 541 sensitivity/vulnerability: 543 o rplActiveInstance: [TBD] explain sensitivity 545 Some of the readable objects in this MIB module (i.e., objects with a 546 MAX-ACCESS other than not-accessible) may be considered sensitive or 547 vulnerable in some network environments. It is thus important to 548 control even GET and/or NOTIFY access to these objects and possibly 549 to even encrypt the values of these objects when sending them over 550 the network via SNMP. These are the tables and objects and their 551 sensitivity/vulnerability: 553 o rplActiveInstance: [TBD] explain sensitivity 555 o rplDodagRoot: [TBD] explain sensitivity 557 o rplDodagVersion: [TBD] explain sensitivity 559 o rplDodagRank: [TBD] explain sensitivity 561 o rplDodagOCP: [TBD] explain sensitivity 563 o rplDodagState: [TBD] explain sensitivity 565 o rplDodagParentID: [TBD] explain sensitivity 567 o rplDodagChildID: [TBD] explain sensitivity 569 o rplStatsMemOverflows: [TBD] explain sensitivity 571 o rplStatsValidParentFailures: [TBD] explain sensitivity 573 o rplStatsNoInstanceIDs: [TBD] explain sensitivity 575 o rplStatsTriggeredLocalRepairs: [TBD] explain sensitivity 577 o rplStatsTriggeredGlobalRepairs: [TBD] explain sensitivity 579 o rplStatsParseErrors: [TBD] explain sensitivity 580 o rplStatsNoParentSecs: [TBD] explain sensitivity 582 o rplStatsActiveNoParentSecs: [TBD] explain sensitivity 584 SNMP versions prior to SNMPv3 did not include adequate security. 585 Even if the network itself is secure (for example by using IPsec), 586 even then, there is no control as to who on the secure network is 587 allowed to access and GET/SET (read/change/create/delete) the objects 588 in this MIB module. 590 It is RECOMMENDED that implementers consider the security features as 591 provided by the SNMPv3 framework (see [RFC3410], section 8), 592 including full support for the SNMPv3 cryptographic mechanisms (for 593 authentication and privacy). 595 Further, deployment of SNMP versions prior to SNMPv3 is NOT 596 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 597 enable cryptographic security. It is then a customer/operator 598 responsibility to ensure that the SNMP entity giving access to an 599 instance of this MIB module is properly configured to give access to 600 the objects only to those principals (users) that have legitimate 601 rights to indeed GET or SET (change/create/delete) them. 603 8. IANA Considerations 605 IANA is requested to assign a value for "XXX" under the 'mib-2' 606 subtree and to record the assignment in the SMI Numbers registry. 607 When the assignment has been made, the RFC Editor is asked to replace 608 "XXX" (here and in the MIB module) with the assigned value and to 609 remove this note. 611 9. References 613 9.1. Normative References 615 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 616 Requirement Levels", BCP 14, RFC 2119, March 1997. 618 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 619 Schoenwaelder, Ed., "Structure of Management Information 620 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 622 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 623 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 624 STD 58, RFC 2579, April 1999. 626 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 627 "Conformance Statements for SMIv2", STD 58, RFC 2580, 628 April 1999. 630 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 631 MIB", RFC 2863, June 2000. 633 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 634 Schoenwaelder, "Textual Conventions for Internet Network 635 Addresses", RFC 4001, February 2005. 637 [ID-RPL] Winter, T., Ed. and P. Thubert, Ed., "RPL: IPv6 Routing 638 Protocol for Low power and Lossy Networks", 639 draft-ietf-roll-rpl-12 (work in progress). 641 9.2. Informative References 643 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 644 "Introduction and Applicability Statements for Internet- 645 Standard Management Framework", RFC 3410, December 2002. 647 Authors' Addresses 649 Kevin Korte 650 Jacobs University 651 Campus Ring 1 652 Bremen 28759 653 Germany 655 EMail: k.korte@jacobs-university.de 657 Juergen Schoenwaelder 658 Jacobs University 659 Campus Ring 1 660 Bremen 28759 661 Germany 663 EMail: j.schoenwaelder@jacobs-university.de 665 Anuj Sehgal 666 Jacobs University 667 Campus Ring 1 668 Bremen 28759 669 Germany 671 EMail: s.anuj@jacobs-university.de