idnits 2.17.1 draft-ietf-manet-olsrv2-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. 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 1258 has weird spacing: '... "The is th...' == Line 1274 has weird spacing: '...AR_time is th...' == 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 (May 3, 2009) is 5472 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: 'TODO' is mentioned on line 1918, but not defined == Missing Reference: 'RFC4001' is mentioned on line 263, but not defined == Missing Reference: 'RFC5148' is mentioned on line 659, but not defined == Missing Reference: 'RFC 4001' is mentioned on line 1601, but not defined == Missing Reference: 'TODOs' is mentioned on line 2053, but not defined == Outdated reference: A later version (-19) exists of draft-ietf-manet-olsrv2-08 Summary: 1 error (**), 0 flaws (~~), 10 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force R. Cole 3 Internet-Draft Johns Hopkins University 4 Intended status: Standards Track T. Clausen 5 Expires: November 4, 2009 LIX, Ecole Polytechnique 6 May 3, 2009 8 Definition of Managed Objects for the MANET Optimized Link State Routing 9 Protocol version 2 10 draft-ietf-manet-olsrv2-mib-00 12 Status of This Memo 14 This Internet-Draft is submitted to IETF in full conformance with the 15 provisions of BCP 78 and BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on November 4, 2009. 35 Copyright Notice 37 Copyright (c) 2009 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents in effect on the date of 42 publication of this document (http://trustee.ietf.org/license-info). 43 Please review these documents carefully, as they describe your rights 44 and restrictions with respect to this document. 46 Abstract 48 This memo defines a portion of the Management Information Base (MIB) 49 for use with network management protocols in the Internet community. 50 In particular, it describes objects for configuring and managing 51 aspects of the Optimized Link State Routing protocol version 2. The 52 Optimized Link State Routing MIB also reports state information, 53 performance metrics, and notifications. In addition to 54 configuration, this additional state and performance information is 55 useful to management stations troubleshooting Mobile Ad-Hoc Networks 56 routing problems. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. The Internet-Standard Management Framework . . . . . . . . . . 3 62 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 4.1. OLSRv2 Management Model . . . . . . . . . . . . . . . . . 3 65 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 67 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 68 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 5 69 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 5 70 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 5 71 5.5. The Notifications Group . . . . . . . . . . . . . . . . . 5 72 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 73 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 5 74 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 5 75 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 6 76 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 77 8. Security Considerations . . . . . . . . . . . . . . . . . . . 40 78 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42 79 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 42 80 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 43 81 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43 82 12.1. Normative References . . . . . . . . . . . . . . . . . . . 43 83 12.2. Informative References . . . . . . . . . . . . . . . . . . 43 84 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 43 85 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 44 86 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 45 88 1. Introduction 90 This memo defines a portion of the Management Information Base (MIB) 91 for use with network management protocols in the Internet community. 92 In particular, it describes objects for configuring aspects of a 93 process implementing the Optimized Link State Routing Protocol 94 version 2 (OLSRv2) [I-D.ietf-manet-olsrv2]. OLSRv2 provides ... 96 2. The Internet-Standard Management Framework 98 For a detailed overview of the documents that describe the current 99 Internet-Standard Management Framework, please refer to section 7 of 100 RFC 3410 [RFC3410]. 102 Managed objects are accessed via a virtual information store, termed 103 the Management Information Base or MIB. MIB objects are generally 104 accessed through the Simple Network Management Protocol (SNMP). 105 Objects in the MIB are defined using the mechanisms defined in the 106 Structure of Management Information (SMI). This memo specifies a MIB 107 module that is compliant to the SMIv2, which is described in STD 58, 108 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 109 [RFC2580]. 111 3. Conventions 113 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 114 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 115 document are to be interpreted as described in RFC 2119 [RFC2119]. 117 4. Overview 119 Optimized Link State Routing (OLSR) protocol version 2 (OLSRv2) 120 provides ... 122 4.1. OLSRv2 Management Model 124 This section describes the management model for the OLSRv2 node 125 routing process. Specifically, ... 127 4.2. Terms 129 The following definitions apply throughout this document: 131 o Configuration Objects - switches, tables, objects which are 132 initialized to default settings or set through the management 133 interface defined by this MIB. 135 o Tunable Configuration Objects - objects whose values affect timing 136 or attempt bounds on the OLSRv2 routing process. 138 o State Objects - automatically generated values which define the 139 current operating state of the OLSRv2 routing process in the 140 router. 142 o Performance Objects - automatically generated values which help an 143 administrator or automated tool to assess the performance of the 144 OLSRv2 routing process on the router and the overall packet 145 forwarding performance within the MANET routing domain. 147 5. Structure of the MIB Module 149 This section presents the structure of the Optimized Link State 150 Routing version 2 Management Information Base (OLSRv2-MIB) module. 151 The objects are arranged into the following groups: 153 o olsrMIBNotifications - defines the notifications associated with 154 the OLSRv2-MIB. 156 o olsrMIBObjects - defines the objects forming the basis for the 157 OLSRv2-MIB. These objects are divided up by function into the 158 following groups: 160 o 162 * Configuration Group - This group contains the OLSRv2 objects 163 that configure specific options that determine the overall 164 operation of the OLSRv2 routing process and the unicast packet 165 forwarding performance. 167 * State Group - Contains information describing the current state 168 of the OLSRv2 routing process such as the ... 170 * Performance Group - Contains objects which help to characterize 171 the performance of the OLSRv2 routing process, typically 172 statistics counters. 174 o olsrMIBConformance - defines minimal and full conformance of 175 implementations to this OLSRv2-MIB. 177 5.1. Textual Conventions 179 The textual conventions used in the OLSRv2-MIB are as follows. The 180 RowStatus textual convention is imported from RFC 2579 [RFC2579]. 181 Further, ... 183 5.2. The Configuration Group 185 The OLSRv2 device is configured with a set of controls. The list of 186 configuration controls for the OLSRv2 device follow. 188 o ... 190 5.3. The State Group 192 The State Subtree reports current state information. Specifically, 193 ... 195 o ... 197 5.4. The Performance Group 199 The Performance subtree reports primarily counters that relate to 200 OLSRv2 routing performance. Specifically, ... 202 o ... 204 5.5. The Notifications Group 206 The Notifications Subtree contains the list of notifications 207 supported within the OLSRv2-MIB and their intended purpose or 208 utility. This group is currently empty. 210 6. Relationship to Other MIB Modules 212 [TODO]: The text of this section specifies the relationship of the 213 MIB modules contained in this document to other standards, 214 particularly to standards containing other MIB modules. Definitions 215 imported from other MIB modules and other MIB modules that SHOULD be 216 implemented in conjunction with the MIB module contained within this 217 document are identified in this section. 219 6.1. Relationship to the SNMPv2-MIB 221 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 222 mandatory for all systems, and the objects apply to the entity as a 223 whole. The 'system' group provides identification of the management 224 entity and certain other system-wide data. The OLSRv2-MIB does not 225 duplicate those objects. 227 6.2. Relationship to the IF-MIB 229 [TODO] This section is included as an example; If the MIB module is 230 not an adjunct of the Interface MIB, then this section should be 231 removed. 233 6.3. MIB modules required for IMPORTS 235 [TODO]: Citations are not permitted within a MIB module, but any 236 module mentioned in an IMPORTS clause or document mentioned in a 237 REFERENCE clause is a Normative reference, and must be cited 238 someplace within the narrative sections. If there are imported items 239 in the MIB module, such as Textual Conventions, that are not already 240 cited, they can be cited in text here. Since relationships to other 241 MIB modules should be described in the narrative text, this section 242 is typically used to cite modules from which Textual Conventions are 243 imported. 245 The following OLSRv2-MIB module IMPORTS objects from SNMPv2-SMI 246 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB 247 [RFC2863] 249 7. Definitions 251 MANET-OLSRv2-MIB DEFINITIONS ::= BEGIN 253 IMPORTS 254 MODULE-IDENTITY, OBJECT-TYPE, 255 Counter32, Unsigned32, mib-2 256 FROM SNMPv2-SMI -- [RFC2578] 257 TruthValue, RowStatus 258 FROM SNMPv2-TC -- [RFC2579] 259 MODULE-COMPLIANCE, OBJECT-GROUP 260 FROM SNMPv2-CONF -- [RFC2580] 261 InetAddress, InetAddressType, 262 InetAddressPrefixLength 263 FROM INET-ADDRESS-MIB -- [RFC4001] 264 NeighborNodeId 265 FROM NHDP-MIB -- [draft nhdp-mib] 266 ; 268 manetOlsrv2MIB MODULE-IDENTITY 269 LAST-UPDATED "200905031300Z" -- May 3, 2009 270 ORGANIZATION "IETF MANET Working Group" 271 CONTACT-INFO 272 "WG E-Mail: manet@ietf.org 274 WG Chairs: ian.chakeres@gmail.com 275 jmacker@nrl.navy.mil 277 Editors: Robert G. Cole 278 Johns Hopkins University 279 Applied Physics Lab and 280 Department of Computer Science 281 11000 Johns Hopkins Road 282 Room 02-257 283 Laurel, MD 22014 284 USA 285 +1 443 778-6951 286 robert.cole@jhuapl.edu 288 Thomas Heide Clausen 289 LIX, Ecole Polytechnique 290 France 291 T.Clausen@computer.org" 293 DESCRIPTION 294 "This MIB module contains managed object definitions 295 for the Manet OLSRv2 routing process defined in: 296 Clausen, T. et.al., Optimized Link State Routing 297 version 2 draft-ietf-manet-olsrv2-07, July 10, 2008. 299 Copyright (C) The IETF Trust (2009). This version 300 of this MIB module is part of RFC xxxx; see the RFC 301 itself for full legal notices." 303 -- Revision History 304 REVISION "200905031300Z" -- May 3, 2009 305 DESCRIPTION 306 "Third draft of this MIB module published as 307 draft-ietf-manet-olsrv2-mib-00.txt. Rev'd 308 as a new MANET WG document. Cleaned up SYNTAX 309 errors and other typos found by 'smilint'." 310 REVISION "200902151300Z" -- February 15, 2009 311 DESCRIPTION 312 "Second draft of this MIB module published as 313 draft-cole-manet-olsrv2-mib-01.txt. Cleaned up 314 table indexing and aligned with the NHDP-MIB 315 draft (draft-cole-manet-nhdp-mib-01.txt)." 316 REVISION "200810241300Z" -- October 24, 2008 317 DESCRIPTION 318 "Initial draft of this MIB module published as 319 draft-cole-manet-olsrv2-mib-00.txt." 320 -- RFC-Editor assigns XXXX 321 ::= { mib-2 998 } -- to be assigned by IANA 323 -- 324 -- TEXTUAL CONVENTIONs 325 -- 327 -- none 329 -- 330 -- Top-Level Object Identifier Assignments 331 -- 333 olsrv2MIBNotifications OBJECT IDENTIFIER ::= { manetOlsrv2MIB 0 } 334 olsrv2MIBObjects OBJECT IDENTIFIER ::= { manetOlsrv2MIB 1 } 335 olsrv2MIBConformance OBJECT IDENTIFIER ::= { manetOlsrv2MIB 2 } 337 -- 338 -- olsrv2ConfigurationGroup 339 -- 340 -- This group contains the OLSRv2 objects that configure specific 341 -- options that determine the overall performance and operation 342 -- of the unicast routing process for the router device 343 -- and its interfaces. 344 -- 346 olsrv2ConfigurationGroup OBJECT IDENTIFIER ::= {olsrv2MIBObjects 1} 348 olsrv2OperationalMode OBJECT-TYPE 349 SYNTAX INTEGER { 350 withNHDP(1) 351 } 352 MAX-ACCESS read-write 353 STATUS current 354 DESCRIPTION 355 "The OLSRv2 node operational mode. 357 The value withNHDP(1) indicates ..." 358 DEFVAL { 1 } 359 ::= { olsrv2ConfigurationGroup 1 } 361 -- Protocol Parameters for the OLSRv2 routing process. 362 -- These are categorized following Section 5 of the 363 -- OLSRv2 draft. 365 -- Local history times 366 olsrv2OHoldTime OBJECT-TYPE 367 SYNTAX Unsigned32 (0..255) 368 UNITS "seconds" 369 MAX-ACCESS read-write 370 STATUS current 371 DESCRIPTION 372 "The O_HOLD_TIME is used to define the time 373 for which a recently used and replaced 374 originator address is used to recognize 375 the node's own messages. 377 The following constraint applies to this 378 parameter: olsrv2OHoldTime >= 0" 379 REFERENCE 380 "The OLSR version 2 draft. 381 Section 5 on Protocol Parameters." 382 DEFVAL { 10 } 383 ::= { olsrv2ConfigurationGroup 2 } 385 -- Message intervals 387 olsrv2TcInterval OBJECT-TYPE 388 SYNTAX Unsigned32 (0..255) 389 UNITS "seconds" 390 MAX-ACCESS read-write 391 STATUS current 392 DESCRIPTION 393 "The TC_INTERVAL - is the maximum time 394 between the transmission of two successive 395 TC messages by this node. When no TC 396 messages are sent in response to local 397 network changes (by design, or because the 398 local network is not changing) then TC 399 messages SHOULD be sent at a regular 400 interval TC_INTERVAL, possibly modified 401 by jitter as specified in [RFC5148]. 403 The following constraint applies to this 404 parameter: 406 olsrv2TcInterval > 0 407 olsrv2TcInterval >= olsrv2TcMinInterval" 408 REFERENCE 409 "The OLSR version 2 draft. 410 Section 5 on Protocol Parameters." 411 DEFVAL { 10 } 413 ::= { olsrv2ConfigurationGroup 3 } 415 olsrv2TcMinInterval OBJECT-TYPE 416 SYNTAX Unsigned32 (0..255) 417 UNITS "seconds" 418 MAX-ACCESS read-write 419 STATUS current 420 DESCRIPTION 421 "The TC_MIN_INTERVAL is the minimum 422 interval between transmission of two 423 successive TC messages by this node. 424 (This minimum interval MAY be modified 425 by jitter, as specified in [RFC5148].) 427 The following constraint applies to this 428 parameter: 430 TC_MIN_INTERVAL >= 0 431 TC_INTERVAL >= TC_MIN_INTERVAL" 432 REFERENCE 433 "The OLSR version 2 draft. 434 Section 5 on Protocol Parameters." 435 DEFVAL { 10 } 436 ::= { olsrv2ConfigurationGroup 4 } 438 -- Advertised information validity times 440 olsrv2THoldTime OBJECT-TYPE 441 SYNTAX Unsigned32 (0..255) 442 UNITS "seconds" 443 MAX-ACCESS read-write 444 STATUS current 445 DESCRIPTION 446 "The olsrv2THoldTime is used to define the 447 minimum value in the VALIDITY_TIME TLV 448 included in all TC messages sent by this node. 449 If a single value of parameter TC_HOP_LIMIT 450 (see Section 5.6) is used then this will be 451 the only value in that TLV. 453 The following constraint applies to this 454 parameter: 456 T_HOLD_TIME > 0 457 A_HOLD_TIME >= 0 458 T_HOLD_TIME >= TC_INTERVAL 460 If TC messages can be lost, then both 461 T_HOLD_TIME and A_HOLD_TIME SHOULD be 462 significantly greater than TC_INTERVAL; 463 a value >= 3 x TC_INTERVAL is RECOMMENDED. 465 T_HOLD_TIME MUST be representable as 466 described in [timetlv]." 467 REFERENCE 468 "The OLSR version 2 draft. 469 Section 5 on Protocol Parameters." 470 DEFVAL { 10 } 471 ::= { olsrv2ConfigurationGroup 5 } 473 olsrv2AHoldTime OBJECT-TYPE 474 SYNTAX Unsigned32 (0..255) 475 UNITS "seconds" 476 MAX-ACCESS read-write 477 STATUS current 478 DESCRIPTION 479 "The olsrv2AHoldTime is the period during 480 which TC messages are sent after they no 481 longer have any advertised information 482 to report, but are sent in order to 483 accelerate outdated information removal by 484 other nodes. 486 The following constraint applies to this 487 parameter: 489 T_HOLD_TIME > 0 490 A_HOLD_TIME >= 0 491 T_HOLD_TIME >= TC_INTERVAL 493 If TC messages can be lost, then both 494 T_HOLD_TIME and A_HOLD_TIME SHOULD be 495 significantly greater than TC_INTERVAL; 496 a value >= 3 x TC_INTERVAL is RECOMMENDED. 498 T_HOLD_TIME MUST be representable as 499 described in [timetlv]." 500 REFERENCE 501 "The OLSR version 2 draft. 502 Section 5 on Protocol Parameters." 503 DEFVAL { 10 } 504 ::= { olsrv2ConfigurationGroup 6 } 506 -- Received message validity times 507 olsrv2RxHoldTime OBJECT-TYPE 508 SYNTAX Unsigned32 (0..255) 509 UNITS "seconds" 510 MAX-ACCESS read-write 511 STATUS current 512 DESCRIPTION 513 "The olsrv2RxHoldTime is an interface parameter, 514 and is the period after receipt of a message 515 by the appropriate OLSRv2 interface of this 516 node for which that information is recorded, 517 in order that the message is recognized as 518 having been previously received on this 519 OLSRv2 interface. 521 The following constraint applies to this 522 parameter: 524 RX_HOLD_TIME > 0 526 All of these parameters SHOULD be greater 527 than the maximum difference in time that a 528 message may take to traverse the MANET, 529 taking into account any message forwarding 530 jitter as well as propagation, queuing, 531 and processing delays." 532 REFERENCE 533 "The OLSR version 2 draft. 534 Section 5 on Protocol Parameters." 535 DEFVAL { 10 } 536 ::= { olsrv2ConfigurationGroup 7 } 538 olsrv2PHoldTime OBJECT-TYPE 539 SYNTAX Unsigned32 (0..255) 540 UNITS "seconds" 541 MAX-ACCESS read-write 542 STATUS current 543 DESCRIPTION 544 "The olsrv2PHoldTime is the period after 545 receipt of a message which is processed by 546 this node for which that information is 547 recorded, in order that the message is 548 not processed again if received again. 550 The following constraint applies to this 551 parameter: 553 P_HOLD_TIME > 0 555 All of these parameters SHOULD be greater 556 than the maximum difference in time that a 557 message may take to traverse the MANET, 558 taking into account any message forwarding 559 jitter as well as propagation, queuing, 560 and processing delays." 561 REFERENCE 562 "The OLSR version 2 draft. 563 Section 5 on Protocol Parameters." 564 DEFVAL { 10 } 565 ::= { olsrv2ConfigurationGroup 8 } 567 olsrv2FHoldTime OBJECT-TYPE 568 SYNTAX Unsigned32 (0..255) 569 UNITS "seconds" 570 MAX-ACCESS read-write 571 STATUS current 572 DESCRIPTION 573 "The olsrv2FHoldTime is the period after 574 receipt of a message which is forwarded 575 by this node for which that information 576 is recorded, in order that the message 577 is not forwarded again if received again. 579 The following constraint applies to this 580 parameter: 582 F_HOLD_TIME > 0 584 All of these parameters SHOULD be greater 585 than the maximum difference in time that a 586 message may take to traverse the MANET, 587 taking into account any message forwarding 588 jitter as well as propagation, queuing, 589 and processing delays." 590 REFERENCE 591 "The OLSR version 2 draft. 592 Section 5 on Protocol Parameters." 593 DEFVAL { 10 } 594 ::= { olsrv2ConfigurationGroup 9 } 596 -- Jitter times 598 olsrv2TpMaxJitter OBJECT-TYPE 599 SYNTAX Unsigned32 (0..65535) 600 UNITS "milliseconds" 601 MAX-ACCESS read-write 602 STATUS current 603 DESCRIPTION 604 "If jitter, as defined in [RFC5148], is used 605 then the jitter parameters are as follows: 607 olsrv2TpMaxJitter represents the value of 608 MAXJITTER used in [RFC5148] for periodically 609 generated TC messages sent by this node. 611 For constraints on these parameters, 612 see [RFC5148]." 613 REFERENCE 614 "The OLSR version 2 draft. 615 Section 5 on Protocol Parameters." 616 DEFVAL { 10 } 617 ::= { olsrv2ConfigurationGroup 10 } 619 olsrv2TtMaxJitter OBJECT-TYPE 620 SYNTAX Unsigned32 (0..65535) 621 UNITS "milliseconds" 622 MAX-ACCESS read-write 623 STATUS current 624 DESCRIPTION 625 "If jitter, as defined in [RFC5148], is used 626 then the jitter parameters are as follows: 628 olsrv2TtMaxJitter represents the value of 629 MAXJITTER used in [RFC5148] for externally 630 triggered TC messages sent by this node. 632 For constraints on these parameters, 633 see [RFC5148]." 634 REFERENCE 635 "The OLSR version 2 draft. 636 Section 5 on Protocol Parameters." 637 DEFVAL { 10 } 638 ::= { olsrv2ConfigurationGroup 11 } 640 olsrv2FMaxJitter OBJECT-TYPE 641 SYNTAX Unsigned32 (0..65535) 642 UNITS "milliseconds" 643 MAX-ACCESS read-write 644 STATUS current 645 DESCRIPTION 646 "If jitter, as defined in [RFC5148], is used 647 then the jitter parameters are as follows: 649 olsrv2FMaxJitter represents the default 650 value of MAXJITTER used in [RFC5148] for 651 messages forwarded by this node. However 652 before using F_MAXJITTER a node MAY attempt 653 to deduce a more appropriate value of MAXJITTER, 654 for example based on any INTERVAL_TIME or 655 VALIDITY_TIME TLVs contained in the message 656 to be forwarded. 658 For constraints on these parameters, 659 see [RFC5148]." 660 REFERENCE 661 "The OLSR version 2 draft. 662 Section 5 on Protocol Parameters." 663 DEFVAL { 10 } 664 ::= { olsrv2ConfigurationGroup 12 } 666 -- Hop limits 668 olsrv2TcHopLimit OBJECT-TYPE 669 SYNTAX Unsigned32 (0..255) 670 UNITS "hops" 671 MAX-ACCESS read-write 672 STATUS current 673 DESCRIPTION 674 "The parameter olsrv2TcHopLimit is the 675 hop limit set in each TC message. 676 TC_HOP_LIMIT MAY be a single fixed value, 677 or MAY be different in TC messages sent 678 by the same node. 680 The following constraint applies to this 681 parameter: 683 The maximum value of 684 olsrv2TcHopLimit >= the network diameter 685 in hops, a value of 255 is RECOMMENDED. 687 All values of olsrv2TcHopLimit >= 2." 688 REFERENCE 689 "The OLSR version 2 draft. 690 Section 5 on Protocol Parameters." 691 DEFVAL { 10 } 692 ::= { olsrv2ConfigurationGroup 13 } 694 -- Willingness 695 olsrv2Williness OBJECT-TYPE 696 SYNTAX Unsigned32 (0..255) 697 MAX-ACCESS read-write 698 STATUS current 699 DESCRIPTION 700 "The olsrv2Williness MUST be in the range 701 WILL_NEVER (0) to WILL_ALWAYS (255), inclusive, 702 and represents its willingness to be an MPR, 703 and hence its willingness to forward messages 704 and be an intermediate node on routes. 706 Note: Need to rethink the range and units for 707 this parameter." 708 REFERENCE 709 "The OLSR version 2 draft. 710 Section 5 on Protocol Parameters." 711 DEFVAL { 10 } 712 ::= { olsrv2ConfigurationGroup 14 } 714 -- Local Attached Network Set 716 -- This table is part of the OLSR/NHDP 717 -- Local Information Base (LIB). It is 718 -- placed in the Configuration Group because 719 -- this table contains configured information. 721 olsrv2LibLocAttNetSetTable OBJECT-TYPE 722 SYNTAX SEQUENCE OF Olsrv2LibLocAttNetSetEntry 723 MAX-ACCESS not-accessible 724 STATUS obsolete 725 DESCRIPTION 726 " A node's Local Attached Network Set records 727 its local non-OLSRv2 interfaces that can act 728 as gateways to other networks. The Local 729 Attached Network Set is not modified by this 730 protocol. This protocol MAY respond to changes 731 to the Local Attached Network Set, which MUST 732 reflect corresponding changes in the node's status. 734 Note: Need clarification on the above claim that 735 this set records interface information. The 736 tuple included in this set is only network 737 address information." 738 REFERENCE 739 "The OLSRv2 draft." 740 ::= { olsrv2ConfigurationGroup 15 } 741 olsrv2LibLocAttNetSetEntry OBJECT-TYPE 742 SYNTAX Olsrv2LibLocAttNetSetEntry 743 MAX-ACCESS not-accessible 744 STATUS current 745 DESCRIPTION 746 "The entries include the Local Attached 747 Network Tuples: 749 (AL_net_addr, AL_dist) 751 where: 753 AL_net_addr is the network address 754 of an attached network which can 755 be reached via this node. 757 AL_dist is the number of hops to 758 the network with address AL_net_addr 759 from this node." 760 REFERENCE 761 "The OLSRv2 draft." 762 INDEX { olsrv2LibLocAttNetSetIpAddr, 763 olsrv2LibLocAttNetSetIpAddrPrefixLen } 764 ::= { olsrv2LibLocAttNetSetTable 1 } 766 Olsrv2LibLocAttNetSetEntry ::= 767 SEQUENCE { 768 olsrv2LibLocAttNetSetIpAddrType 769 InetAddressType, 770 olsrv2LibLocAttNetSetIpAddr 771 InetAddress, 772 olsrv2LibLocAttNetSetIpAddrPrefixLen 773 InetAddressPrefixLength, 774 olsrv2LibLocAttNetSetDistance 775 Unsigned32, 776 olsrv2LibLocAttNetSetRowStatus 777 RowStatus 778 } 780 olsrv2LibLocAttNetSetIpAddrType OBJECT-TYPE 781 SYNTAX InetAddressType 782 MAX-ACCESS read-write 783 STATUS current 784 DESCRIPTION 785 "The type of the olsrv2LibLocAttNetSetIpAddr, as defined 786 in the InetAddress MIB [RFC 4001]." 787 REFERENCE 788 "The OLSRv2 draft." 790 ::= { olsrv2LibLocAttNetSetEntry 1 } 792 olsrv2LibLocAttNetSetIpAddr OBJECT-TYPE 793 SYNTAX InetAddress 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "This is the network address of an attached 798 network which can be reached via this node. 799 This node will act as a gateway for this 800 address for the OLSR MANET." 801 REFERENCE 802 "The OLSRv2 draft." 803 ::= { olsrv2LibLocAttNetSetEntry 2 } 805 olsrv2LibLocAttNetSetIpAddrPrefixLen OBJECT-TYPE 806 SYNTAX InetAddressPrefixLength 807 MAX-ACCESS not-accessible 808 STATUS current 809 DESCRIPTION 810 "Indicates the number of leading one bits that form the 811 mask to be logical-ANDed with the destination address 812 before being compared to the value in the 813 olsrv2LibLocAttNetSetIpAddr field." 814 REFERENCE 815 "The OLSRv2 draft." 816 ::= { olsrv2LibLocAttNetSetEntry 3 } 818 olsrv2LibLocAttNetSetDistance OBJECT-TYPE 819 SYNTAX Unsigned32 (1..255) 820 UNITS "hops" 821 MAX-ACCESS read-write 822 STATUS current 823 DESCRIPTION 824 "This object specifies the number of hops 825 to the network with address AL_net_addr 826 from this node." 827 REFERENCE 828 "The OLSRv2 draft." 829 ::= { olsrv2LibLocAttNetSetEntry 4 } 831 olsrv2LibLocAttNetSetRowStatus OBJECT-TYPE 832 SYNTAX RowStatus 833 MAX-ACCESS read-create 834 STATUS current 835 DESCRIPTION 836 "This object permits management of the table 837 by facilitating actions such as row creation, 838 construction, and destruction. The value of 839 this object has no effect on whether other 840 objects in this conceptual row can be 841 modified." 842 ::= { olsrv2LibLocAttNetSetEntry 5 } 844 -- 845 -- olsrv2StateGroup 846 -- 847 -- Contains information describing the current state of the 848 -- OLSRv2 routing process such as the ... 849 -- 851 -- 852 -- Note: the OLSRv2 draft discusses the option for dynamically 853 -- changing the values of the configuration parameters 854 -- identified above. In this case we would want to include 855 -- a set of state objects (potentially) which track the current 856 -- values or the range of values that these dynamic objects 857 -- have. 858 -- 860 olsrv2StateGroup OBJECT IDENTIFIER ::= { olsrv2MIBObjects 2 } 862 olsrv2NodeStatus OBJECT-TYPE 863 SYNTAX TruthValue 864 MAX-ACCESS read-only 865 STATUS current 866 DESCRIPTION 867 "The current status of the OLSRv2 node 868 routing process ..." 869 ::= { olsrv2StateGroup 1 } 871 -- 872 -- The OLSRv2 draft defines several information bases 873 -- to be maintained by the OLSRv2 compliant nodes. 874 -- We list these in the order defined in the OLSRv2 875 -- draft. 876 -- 878 -- 879 -- Local Information Base - as defined in [nhdp], 880 -- extended by the addition of an Originator Set, 881 -- defined in Section 6.1.1 and a Local Attached 882 -- Network Set, defined in Section 6.1.2. 884 -- 886 -- Originator Set 888 olsrv2LibOrigSetTable OBJECT-TYPE 889 SYNTAX SEQUENCE OF Olsrv2LibOrigSetEntry 890 MAX-ACCESS not-accessible 891 STATUS obsolete 892 DESCRIPTION 893 " A node's Originator Set records addresses 894 that were recently originator addresses. 895 If a node's originator address is immutable 896 then this set is always empty and MAY be 897 omitted. It consists of Originator Tuples: 898 (O_orig_addr, O_time)." 899 REFERENCE 900 "The OLSRv2 draft." 901 ::= { olsrv2StateGroup 2 } 903 olsrv2LibOrigSetEntry OBJECT-TYPE 904 SYNTAX Olsrv2LibOrigSetEntry 905 MAX-ACCESS not-accessible 906 STATUS current 907 DESCRIPTION 908 " A node's Originator Set records addresses 909 that were recently originator addresses. 910 If a node's originator address is immutable 911 then this set is always empty and MAY be 912 omitted. It consists of Originator Tuples: 913 (O_orig_addr, O_time)." 914 REFERENCE 915 "The OLSRv2 draft." 916 INDEX { olsrv2LibOrigSetIpAddr } 917 ::= { olsrv2LibOrigSetTable 1 } 919 Olsrv2LibOrigSetEntry ::= 920 SEQUENCE { 921 olsrv2LibOrigSetIpAddrType 922 InetAddressType, 923 olsrv2LibOrigSetIpAddr 924 InetAddress, 925 olsrv2LibOrigSetExpireTime 926 Unsigned32 927 } 929 olsrv2LibOrigSetIpAddrType OBJECT-TYPE 930 SYNTAX InetAddressType 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "The type of the olsrv2LibOrigSetIpAddr, as defined 935 in the InetAddress MIB [RFC 4001]." 936 REFERENCE 937 "The OLSRv2 draft." 938 ::= { olsrv2LibOrigSetEntry 1 } 940 olsrv2LibOrigSetIpAddr OBJECT-TYPE 941 SYNTAX InetAddress 942 MAX-ACCESS not-accessible 943 STATUS current 944 DESCRIPTION 945 "A recently used originator address 946 by this node." 947 REFERENCE 948 "The OLSRv2 draft." 949 ::= { olsrv2LibOrigSetEntry 2 } 951 olsrv2LibOrigSetExpireTime OBJECT-TYPE 952 SYNTAX Unsigned32 (0..65535) 953 UNITS "milliseconds" 954 MAX-ACCESS not-accessible 955 STATUS current 956 DESCRIPTION 957 "This object specifies the time at which this 958 entry expires and MUST be removed. 960 Note: need to change the type here to a time/date type, 961 not a time in seconds left to expire." 962 REFERENCE 963 "The OLSRv2 draft." 964 ::= { olsrv2LibOrigSetEntry 3 } 966 -- 967 -- Interface Information Bases - as defined in 968 -- [nhdp], one Interface Information Base for 969 -- each OLSRv2 interface. 970 -- 972 -- Note: The IIB is fully defined in the NHRP 973 -- and its associated MIB. 975 -- 976 -- Node Information Base - as defined in [nhdp], 977 -- extended by the addition of three elements to 978 -- each Neighbor Tuple, as defined in Section 6.2. 979 -- 981 -- Neighbor Set 983 olsrv2NibNeighborSetTable OBJECT-TYPE 984 SYNTAX SEQUENCE OF Olsrv2NibNeighborSetEntry 985 MAX-ACCESS not-accessible 986 STATUS obsolete 987 DESCRIPTION 988 "Each Neighbor Tuple in the Neighbor Set, defined 989 in [nhdp], has these additional elements: 990 N_willingness 991 N_mpr 992 N_mpr_selector 993 defined here as extensions." 994 REFERENCE 995 "The OLSRv2 draft." 996 ::= { olsrv2StateGroup 4 } 998 olsrv2NibNeighborSetEntry OBJECT-TYPE 999 SYNTAX Olsrv2NibNeighborSetEntry 1000 MAX-ACCESS not-accessible 1001 STATUS current 1002 DESCRIPTION 1003 "Each Neighbor Tuple in the Neighbor Set, defined 1004 in [nhdp], has these additional elements: 1005 N_willingness 1006 N_mpr 1007 N_mpr_selector 1008 defined here as extensions." 1009 REFERENCE 1010 "The OLSRv2 draft." 1011 INDEX { olsrv2NibNeighborSetNodeId } 1012 ::= { olsrv2NibNeighborSetTable 1 } 1014 Olsrv2NibNeighborSetEntry ::= 1015 SEQUENCE { 1016 olsrv2NibNeighborSetNodeId 1017 NeighborNodeId, 1018 olsrv2NibNeighborSetNWilliness 1019 Unsigned32, 1020 olsrv2NibNeighborSetNMpr 1021 TruthValue, 1022 olsrv2NibNeighborSetNMprSelector 1023 TruthValue 1024 } 1026 olsrv2NibNeighborSetNodeId OBJECT-TYPE 1027 SYNTAX NeighborNodeId 1028 MAX-ACCESS not-accessible 1029 STATUS current 1030 DESCRIPTION 1031 "The object olsrv2NibNeighborSetNodeId is 1032 the locally assigned ID of the remote node 1033 referenced in this row. The IP addrs 1034 associated with this node is contained 1035 in the NHDP-MIB's 'nhdpDiscIfSetTable'. 1036 " 1037 REFERENCE 1038 "The OLSRv2 draft." 1039 ::= { olsrv2NibNeighborSetEntry 1 } 1041 olsrv2NibNeighborSetNWilliness OBJECT-TYPE 1042 SYNTAX Unsigned32 (1..255) 1043 MAX-ACCESS read-only 1044 STATUS current 1045 DESCRIPTION 1046 "This object, N_willingness, is the neighbor 1047 node's willingness to be selected as an MPR, in 1048 the range from WILL_NEVER (0) to WILL_ALWAYS 1049 (255), both inclusive." 1050 REFERENCE 1051 "The OLSRv2 draft." 1052 ::= { olsrv2NibNeighborSetEntry 2 } 1054 olsrv2NibNeighborSetNMpr OBJECT-TYPE 1055 SYNTAX TruthValue 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "This object, N_mpr, is a boolean flag, 1060 describing if this neighbor is selected as 1061 an MPR by this node. 1063 When set to 'true', this neighbor is selected 1064 as an MPR by this node. When set to 'false', 1065 it is not selected by this node as an MPR." 1066 REFERENCE 1067 "The OLSRv2 draft." 1068 ::= { olsrv2NibNeighborSetEntry 3 } 1070 olsrv2NibNeighborSetNMprSelector OBJECT-TYPE 1071 SYNTAX TruthValue 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "This object, N_mpr_selector, is a boolean flag, 1076 describing if this neighbor has selected this node 1077 as an MPR, i.e. is an MPR selector of this node. 1079 When set to 'true', then this node is selected as 1080 an MPR by the neighbor node. When set to 'false', 1081 then this node is not selected by the neighbor 1082 as an MPR" 1083 REFERENCE 1084 "The OLSRv2 draft." 1085 ::= { olsrv2NibNeighborSetEntry 4 } 1087 -- 1088 -- Topology Information Base - this Information 1089 -- Base is specific to OLSRv2, and is defined in 1090 -- Section 6.3. 1091 -- 1093 -- Advertised Neighbor Set 1095 olsrv2TibAdNeighborSetSeqNo OBJECT-TYPE 1096 SYNTAX Unsigned32 (0..65535) 1097 MAX-ACCESS read-only 1098 STATUS current 1099 DESCRIPTION 1100 "The Advertised Neighbor Set Sequence Number 1101 (ANSN) is maintained associated with the 1102 olsrv2TibAdNeighborSetTable. Each time the 1103 Advertised Neighbor Set Table is updated, the 1104 ANSN MUST be incremented. The ANSN MUST also 1105 be incremented if there is a change to the 1106 set of Local Attached Network Tuples that are to 1107 be advertised in the node's TC messages." 1108 REFERENCE 1109 "The OLSRv2 draft." 1110 ::= { olsrv2StateGroup 5 } 1112 olsrv2TibAdNeighborSetTable OBJECT-TYPE 1113 SYNTAX SEQUENCE OF Olsrv2TibAdNeighborSetEntry 1114 MAX-ACCESS not-accessible 1115 STATUS obsolete 1116 DESCRIPTION 1117 "A node's Advertised Neighbor Set Table contains 1118 interface addresses of symmetric 1-hop neighbors 1119 which are to be advertised through TC messages." 1120 REFERENCE 1121 "The OLSRv2 draft." 1122 ::= { olsrv2StateGroup 6 } 1124 olsrv2TibAdNeighborSetEntry OBJECT-TYPE 1125 SYNTAX Olsrv2TibAdNeighborSetEntry 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "A node's Advertised Neighbor Set Table contains 1130 interface addresses of symmetric 1-hop neighbors 1131 which are to be advertised through TC messages." 1132 REFERENCE 1133 "The OLSRv2 draft." 1134 INDEX { olsrv2TibAdNeighborSetIpAddr } 1135 ::= { olsrv2TibAdNeighborSetTable 1 } 1137 Olsrv2TibAdNeighborSetEntry ::= 1138 SEQUENCE { 1139 olsrv2TibAdNeighborSetIpAddrType 1140 InetAddressType, 1141 olsrv2TibAdNeighborSetIpAddr 1142 InetAddress 1143 } 1145 olsrv2TibAdNeighborSetIpAddrType OBJECT-TYPE 1146 SYNTAX InetAddressType 1147 MAX-ACCESS read-only 1148 STATUS current 1149 DESCRIPTION 1150 "The type of the olsrv2TibAdNeighborSetIpAddr, as defined 1151 in the InetAddress MIB [RFC 4001]." 1152 REFERENCE 1153 "The OLSRv2 draft." 1154 ::= { olsrv2TibAdNeighborSetEntry 1 } 1156 olsrv2TibAdNeighborSetIpAddr OBJECT-TYPE 1157 SYNTAX InetAddress 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "This is the interface address of a 1162 symmetric 1-hop neighbor which is to be 1163 advertised through TC messages." 1164 REFERENCE 1165 "The OLSRv2 draft." 1166 ::= { olsrv2TibAdNeighborSetEntry 2 } 1168 -- Advertised Remote Node Set 1170 -- Note: Need to think more about the structure of this table 1171 -- due to the existence of multiple IfAddrs per Remote Node 1173 olsrv2TibAdRemoteNodeSetTable OBJECT-TYPE 1174 SYNTAX SEQUENCE OF Olsrv2TibAdRemoteNodeSetEntry 1175 MAX-ACCESS not-accessible 1176 STATUS obsolete 1177 DESCRIPTION 1178 "A node's Advertising Remote Node Set records 1179 information describing each remote node in the 1180 network that transmits TC messages." 1181 REFERENCE 1182 "The OLSRv2 draft." 1183 ::= { olsrv2StateGroup 7 } 1185 olsrv2TibAdRemoteNodeSetEntry OBJECT-TYPE 1186 SYNTAX Olsrv2TibAdRemoteNodeSetEntry 1187 MAX-ACCESS not-accessible 1188 STATUS current 1189 DESCRIPTION 1190 "A node's Advertised Neighbor Set Table entry 1191 It consists of Advertising Remote Node Tuples: 1193 (AR_orig_addr, AR_seq_number, 1194 AR_iface_addr_list, AR_time) 1196 Addresses associated with this node are 1197 found in the NHDP-MIB's 'nhdpDiscIfSetTable'. 1198 " 1199 REFERENCE 1200 "The OLSRv2 draft." 1201 INDEX { olsrv2TibAdRemoteNodeSetNodeId } 1202 ::= { olsrv2TibAdRemoteNodeSetTable 1 } 1204 Olsrv2TibAdRemoteNodeSetEntry ::= 1205 SEQUENCE { 1206 olsrv2TibAdRemoteNodeSetIpAddrType 1207 InetAddressType, 1209 olsrv2TibAdRemoteNodeSetIpAddr 1210 InetAddress, 1211 olsrv2TibAdRemoteNodeSetNodeId 1212 NeighborNodeId, 1213 olsrv2TibAdRemoteNodeSetMaxSeqNo 1214 Unsigned32, 1215 olsrv2TibAdRemoteNodeSetExpireTime 1216 Unsigned32 1217 } 1219 olsrv2TibAdRemoteNodeSetIpAddrType OBJECT-TYPE 1220 SYNTAX InetAddressType 1221 MAX-ACCESS read-only 1222 STATUS current 1223 DESCRIPTION 1224 "The type of the olsrv2TibAdRemoteNodeSetIpAddr, 1225 as defined in the InetAddress MIB [RFC 4001]." 1226 REFERENCE 1227 "The OLSRv2 draft." 1228 ::= { olsrv2TibAdRemoteNodeSetEntry 1 } 1230 olsrv2TibAdRemoteNodeSetIpAddr OBJECT-TYPE 1231 SYNTAX InetAddress 1232 MAX-ACCESS read-only 1233 STATUS current 1234 DESCRIPTION 1235 "This is the originator address of a received 1236 TC message." 1237 REFERENCE 1238 "The OLSRv2 draft." 1239 ::= { olsrv2TibAdRemoteNodeSetEntry 2 } 1241 olsrv2TibAdRemoteNodeSetNodeId OBJECT-TYPE 1242 SYNTAX NeighborNodeId 1243 MAX-ACCESS not-accessible 1244 STATUS current 1245 DESCRIPTION 1246 "This object is an additional index for each 1247 Remote Node's IfAddr associated with the 1248 olsrv2TibAdRemoteNodeSetIpAddr." 1249 REFERENCE 1250 "The OLSRv2 draft." 1251 ::= { olsrv2TibAdRemoteNodeSetEntry 3 } 1253 olsrv2TibAdRemoteNodeSetMaxSeqNo OBJECT-TYPE 1254 SYNTAX Unsigned32 (0..65535) 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "The is the greatest ANSN in any TC message 1259 received which originated from the node 1260 with originator address AR_orig_addr 1261 (i.e. which contributed to the information 1262 contained in this Tuple)." 1263 REFERENCE 1264 "The OLSRv2 draft." 1265 ::= { olsrv2TibAdRemoteNodeSetEntry 4 } 1267 -- Need to change this type to a time syntax. 1268 olsrv2TibAdRemoteNodeSetExpireTime OBJECT-TYPE 1269 SYNTAX Unsigned32 (0..65535) 1270 UNITS "seconds" 1271 MAX-ACCESS read-only 1272 STATUS current 1273 DESCRIPTION 1274 "The AR_time is the time at which this 1275 Tuple expires and MUST be removed." 1276 REFERENCE 1277 "The OLSRv2 draft." 1278 ::= { olsrv2TibAdRemoteNodeSetEntry 5 } 1280 -- Topology Set 1282 -- Note: Need to think more about the structure of this table 1283 -- due to the existence of multiple DestAddrs per Orig Addr 1285 olsrv2TibTopologySetTable OBJECT-TYPE 1286 SYNTAX SEQUENCE OF Olsrv2TibTopologySetEntry 1287 MAX-ACCESS not-accessible 1288 STATUS obsolete 1289 DESCRIPTION 1290 "A node's Topology Set records topology 1291 information about the network." 1292 REFERENCE 1293 "The OLSRv2 draft." 1294 ::= { olsrv2StateGroup 8 } 1296 olsrv2TibTopologySetEntry OBJECT-TYPE 1297 SYNTAX Olsrv2TibTopologySetEntry 1298 MAX-ACCESS not-accessible 1299 STATUS current 1300 DESCRIPTION 1301 "It consists of Topology Tuples: 1303 (T_dest_iface_addr, T_orig_addr, 1304 T_seq_number, T_time)" 1305 REFERENCE 1306 "The OLSRv2 draft." 1307 INDEX { olsrv2TibTopologySetDestIfIpAddr } 1308 ::= { olsrv2TibTopologySetTable 1 } 1310 Olsrv2TibTopologySetEntry ::= 1311 SEQUENCE { 1312 olsrv2TibTopologySetDestIfIpAddrType 1313 InetAddressType, 1314 olsrv2TibTopologySetDestIfIpAddr 1315 InetAddress, 1316 olsrv2TibTopologySetOrigIpAddrType 1317 InetAddressType, 1318 olsrv2TibTopologySetOrigIpAddr 1319 InetAddress, 1320 olsrv2TibTopologySetSeqNo 1321 Unsigned32, 1322 olsrv2TibTopologySetExpireTime 1323 Unsigned32 1324 } 1326 olsrv2TibTopologySetDestIfIpAddrType OBJECT-TYPE 1327 SYNTAX InetAddressType 1328 MAX-ACCESS read-only 1329 STATUS current 1330 DESCRIPTION 1331 "The type of the olsrv2TibTopologySetDestIfIpAddr 1332 and olsrv2TibTopologySetDestIfIpAddr, 1333 as defined in the InetAddress MIB [RFC 4001]." 1334 REFERENCE 1335 "The OLSRv2 draft." 1336 ::= { olsrv2TibTopologySetEntry 1 } 1338 olsrv2TibTopologySetDestIfIpAddr OBJECT-TYPE 1339 SYNTAX InetAddress 1340 MAX-ACCESS not-accessible 1341 STATUS current 1342 DESCRIPTION 1343 "This is an interface address of a 1344 destination node, which may be reached 1345 in one hop from the node with originator 1346 address T_orig_addr." 1347 REFERENCE 1348 "The OLSRv2 draft." 1349 ::= { olsrv2TibTopologySetEntry 2 } 1350 olsrv2TibTopologySetOrigIpAddrType OBJECT-TYPE 1351 SYNTAX InetAddressType 1352 MAX-ACCESS read-only 1353 STATUS current 1354 DESCRIPTION 1355 "The type of the olsrv2TibTopologySetOrigIpAddr 1356 and olsrv2TibTopologySetDestIfIpAddr, 1357 as defined in the InetAddress MIB [RFC 4001]." 1358 REFERENCE 1359 "The OLSRv2 draft." 1360 ::= { olsrv2TibTopologySetEntry 3 } 1362 olsrv2TibTopologySetOrigIpAddr OBJECT-TYPE 1363 SYNTAX InetAddress 1364 MAX-ACCESS read-only 1365 STATUS current 1366 DESCRIPTION 1367 "This is the originator address of a node 1368 which is the last hop on a path towards 1369 the node with interface address 1370 T_dest_iface_addr." 1371 REFERENCE 1372 "The OLSRv2 draft." 1373 ::= { olsrv2TibTopologySetEntry 4 } 1375 olsrv2TibTopologySetSeqNo OBJECT-TYPE 1376 SYNTAX Unsigned32 (0..65535) 1377 MAX-ACCESS read-only 1378 STATUS current 1379 DESCRIPTION 1380 "The is the greatest ANSN in any 1381 TC message received which originated from 1382 the node with originator address T_orig_addr 1383 (i.e. which contributed to the information 1384 contained in this Tuple)." 1385 REFERENCE 1386 "The OLSRv2 draft." 1387 ::= { olsrv2TibTopologySetEntry 5 } 1389 -- Need to change this type to a time syntax. 1390 olsrv2TibTopologySetExpireTime OBJECT-TYPE 1391 SYNTAX Unsigned32 (0..65535) 1392 UNITS "seconds" 1393 MAX-ACCESS read-only 1394 STATUS current 1395 DESCRIPTION 1396 "This is the time at which this 1397 Tuple expires and MUST be removed." 1399 REFERENCE 1400 "The OLSRv2 draft." 1401 ::= { olsrv2TibTopologySetEntry 6 } 1403 -- Attached Network Set 1405 olsrv2TibAttNetworksSetTable OBJECT-TYPE 1406 SYNTAX SEQUENCE OF Olsrv2TibAttNetworksSetEntry 1407 MAX-ACCESS not-accessible 1408 STATUS obsolete 1409 DESCRIPTION 1410 "A node's Attached Network Set records information 1411 about networks attached to other nodes." 1412 REFERENCE 1413 "The OLSRv2 draft." 1414 ::= { olsrv2StateGroup 9 } 1416 olsrv2TibAttNetworksSetEntry OBJECT-TYPE 1417 SYNTAX Olsrv2TibAttNetworksSetEntry 1418 MAX-ACCESS not-accessible 1419 STATUS current 1420 DESCRIPTION 1421 "It consists of Attached Network Tuples: 1423 (AN_net_addr, AN_orig_addr, 1424 AN_dist, AN_seq_number, AN_time)" 1426 REFERENCE 1427 "The OLSRv2 draft." 1428 INDEX { olsrv2TibAttNetworksSetNetIpAddrType, 1429 olsrv2TibAttNetworksSetNetIpAddr, 1430 olsrv2TibAttNetworksSetNetIpAddrPrefixLen } 1431 ::= { olsrv2TibAttNetworksSetTable 1 } 1433 Olsrv2TibAttNetworksSetEntry ::= 1434 SEQUENCE { 1435 olsrv2TibAttNetworksSetNetIpAddrType 1436 InetAddressType, 1437 olsrv2TibAttNetworksSetNetIpAddr 1438 InetAddress, 1439 olsrv2TibAttNetworksSetNetIpAddrPrefixLen 1440 InetAddressPrefixLength, 1441 olsrv2TibAttNetworksSetOrigIpAddr 1442 InetAddress, 1443 olsrv2TibAttNetworksSetSeqNo 1444 Unsigned32, 1445 olsrv2TibAttNetworksSetDist 1446 Unsigned32, 1447 olsrv2TibAttNetworksSetExpireTime 1448 Unsigned32 1449 } 1451 olsrv2TibAttNetworksSetNetIpAddrType OBJECT-TYPE 1452 SYNTAX InetAddressType 1453 MAX-ACCESS not-accessible 1454 STATUS current 1455 DESCRIPTION 1456 "The type of the olsrv2TibAttNetworksSetNetIpAddr, 1457 as defined in the InetAddress MIB [RFC 4001]." 1458 REFERENCE 1459 "The OLSRv2 draft." 1460 ::= { olsrv2TibAttNetworksSetEntry 1 } 1462 olsrv2TibAttNetworksSetNetIpAddr OBJECT-TYPE 1463 SYNTAX InetAddress 1464 MAX-ACCESS not-accessible 1465 STATUS current 1466 DESCRIPTION 1467 "This is is the network address of an 1468 attached network, which may be reached via 1469 the node with originator address AN_orig_addr." 1470 REFERENCE 1471 "The OLSRv2 draft." 1472 ::= { olsrv2TibAttNetworksSetEntry 2 } 1474 olsrv2TibAttNetworksSetNetIpAddrPrefixLen OBJECT-TYPE 1475 SYNTAX InetAddressPrefixLength 1476 MAX-ACCESS not-accessible 1477 STATUS current 1478 DESCRIPTION 1479 "Indicates the number of leading one bits that form the 1480 mask to be logical-ANDed with the destination address 1481 before being compared to the value in the 1482 olsrv2TibAttNetworksSetNetIpAddr field." 1483 REFERENCE 1484 "The OLSRv2 draft." 1485 ::= { olsrv2TibAttNetworksSetEntry 3 } 1487 olsrv2TibAttNetworksSetOrigIpAddr OBJECT-TYPE 1488 SYNTAX InetAddress 1489 MAX-ACCESS not-accessible 1490 STATUS current 1491 DESCRIPTION 1492 "This is the originator address of a 1493 node which can act as gateway to the 1494 network with address AN_net_addr, 1495 note that this does not include a 1496 prefix length." 1497 REFERENCE 1498 "The OLSRv2 draft." 1499 ::= { olsrv2TibAttNetworksSetEntry 4 } 1501 olsrv2TibAttNetworksSetSeqNo OBJECT-TYPE 1502 SYNTAX Unsigned32 (0..65535) 1503 MAX-ACCESS read-only 1504 STATUS current 1505 DESCRIPTION 1506 "The is the greatest ANSN in any TC 1507 message received which originated from the 1508 node with originator address AN_orig_addr 1509 (i.e. which contributed to the information 1510 contained in this Tuple)." 1511 REFERENCE 1512 "The OLSRv2 draft." 1513 ::= { olsrv2TibAttNetworksSetEntry 5 } 1515 olsrv2TibAttNetworksSetDist OBJECT-TYPE 1516 SYNTAX Unsigned32 (0..255) 1517 UNITS "hops" 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "The is the number of hops to the network 1522 with address AN_net_addr from the node with 1523 originator address AN_orig_addr." 1524 REFERENCE 1525 "The OLSRv2 draft." 1526 ::= { olsrv2TibAttNetworksSetEntry 6 } 1528 -- Need to change this type to a time syntax. 1529 olsrv2TibAttNetworksSetExpireTime OBJECT-TYPE 1530 SYNTAX Unsigned32 (0..65535) 1531 UNITS "seconds" 1532 MAX-ACCESS read-only 1533 STATUS current 1534 DESCRIPTION 1535 "This is the time at which this 1536 Tuple expires and MUST be removed." 1537 REFERENCE 1538 "The OLSRv2 draft." 1539 ::= { olsrv2TibAttNetworksSetEntry 7 } 1541 -- Routing Set 1543 -- Note: Does this RoutingSetTable overlap too much with the 1544 -- information already available in the latest standard MIB 1545 -- forwarding table? 1547 -- Note: Do all of these addresses contained in a single 1548 -- entry in the Routing Set have to have the same addrType? 1550 olsrv2TibRoutingSetTable OBJECT-TYPE 1551 SYNTAX SEQUENCE OF Olsrv2TibRoutingSetEntry 1552 MAX-ACCESS not-accessible 1553 STATUS obsolete 1554 DESCRIPTION 1555 "A node's Routing Set records the selected path to 1556 each destination for which a route is known." 1557 REFERENCE 1558 "The OLSRv2 draft." 1559 ::= { olsrv2StateGroup 10 } 1561 olsrv2TibRoutingSetEntry OBJECT-TYPE 1562 SYNTAX Olsrv2TibRoutingSetEntry 1563 MAX-ACCESS not-accessible 1564 STATUS current 1565 DESCRIPTION 1566 "It consists of Routing Tuples: 1568 (R_dest_addr, R_next_iface_addr, 1569 R_dist, R_local_iface_addr)." 1570 REFERENCE 1571 "The OLSRv2 draft." 1572 INDEX { olsrv2TibRoutingSetDestIpAddrType, 1573 olsrv2TibRoutingSetDestIpAddr, 1574 olsrv2TibRoutingSetDestIpAddrPrefLen } 1575 ::= { olsrv2TibRoutingSetTable 1 } 1577 Olsrv2TibRoutingSetEntry ::= 1578 SEQUENCE { 1579 olsrv2TibRoutingSetDestIpAddrType 1580 InetAddressType, 1581 olsrv2TibRoutingSetDestIpAddr 1582 InetAddress, 1584 olsrv2TibRoutingSetDestIpAddrPrefLen 1585 InetAddressPrefixLength, 1586 olsrv2TibRoutingSetNextIfIpAddr 1587 InetAddress, 1588 olsrv2TibRoutingSetDist 1589 Unsigned32, 1590 olsrv2TibRoutingSetLocalIfIpAddr 1591 InetAddress 1592 } 1594 olsrv2TibRoutingSetDestIpAddrType OBJECT-TYPE 1595 SYNTAX InetAddressType 1596 MAX-ACCESS not-accessible 1597 STATUS current 1598 DESCRIPTION 1599 "The type of the olsrv2TibRoutingSetDestIpAddr 1600 and olsrv2TibRoutingSetNextIfIpAddr, 1601 as defined in the InetAddress MIB [RFC 4001]." 1602 REFERENCE 1603 "The OLSRv2 draft." 1604 ::= { olsrv2TibRoutingSetEntry 1 } 1606 olsrv2TibRoutingSetDestIpAddr OBJECT-TYPE 1607 SYNTAX InetAddress 1608 MAX-ACCESS not-accessible 1609 STATUS current 1610 DESCRIPTION 1611 "This is the address of the destination, 1612 either the address of an interface of 1613 a destination node, or the network 1614 address of an attached network." 1615 REFERENCE 1616 "The OLSRv2 draft." 1617 ::= { olsrv2TibRoutingSetEntry 2 } 1619 olsrv2TibRoutingSetDestIpAddrPrefLen OBJECT-TYPE 1620 SYNTAX InetAddressPrefixLength 1621 MAX-ACCESS not-accessible 1622 STATUS current 1623 DESCRIPTION 1624 "Indicates the number of leading one bits that form the 1625 mask to be logical-ANDed with the destination address 1626 before being compared to the value in the 1627 olsrv2TibRoutingSetDestNetIpAddr field. 1629 Note: This definition needs to be consistent 1630 with the current forwarding table MIB description. 1631 Specifically, it should allow for longest prefix 1632 matching of network addresses." 1633 REFERENCE 1634 "The OLSRv2 draft." 1635 ::= { olsrv2TibRoutingSetEntry 3 } 1637 olsrv2TibRoutingSetNextIfIpAddr OBJECT-TYPE 1638 SYNTAX InetAddress 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "This is the OLSRv2 interface address of the 1643 'next hop' on the selected path to the 1644 destination." 1645 REFERENCE 1646 "The OLSRv2 draft." 1647 ::= { olsrv2TibRoutingSetEntry 4 } 1649 olsrv2TibRoutingSetDist OBJECT-TYPE 1650 SYNTAX Unsigned32 (0..255) 1651 UNITS "hops" 1652 MAX-ACCESS read-only 1653 STATUS current 1654 DESCRIPTION 1655 "The is the number of hops on the selected 1656 path to the destination." 1657 REFERENCE 1658 "The OLSRv2 draft." 1659 ::= { olsrv2TibRoutingSetEntry 5 } 1661 olsrv2TibRoutingSetLocalIfIpAddr OBJECT-TYPE 1662 SYNTAX InetAddress 1663 MAX-ACCESS read-only 1664 STATUS current 1665 DESCRIPTION 1666 "This is the address of the local OLSRv2 1667 interface over which a packet MUST be 1668 sent to reach the destination by the 1669 selected path." 1670 REFERENCE 1671 "The OLSRv2 draft." 1672 ::= { olsrv2TibRoutingSetEntry 6 } 1674 -- 1675 -- Processing and Forwarding Information Base - this 1676 -- Information Base is specific to OLSRv2, and 1677 -- is defined in Section 6.4. 1679 -- 1681 -- Note: Is it appropriate or necessary to put the 1682 -- level of detail found in the Processing and 1683 -- Forwarding Information Base into the OLSRv2-MIB? 1685 -- Received Set 1687 -- Processed Set 1689 -- Forwarded Set 1691 -- Relayed Set 1693 -- 1694 -- OLSRv2 Performance Group 1695 -- 1696 -- Contains objects which help to characterize the 1697 -- performance of the OLSRv2 routing process, such as ... 1698 -- 1700 olsrv2PerformanceGroup OBJECT IDENTIFIER ::= { olsrv2MIBObjects 3 } 1702 olsrv2GlPerfGroup OBJECT IDENTIFIER ::= {olsrv2PerformanceGroup 1} 1704 -- Note: Objects to be defined. 1706 -- 1707 -- Per OLSRv2 Interface Performance Table 1708 -- 1710 olsrv2IfPerfGroup OBJECT IDENTIFIER ::= {olsrv2PerformanceGroup 2} 1712 -- Note: Objects to be defined. 1714 -- 1715 -- Notifications 1716 -- 1718 -- Note: What notifications do we want for this MIB? 1719 -- 1720 -- Compliance Statements 1721 -- 1723 -- Note: need to update the Compliance section once the mib 1724 -- objects stabilize. 1726 olsrv2Compliances OBJECT IDENTIFIER ::= { olsrv2MIBConformance 1 } 1727 olsrv2MIBGroups OBJECT IDENTIFIER ::= { olsrv2MIBConformance 2 } 1729 olsrv2BasicCompliance MODULE-COMPLIANCE 1730 STATUS current 1731 DESCRIPTION "The basic implementation requirements for 1732 managed network entities that implement 1733 the OLSRv2 routing process." 1734 MODULE -- this module 1735 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup } 1736 ::= { olsrv2Compliances 1 } 1738 olsrv2FullCompliance MODULE-COMPLIANCE 1739 STATUS current 1740 DESCRIPTION "The full implementation requirements for 1741 managed network entities that implement 1742 the OLSRv2 routing process." 1743 MODULE -- this module 1744 -- MANDATORY-GROUPS { olsrv2ConfigObjectsGroup, 1745 -- olsrv2StateObjectsGroup, 1746 -- olsrv2PerfObjectsGroup } 1747 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup, 1748 olsrv2StateObjectsGroup } 1749 ::= { olsrv2Compliances 2 } 1751 -- 1752 -- Units of Conformance 1753 -- 1755 olsrv2ConfigObjectsGroup OBJECT-GROUP 1756 OBJECTS { 1757 olsrv2OperationalMode, 1758 olsrv2OHoldTime, 1759 olsrv2TcInterval, 1760 olsrv2TcMinInterval, 1761 olsrv2THoldTime, 1762 olsrv2AHoldTime, 1763 olsrv2RxHoldTime, 1764 olsrv2PHoldTime, 1765 olsrv2FHoldTime, 1766 olsrv2TpMaxJitter, 1767 olsrv2TtMaxJitter, 1768 olsrv2FMaxJitter, 1769 olsrv2TcHopLimit, 1770 olsrv2Williness, 1771 olsrv2LibLocAttNetSetDistance, 1772 olsrv2LibLocAttNetSetRowStatus 1773 } 1774 STATUS current 1775 DESCRIPTION 1776 "Set of OLSRv2 configuration objects implemented 1777 in this module." 1778 ::= { olsrv2MIBGroups 1 } 1780 olsrv2StateObjectsGroup OBJECT-GROUP 1781 OBJECTS { 1782 olsrv2NodeStatus, 1783 olsrv2LibLocAttNetSetIpAddrType, 1784 olsrv2LibOrigSetIpAddrType, 1785 olsrv2NibNeighborSetNWilliness, 1786 olsrv2NibNeighborSetNMpr, 1787 olsrv2NibNeighborSetNMprSelector, 1788 olsrv2TibAdNeighborSetSeqNo, 1789 olsrv2TibAdNeighborSetIpAddrType, 1790 olsrv2TibAdRemoteNodeSetIpAddrType, 1791 olsrv2TibAdRemoteNodeSetIpAddr, 1792 olsrv2TibAdRemoteNodeSetMaxSeqNo, 1793 olsrv2TibAdRemoteNodeSetExpireTime, 1794 olsrv2TibTopologySetDestIfIpAddrType, 1795 olsrv2TibTopologySetOrigIpAddrType, 1796 olsrv2TibTopologySetOrigIpAddr, 1797 olsrv2TibTopologySetSeqNo, 1798 olsrv2TibTopologySetExpireTime, 1799 olsrv2TibAttNetworksSetSeqNo, 1800 olsrv2TibAttNetworksSetDist, 1801 olsrv2TibAttNetworksSetExpireTime, 1802 olsrv2TibRoutingSetNextIfIpAddr, 1803 olsrv2TibRoutingSetDist, 1804 olsrv2TibRoutingSetLocalIfIpAddr 1805 } 1806 STATUS current 1807 DESCRIPTION 1808 "Set of OLSRv2 state objects implemented 1809 in this module." 1810 ::= { olsrv2MIBGroups 2 } 1812 -- olsrv2PerfObjectsGroup OBJECT-GROUP 1813 -- OBJECTS { 1814 -- 1815 -- 1816 -- } 1817 -- STATUS current 1818 -- DESCRIPTION 1819 -- "Set of OLSRv2 performance objects implemented 1820 -- in this module by total and per interface." 1821 -- ::= { olsrv2MIBGroups 3 } 1823 END 1825 8. Security Considerations 1827 [TODO] Each specification that defines one or more MIB modules MUST 1828 contain a section that discusses security considerations relevant to 1829 those modules. This section MUST be patterned after the latest 1830 approved template (available at 1831 http://www.ops.ietf.org/mib-security.html). Remember that the 1832 objective is not to blindly copy text from the template, but rather 1833 to think and evaluate the risks/vulnerabilities and then state/ 1834 document the result of this evaluation. 1836 [TODO] if you have any read-write and/or read-create objects, please 1837 include the following boilerplate paragraph. 1839 There are a number of management objects defined in this MIB module 1840 with a MAX-ACCESS clause of read-write and/or read-create. Such 1841 objects may be considered sensitive or vulnerable in some network 1842 environments. The support for SET operations in a non-secure 1843 environment without proper protection can have a negative effect on 1844 network operations. These are the tables and objects and their 1845 sensitivity/vulnerability: 1847 o [TODO] writable MIB objects that could be especially disruptive if 1848 abused MUST be explicitly listed by name and the associated 1849 security risks MUST be spelled out; RFC 2669 has a very good 1850 example. 1852 o [TODO] list the writable tables and objects and state why they are 1853 sensitive. 1855 [TODO] else if there are no read-write objects in your MIB module, 1856 use the following boilerplate paragraph. 1858 There are no management objects defined in this MIB module that have 1859 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1860 MIB module is implemented correctly, then there is no risk that an 1861 intruder can alter or create any management objects of this MIB 1862 module via direct SNMP SET operations. 1864 [TODO] if you have any sensitive readable objects, please include the 1865 following boilerplate paragraph. 1867 Some of the readable objects in this MIB module (i.e., objects with a 1868 MAX-ACCESS other than not-accessible) may be considered sensitive or 1869 vulnerable in some network environments. It is thus important to 1870 control even GET and/or NOTIFY access to these objects and possibly 1871 to even encrypt the values of these objects when sending them over 1872 the network via SNMP. These are the tables and objects and their 1873 sensitivity/vulnerability: 1875 o [TODO] you must explicitly list by name any readable objects that 1876 are sensitive or vulnerable and the associated security risks MUST 1877 be spelled out (for instance, if they might reveal customer 1878 information or violate personal privacy laws such as those of the 1879 European Union if exposed to unauthorized parties) 1881 o [TODO] list the tables and objects and state why they are 1882 sensitive. 1884 [TODO] discuss what security the protocol used to carry the 1885 information should have. The following three boilerplate paragraphs 1886 should not be changed without very good reason. Changes will almost 1887 certainly require justification during IESG review. 1889 SNMP versions prior to SNMPv3 did not include adequate security. 1890 Even if the network itself is secure (for example by using IPSec), 1891 even then, there is no control as to who on the secure network is 1892 allowed to access and GET/SET (read/change/create/delete) the objects 1893 in this MIB module. 1895 It is RECOMMENDED that implementers consider the security features as 1896 provided by the SNMPv3 framework (see [RFC3410], section 8), 1897 including full support for the SNMPv3 cryptographic mechanisms (for 1898 authentication and privacy). 1900 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1901 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1902 enable cryptographic security. It is then a customer/operator 1903 responsibility to ensure that the SNMP entity giving access to an 1904 instance of this MIB module is properly configured to give access to 1905 the objects only to those principals (users) that have legitimate 1906 rights to indeed GET or SET (change/create/delete) them. 1908 9. IANA Considerations 1910 [TODO] In order to comply with IESG policy as set forth in 1911 http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is 1912 submitted to the IESG for publication MUST contain an IANA 1913 Considerations section. The requirements for this section vary 1914 depending what actions are required of the IANA. see RFC4181 section 1915 3.5 for more information on writing an IANA clause for a MIB module 1916 document. 1918 [TODO] select an option and provide the necessary details. 1920 Option #1: 1922 The MIB module in this document uses the following IANA-assigned 1923 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1925 Descriptor OBJECT IDENTIFIER value 1926 ---------- ----------------------- 1928 sampleMIB { mib-2 XXX } 1930 Option #2: 1932 Editor's Note (to be removed prior to publication): the IANA is 1933 requested to assign a value for "XXX" under the 'mib-2' subtree and 1934 to record the assignment in the SMI Numbers registry. When the 1935 assignment has been made, the RFC Editor is asked to replace "XXX" 1936 (here and in the MIB module) with the assigned value and to remove 1937 this note. 1939 Note well: prior to official assignment by the IANA, a draft document 1940 MUST use place holders (such as "XXX" above) rather than actual 1941 numbers. See RFC4181 Section 4.5 for an example of how this is done 1942 in a draft MIB module. 1944 Option #3: 1946 This memo includes no request to IANA. 1948 10. Contributors 1950 This MIB document uses the template authored by D. Harrington which 1951 is based on contributions from the MIB Doctors, especially Juergen 1952 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 1954 11. Acknowledgements 1956 12. References 1958 12.1. Normative References 1960 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1961 Interfaces Group MIB", RFC 2863, June 2000. 1963 [RFC3418] Presuhn, R., "Management Information Base 1964 (MIB) for the Simple Network Management 1965 Protocol (SNMP)", STD 62, RFC 3418, 1966 December 2002. 1968 [RFC2119] Bradner, S., "Key words for use in RFCs to 1969 Indicate Requirement Levels", BCP 14, 1970 RFC 2119, March 1997. 1972 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and 1973 J. Schoenwaelder, Ed., "Structure of 1974 Management Information Version 2 (SMIv2)", 1975 STD 58, RFC 2578, April 1999. 1977 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and 1978 J. Schoenwaelder, Ed., "Textual Conventions 1979 for SMIv2", STD 58, RFC 2579, April 1999. 1981 [RFC2580] McCloghrie, K., Perkins, D., and J. 1982 Schoenwaelder, "Conformance Statements for 1983 SMIv2", STD 58, RFC 2580, April 1999. 1985 [I-D.ietf-manet-olsrv2] Clausen, T., Dearlove, C., and P. Jacquet, 1986 "The Optimized Link State Routing Protocol 1987 version 2", draft-ietf-manet-olsrv2-08 (work 1988 in progress), March 2009. 1990 12.2. Informative References 1992 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 1993 Stewart, "Introduction and Applicability 1994 Statements for Internet-Standard Management 1995 Framework", RFC 3410, December 2002. 1997 Appendix A. Change Log 1999 This section identifies the changes made during the development of 2000 this MIB. 2002 Here we list the changes made in developing 2003 draft-ietf-manet-olsrv2-mib-00. 2005 1. Rev'd the draft as a new working group document. 2007 2. Ran 'smilint' against the module and cleaned up syntax errors and 2008 other issues discovered by the checker. 2010 Here we list the changes made in developing 2011 draft-cole-manet-olsr-mib-01. 2013 1. Completely reworked the entire Configuration Objects group in 2014 order to align with the newly developed NHDP-MIB draft. 2016 Appendix B. Open Issues 2018 This section contains the set of open issues related to the 2019 development and design of the OLSRv2-MIB. This section will not be 2020 present in the final version of the MIB and will be removed once all 2021 the open issues have been resolved. 2023 1. Look into possible redundancy between the TIB Routing Set and 2024 the latest standard MIB forwarding table. 2026 2. Fill out the performance objects group. 2028 3. Complete notification group. 2030 4. Complete conformance group. 2032 5. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 2034 6. Identify all objects requiring non-volatile storage in their 2035 DESCRIPTION clauses. 2037 7. Incorporate parameter relationship conditions into their 2038 DESCRIPTION clauses. 2040 8. Also, specify specific SNMP response to the snmp set request, 2041 i.e., 'generic error', 'bad value', etc. 2043 9. Fill in all of the DEFVAL within the configuration group objects 2044 with their correct values. 2046 10. Run through the MIB checker. 2048 11. Complete the security analysis and section. 2050 12. Clean up all of the 'Note:' statements within the body of the 2051 MIB. 2053 13. Cleanup all the [TODOs] from the MIB template. 2055 Appendix C. 2057 *************************************************************** 2058 * Note to the RFC Editor (to be removed prior to publication) * 2059 * * 2060 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 2061 * of the MIB module point to this draft and are to be * 2062 * assigned by the RFC Editor. * 2063 * * 2064 * 2) The reference to RFCXXX2 throughout this document point * 2065 * to the current draft-ietf-manet-olsrv2-xx.txt. This * 2066 * need to be replaced with the XXX RFC number. * 2067 * * 2068 *************************************************************** 2070 Authors' Addresses 2072 Robert G. Cole 2073 Johns Hopkins University 2074 11100 Johns Hopkins Road, Room 257 2075 Laurel, Maryland 21073 2076 USA 2078 Phone: +1 443 778 6951 2079 EMail: robert.cole@jhuapl.edu 2080 URI: http://www.cs.jhu.edu/~rgcole/ 2082 Thomas Heide Clausen 2083 LIX, Ecole Polytechnique 2084 France 2086 Phone: +33 6 6058 9349 2087 EMail: T.Clausen@computer.org 2088 URI: http://www.ThomasClausen.org/