idnits 2.17.1 draft-cole-manet-olsrv2-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1259 has weird spacing: '... "The is th...' == Line 1275 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 seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 21, 2009) is 5536 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 1877, but not defined == Missing Reference: 'RFC4001' is mentioned on line 266, but not defined == Missing Reference: 'RFC5148' is mentioned on line 656, but not defined == Missing Reference: 'RFC 4001' is mentioned on line 1600, but not defined == Missing Reference: 'TODOs' is mentioned on line 2004, but not defined == Outdated reference: A later version (-19) exists of draft-ietf-manet-olsrv2-07 Summary: 0 errors (**), 0 flaws (~~), 10 warnings (==), 2 comments (--). 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: August 25, 2009 LIX, Ecole Polytechnique 6 February 21, 2009 8 Definition of Managed Objects for the MANET Optimized Link State Routing 9 Protocol version 2 10 draft-cole-manet-olsrv2-mib-01 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 August 25, 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 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. 47 Abstract 49 This memo defines a portion of the Management Information Base (MIB) 50 for use with network management protocols in the Internet community. 51 In particular, it describes objects for configuring and managing 52 aspects of the Optimized Link State Routing protocol version 2. The 53 Optimized Link State Routing MIB also reports state information, 54 performance metrics, and notifications. In addition to 55 configuration, this additional state and performance information is 56 useful to management stations troubleshooting Mobile Ad-Hoc Networks 57 routing problems. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. The Internet-Standard Management Framework . . . . . . . . . . 3 63 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 4.1. OLSRv2 Management Model . . . . . . . . . . . . . . . . . 3 66 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 68 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 69 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 5 70 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 5 71 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 5 72 5.5. The Notifications Group . . . . . . . . . . . . . . . . . 5 73 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 74 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 5 75 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 5 76 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 6 77 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 78 8. Security Considerations . . . . . . . . . . . . . . . . . . . 39 79 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 80 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 42 81 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 42 82 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 42 83 12.1. Normative References . . . . . . . . . . . . . . . . . . . 42 84 12.2. Informative References . . . . . . . . . . . . . . . . . . 42 85 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 43 86 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 43 87 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 44 89 1. Introduction 91 This memo defines a portion of the Management Information Base (MIB) 92 for use with network management protocols in the Internet community. 93 In particular, it describes objects for configuring aspects of a 94 process implementing the Optimized Link State Routing Protocol 95 version 2 (OLSRv2) [I-D.ietf-manet-olsrv2]. OLSRv2 provides ... 97 2. The Internet-Standard Management Framework 99 For a detailed overview of the documents that describe the current 100 Internet-Standard Management Framework, please refer to section 7 of 101 RFC 3410 [RFC3410]. 103 Managed objects are accessed via a virtual information store, termed 104 the Management Information Base or MIB. MIB objects are generally 105 accessed through the Simple Network Management Protocol (SNMP). 106 Objects in the MIB are defined using the mechanisms defined in the 107 Structure of Management Information (SMI). This memo specifies a MIB 108 module that is compliant to the SMIv2, which is described in STD 58, 109 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 110 [RFC2580]. 112 3. Conventions 114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 116 document are to be interpreted as described in RFC 2119 [RFC2119]. 118 4. Overview 120 Optimized Link State Routing (OLSR) protocol version 2 (OLSRv2) 121 provides ... 123 4.1. OLSRv2 Management Model 125 This section describes the management model for the OLSRv2 node 126 routing process. Specifically, ... 128 4.2. Terms 130 The following definitions apply throughout this document: 132 o Configuration Objects - switches, tables, objects which are 133 initialized to default settings or set through the management 134 interface defined by this MIB. 136 o Tunable Configuration Objects - objects whose values affect timing 137 or attempt bounds on the OLSRv2 routing process. 139 o State Objects - automatically generated values which define the 140 current operating state of the OLSRv2 routing process in the 141 router. 143 o Performance Objects - automatically generated values which help an 144 administrator or automated tool to assess the performance of the 145 OLSRv2 routing process on the router and the overall packet 146 forwarding performance within the MANET routing domain. 148 5. Structure of the MIB Module 150 This section presents the structure of the Optimized Link State 151 Routing version 2 Management Information Base (OLSRv2-MIB) module. 152 The objects are arranged into the following groups: 154 o olsrMIBNotifications - defines the notifications associated with 155 the OLSRv2-MIB. 157 o olsrMIBObjects - defines the objects forming the basis for the 158 OLSRv2-MIB. These objects are divided up by function into the 159 following groups: 161 o 163 * Configuration Group - This group contains the OLSR objects that 164 configure specific options that determine the overall operation 165 of the OLSR routing process and the unicast packet forwarding 166 performance. 168 * State Group - Contains information describing the current state 169 of the OLSR routing process such as the ... 171 * Performance Group - Contains objects which help to characterize 172 the performance of the OLSR routing process, typically 173 statistics counters. 175 o olsrMIBConformance - defines minimal and full conformance of 176 implementations to this OLSRv2-MIB. 178 5.1. Textual Conventions 180 The textual conventions used in the OLSRv2-MIB are as follows. The 181 RowStatus textual convention is imported from RFC 2579 [RFC2579]. 182 Further, ... 184 5.2. The Configuration Group 186 The OLSR device is configured with a set of controls. The list of 187 configuration controls for the OLSR device follow. 189 o ... 191 5.3. The State Group 193 The State Subtree reports current state information. Specifically, 194 ... 196 o ... 198 5.4. The Performance Group 200 The Performance subtree reports primarily counters that relate to 201 OLSR routing performance. Specifically, ... 203 o ... 205 5.5. The Notifications Group 207 The Notifications Subtree contains the list of notifications 208 supported within the OLSRv2-MIB and their intended purpose or 209 utility. This group is currently empty. 211 6. Relationship to Other MIB Modules 213 [TODO]: The text of this section specifies the relationship of the 214 MIB modules contained in this document to other standards, 215 particularly to standards containing other MIB modules. Definitions 216 imported from other MIB modules and other MIB modules that SHOULD be 217 implemented in conjunction with the MIB module contained within this 218 document are identified in this section. 220 6.1. Relationship to the SNMPv2-MIB 222 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 223 mandatory for all systems, and the objects apply to the entity as a 224 whole. The 'system' group provides identification of the management 225 entity and certain other system-wide data. The OLSRv2-MIB does not 226 duplicate those objects. 228 6.2. Relationship to the IF-MIB 230 [TODO] This section is included as an example; If the MIB module is 231 not an adjunct of the Interface MIB, then this section should be 232 removed. 234 6.3. MIB modules required for IMPORTS 236 [TODO]: Citations are not permitted within a MIB module, but any 237 module mentioned in an IMPORTS clause or document mentioned in a 238 REFERENCE clause is a Normative reference, and must be cited 239 someplace within the narrative sections. If there are imported items 240 in the MIB module, such as Textual Conventions, that are not already 241 cited, they can be cited in text here. Since relationships to other 242 MIB modules should be described in the narrative text, this section 243 is typically used to cite modules from which Textual Conventions are 244 imported. 246 The following OLSRv2-MIB module IMPORTS objects from SNMPv2-SMI 247 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB 248 [RFC2863] 250 7. Definitions 252 MANET-OLSRv2-MIB DEFINITIONS ::= BEGIN 254 IMPORTS 255 MODULE-IDENTITY, OBJECT-TYPE, 256 Counter32, mib-2 257 FROM SNMPv2-SMI -- [RFC2578] 258 TruthValue 259 FROM SNMPv2-TC -- [RFC2579] 260 MODULE-COMPLIANCE, OBJECT-GROUP 261 FROM SNMPv2-CONF -- [RFC2580] 262 InterfaceIndex 263 FROM IF-MIB -- [RFC2863] 264 InetAddress, InetAddressType, 265 InetAddressPrefixLength 266 FROM INET-ADDRESS-MIB -- [RFC4001] 267 NeighborNodeId 268 FROM NHDP-MIB -- [draft nhdp-mib] 269 ; 271 manetOlsrv2MIB MODULE-IDENTITY 272 LAST-UPDATED "200902151300Z" -- Jebruary 15, 2009 273 ORGANIZATION "IETF MANET Working Group" 274 CONTACT-INFO 275 "WG E-Mail: manet@ietf.org 277 WG Chairs: ian.chakeres@gmail.com 278 jmacker@nrl.navy.mil 280 Editors: Robert G. Cole 281 Johns Hopkins University 282 Applied Physics Lab and 283 Department of Computer Science 284 11000 Johns Hopkins Road 285 Room 02-257 286 Laurel, MD 22014 287 USA 288 +1 443 778-6951 289 robert.cole@jhuapl.edu 291 Thomas Heide Clausen 292 LIX, Ecole Polytechnique 293 France 294 T.Clausen@computer.org" 296 DESCRIPTION 297 "This MIB module contains managed object definitions 298 for the Manet OLSRv2 routing process defined in: 299 Clausen, T. et.al., Optimized Link State Routing 300 version 2 draft-ietf-manet-olsrv2-07, July 10, 2008. 302 Copyright (C) The IETF Trust (2009). This version 303 of this MIB module is part of RFC xxxx; see the RFC 304 itself for full legal notices." 306 -- Revision History 307 REVISION "200902151300Z" -- February 15, 2009 308 DESCRIPTION 309 "Second draft of this MIB module published as 310 draft-cole-manet-olsrv2-mib-01.txt. Cleaned up 311 table indexing and aligned with the NHDP-MIB 312 draft (draft-cole-manet-nhdp-mib-01.txt)." 313 REVISION "200810241300Z" -- October 24, 2008 314 DESCRIPTION 315 "Initial draft of this MIB module published as 316 draft-cole-manet-olsrv2-mib-00.txt." 317 -- RFC-Editor assigns XXXX 318 ::= { mib-2 998 } -- to be assigned by IANA 320 -- 321 -- TEXTUAL CONVENTIONs 322 -- 323 -- none 325 -- 326 -- Top-Level Object Identifier Assignments 327 -- 329 olsrv2MIBNotifications OBJECT IDENTIFIER ::= { manetOlsrv2MIB 0 } 330 olsrv2MIBObjects OBJECT IDENTIFIER ::= { manetOlsrv2MIB 1 } 331 olsrv2MIBConformance OBJECT IDENTIFIER ::= { manetOlsrv2MIB 2 } 333 -- 334 -- olsrv2ConfigurationGroup 335 -- 336 -- This group contains the OLSRv2 objects that configure specific 337 -- options that determine the overall performance and operation 338 -- of the unicast routing process for the router device 339 -- and its interfaces. 340 -- 342 olsrv2ConfigurationGroup OBJECT IDENTIFIER ::= {olsrv2MIBObjects 1} 344 olsrv2OperationalMode OBJECT-TYPE 345 SYNTAX INTEGER { 346 withNHDP(1) 347 } 348 MAX-ACCESS read-write 349 STATUS current 350 DESCRIPTION 351 "The OLSRv2 node operational mode. 353 The value withNHDP(1) indicates ..." 354 DEFVAL { 1 } 355 ::= { olsrv2ConfigurationGroup 1 } 357 -- Protocol Parameters for the OLSRv2 routing process. 358 -- These are categorized following Section 5 of the 359 -- OLSRv2 draft. 361 -- Local history times 363 olsrv2OHoldTime OBJECT-TYPE 364 SYNTAX Unsigned32 (0..255) 365 UNITS "seconds" 366 MAX-ACCESS read-write 367 STATUS current 368 DESCRIPTION 369 "The O_HOLD_TIME is used to define the time 370 for which a recently used and replaced 371 originator address is used to recognize 372 the node's own messages. 374 The following constraint applies to this 375 parameter: olsrv2OHoldTime >= 0" 376 DEFVAL { TBD } 377 REFERENCE 378 "The OLSR version 2 draft. 379 Section 5 on Protocol Parameters." 380 ::= { olsrv2ConfigurationGroup 2 } 382 -- Message intervals 384 olsrv2TcInterval OBJECT-TYPE 385 SYNTAX Unsigned32 (0..255) 386 UNITS "seconds" 387 MAX-ACCESS read-write 388 STATUS current 389 DESCRIPTION 390 "The TC_INTERVAL - is the maximum time 391 between the transmission of two successive 392 TC messages by this node. When no TC 393 messages are sent in response to local 394 network changes (by design, or because the 395 local network is not changing) then TC 396 messages SHOULD be sent at a regular 397 interval TC_INTERVAL, possibly modified 398 by jitter as specified in [RFC5148]. 400 The following constraint applies to this 401 parameter: 403 olsrv2TcInterval > 0 404 olsrv2TcInterval >= olsrv2TcMinInterval" 405 DEFVAL { TBD } 406 REFERENCE 407 "The OLSR version 2 draft. 408 Section 5 on Protocol Parameters." 409 ::= { olsrv2ConfigurationGroup 3 } 411 olsrv2TcMinInterval OBJECT-TYPE 412 SYNTAX Unsigned32 (0..255) 413 UNITS "seconds" 414 MAX-ACCESS read-write 415 STATUS current 416 DESCRIPTION 417 "The TC_MIN_INTERVAL is the minimum 418 interval between transmission of two 419 successive TC messages by this node. 420 (This minimum interval MAY be modified 421 by jitter, as specified in [RFC5148].) 423 The following constraint applies to this 424 parameter: 426 TC_MIN_INTERVAL >= 0 427 TC_INTERVAL >= TC_MIN_INTERVAL" 428 DEFVAL { TBD } 429 REFERENCE 430 "The OLSR version 2 draft. 431 Section 5 on Protocol Parameters." 432 ::= { olsrv2ConfigurationGroup 4 } 434 -- Advertised information validity times 436 olsrv2THoldTime OBJECT-TYPE 437 SYNTAX Unsigned32 (0..255) 438 UNITS "seconds" 439 MAX-ACCESS read-write 440 STATUS current 441 DESCRIPTION 442 "The olsrv2THoldTime is used to define the 443 minimum value in the VALIDITY_TIME TLV 444 included in all TC messages sent by this node. 445 If a single value of parameter TC_HOP_LIMIT 446 (see Section 5.6) is used then this will be 447 the only value in that TLV. 449 The following constraint applies to this 450 parameter: 452 T_HOLD_TIME > 0 453 A_HOLD_TIME >= 0 454 T_HOLD_TIME >= TC_INTERVAL 456 If TC messages can be lost, then both 457 T_HOLD_TIME and A_HOLD_TIME SHOULD be 458 significantly greater than TC_INTERVAL; 459 a value >= 3 x TC_INTERVAL is RECOMMENDED. 461 T_HOLD_TIME MUST be representable as 462 described in [timetlv]." 463 DEFVAL { TBD } 464 REFERENCE 465 "The OLSR version 2 draft. 466 Section 5 on Protocol Parameters." 467 ::= { olsrv2ConfigurationGroup 5 } 469 olsrv2AHoldTime OBJECT-TYPE 470 SYNTAX Unsigned32 (0..255) 471 UNITS "seconds" 472 MAX-ACCESS read-write 473 STATUS current 474 DESCRIPTION 475 "The olsrv2AHoldTime is the period during 476 which TC messages are sent after they no 477 longer have any advertised information 478 to report, but are sent in order to 479 accelerate outdated information removal by 480 other nodes. 482 The following constraint applies to this 483 parameter: 485 T_HOLD_TIME > 0 486 A_HOLD_TIME >= 0 487 T_HOLD_TIME >= TC_INTERVAL 489 If TC messages can be lost, then both 490 T_HOLD_TIME and A_HOLD_TIME SHOULD be 491 significantly greater than TC_INTERVAL; 492 a value >= 3 x TC_INTERVAL is RECOMMENDED. 494 T_HOLD_TIME MUST be representable as 495 described in [timetlv]." 496 DEFVAL { TBD } 497 REFERENCE 498 "The OLSR version 2 draft. 499 Section 5 on Protocol Parameters." 500 ::= { olsrv2ConfigurationGroup 6 } 502 -- Received message validity times 504 olsrv2RxHoldTime OBJECT-TYPE 505 SYNTAX Unsigned32 (0..255) 506 UNITS "seconds" 507 MAX-ACCESS read-write 508 STATUS current 509 DESCRIPTION 510 "The olsrv2RxHoldTime is an interface parameter, 511 and is the period after receipt of a message 512 by the appropriate OLSRv2 interface of this 513 node for which that information is recorded, 514 in order that the message is recognized as 515 having been previously received on this 516 OLSRv2 interface. 518 The following constraint applies to this 519 parameter: 521 RX_HOLD_TIME > 0 523 All of these parameters SHOULD be greater 524 than the maximum difference in time that a 525 message may take to traverse the MANET, 526 taking into account any message forwarding 527 jitter as well as propagation, queuing, 528 and processing delays." 529 DEFVAL { TBD } 530 REFERENCE 531 "The OLSR version 2 draft. 532 Section 5 on Protocol Parameters." 533 ::= { olsrv2ConfigurationGroup 7 } 535 olsrv2PHoldTime OBJECT-TYPE 536 SYNTAX Unsigned32 (0..255) 537 UNITS "seconds" 538 MAX-ACCESS read-write 539 STATUS current 540 DESCRIPTION 541 "The olsrv2PHoldTime is the period after 542 receipt of a message which is processed by 543 this node for which that information is 544 recorded, in order that the message is 545 not processed again if received again. 547 The following constraint applies to this 548 parameter: 550 P_HOLD_TIME > 0 552 All of these parameters SHOULD be greater 553 than the maximum difference in time that a 554 message may take to traverse the MANET, 555 taking into account any message forwarding 556 jitter as well as propagation, queuing, 557 and processing delays." 558 DEFVAL { TBD } 559 REFERENCE 560 "The OLSR version 2 draft. 561 Section 5 on Protocol Parameters." 562 ::= { olsrv2ConfigurationGroup 8 } 564 olsrv2FHoldTime OBJECT-TYPE 565 SYNTAX Unsigned32 (0..255) 566 UNITS "seconds" 567 MAX-ACCESS read-write 568 STATUS current 569 DESCRIPTION 570 "The olsrv2FHoldTime is the period after 571 receipt of a message which is forwarded 572 by this node for which that information 573 is recorded, in order that the message 574 is not forwarded again if received again. 576 The following constraint applies to this 577 parameter: 579 F_HOLD_TIME > 0 581 All of these parameters SHOULD be greater 582 than the maximum difference in time that a 583 message may take to traverse the MANET, 584 taking into account any message forwarding 585 jitter as well as propagation, queuing, 586 and processing delays." 587 DEFVAL { TBD } 588 REFERENCE 589 "The OLSR version 2 draft. 590 Section 5 on Protocol Parameters." 591 ::= { olsrv2ConfigurationGroup 9 } 593 -- Jitter times 595 olsrv2TpMaxJitter OBJECT-TYPE 596 SYNTAX Unsigned32 (0..65535) 597 UNITS "milliseconds" 598 MAX-ACCESS read-write 599 STATUS current 600 DESCRIPTION 601 "If jitter, as defined in [RFC5148], is used 602 then the jitter parameters are as follows: 604 olsrv2TpMaxJitter represents the value of 605 MAXJITTER used in [RFC5148] for periodically 606 generated TC messages sent by this node. 608 For constraints on these parameters, 609 see [RFC5148]." 610 DEFVAL { TBD } 611 REFERENCE 612 "The OLSR version 2 draft. 613 Section 5 on Protocol Parameters." 614 ::= { olsrv2ConfigurationGroup 10 } 616 olsrv2TtMaxJitter OBJECT-TYPE 617 SYNTAX Unsigned32 (0..65535) 618 UNITS "milliseconds" 619 MAX-ACCESS read-write 620 STATUS current 621 DESCRIPTION 622 "If jitter, as defined in [RFC5148], is used 623 then the jitter parameters are as follows: 625 olsrv2TtMaxJitter represents the value of 626 MAXJITTER used in [RFC5148] for externally 627 triggered TC messages sent by this node. 629 For constraints on these parameters, 630 see [RFC5148]." 631 DEFVAL { TBD } 632 REFERENCE 633 "The OLSR version 2 draft. 634 Section 5 on Protocol Parameters." 635 ::= { olsrv2ConfigurationGroup 11 } 637 olsrv2FMaxJitter OBJECT-TYPE 638 SYNTAX Unsigned32 (0..65535) 639 UNITS "milliseconds" 640 MAX-ACCESS read-write 641 STATUS current 642 DESCRIPTION 643 "If jitter, as defined in [RFC5148], is used 644 then the jitter parameters are as follows: 646 olsrv2FMaxJitter represents the default 647 value of MAXJITTER used in [RFC5148] for 648 messages forwarded by this node. However 649 before using F_MAXJITTER a node MAY attempt 650 to deduce a more appropriate value of MAXJITTER, 651 for example based on any INTERVAL_TIME or 652 VALIDITY_TIME TLVs contained in the message 653 to be forwarded. 655 For constraints on these parameters, 656 see [RFC5148]." 657 DEFVAL { TBD } 658 REFERENCE 659 "The OLSR version 2 draft. 660 Section 5 on Protocol Parameters." 661 ::= { olsrv2ConfigurationGroup 12 } 663 -- Hop limits 665 olsrv2TcHopLimit OBJECT-TYPE 666 SYNTAX Unsigned32 (0..255) 667 UNITS "hops" 668 MAX-ACCESS read-write 669 STATUS current 670 DESCRIPTION 671 "The parameter olsrv2TcHopLimit is the 672 hop limit set in each TC message. 673 TC_HOP_LIMIT MAY be a single fixed value, 674 or MAY be different in TC messages sent 675 by the same node. 677 The following constraint applies to this 678 parameter: 680 The maximum value of 681 olsrv2TcHopLimit >= the network diameter 682 in hops, a value of 255 is RECOMMENDED. 684 All values of olsrv2TcHopLimit >= 2." 685 DEFVAL { TBD } 686 REFERENCE 687 "The OLSR version 2 draft. 688 Section 5 on Protocol Parameters." 689 ::= { olsrv2ConfigurationGroup 13 } 691 -- Willingness 693 olsrv2Williness OBJECT-TYPE 694 SYNTAX Unsigned32 (0..255) 695 UNITS "" 696 MAX-ACCESS read-write 697 STATUS current 698 DESCRIPTION 699 "The olsrv2Williness MUST be in the range 700 WILL_NEVER (0) to WILL_ALWAYS (255), inclusive, 701 and represents its willingness to be an MPR, 702 and hence its willingness to forward messages 703 and be an intermediate node on routes. 705 Note: Need to rethink the range and units for 706 this parameter." 707 DEFVAL { TBD } 708 REFERENCE 709 "The OLSR version 2 draft. 710 Section 5 on Protocol Parameters." 711 ::= { olsrv2ConfigurationGroup 14 } 713 -- Local Attached Network Set 715 -- This table is part of the OLSR/NHDP 716 -- Local Information Base (LIB). It is 717 -- placed in the Configuration Group because 718 -- this table contains configured information. 720 olsrv2LibLocAttNetSetTable OBJECT-TYPE 721 SYNTAX SEQUENCE OF Olsrv2LibLocAttNetSetEntry 722 MAX-ACCESS not-accessible 723 STATUS obsolete 724 DESCRIPTION 725 " A node's Local Attached Network Set records 726 its local non-OLSRv2 interfaces that can act 727 as gateways to other networks. The Local 728 Attached Network Set is not modified by this 729 protocol. This protocol MAY respond to changes 730 to the Local Attached Network Set, which MUST 731 reflect corresponding changes in the node's status. 733 Note: Need clarification on the above claim that 734 this set records interface information. The 735 tuple included in this set is only network 736 address information." 737 REFERENCE 738 "The OLSRv2 draft." 739 ::= { olsrv2ConfigurationGroup 15 } 740 olsrv2LibLocAttNetSetEntry OBJECT-TYPE 741 SYNTAX Olsrv2LibLocAttNetSetEntry 742 MAX-ACCESS not-accessible 743 STATUS current 744 DESCRIPTION 745 "The entries include the Local Attached 746 Network Tuples: 748 (AL_net_addr, AL_dist) 750 where: 752 AL_net_addr is the network address 753 of an attached network which can 754 be reached via this node. 756 AL_dist is the number of hops to 757 the network with address AL_net_addr 758 from this node." 759 REFERENCE 760 "The OLSRv2 draft." 761 INDEX { olsrv2LibLocAttNetSetIpAddr, 762 olsrv2LibLocAttNetSetIpAddrPrefixLen } 763 ::= { olsrv2LibLocAttNetSetTable 1 } 765 Olsrv2LibLocAttNetSetEntry ::= 766 SEQUENCE { 767 olsrv2LibLocAttNetSetIpAddrType 768 InetAddressType, 769 olsrv2LibLocAttNetSetIpAddr 770 InetAddress, 771 olsrv2LibLocAttNetSetIpAddrPrefixLen 772 InetAddressPrefixLength, 773 olsrv2LibLocAttNetSetDistance 774 Unsigned32, 775 olsrv2LibLocAttNetSetRowStatus 776 RowStatus 777 } 779 olsrv2LibLocAttNetSetIpAddrType OBJECT-TYPE 780 SYNTAX InetAddressType 781 MAX-ACCESS read-write 782 STATUS current 783 DESCRIPTION 784 "The type of the olsrv2LibLocAttNetSetIpAddr, as defined 785 in the InetAddress MIB [RFC 4001]." 786 REFERENCE 787 "The OLSRv2 draft." 789 ::= { olsrv2LibLocAttNetSetEntry 1 } 791 olsrv2LibLocAttNetSetIpAddr OBJECT-TYPE 792 SYNTAX InetAddress 793 MAX-ACCESS read-write 794 STATUS current 795 DESCRIPTION 796 "This is the network address of an attached 797 network which can be reached via this node. 798 This node will act as a gateway for this 799 address for the OLSR MANET." 800 REFERENCE 801 "The OLSRv2 draft." 802 ::= { olsrv2LibLocAttNetSetEntry 2 } 804 olsrv2LibLocAttNetSetIpAddrPrefixLen OBJECT-TYPE 805 SYNTAX InetAddressPrefixLength 806 MAX-ACCESS read-write 807 STATUS current 808 DESCRIPTION 809 "Indicates the number of leading one bits that form the 810 mask to be logical-ANDed with the destination address 811 before being compared to the value in the 812 olsrv2LibLocAttNetSetIpAddr field." 813 REFERENCE 814 "The OLSRv2 draft." 815 ::= { olsrv2LibLocAttNetSetEntry 3 } 817 olsrv2LibLocAttNetSetDistance OBJECT-TYPE 818 SYNTAX Unsigned32 (1..255) 819 UNITS "hops" 820 MAX-ACCESS read-write 821 STATUS current 822 DESCRIPTION 823 "This object specifies the number of hops 824 to the network with address AL_net_addr 825 from this node." 826 REFERENCE 827 "The OLSRv2 draft." 828 ::= { olsrv2LibLocAttNetSetEntry 4 } 830 olsrv2LibLocAttNetSetRowStatus OBJECT-TYPE 831 SYNTAX RowStatus 832 MAX-ACCESS read-create 833 STATUS current 834 DESCRIPTION 835 "This object permits management of the table 836 by facilitating actions such as row creation, 837 construction, and destruction. The value of 838 this object has no effect on whether other 839 objects in this conceptual row can be 840 modified." 841 ::= { olsrv2LibLocAttNetSetEntry 5 } 843 -- 844 -- olsrv2StateGroup 845 -- 846 -- Contains information describing the current state of the 847 -- OLSRv2 routing process such as the ... 848 -- 850 -- 851 -- Note: the OLSRv2 draft discusses the option for dynamically 852 -- changing the values of the configuration parameters 853 -- identified above. In this case we would want to include 854 -- a set of state objects (potentially) which track the current 855 -- values or the range of values that these dynamic objects 856 -- have. 857 -- 859 olsrv2StateGroup OBJECT IDENTIFIER ::= { olsrv2MIBObjects 2 } 861 olsrv2NodeStatus OBJECT-TYPE 862 SYNTAX TruthValue 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "The current status of the OLSRv2 node 867 routing process ..." 868 ::= { olsrv2StateGroup 1 } 870 -- 871 -- The OLSRv2 draft defines several information bases 872 -- to be maintained by the OLSRv2 compliant nodes. 873 -- We list these in the order defined in the OLSRv2 874 -- draft. 875 -- 877 -- 878 -- Local Information Base - as defined in [nhdp], 879 -- extended by the addition of an Originator Set, 880 -- defined in Section 6.1.1 and a Local Attached 881 -- Network Set, defined in Section 6.1.2. 883 -- 885 -- Originator Set 887 olsrv2LibOrigSetTable OBJECT-TYPE 888 SYNTAX SEQUENCE OF Olsrv2LibOrigSetEntry 889 MAX-ACCESS not-accessible 890 STATUS obsolete 891 DESCRIPTION 892 " A node's Originator Set records addresses 893 that were recently originator addresses. 894 If a node's originator address is immutable 895 then this set is always empty and MAY be 896 omitted. It consists of Originator Tuples: 897 (O_orig_addr, O_time)." 898 REFERENCE 899 "The OLSRv2 draft." 900 ::= { olsrv2StateGroup 2 } 902 olsrv2LibOrigSetEntry OBJECT-TYPE 903 SYNTAX Olsrv2LibOrigSetEntry 904 MAX-ACCESS not-accessible 905 STATUS current 906 DESCRIPTION 907 " A node's Originator Set records addresses 908 that were recently originator addresses. 909 If a node's originator address is immutable 910 then this set is always empty and MAY be 911 omitted. It consists of Originator Tuples: 912 (O_orig_addr, O_time)." 913 REFERENCE 914 "The OLSRv2 draft." 915 INDEX { olsrv2LibOrigSetIpAddr } 916 ::= { olsrv2LibOrigSetTable 1 } 918 Olsrv2LibOrigSetEntry ::= 919 SEQUENCE { 920 olsrv2LibOrigSetIpAddrType 921 InetAddressType, 922 olsrv2LibOrigSetIpAddr 923 InetAddress, 924 olsrv2LibOrigSetExpireTime 925 Unsigned32 926 } 928 olsrv2LibOrigSetIpAddrType OBJECT-TYPE 929 SYNTAX InetAddressType 930 MAX-ACCESS read-only 931 STATUS current 932 DESCRIPTION 933 "The type of the olsrv2LibOrigSetIpAddr, as defined 934 in the InetAddress MIB [RFC 4001]." 935 REFERENCE 936 "The OLSRv2 draft." 937 ::= { olsrv2LibOrigSetEntry 1 } 939 olsrv2LibOrigSetIpAddr OBJECT-TYPE 940 SYNTAX InetAddress 941 MAX-ACCESS read-only 942 STATUS current 943 DESCRIPTION 944 "A recently used originator address 945 by this node." 946 REFERENCE 947 "The OLSRv2 draft." 948 ::= { olsrv2LibOrigSetEntry 2 } 950 olsrv2LibOrigSetExpireTime OBJECT-TYPE 951 SYNTAX Unsigned32 (0..65535) 952 UNITS "milliseconds" 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "This object specifies the time at which this 957 entry expires and MUST be removed. 959 Note: need to change the type here to a time/date type, 960 not a time in seconds left to expire." 961 REFERENCE 962 "The OLSRv2 draft." 963 ::= { olsrv2LibOrigSetEntry 3 } 965 -- 966 -- Interface Information Bases - as defined in 967 -- [nhdp], one Interface Information Base for 968 -- each OLSRv2 interface. 969 -- 971 -- Note: The IIB is fully defined in the NHRP 972 -- and its associated MIB. 974 -- 975 -- Node Information Base - as defined in [nhdp], 976 -- extended by the addition of three elements to 977 -- each Neighbor Tuple, as defined in Section 6.2. 978 -- 980 -- Neighbor Set 982 olsrv2NibNeighborSetTable OBJECT-TYPE 983 SYNTAX SEQUENCE OF Olsrv2NibNeighborSetEntry 984 MAX-ACCESS not-accessible 985 STATUS obsolete 986 DESCRIPTION 987 "Each Neighbor Tuple in the Neighbor Set, defined 988 in [nhdp], has these additional elements: 989 N_willingness 990 N_mpr 991 N_mpr_selector 992 defined here as extensions." 993 REFERENCE 994 "The OLSRv2 draft." 995 ::= { olsrv2StateGroup 4 } 997 olsrv2NibNeighborSetEntry OBJECT-TYPE 998 SYNTAX Olsrv2NibNeighborSetEntry 999 MAX-ACCESS not-accessible 1000 STATUS current 1001 DESCRIPTION 1002 "Each Neighbor Tuple in the Neighbor Set, defined 1003 in [nhdp], has these additional elements: 1004 N_willingness 1005 N_mpr 1006 N_mpr_selector 1007 defined here as extensions." 1008 REFERENCE 1009 "The OLSRv2 draft." 1010 INDEX { olsrv2NibNeighborSetNodeId } 1011 ::= { olsrv2NibNeighborSetTable 1 } 1013 Olsrv2NibNeighborSetEntry ::= 1014 SEQUENCE { 1015 olsrv2NibNeighborSetNodeId 1016 NeighborNodeId, 1017 olsrv2NibNeighborSetNWilliness 1018 Unsigned32, 1019 olsrv2NibNeighborSetNMpr 1020 TruthValue, 1021 olsrv2NibNeighborSetNMprSelector 1022 TruthValue 1023 } 1025 olsrv2NibNeighborSetNodeId OBJECT-TYPE 1026 SYNTAX NeighborNodeId 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "The object olsrv2NibNeighborSetNodeId is 1031 the locally assigned ID of the remote node 1032 referenced in this row. The IP addrs 1033 associated with this node is contained 1034 in the NHDP-MIB's 'nhdpDiscIfSetTable'. 1035 " 1036 REFERENCE 1037 "The OLSRv2 draft." 1038 ::= { olsrv2NibNeighborSetEntry 1 } 1040 olsrv2NibNeighborSetNWilliness OBJECT-TYPE 1041 SYNTAX Unsigned32 (1..255) 1042 UNITS "" 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 UNITS "" 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "This object, N_mpr, is a boolean flag, 1061 describing if this neighbor is selected as 1062 an MPR by this node. 1064 When set to 'true', this neighbor is selected 1065 as an MPR by this node. When set to 'false', 1066 it is not selected by this node as an MPR." 1067 REFERENCE 1068 "The OLSRv2 draft." 1069 ::= { olsrv2NibNeighborSetEntry 3 } 1070 olsrv2NibNeighborSetNMprSelector OBJECT-TYPE 1071 SYNTAX TruthValue 1072 UNITS "" 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "This object, N_mpr_selector, is a boolean flag, 1077 describing if this neighbor has selected this node 1078 as an MPR, i.e. is an MPR selector of this node. 1080 When set to 'true', then this node is selected as 1081 an MPR by the neighbor node. When set to 'false', 1082 then this node is not selected by the neighbor 1083 as an MPR" 1084 REFERENCE 1085 "The OLSRv2 draft." 1086 ::= { olsrv2NibNeighborSetEntry 4 } 1088 -- 1089 -- Topology Information Base - this Information 1090 -- Base is specific to OLSRv2, and is defined in 1091 -- Section 6.3. 1092 -- 1094 -- Advertised Neighbor Set 1096 olsrv2TipAdNeighborSetSeqNo OBJECT-TYPE 1097 SYNTAX Unsigned32 (0..65535) 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "The Advertised Neighbor Set Sequence Number 1102 (ANSN) is maintained associated with the 1103 olsrv2TipAdNeighborSetTable. Each time the 1104 Advertised Neighbor Set Table is updated, the 1105 ANSN MUST be incremented. The ANSN MUST also 1106 be incremented if there is a change to the 1107 set of Local Attached Network Tuples that are to 1108 be advertised in the node's TC messages." 1109 REFERENCE 1110 "The OLSRv2 draft." 1111 ::= { olsrv2StateGroup 5 } 1112 olsrv2TipAdNeighborSetTable 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 olsrv2NibNeighborSetIpAddr 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 read-only 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 olsrv2TipAdRemoteNodeSetTable 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 ::= { olsrv2TibAdNeighborSetTable 1 } 1204 Olsrv2TibAdNeighborSetEntry ::= 1205 SEQUENCE { 1206 olsrv2TibAdRemoteNodeSetIpAddrType 1207 InetAddressType, 1208 olsrv2TibAdRemoteNodeSetIpAddr 1209 InetAddress, 1210 olsrv2TibAdRemoteNodeSetNodeId 1211 NeighborNodeId, 1212 olsrv2TibAdRemoteNodeSetMaxSeqNo 1213 Unsigned32, 1214 olsrv2TibAdRemoteNodeSetExpireTime 1215 Unsigned32 1216 } 1218 olsrv2TibAdRemoteNodeSetIpAddrType OBJECT-TYPE 1219 SYNTAX InetAddressType 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "The type of the olsrv2TibAdRemoteNodeSetIpAddr, 1224 as defined in the InetAddress MIB [RFC 4001]." 1225 REFERENCE 1226 "The OLSRv2 draft." 1227 ::= { olsrv2TibAdRemoteNodeSetEntry 1 } 1229 olsrv2TibAdRemoteNodeSetIpAddr OBJECT-TYPE 1230 SYNTAX InetAddress 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "This is the originator address of a received 1235 TC message." 1236 REFERENCE 1237 "The OLSRv2 draft." 1238 ::= { olsrv2TibAdRemoteNodeSetEntry 2 } 1240 olsrv2TibAdRemoteNodeSetNodeId OBJECT-TYPE 1241 SYNTAX NeighborNodeId 1242 UNITS "" 1243 MAX-ACCESS read-only 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 olsrv2TipAdRemoteNodeSetMaxSeqNo OBJECT-TYPE 1254 SYNTAX Unsigned32 (0..65535) 1255 UNITS "" 1256 MAX-ACCESS read-only 1257 STATUS current 1258 DESCRIPTION 1259 "The is the greatest ANSN in any TC message 1260 received which originated from the node 1261 with originator address AR_orig_addr 1262 (i.e. which contributed to the information 1263 contained in this Tuple)." 1264 REFERENCE 1265 "The OLSRv2 draft." 1266 ::= { olsrv2TibAdRemoteNodeSetEntry 4 } 1268 -- Need to change this type to a time syntax. 1269 olsrv2TipAdRemoteNodeSetExpireTime OBJECT-TYPE 1270 SYNTAX Unsigned32 (0..65535) 1271 UNITS "" 1272 MAX-ACCESS read-only 1273 STATUS current 1274 DESCRIPTION 1275 "The AR_time is the time at which this 1276 Tuple expires and MUST be removed." 1277 REFERENCE 1278 "The OLSRv2 draft." 1279 ::= { olsrv2TibAdRemoteNodeSetEntry 5 } 1281 -- Topology Set 1283 -- Note: Need to think more about the structure of this table 1284 -- due to the existence of multiple DestAddrs per Orig Addr 1286 olsrv2TipTopologySetTable OBJECT-TYPE 1287 SYNTAX SEQUENCE OF Olsrv2TibTopologySetEntry 1288 MAX-ACCESS not-accessible 1289 STATUS obsolete 1290 DESCRIPTION 1291 "A node's Topology Set records topology 1292 information about the network." 1293 REFERENCE 1294 "The OLSRv2 draft." 1295 ::= { olsrv2StateGroup 8 } 1297 olsrv2TibTopologySetEntry OBJECT-TYPE 1298 SYNTAX Olsrv2TibTopologySetEntry 1299 MAX-ACCESS not-accessible 1300 STATUS current 1301 DESCRIPTION 1302 "It consists of Topology Tuples: 1304 (T_dest_iface_addr, T_orig_addr, 1305 T_seq_number, T_time)" 1306 REFERENCE 1307 "The OLSRv2 draft." 1308 INDEX { olsrv2TibTopologySetDestIfIpAddr } 1309 ::= { olsrv2TibTopologySetTable 1 } 1311 Olsrv2TibTopologySetEntry ::= 1312 SEQUENCE { 1313 olsrv2TibTopologySetDestIfIpAddr 1314 InetAddress, 1315 olsrv2TibTopologySetOrigIpAddrType 1316 InetAddressType, 1317 olsrv2TibTopologySetOrigIpAddr 1318 InetAddress, 1319 olsrv2TibTopologySetSeqNo 1320 Unsigned32, 1321 olsrv2TibTopologySetExpireTime 1322 Unsigned32 1323 } 1325 olsrv2TibTopologySetDestIfIpAddrType OBJECT-TYPE 1326 SYNTAX InetAddressType 1327 MAX-ACCESS read-only 1328 STATUS current 1329 DESCRIPTION 1330 "The type of the olsrv2TibTopologySetDestIfIpAddr 1331 and olsrv2TibTopologySetDestIfIpAddr, 1332 as defined in the InetAddress MIB [RFC 4001]." 1333 REFERENCE 1334 "The OLSRv2 draft." 1335 ::= { olsrv2TibTopologySetEntry 1 } 1337 olsrv2TibTopologySetDestIfIpAddr OBJECT-TYPE 1338 SYNTAX InetAddress 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION 1342 "This is an interface address of a 1343 destination node, which may be reached 1344 in one hop from the node with originator 1345 address T_orig_addr." 1346 REFERENCE 1347 "The OLSRv2 draft." 1348 ::= { 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 olsrv2TipTopologySetSeqNo 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 olsrv2TipTopologySetExpireTime OBJECT-TYPE 1391 SYNTAX Unsigned32 (0..65535) 1392 UNITS "" 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." 1398 REFERENCE 1399 "The OLSRv2 draft." 1400 ::= { olsrv2TibTopologySetEntry 6 } 1402 -- Attached Network Set 1404 olsrv2TipAttNetworksSetTable OBJECT-TYPE 1405 SYNTAX SEQUENCE OF Olsrv2TibAttNetworksSetEntry 1406 MAX-ACCESS not-accessible 1407 STATUS obsolete 1408 DESCRIPTION 1409 "A node's Attached Network Set records information 1410 about networks attached to other nodes." 1411 REFERENCE 1412 "The OLSRv2 draft." 1413 ::= { olsrv2StateGroup 9 } 1415 olsrv2TibAttNetworksSetEntry OBJECT-TYPE 1416 SYNTAX Olsrv2TibAttNetworksSetEntry 1417 MAX-ACCESS not-accessible 1418 STATUS current 1419 DESCRIPTION 1420 "It consists of Attached Network Tuples: 1422 (AN_net_addr, AN_orig_addr, 1423 AN_dist, AN_seq_number, AN_time)" 1425 REFERENCE 1426 "The OLSRv2 draft." 1427 INDEX { olsrv2TibAttNetworksSetNetIpAddrType, 1428 olsrv2TibAttNetworksSetNetIpAddr, 1429 olsrv2TibAttNetworksSetNetIpAddrPrefixLen } 1430 ::= { olsrv2TibTopologySetTable 1 } 1432 Olsrv2TibAttNetworksSetEntry ::= 1433 SEQUENCE { 1434 olsrv2TibAttNetworksSetNetIpAddrType 1435 InetAddressType, 1436 olsrv2TibAttNetworksSetNetIpAddr 1437 InetAddress, 1438 olsrv2TibAttNetworksSetNetIpAddrPrefixLen 1439 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 read-only 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 olsrv2TipAttNetworksSetDist OBJECT-TYPE 1502 SYNTAX Unsigned32 (0..255) 1503 MAX-ACCESS read-only 1504 UNITS "hops" 1505 STATUS current 1506 DESCRIPTION 1507 "The is the number of hops to the network 1508 with address AN_net_addr from the node with 1509 originator address AN_orig_addr." 1510 REFERENCE 1511 "The OLSRv2 draft." 1512 ::= { olsrv2TibAttNetworksSetEntry 5 } 1514 olsrv2TipAttNetworksSetSeqNo OBJECT-TYPE 1515 SYNTAX Unsigned32 (0..65535) 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "The is the greatest ANSN in any TC 1520 message received which originated from the 1521 node with originator address AN_orig_addr 1522 (i.e. which contributed to the information 1523 contained in this Tuple)." 1524 REFERENCE 1525 "The OLSRv2 draft." 1526 ::= { olsrv2TibAttNetworksSetEntry 6 } 1528 -- Need to change this type to a time syntax. 1529 olsrv2TipAttNetworksSetExpireTime OBJECT-TYPE 1530 SYNTAX Unsigned32 (0..65535) 1531 UNITS "" 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 olsrv2TipRoutingSetTable OBJECT-TYPE 1551 SYNTAX SEQUENCE OF Olsrv2TibRoutingSetSetEntry 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 Olsrv2TibAttNetworksSetEntry ::= 1578 SEQUENCE { 1579 olsrv2TibRoutingSetDestIpAddrType 1580 InetAddressType, 1581 olsrv2TibRoutingSetDestIpAddr 1582 InetAddress, 1583 olsrv2TibRoutingSetDestIpAddrPrefLen 1584 InetAddressPrefixLength, 1585 olsrv2TibRoutingSetNextIfIpAddr 1586 InetAddress, 1587 olsrv2TibRoutingSetDist 1588 Unsigned32, 1589 olsrv2TibRoutingSetLocalIfIpAddr 1590 InetAddress 1591 } 1593 olsrv2TibRoutingSetDestIpAddrType OBJECT-TYPE 1594 SYNTAX InetAddressType 1595 MAX-ACCESS not-accessible 1596 STATUS current 1597 DESCRIPTION 1598 "The type of the olsrv2TibRoutingSetDestIpAddr 1599 and olsrv2TibRoutingSetNextIfIpAddr, 1600 as defined in the InetAddress MIB [RFC 4001]." 1601 REFERENCE 1602 "The OLSRv2 draft." 1603 ::= { olsrv2TibRoutingSetEntry 1 } 1605 olsrv2TibRoutingSetDestIpAddr OBJECT-TYPE 1606 SYNTAX InetAddress 1607 MAX-ACCESS not-accessible 1608 STATUS current 1609 DESCRIPTION 1610 "This is the address of the destination, 1611 either the address of an interface of 1612 a destination node, or the network 1613 address of an attached network." 1614 REFERENCE 1615 "The OLSRv2 draft." 1616 ::= { olsrv2TibRoutingSetEntry 2 } 1618 olsrv2TibRoutingSetDestIpAddrPrefixLen OBJECT-TYPE 1619 SYNTAX InetAddressPrefixLength 1620 MAX-ACCESS not-accessible 1621 STATUS current 1622 DESCRIPTION 1623 "Indicates the number of leading one bits that form the 1624 mask to be logical-ANDed with the destination address 1625 before being compared to the value in the 1626 olsrv2TibRoutingSetDestNetIpAddr field. 1628 Note: This definition needs to be consistent 1629 with the current forwarding table MIB description. 1630 Specifically, it should allow for longest prefix 1631 matching of network addresses." 1632 REFERENCE 1633 "The OLSRv2 draft." 1634 ::= { olsrv2TibRoutingSetEntry 3 } 1636 olsrv2TibRoutingSetNextIfIpAddr OBJECT-TYPE 1637 SYNTAX InetAddress 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "This is the OLSRv2 interface address of the 1642 'next hop' on the selected path to the 1643 destination." 1644 REFERENCE 1645 "The OLSRv2 draft." 1646 ::= { olsrv2TibRoutingSetEntry 4 } 1648 olsrv2TipRoutingSetDist OBJECT-TYPE 1649 SYNTAX Unsigned32 (0..255) 1650 MAX-ACCESS read-only 1651 UNITS "hops" 1652 STATUS current 1653 DESCRIPTION 1654 "The is the number of hops on the selected 1655 path to the destination." 1656 REFERENCE 1657 "The OLSRv2 draft." 1658 ::= { olsrv2TibRoutingSetEntry 5 } 1660 olsrv2TibRoutingSetLocalIfIpAddr OBJECT-TYPE 1661 SYNTAX InetAddress 1662 MAX-ACCESS read-only 1663 STATUS current 1664 DESCRIPTION 1665 "This is the address of the local OLSRv2 1666 interface over which a packet MUST be 1667 sent to reach the destination by the 1668 selected path." 1669 REFERENCE 1670 "The OLSRv2 draft." 1671 ::= { olsrv2TibRoutingSetEntry 6 } 1673 -- 1674 -- Processing and Forwarding Information Base - this 1675 -- Information Base is specific to OLSRv2, and 1676 -- is defined in Section 6.4. 1677 -- 1679 -- Note: Is it appropriate or necessary to put the 1680 -- level of detail found in the Processing and 1681 -- Forwarding Information Base into the OLSRv2-MIB? 1683 -- Received Set 1685 -- Processed Set 1687 -- Forwarded Set 1689 -- Relayed Set 1691 -- 1692 -- OLSRv2 Performance Group 1693 -- 1694 -- Contains objects which help to characterize the 1695 -- performance of the OLSRv2 routing process, such as ... 1696 -- 1698 olsrv2PerformanceGroup OBJECT IDENTIFIER ::= { olsrv2MIBObjects 3 } 1700 olsrv2GlPerfGroup OBJECT IDENTIFIER ::= {olsrv2PerformanceGroup 1} 1702 -- Note: Objects to be defined. 1704 -- 1705 -- Per OLSRv2 Interface Performance Table 1706 -- 1708 olsrv2IfPerfGroup OBJECT IDENTIFIER ::= {olsrv2PerformanceGroup 2} 1710 -- Note: Objects to be defined. 1712 -- 1713 -- Notifications 1714 -- 1716 -- Note: What notifications do we want for this MIB? 1717 -- 1718 -- Compliance Statements 1719 -- 1721 -- Note: need to update the Compliance section once the mib 1722 -- objects stabilize. 1724 olsrv2Compliances OBJECT IDENTIFIER ::= { olsrv2MIBConformance 1 } 1725 olsrv2MIBGroups OBJECT IDENTIFIER ::= { olsrv2MIBConformance 2 } 1727 olsrv2BasicCompliance MODULE-COMPLIANCE 1728 STATUS current 1729 DESCRIPTION "The basic implementation requirements for 1730 managed network entities that implement 1731 the OLSRv2 routing process." 1732 MODULE -- this module 1733 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup } 1734 ::= { olsrv2Compliances 1 } 1736 olsrv2FullCompliance MODULE-COMPLIANCE 1737 STATUS current 1738 DESCRIPTION "The full implementation requirements for 1739 managed network entities that implement 1740 the OLSRv2 routing process." 1741 MODULE -- this module 1742 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup, 1743 olsrv2StateObjectsGroup, 1744 olsrv2PerfObjectsGroup } 1745 ::= { olsrv2Compliances 2 } 1747 -- 1748 -- Units of Conformance 1749 -- 1751 olsrv2ConfigObjectsGroup OBJECT-GROUP 1752 OBJECTS { 1753 losrv2OperationalMode 1754 } 1755 STATUS current 1756 DESCRIPTION 1757 "Set of OLSRv2 configuration objects implemented 1758 in this module." 1759 ::= { olsrv2MIBGroups 1 } 1761 olsrv2StateObjectsGroup OBJECT-GROUP 1762 OBJECTS { 1763 olsrv2NodeStatus 1765 } 1766 STATUS current 1767 DESCRIPTION 1768 "Set of OLSRv2 state objects implemented 1769 in this module." 1770 ::= { olsrv2MIBGroups 2 } 1772 olsrv2PerfObjectsGroup OBJECT-GROUP 1773 OBJECTS { 1774 olsrv2PktsRecvTotal 1775 } 1776 STATUS current 1777 DESCRIPTION 1778 "Set of OLSRv2 performance objects implemented 1779 in this module by total and per interface." 1780 ::= { olsrv2MIBGroups 3 } 1782 END 1784 8. Security Considerations 1786 [TODO] Each specification that defines one or more MIB modules MUST 1787 contain a section that discusses security considerations relevant to 1788 those modules. This section MUST be patterned after the latest 1789 approved template (available at 1790 http://www.ops.ietf.org/mib-security.html). Remember that the 1791 objective is not to blindly copy text from the template, but rather 1792 to think and evaluate the risks/vulnerabilities and then state/ 1793 document the result of this evaluation. 1795 [TODO] if you have any read-write and/or read-create objects, please 1796 include the following boilerplate paragraph. 1798 There are a number of management objects defined in this MIB module 1799 with a MAX-ACCESS clause of read-write and/or read-create. Such 1800 objects may be considered sensitive or vulnerable in some network 1801 environments. The support for SET operations in a non-secure 1802 environment without proper protection can have a negative effect on 1803 network operations. These are the tables and objects and their 1804 sensitivity/vulnerability: 1806 o [TODO] writable MIB objects that could be especially disruptive if 1807 abused MUST be explicitly listed by name and the associated 1808 security risks MUST be spelled out; RFC 2669 has a very good 1809 example. 1811 o [TODO] list the writable tables and objects and state why they are 1812 sensitive. 1814 [TODO] else if there are no read-write objects in your MIB module, 1815 use the following boilerplate paragraph. 1817 There are no management objects defined in this MIB module that have 1818 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1819 MIB module is implemented correctly, then there is no risk that an 1820 intruder can alter or create any management objects of this MIB 1821 module via direct SNMP SET operations. 1823 [TODO] if you have any sensitive readable objects, please include the 1824 following boilerplate paragraph. 1826 Some of the readable objects in this MIB module (i.e., objects with a 1827 MAX-ACCESS other than not-accessible) may be considered sensitive or 1828 vulnerable in some network environments. It is thus important to 1829 control even GET and/or NOTIFY access to these objects and possibly 1830 to even encrypt the values of these objects when sending them over 1831 the network via SNMP. These are the tables and objects and their 1832 sensitivity/vulnerability: 1834 o [TODO] you must explicitly list by name any readable objects that 1835 are sensitive or vulnerable and the associated security risks MUST 1836 be spelled out (for instance, if they might reveal customer 1837 information or violate personal privacy laws such as those of the 1838 European Union if exposed to unauthorized parties) 1840 o [TODO] list the tables and objects and state why they are 1841 sensitive. 1843 [TODO] discuss what security the protocol used to carry the 1844 information should have. The following three boilerplate paragraphs 1845 should not be changed without very good reason. Changes will almost 1846 certainly require justification during IESG review. 1848 SNMP versions prior to SNMPv3 did not include adequate security. 1849 Even if the network itself is secure (for example by using IPSec), 1850 even then, there is no control as to who on the secure network is 1851 allowed to access and GET/SET (read/change/create/delete) the objects 1852 in this MIB module. 1854 It is RECOMMENDED that implementers consider the security features as 1855 provided by the SNMPv3 framework (see [RFC3410], section 8), 1856 including full support for the SNMPv3 cryptographic mechanisms (for 1857 authentication and privacy). 1859 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1860 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1861 enable cryptographic security. It is then a customer/operator 1862 responsibility to ensure that the SNMP entity giving access to an 1863 instance of this MIB module is properly configured to give access to 1864 the objects only to those principals (users) that have legitimate 1865 rights to indeed GET or SET (change/create/delete) them. 1867 9. IANA Considerations 1869 [TODO] In order to comply with IESG policy as set forth in 1870 http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is 1871 submitted to the IESG for publication MUST contain an IANA 1872 Considerations section. The requirements for this section vary 1873 depending what actions are required of the IANA. see RFC4181 section 1874 3.5 for more information on writing an IANA clause for a MIB module 1875 document. 1877 [TODO] select an option and provide the necessary details. 1879 Option #1: 1881 The MIB module in this document uses the following IANA-assigned 1882 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1884 Descriptor OBJECT IDENTIFIER value 1885 ---------- ----------------------- 1887 sampleMIB { mib-2 XXX } 1889 Option #2: 1891 Editor's Note (to be removed prior to publication): the IANA is 1892 requested to assign a value for "XXX" under the 'mib-2' subtree and 1893 to record the assignment in the SMI Numbers registry. When the 1894 assignment has been made, the RFC Editor is asked to replace "XXX" 1895 (here and in the MIB module) with the assigned value and to remove 1896 this note. 1898 Note well: prior to official assignment by the IANA, a draft document 1899 MUST use place holders (such as "XXX" above) rather than actual 1900 numbers. See RFC4181 Section 4.5 for an example of how this is done 1901 in a draft MIB module. 1903 Option #3: 1905 This memo includes no request to IANA. 1907 10. Contributors 1909 This MIB document uses the template authored by D. Harrington which 1910 is based on contributions from the MIB Doctors, especially Juergen 1911 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 1913 11. Acknowledgements 1915 12. References 1917 12.1. Normative References 1919 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1920 Interfaces Group MIB", RFC 2863, June 2000. 1922 [RFC3418] Presuhn, R., "Management Information Base 1923 (MIB) for the Simple Network Management 1924 Protocol (SNMP)", STD 62, RFC 3418, 1925 December 2002. 1927 [RFC2119] Bradner, S., "Key words for use in RFCs to 1928 Indicate Requirement Levels", BCP 14, 1929 RFC 2119, March 1997. 1931 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and 1932 J. Schoenwaelder, Ed., "Structure of 1933 Management Information Version 2 (SMIv2)", 1934 STD 58, RFC 2578, April 1999. 1936 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and 1937 J. Schoenwaelder, Ed., "Textual Conventions 1938 for SMIv2", STD 58, RFC 2579, April 1999. 1940 [RFC2580] McCloghrie, K., Perkins, D., and J. 1941 Schoenwaelder, "Conformance Statements for 1942 SMIv2", STD 58, RFC 2580, April 1999. 1944 [I-D.ietf-manet-olsrv2] Clausen, T., Dearlove, C., and P. Jacquet, 1945 "The Optimized Link State Routing Protocol 1946 version 2", draft-ietf-manet-olsrv2-07 (work 1947 in progress), July 2008. 1949 12.2. Informative References 1951 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 1952 Stewart, "Introduction and Applicability 1953 Statements for Internet-Standard Management 1954 Framework", RFC 3410, December 2002. 1956 Appendix A. Change Log 1958 This section identifies the cahnges made during the development of 1959 this MIB. 1961 Here we list the changes made in developing 1962 draft-cole-manet-olsr-mib-01. 1964 1. Completely reworked the entire Configuration Objects group in 1965 order to align with the newly developed NHDP-MIB draft. 1967 Appendix B. Open Issues 1969 This section contains the set of open issues related to the 1970 development and design of the OLSRv2-MIB. This section will not be 1971 present in the final version of the MIB and will be removed once all 1972 the open issues have been resolved. 1974 1. Look into possible redundancy between the TIB Routing Set and 1975 the latest standard MIB forwarding table. 1977 2. Fill out the performance objects group. 1979 3. Complete notification group. 1981 4. Complete conformance group. 1983 5. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 1985 6. Identify all objects requiring non-volatile storage in their 1986 DESCRIPTION clauses. 1988 7. Incorporate parameter relationship conditions into their 1989 DESCRIPTION clauses. 1991 8. Also, specify specific SNMP response to the snmp set request, 1992 i.e., 'generic error', 'bad value', etc. 1994 9. Fill in all of the DEFVAL within the configuration group 1995 objects. 1997 10. Run through the MIB checker. 1999 11. Complete the security analysis and section. 2001 12. Clean up all of the 'Note:' statements within the body of the 2002 MIB. 2004 13. Cleanup all the [TODOs] from the MIB template. 2006 Appendix C. 2008 *************************************************************** 2009 * Note to the RFC Editor (to be removed prior to publication) * 2010 * * 2011 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 2012 * of the MIB module point to this draft and are to be * 2013 * assigned by the RFC Editor. * 2014 * * 2015 * 2) The reference to RFCXXX2 throughout this document point * 2016 * to the current draft-ietf-manet-olsrv2-xx.txt. This * 2017 * need to be replaced with the XXX RFC number. * 2018 * * 2019 *************************************************************** 2021 Authors' Addresses 2023 Robert G. Cole 2024 Johns Hopkins University 2025 11100 Johns Hopkins Road, Room 257 2026 Laurel, Maryland 21073 2027 USA 2029 Phone: +1 443 778 6951 2030 EMail: robert.cole@jhuapl.edu 2031 URI: http://www.cs.jhu.edu/~rgcole/ 2033 Thomas Heide Clausen 2034 LIX, Ecole Polytechnique 2035 France 2037 Phone: +33 6 6058 9349 2038 EMail: T.Clausen@computer.org 2039 URI: http://www.ThomasClausen.org/