idnits 2.17.1 draft-herberg-lln-loadng-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (July 4, 2014) is 3555 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) == Outdated reference: A later version (-15) exists of draft-clausen-lln-loadng-09 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force U. Herberg 3 Internet-Draft Fujitsu Laboratories of America 4 Intended status: Standards Track R. Cole 5 Expires: January 5, 2015 US Army CERDEC 6 T. Clausen 7 LIX, Ecole Polytechnique 8 July 4, 2014 10 Definition of Managed Objects for the Lightweight On-demand Ad hoc 11 Distance-vector Routing Protocol - Next Generation (LOADng) 12 draft-herberg-lln-loadng-mib-04 14 Abstract 16 This memo defines a portion of the Management Information Base (MIB) 17 for use with network management protocols in the Internet community. 18 In particular, it describes objects for configuring parameters of the 19 Lightweight On-demand Ad hoc Distance-vector Routing Protocol - Next 20 Generation (LOADng) process on a router. The MIB module defined in 21 this memo, denoted LOADng-MIB, also reports state. While LOADng is 22 layer agnostic and can be run with different address families (e.g., 23 on L2 using MAC addresses, or on L3 using IP address), this MIB 24 module assumes that LOADng is used on L3, and uses only IPv4/IPv6 25 addresses. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on January 5, 2015. 44 Copyright Notice 46 Copyright (c) 2014 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 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. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 67 5.1. The Configuration Group . . . . . . . . . . . . . . . . . 4 68 5.2. The State Group . . . . . . . . . . . . . . . . . . . . . 5 69 5.3. Tables and Indexing . . . . . . . . . . . . . . . . . . . 5 70 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 71 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 6 72 6.2. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 6 73 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 74 8. Security Considerations . . . . . . . . . . . . . . . . . . . 39 75 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 76 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 42 77 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 42 78 11.1. Normative References . . . . . . . . . . . . . . . . . . . 42 79 11.2. Informative References . . . . . . . . . . . . . . . . . . 42 80 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 43 82 1. Introduction 84 This document defines a portion of the Management Information Base 85 (MIB) for use with network management protocols in the Internet 86 community. In particular, it describes objects for configuring 87 parameters of the Lightweight On-demand Ad hoc Distance-vector 88 Routing Protocol - Next Generation (LOADng) [LOADng] process on a 89 router. The MIB module defined in this document, denoted LOADng-MIB, 90 also reports state. While LOADng is layer agnostic and can be run 91 with different address families (e.g., on L2 using MAC addresses, or 92 on L3 using IP address), this MIB module assumes that LOADng is used 93 on L3, and uses only IPv4/IPv6 addresses. 95 2. The Internet-Standard Management Framework 97 For a detailed overview of the documents that describe the current 98 Internet-Standard Management Framework, please refer to section 7 of 99 RFC 3410 [RFC3410]. 101 Managed objects are accessed via a virtual information store, termed 102 the Management Information Base or MIB. MIB objects are generally 103 accessed through the Simple Network Management Protocol (SNMP). 104 Objects in the MIB are defined using the mechanisms defined in the 105 Structure of Management Information (SMI). This memo specifies a MIB 106 module that is compliant to SMIv2, which is described in STD 58, RFC 107 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 108 [RFC2580]. 110 3. Conventions 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 114 OPTIONAL" in this document are to be interpreted as described in 115 [RFC2119]. 117 4. Overview 119 The Lightweight On-demand Ad hoc Distance-vector Routing Protocol - 120 Next Generation (LOADng) [LOADng] is a routing protocol, derived from 121 AODV [RFC3561] and extended for use in Mobile Ad Hoc Networks 122 (MANETs). As a reactive protocol, the basic operations of LOADng 123 include generation of Route Requests (RREQs) by a router (originator) 124 for when discovering a route to a destination, forwarding of such 125 RREQs until they reach the destination router, generation of Route 126 Replies (RREPs) upon receipt of an RREQ by the indicated destination, 127 and unicast hop-by-hop forwarding of these RREPs towards the 128 originator. If a route is detected broken, i.e., if forwarding of a 129 data packet to the recorded next hop on the route to the destination 130 is detected to fail, a Route Error (RERR) message is returned in 131 unicast to the originator of that data packet. 133 This MIB module describes objects for configuring parameters of a 134 LOADng process on a router, as well as for the relevant state of a 135 LOADng process on a router, in order to monitor and manage parameters 136 and information bases of LOADng. 138 4.1. Terms 140 The following definitions apply throughout this document: 142 o Configuration Objects - switches, tables, objects which are 143 initialized to default settings or set through the management 144 interface defined by this MIB module. 146 o State Objects - automatically generated values which define the 147 current operating state of the LOADng protocol process in the 148 router. 150 5. Structure of the MIB Module 152 This section presents the structure of the LOADng-MIB module. The 153 MIB module is arranged into the following structure: 155 o LOADngObjects - defining objects within this MIB module. The 156 objects are arranged into the following groups: 158 * Configuration Group - defining objects related to the 159 configuration of the LOADng instance on the router. 161 * State Group - defining objects which reflect the current state 162 of the LOADng instance running on the router. 164 o LOADngConformance - defining the minimal and maximal conformance 165 requirements for implementations of this MIB module. 167 5.1. The Configuration Group 169 The LOADng router is configured with a set of controls. The 170 authoritative list of configuration controls within the LOADng-MIB 171 module are found within the MIB module itself. Generally, an attempt 172 was made in developing the LOADng-MIB module to support all 173 configuration objects defined in [LOADng]. For all of the 174 configuration parameters, the same default values of these parameters 175 as defined in [LOADng] are followed. 177 5.2. The State Group 179 The State Group reports current state information of a router running 180 [LOADng]. The LOADng-MIB State Group tables were designed to contain 181 the complete set of state information defined within the information 182 bases specified in Section 6 of [LOADng]. 184 5.3. Tables and Indexing 186 The LOADng-MIB module contains a number of tables which record data 187 related to: 189 o the local LOADng router, 191 o a local LOADng interface on the LOADng router, 193 o other LOADng routers in the routing domain. 195 The LOADng-MIB module's tables and their indexing are: 197 o loadngInterfaceTable - describes the configuration of the 198 interfaces of this LOADng router. This table is indexed by 199 loadngIfIndex. 201 o loadngLibLocalIfSetTable - records all network addresses which are 202 defined as local interface network addresses on this LOADng 203 router. This table is indexed by loadngLibLocalIfSetIfAddrIndex, 204 loadngLibLocalIfSetIfIndex. 206 o loadngLibDestaddressetTable - records addresses, for which a 207 LOADng Router will generate RREPs in response to received RREQs, 208 in addition to its own interface addresses (as listed in the Local 209 Interface Set). This table is indexed by 210 loadngLibDestaddressetIndex. 212 o loadngBlacklistedNeighborSetTable - records the neighbor interface 213 addresses of a LOADng Router, with which connectivity has been 214 detected to be unidirectional. This table is indexed by 215 loadngBlacklistedNeighborSetIndex. 217 o loadngRoutingSetTable - records the next hop on the route to each 218 known destination. This table is indexed by 219 loadngRoutingSetIndex. 221 o loadngPendingAckSetTable - records information about RREPs which 222 have been transmitted with the ackrequired flag set, and for which 223 an RREP_ACK has not yet been received. This table is indexed by 224 loadngPendingAckSetIndex . 226 6. Relationship to Other MIB Modules 228 This section specifies the relationship of the MIB module contained 229 in this document to other standards, particularly to standards 230 containing other MIB modules. MIB modules and specific definitions 231 imported from MIB modules that SHOULD be implemented in conjunction 232 with the MIB module contained within this document are identified in 233 this section. 235 6.1. Relationship to the SNMPv2-MIB 237 The System group in the SNMPv2-MIB module [RFC3418] is defined as 238 being mandatory for all systems, and the objects apply to the entity 239 as a whole. The System group provides identification of the 240 management entity and certain other system-wide data. The LOADng-MIB 241 module does not duplicate those objects. 243 6.2. MIB Modules Required for IMPORTS 245 The following LOADng-MIB module IMPORTS objects from SNMPv2-SMI 246 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB 247 [RFC2863], and INET-ADDRESS-MIB [RFC4001]. 249 7. Definitions 251 This section contains the MIB module defined by the specification. 253 LOADNG-MIB DEFINITIONS ::= BEGIN 255 -- This MIB module defines objects for the management of 256 -- RFC XXXX: Lightweight On-demand Ad hoc Distance-vector 257 -- Routing Protocol - Next Generation (LOADng), 258 -- T. Clausen, A. Colin de Verdiere, 259 -- J. Yi, A. Niktash, Y. Igarashi, H. Satoh, U. Herberg, 260 -- C. Lavenu, T. Lys, and J. Dean, July 2013. 262 IMPORTS 264 MODULE-IDENTITY, OBJECT-TYPE, 265 Integer32, Unsigned32, mib-2 266 FROM SNMPv2-SMI -- RFC2578 268 TruthValue, TimeStamp, 269 RowStatus 270 FROM SNMPv2-TC -- RFC2579 272 MODULE-COMPLIANCE, OBJECT-GROUP 273 FROM SNMPv2-CONF -- STD58 275 InetAddressType, InetAddress 276 FROM INET-ADDRESS-MIB -- RFC4001 278 InterfaceIndex 279 FROM IF-MIB -- RFC2863 281 ; 283 loadngMIB MODULE-IDENTITY 284 LAST-UPDATED "201307110000Z" -- 11 July 2013 285 ORGANIZATION "IETF ??? Working Group" 286 CONTACT-INFO 287 "WG E-Mail: ??@ietf.org 289 WG Chairs: ?? 290 ?? 292 Editors: Ulrich Herberg 293 Fujitsu Laboratories of America 294 Sunnyvale, CA, 94085 295 US 296 ulrich@herberg.name 297 http://www.herberg.name/ 299 Robert G. Cole 300 US Army CERDEC 301 Space and Terrestrial Communications 302 6010 Frankford Street 303 Bldg 6010, Room 453H 304 Aberdeen Proving Ground, MD 21005 305 USA 306 +1 443 395-8744 307 robert.g.cole@us.army.mil 308 http://www.cs.jhu.edu/~rgcole/ 310 Thomas Heide Clausen 311 Ecole Polytechnique 312 LIX 313 91128 Palaiseau Cedex 314 France 315 http://www.thomasclausen.org/ 316 T.Clausen@computer.org" 318 DESCRIPTION 319 "This loadng-MIB module is applicable to routers 320 implementing the Lightweight On-demand Ad hoc 321 Distance-vector Routing Protocol - 322 Next Generation (LOADng). 324 Copyright (c) 2012 IETF Trust and the persons 325 identified as authors of the code. All rights reserved. 327 Redistribution and use in source and binary forms, with 328 or without modification, is permitted pursuant to, and 329 subject to the license terms contained in, the Simplified 330 BSD License set forth in Section 4.c of the IETF Trust's 331 Legal Provisions Relating to IETF Documents 332 (http://trustee.ietf.org/license-info). 334 This version of this MIB module is part of RFC XXXX; see 335 the RFC itself for full legal notices." 337 -- revision 338 REVISION "201307110000Z" -- 11 July 2013 339 DESCRIPTION 340 "Initial version of this MIB module, 341 published as RFC XXXX." 342 -- RFC-Editor assigns XXXX 343 ::= { mib-2 XXXX } -- to be assigned by IANA 345 -- 346 -- Top-Level Components of this MIB Module 347 -- 348 loadngObjects OBJECT IDENTIFIER ::= { loadngMIB 1 } 349 loadngConformance OBJECT IDENTIFIER ::= { loadngMIB 2 } 351 -- 352 -- loadngObjects 353 -- 355 -- 1) Configuration Objects Group 356 -- 2) State Objects Group 358 -- 359 -- loadngConfigurationObjGrp 360 -- 362 -- Contains the LOADng objects which configure specific options 363 -- which determine the overall performance and operation of the 364 -- LOADng protocol. 366 loadngConfigurationObjGrp OBJECT IDENTIFIER ::= { loadngObjects 1 } 367 loadngInterfaceTable OBJECT-TYPE 368 SYNTAX SEQUENCE OF LoadngInterfaceEntry 369 MAX-ACCESS not-accessible 370 STATUS current 371 DESCRIPTION 372 "loadngInterfaceTable describes the 373 configuration of the interfaces of this router 374 that are intended to use MANET control protocols. 375 As such, this table 'sparse augments' the ifTable 376 specifically when LOADng is to be configured to 377 operate over this interface. The interface is 378 identified by the ifIndex from the interfaces 379 group defined in the Interfaces Group MIB module. 381 A conceptual row in this table exists if and only 382 if either a manager has explicitly created the row 383 or there is an interface on the managed device 384 that supports and runs LOADng. 386 The manager can create a row by setting 387 rowStatus to 'createAndGo' or 'createAndWait'. 388 Row objects having associated DEFVAL clauses are 389 automatically defined by the agent with these 390 values during row creation, unless the manager 391 explicitly defines these object values during the 392 row creation. 394 If the corresponding entry with ifIndex value 395 is deleted from the Interface Table, then the entry 396 in this table is automatically deleted, 397 LOADng is disabled on this interface, 398 and all configuration and state information 399 related to this interface is to be removed 400 from memory." 401 REFERENCE 402 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 403 K., and F. Kastenholtz, June 2000" 404 ::= { loadngConfigurationObjGrp 1 } 406 loadngInterfaceEntry OBJECT-TYPE 407 SYNTAX LoadngInterfaceEntry 408 MAX-ACCESS not-accessible 409 STATUS current 410 DESCRIPTION 411 "loadngInterfaceEntry describes one LOADng 412 local interface configuration as indexed by 413 its ifIndex as defined in the Standard MIB II 414 Interface Table (RFC 2863). 416 The objects in this table are persistent, and when 417 written, the device SHOULD save the change to 418 non-volatile storage. For further information 419 on the storage behavior for these objects, refer 420 to the description for the loadngIfRowStatus 421 object." 422 INDEX { loadngIfIndex } 423 ::= { loadngInterfaceTable 1 } 425 LoadngInterfaceEntry ::= 426 SEQUENCE { 427 loadngIfIndex 428 InterfaceIndex, 429 loadngRreqMaxJitter 430 Unsigned32, 431 loadngRREPAckRequired 432 TruthValue, 433 loadngUseBidirectionalLinkOnly 434 TruthValue, 435 loadngRREPAckTimeout 436 Unsigned32, 437 loadngIfRowStatus 438 RowStatus 439 } 441 loadngIfIndex OBJECT-TYPE 442 SYNTAX InterfaceIndex 443 MAX-ACCESS not-accessible 444 STATUS current 445 DESCRIPTION 446 "This value MUST correspond to an ifIndex referring 447 to a valid entry in the Interfaces Table." 448 REFERENCE 449 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 450 and F. Kastenholtz, June 2000" 451 ::= { loadngInterfaceEntry 1 } 453 loadngRreqMaxJitter OBJECT-TYPE 454 SYNTAX Unsigned32 455 UNITS "milliseconds" 456 MAX-ACCESS read-create 457 STATUS current 458 DESCRIPTION 459 "loadngRreqMaxJitter corresponds to 460 RREQ_MAX_JITTER of LOADng. It represents 461 default value of MAXJITTER used in RFC 5148 for 462 RREQ messages forwarded by this LOADng Router. 464 This object is persistent and when written 465 the entity SHOULD save the change to 466 non-volatile storage." 467 REFERENCE 468 "Section 5 of RFC 5148 - Jitter Considerations in 469 Mobile Ad Hoc Networks (MANETs), 470 Clausen, T., Dearlove, C., and B. Adamson, February 2008" 471 DEFVAL { 500 } 472 ::= { loadngInterfaceEntry 2 } 474 loadngRREPAckRequired OBJECT-TYPE 475 SYNTAX TruthValue 476 MAX-ACCESS read-create 477 STATUS current 478 DESCRIPTION 479 "loadngRREPAckRequired corresponds to 480 RREP_ACK_REQUIRED of LOADng. It represents 481 a boolean flag, which indicates (if 482 set) that the router is configured to 483 expect that each RREP it sends be confirmed 484 by an RREP_ACK or (if cleared) that no 485 RREP_ACK is expected. 487 This object is persistent and when written 488 the entity SHOULD save the change to 489 non-volatile storage." 490 REFERENCE 491 "Section 5 on Protocol Parameters of 492 RFC XXXX - The Lightweight On-demand Ad hoc 493 Distance-vector Routing Protocol - Next Generation (LOADng), 494 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 495 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 496 Lys, T., and J. Dean, July 2013" 497 DEFVAL { false } 498 ::= { loadngInterfaceEntry 3 } 500 loadngUseBidirectionalLinkOnly OBJECT-TYPE 501 SYNTAX TruthValue 502 MAX-ACCESS read-create 503 STATUS current 504 DESCRIPTION 505 "loadngUseBidirectionalLinkOnly corresponds to 506 USE_BIDIRECTIONAL_LINK_ONLY of LOADng. It represents 507 a boolean flag, which indicates if the 508 LOADng Router only uses verified bi-directional 509 links for data packet forwarding on this interface. 511 It is set by default. If cleared, then the LOADng 512 Router can use links which have not been verified to 513 be bi-directional on this interface. 515 This object is persistent and when written 516 the entity SHOULD save the change to 517 non-volatile storage." 518 REFERENCE 519 "Section 5 on Protocol Parameters of 520 RFC XXXX - The Lightweight On-demand Ad hoc 521 Distance-vector Routing Protocol - Next Generation (LOADng), 522 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 523 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 524 Lys, T., and J. Dean, July 2013" 525 DEFVAL { true } 526 ::= { loadngInterfaceEntry 4 } 528 loadngRREPAckTimeout OBJECT-TYPE 529 SYNTAX Unsigned32 530 UNITS "milliseconds" 531 MAX-ACCESS read-create 532 STATUS current 533 DESCRIPTION 534 "loadngRREPAckTimeout corresponds to 535 RREP_ACK_TIMEOUT of LOADng. It represents 536 the minimum time after transmission of 537 an RREP, that a LOADng Router should 538 wait for an RREP_ACK from a neighbor 539 LOADng Router, before considering that 540 the link to this neighbor is unidirectional. 542 This object is persistent and when written 543 the entity SHOULD save the change to 544 non-volatile storage." 545 REFERENCE 546 "Section 5 on Protocol Parameters of 547 RFC XXXX - The Lightweight On-demand Ad hoc 548 Distance-vector Routing Protocol - Next Generation (LOADng), 549 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 550 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 551 Lys, T., and J. Dean, July 2013" 552 DEFVAL { 500 } 553 ::= { loadngInterfaceEntry 5 } 555 loadngIfRowStatus OBJECT-TYPE 556 SYNTAX RowStatus 557 MAX-ACCESS read-create 558 STATUS current 559 DESCRIPTION 560 "This object permits management of the table 561 by facilitating actions such as row creation, 562 construction, and destruction. The value of 563 this object has no effect on whether other 564 objects in this conceptual row can be 565 modified. 567 An entry may not exist in the 'active(1)' state unless all 568 objects in the entry have a defined appropriate value. For 569 objects with DEFVAL clauses, the management station 570 does not need to specify the value of this object in order 571 for the row to transit to the 'active(1)' state; the default 572 value for this object is used. For objects that do not 573 have DEFVAL clauses, then the network manager MUST 574 specify the value of this object prior to this row 575 transitioning to the 'active(1)' state. 577 When this object transitions to 'active(1)', all objects 578 in this row SHOULD be written to non-volatile (stable) 579 storage. Read-create objects in this row MAY be modified. 580 When an object in a row with loadngIfRowStatus of 'active(1)' 581 is changed, then the updated value MUST be 582 reflected in LOADng,and this new object value MUST be 583 written to non-volatile storage. 585 If the value of this object is not equal to 'active(1)', 586 all associated entries in the loadngLibLocalIfSetTable 587 MUST be deleted." 588 REFERENCE 589 "RFC XXXX - The Lightweight On-demand Ad hoc 590 Distance-vector Routing Protocol - Next Generation (LOADng), 591 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 592 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 593 Lys, T., and J. Dean, July 2013" 594 DEFVAL { active } 595 ::= { loadngInterfaceEntry 6 } 597 -- 598 -- Router Parameters 599 -- 601 loadngNetTraversalTime OBJECT-TYPE 602 SYNTAX Unsigned32 603 UNITS "milliseconds" 604 MAX-ACCESS read-write 605 STATUS current 606 DESCRIPTION 607 "loadngNetTraversalTime corresponds to 608 NET_TRAVERSAL_TIME of LOADng. It represents 609 the maximum time that a packet is expected 610 to take when traversing from one end of 611 the network to the other. 613 This object is persistent and when written 614 the entity SHOULD save the change to 615 non-volatile storage." 616 REFERENCE 617 "Section 5 on Protocol Parameters of 618 RFC XXXX - The Lightweight On-demand Ad hoc 619 Distance-vector Routing Protocol - Next Generation (LOADng), 620 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 621 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 622 Lys, T., and J. Dean, July 2013" 623 DEFVAL { 500 } 624 ::= { loadngConfigurationObjGrp 2 } 626 loadngRREQRetries OBJECT-TYPE 627 SYNTAX Unsigned32 (0..255) 628 MAX-ACCESS read-write 629 STATUS current 630 DESCRIPTION 631 "loadngRREQRetries corresponds to 632 RREQ_RETRIES of LOADng. It represents 633 the maximum number of subsequent RREQs 634 that a particular router may generate 635 in order to discover a route to a 636 destination, before declaring that 637 destination unreachable. 639 This object is persistent and when written 640 the entity SHOULD save the change to 641 non-volatile storage." 642 REFERENCE 643 "Section 5 on Protocol Parameters of 644 RFC XXXX - The Lightweight On-demand Ad hoc 645 Distance-vector Routing Protocol - Next Generation (LOADng), 646 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 647 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 648 Lys, T., and J. Dean, July 2013" 649 DEFVAL { 3 } 650 ::= { loadngConfigurationObjGrp 3 } 651 loadngRREQMinInterval OBJECT-TYPE 652 SYNTAX Unsigned32 653 UNITS "milliseconds" 654 MAX-ACCESS read-write 655 STATUS current 656 DESCRIPTION 657 "loadngRREQMinInterval corresponds to 658 RREQ_MIN_INTERVAL of LOADng. It represents 659 the minimal interval of RREQs 660 that a particular LOADng Router is 661 allowed to send. 663 This object is persistent and when written 664 the entity SHOULD save the change to 665 non-volatile storage." 666 REFERENCE 667 "Section 5 on Protocol Parameters of 668 RFC XXXX - The Lightweight On-demand Ad hoc 669 Distance-vector Routing Protocol - Next Generation (LOADng), 670 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 671 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 672 Lys, T., and J. Dean, July 2013" 673 DEFVAL { 3 } 674 ::= { loadngConfigurationObjGrp 4 } 676 loadngRHoldTime OBJECT-TYPE 677 SYNTAX Unsigned32 678 UNITS "milliseconds" 679 MAX-ACCESS read-write 680 STATUS current 681 DESCRIPTION 682 "loadngRHoldTime corresponds to 683 R_HOLD_TIME of LOADng. It represents 684 the minimum time a Routing Tuple should 685 be kept in the Routing Set after it was 686 last refreshed. This may be a network-wide 687 constant, but may also be a variable whose 688 value is defined by an auxiliary mechanism, 689 e.g., by an extension to this protocol. 691 This object is persistent and when written 692 the entity SHOULD save the change to 693 non-volatile storage." 694 REFERENCE 695 "Section 5 on Protocol Parameters of 696 RFC XXXX - The Lightweight On-demand Ad hoc 697 Distance-vector Routing Protocol - Next Generation (LOADng), 698 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 699 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 700 Lys, T., and J. Dean, July 2013" 701 DEFVAL { 10000 } 702 ::= { loadngConfigurationObjGrp 5 } 704 loadngMaxDist OBJECT-TYPE 705 SYNTAX Unsigned32 706 MAX-ACCESS read-write 707 STATUS current 708 DESCRIPTION 709 "loadngMaxDist corresponds to 710 MAX_DIST of LOADng. It represents 711 the value representing the 712 maximum possible metric. 714 This object is persistent and when written 715 the entity SHOULD save the change to 716 non-volatile storage." 717 REFERENCE 718 "Section 5 on Protocol Parameters of 719 RFC XXXX - The Lightweight On-demand Ad hoc 720 Distance-vector Routing Protocol - Next Generation (LOADng), 721 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 722 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 723 Lys, T., and J. Dean, July 2013" 724 DEFVAL { 255 } 725 ::= { loadngConfigurationObjGrp 6 } 727 loadngBHoldTime OBJECT-TYPE 728 SYNTAX Unsigned32 729 UNITS "milliseconds" 730 MAX-ACCESS read-write 731 STATUS current 732 DESCRIPTION 733 "loadngBHoldTime corresponds to the 734 B_HOLD_TIME of LOADng. It represents 735 is the time during which the link between the neighbor 736 LOADng Router and this LOADng Router are considered 737 as non-bidirectional. 739 This object is persistent and when written 740 the entity SHOULD save the change to 741 non-volatile storage." 742 REFERENCE 743 "Section 5 on Protocol Parameters of 744 RFC XXXX - The Lightweight On-demand Ad hoc 745 Distance-vector Routing Protocol - Next Generation (LOADng), 746 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 747 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 748 Lys, T., and J. Dean, July 2013" 749 DEFVAL { 15 } 750 ::= { loadngConfigurationObjGrp 7 } 752 loadngMaxHopLimit OBJECT-TYPE 753 SYNTAX Unsigned32 754 MAX-ACCESS read-write 755 STATUS current 756 DESCRIPTION 757 "loadngMaxHopLimit corresponds to 758 MAX_HOP_LIMIT of LOADng. It represents 759 the maximum limit of the number of hops that 760 LOADng routing messages are allowed to traverse. 762 This object is persistent and when written 763 the entity SHOULD save the change to 764 non-volatile storage." 765 REFERENCE 766 "Section 5 on Protocol Parameters of 767 RFC XXXX - The Lightweight On-demand Ad hoc 768 Distance-vector Routing Protocol - Next Generation (LOADng), 769 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 770 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 771 Lys, T., and J. Dean, July 2013" 772 DEFVAL { 255 } 773 ::= { loadngConfigurationObjGrp 8 } 775 -- 776 -- Local Interface Set Table 777 -- 779 loadngLibLocalIfSetTable OBJECT-TYPE 780 SYNTAX SEQUENCE OF LoadngLibLocalIfSetEntry 781 MAX-ACCESS not-accessible 782 STATUS current 783 DESCRIPTION 784 "A router's Local Interface Set records all 785 network addresses that are defined as local 786 interface network addresses. 787 As such, this table 'sparse augments' the 788 loadngInterfaceTable when network addresses are 789 being defined for the interfaces existing within 790 the loadngInterfaceTable. The local interface 791 is defined by the loadngIfIndex. 793 The Local Interface Set consists of Local Interface 794 Address Tuples per MANET interface and their prefix 795 lengths (in order to determine the network addresses 796 related to the interface). 798 A conceptual row in this table exists if and only 799 if a manager has explicitly created the row. The 800 manager can create a row by setting rowStatus 801 to 'createAndGo' or 'createAndWait'." 802 REFERENCE 803 "RFC XXXX - The Lightweight On-demand Ad hoc 804 Distance-vector Routing Protocol - Next Generation (LOADng), 805 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 806 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 807 Lys, T., and J. Dean, July 2013" 808 ::= { loadngConfigurationObjGrp 12 } 810 loadngLibLocalIfSetEntry OBJECT-TYPE 811 SYNTAX LoadngLibLocalIfSetEntry 812 MAX-ACCESS not-accessible 813 STATUS current 814 DESCRIPTION 815 "A router's Local Interface Set consists 816 of Local Interface Tuples for each network 817 interface. 819 (I_local_iface_addr_list) 821 Each tuple contains a list of one 822 or more addresses of this interface." 823 REFERENCE 824 "RFC XXXX - The Lightweight On-demand Ad hoc 825 Distance-vector Routing Protocol - Next Generation (LOADng), 826 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 827 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 828 Lys, T., and J. Dean, July 2013" 829 INDEX { loadngLibLocalIfSetIndex, loadngLibLocalIfSetIfIndex } 830 ::= { loadngLibLocalIfSetTable 1 } 832 LoadngLibLocalIfSetEntry ::= 833 SEQUENCE { 834 loadngLibLocalIfSetIndex 835 Integer32, 836 loadngLibLocalIfSetIfIndex 837 InterfaceIndex, 839 loadngLibLocalIfSetIpAddrType 840 InetAddressType, 841 loadngLibLocalIfSetIpAddr 842 InetAddress, 843 loadngLibLocalIfSetRowStatus 844 RowStatus 845 } 847 loadngLibLocalIfSetIndex OBJECT-TYPE 848 SYNTAX Integer32 (0..65535) 849 MAX-ACCESS not-accessible 850 STATUS current 851 DESCRIPTION 852 "The index for this table. Necessary 853 because multiple addresses may be associated 854 with a given loadngIfIndex." 855 REFERENCE 856 "RFC XXXX - The Lightweight On-demand Ad hoc 857 Distance-vector Routing Protocol - Next Generation (LOADng), 858 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 859 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 860 Lys, T., and J. Dean, July 2013" 861 ::= { loadngLibLocalIfSetEntry 1 } 863 loadngLibLocalIfSetIfIndex OBJECT-TYPE 864 SYNTAX InterfaceIndex 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "Specifies the local loadngIfIndex for which this 869 IP address was added." 870 REFERENCE 871 "RFC XXXX - The Lightweight On-demand Ad hoc 872 Distance-vector Routing Protocol - Next Generation (LOADng), 873 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 874 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 875 Lys, T., and J. Dean, July 2013" 876 ::= { loadngLibLocalIfSetEntry 2 } 878 loadngLibLocalIfSetIpAddrType OBJECT-TYPE 879 SYNTAX InetAddressType 880 MAX-ACCESS read-create 881 STATUS current 882 DESCRIPTION 883 "The type of the loadngLibLocalIfSetIpAddr 884 in the InetAddress MIB (RFC 4001). 886 Only the values 'ipv4(1)' and 887 'ipv6(2)' are supported." 888 REFERENCE 889 "RFC XXXX - The Lightweight On-demand Ad hoc 890 Distance-vector Routing Protocol - Next Generation (LOADng), 891 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 892 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 893 Lys, T., and J. Dean, July 2013" 894 ::= { loadngLibLocalIfSetEntry 3 } 896 loadngLibLocalIfSetIpAddr OBJECT-TYPE 897 SYNTAX InetAddress (SIZE(4|16)) 898 MAX-ACCESS read-create 899 STATUS current 900 DESCRIPTION 901 "loadngLibLocalIfSetIpAddr is an 902 address of an interface of 903 this router. 905 This object is interpreted according to 906 the setting of loadngLibLocalIfSetIpAddrType." 907 REFERENCE 908 "RFC XXXX - The Lightweight On-demand Ad hoc 909 Distance-vector Routing Protocol - Next Generation (LOADng), 910 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 911 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 912 Lys, T., and J. Dean, July 2013" 913 ::= { loadngLibLocalIfSetEntry 4 } 915 loadngLibLocalIfSetRowStatus OBJECT-TYPE 916 SYNTAX RowStatus 917 MAX-ACCESS read-create 918 STATUS current 919 DESCRIPTION 920 "This object permits management of the table 921 by facilitating actions such as row creation, 922 construction, and destruction. The value of 923 this object has no effect on whether other 924 objects in this conceptual row can be 925 modified. 927 An entry may not exist in the 'active(1)' state unless all 928 read-create objects in the entry have a defined 929 appropriate value. As no objects in this table have 930 DEFVAL clauses, the management station MUST specify 931 the values of all read-create objects prior to this row 932 transitioning to the 'active(1)' state. 934 When this object transitions to 'active(1)', all objects 935 in this row SHOULD be written to non-volatile (stable) 936 storage. Read-create objects in this row MAY be modified. 937 When an object in a row with loadngIfRowStatus of 'active(1)' 938 is changed, then the updated value MUST be reflected in 939 LOADng, and this new object value MUST be written to 940 non-volatile storage." 941 REFERENCE 942 "RFC XXXX - The Lightweight On-demand Ad hoc 943 Distance-vector Routing Protocol - Next Generation (LOADng), 944 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 945 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 946 Lys, T., and J. Dean, July 2013" 947 ::= { loadngLibLocalIfSetEntry 5 } 949 -- 950 -- Destination Address Set Table 951 -- Entry (foreach local interface): (D_address) 952 -- 954 loadngLibDestaddressetTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF LoadngLibDestaddressetEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "The Destination Address Set records 960 addresses, for which a LOADng Router 961 will generate RREPs in response to received 962 RREQs, in addition to its own interface addresses 963 (as listed in the Local Interface Set). The 964 Destination Address Set thus represents those 965 destinations (i.e., hosts), for which this LOADng 966 Router is providing connectivity. It consists of 967 Destination Address Tuples." 968 REFERENCE 969 "RFC XXXX - The Lightweight On-demand Ad hoc 970 Distance-vector Routing Protocol - Next Generation (LOADng), 971 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 972 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 973 Lys, T., and J. Dean, July 2013" 974 ::= { loadngConfigurationObjGrp 13 } 976 loadngLibDestaddressetEntry OBJECT-TYPE 977 SYNTAX LoadngLibDestaddressetEntry 978 MAX-ACCESS not-accessible 979 STATUS current 980 DESCRIPTION 981 "The Destination Address Set consists 982 of Destination Address Tuples: 984 (D_address)" 985 REFERENCE 986 "RFC XXXX - The Lightweight On-demand Ad hoc 987 Distance-vector Routing Protocol - Next Generation (LOADng), 988 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 989 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 990 Lys, T., and J. Dean, July 2013" 991 INDEX { loadngLibDestaddressetIndex } 992 ::= { loadngLibDestaddressetTable 1 } 994 LoadngLibDestaddressetEntry ::= 995 SEQUENCE { 996 loadngLibDestaddressetIndex 997 Integer32, 998 loadngLibDestaddressetIpAddrType 999 InetAddressType, 1000 loadngLibDestaddressetIpAddr 1001 InetAddress 1002 } 1004 loadngLibDestaddressetIndex OBJECT-TYPE 1005 SYNTAX Integer32 (0..65535) 1006 MAX-ACCESS not-accessible 1007 STATUS current 1008 DESCRIPTION 1009 "The index for this table. Necessary 1010 because multiple addresses may be associated 1011 with a given loadngIfIndex." 1012 REFERENCE 1013 "RFC XXXX - The Lightweight On-demand Ad hoc 1014 Distance-vector Routing Protocol - Next Generation (LOADng), 1015 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1016 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1017 Lys, T., and J. Dean, July 2013" 1018 ::= { loadngLibDestaddressetEntry 1 } 1020 loadngLibDestaddressetIpAddrType OBJECT-TYPE 1021 SYNTAX InetAddressType 1022 MAX-ACCESS read-write 1023 STATUS current 1024 DESCRIPTION 1025 "The type of the loadngLibDestaddressetIpAddr 1026 in the InetAddress MIB (RFC4001). 1028 Only the values 'ipv4(1)' and 1029 'ipv6(2)' are supported." 1030 REFERENCE 1031 "RFC XXXX - The Lightweight On-demand Ad hoc 1032 Distance-vector Routing Protocol - Next Generation (LOADng), 1033 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1034 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1035 Lys, T., and J. Dean, July 2013" 1036 ::= { loadngLibDestaddressetEntry 2 } 1038 loadngLibDestaddressetIpAddr OBJECT-TYPE 1039 SYNTAX InetAddress (SIZE(4|16)) 1040 MAX-ACCESS read-write 1041 STATUS current 1042 DESCRIPTION 1043 "loadngLibDestaddressetIpAddr is an 1044 address of an interface of 1045 a router. 1047 This object is interpreted according to 1048 the setting of loadngLibDestaddressetIpAddrType." 1049 REFERENCE 1050 "RFC XXXX - The Lightweight On-demand Ad hoc 1051 Distance-vector Routing Protocol - Next Generation (LOADng), 1052 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1053 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1054 Lys, T., and J. Dean, July 2013" 1055 ::= { loadngLibDestaddressetEntry 3 } 1057 -- 1058 -- loadngStateObjGrp 1059 -- 1061 -- Contains information describing the current state of the LOADng 1062 -- process on this router. 1064 loadngStateObjGrp OBJECT IDENTIFIER ::= { loadngObjects 2 } 1066 loadngUpTime OBJECT-TYPE 1067 SYNTAX TimeStamp 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "The value of sysUpTime at the time current LOADng 1072 process was initialized." 1074 ::= { loadngStateObjGrp 1 } 1076 -- 1077 -- Blacklisted Neighbor Set Table 1078 -- 1080 loadngBlacklistedNeighborSetTable OBJECT-TYPE 1081 SYNTAX SEQUENCE OF LoadngBlacklistedNeighborSetEntry 1082 MAX-ACCESS not-accessible 1083 STATUS current 1084 DESCRIPTION 1085 "The Blacklisted Neighbor Set records the neighbor 1086 interface addresses of a LOADng Router, with which 1087 connectivity has been detected to be unidirectional. 1088 Specifically, the Blacklisted Neighbor Set records 1089 neighbors from which an RREQ has been received (i.e., 1090 through which a Forward Route would possible) but 1091 to which it has been determined that it is not 1092 possible to communicate (i.e., forwarding Route 1093 Replies via this neighbor fails, rendering installing 1094 the Forward Route impossible). It consists of 1095 Blacklisted Neighbor Tuples." 1096 REFERENCE 1097 "RFC XXXX - The Lightweight On-demand Ad hoc 1098 Distance-vector Routing Protocol - Next Generation (LOADng), 1099 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1100 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1101 Lys, T., and J. Dean, July 2013" 1102 ::= { loadngStateObjGrp 2 } 1104 loadngBlacklistedNeighborSetEntry OBJECT-TYPE 1105 SYNTAX LoadngBlacklistedNeighborSetEntry 1106 MAX-ACCESS not-accessible 1107 STATUS current 1108 DESCRIPTION 1109 "A router's Blacklisted Neighbor Set consists 1110 of Blacklisted Neighbor Tuples, one per network 1111 address:loadngBlacklistedNeighborSet 1113 (B_neighbor_address, B_valid_time) 1115 The association between these addrs and 1116 the router's Interface is found in the 1117 Standard MIB II's IP address table 1118 (RFC1213)." 1119 REFERENCE 1120 "RFC XXXX - The Lightweight On-demand Ad hoc 1121 Distance-vector Routing Protocol - Next Generation (LOADng), 1122 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1123 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1124 Lys, T., and J. Dean, July 2013" 1125 INDEX { loadngBlacklistedNeighborSetIndex } 1126 ::= { loadngBlacklistedNeighborSetTable 1 } 1128 LoadngBlacklistedNeighborSetEntry ::= 1129 SEQUENCE { 1130 loadngBlacklistedNeighborSetIndex 1131 Integer32, 1132 loadngBlacklistedNeighborSetIpAddrType 1133 InetAddressType, 1134 loadngBlacklistedNeighborSetIpAddr 1135 InetAddress, 1136 loadngBlacklistedNeighborSetBTime 1137 TimeStamp 1138 } 1140 loadngBlacklistedNeighborSetIndex OBJECT-TYPE 1141 SYNTAX Integer32 (0..65535) 1142 MAX-ACCESS not-accessible 1143 STATUS current 1144 DESCRIPTION 1145 "The index for this table." 1146 REFERENCE 1147 "RFC XXXX - The Lightweight On-demand Ad hoc 1148 Distance-vector Routing Protocol - Next Generation (LOADng), 1149 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1150 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1151 Lys, T., and J. Dean, July 2013" 1152 ::= { loadngBlacklistedNeighborSetEntry 1 } 1154 loadngBlacklistedNeighborSetIpAddrType OBJECT-TYPE 1155 SYNTAX InetAddressType 1156 MAX-ACCESS read-only 1157 STATUS current 1158 DESCRIPTION 1159 "The type of the loadngBlacklistedNeighborSetIpAddr 1160 in the InetAddress MIB (RFC 4001). 1162 Only the values 'ipv4(1)' and 1163 'ipv6(2)' are supported." 1164 REFERENCE 1165 "LOADng." 1166 ::= { loadngBlacklistedNeighborSetEntry 2 } 1168 loadngBlacklistedNeighborSetIpAddr OBJECT-TYPE 1169 SYNTAX InetAddress (SIZE(4|16)) 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "loadngBlacklistedNeighborSetIpAddr is the 1174 address of the blacklisted neighbor interface." 1175 REFERENCE 1176 "RFC XXXX - The Lightweight On-demand Ad hoc 1177 Distance-vector Routing Protocol - Next Generation (LOADng), 1178 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1179 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1180 Lys, T., and J. Dean, July 2013" 1181 ::= { loadngBlacklistedNeighborSetEntry 3 } 1183 loadngBlacklistedNeighborSetBTime OBJECT-TYPE 1184 SYNTAX TimeStamp 1185 MAX-ACCESS read-only 1186 STATUS current 1187 DESCRIPTION 1188 "loadngBlacklistedNeighborSetBTime specifies the value 1189 of sysUptime when this entry should expire and be 1190 removed from the loadngBlacklistedNeighborSetTable." 1191 REFERENCE 1192 "RFC XXXX - The Lightweight On-demand Ad hoc 1193 Distance-vector Routing Protocol - Next Generation (LOADng), 1194 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1195 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1196 Lys, T., and J. Dean, July 2013" 1197 ::= { loadngBlacklistedNeighborSetEntry 4 } 1199 -- 1200 -- Routing Set 1201 -- 1203 loadngRoutingSetTable OBJECT-TYPE 1204 SYNTAX SEQUENCE OF LoadngRoutingSetEntry 1205 MAX-ACCESS not-accessible 1206 STATUS current 1207 DESCRIPTION 1208 "The Routing Set records the next hop 1209 on the route to each known destination, 1210 when such a route is known. It consists of 1211 Routing Tuples." 1212 REFERENCE 1213 "RFC XXXX - The Lightweight On-demand Ad hoc 1214 Distance-vector Routing Protocol - Next Generation (LOADng), 1215 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1216 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1217 Lys, T., and J. Dean, July 2013" 1218 ::= { loadngStateObjGrp 3 } 1220 loadngRoutingSetEntry OBJECT-TYPE 1221 SYNTAX LoadngRoutingSetEntry 1222 MAX-ACCESS not-accessible 1223 STATUS current 1224 DESCRIPTION 1225 "A router's Routing Set consists 1226 of Routing Tuples: 1228 (R_dest_addr, R_next_addr, R_metric, 1229 R_metric_type, R_hop_count, 1230 R_seq_num, R_bidirectional, 1231 R_local_iface_addr, R_valid_time)" 1232 REFERENCE 1233 "RFC XXXX - The Lightweight On-demand Ad hoc 1234 Distance-vector Routing Protocol - Next Generation (LOADng), 1235 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1236 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1237 Lys, T., and J. Dean, July 2013" 1238 INDEX { loadngRoutingSetIndex } 1239 ::= { loadngRoutingSetTable 1 } 1241 LoadngRoutingSetEntry ::= 1242 SEQUENCE { 1243 loadngRoutingSetIndex 1244 Integer32, 1245 loadngRoutingSetDestIpAddrType 1246 InetAddressType, 1247 loadngRoutingSetDestIpAddr 1248 InetAddress, 1249 loadngRoutingSetNextIpAddrType 1250 InetAddressType, 1251 loadngRoutingSetNextIpAddr 1252 InetAddress, 1253 loadngRoutingSetMetric 1254 Unsigned32, 1255 loadngRoutingSetMetricType 1256 Integer32, 1257 loadngRoutingSetHopCount 1258 Integer32, 1259 loadngRoutingSetSeqnum 1260 Integer32, 1261 loadngRoutingSetBidirectional 1262 TruthValue, 1263 loadngRoutingSetLocalIfaceIpAddrType 1264 InetAddressType, 1265 loadngRoutingSetLocalIfaceIpAddr 1266 InetAddress, 1267 loadngRoutingSetValidTime 1268 TimeStamp 1269 } 1271 loadngRoutingSetIndex OBJECT-TYPE 1272 SYNTAX Integer32 (0..65535) 1273 MAX-ACCESS not-accessible 1274 STATUS current 1275 DESCRIPTION 1276 "The index for this table." 1277 REFERENCE 1278 "RFC XXXX - The Lightweight On-demand Ad hoc 1279 Distance-vector Routing Protocol - Next Generation (LOADng), 1280 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1281 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1282 Lys, T., and J. Dean, July 2013" 1283 ::= { loadngRoutingSetEntry 1 } 1285 loadngRoutingSetDestIpAddrType OBJECT-TYPE 1286 SYNTAX InetAddressType 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "The type of the loadngRoutingSetDestIpAddr 1291 in the InetAddress MIB (RFC 4001). 1293 Only the values 'ipv4(1)' and 1294 'ipv6(2)' are supported." 1295 REFERENCE 1296 "RFC XXXX - The Lightweight On-demand Ad hoc 1297 Distance-vector Routing Protocol - Next Generation (LOADng), 1298 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1299 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1300 Lys, T., and J. Dean, July 2013" 1301 ::= { loadngRoutingSetEntry 2 } 1303 loadngRoutingSetDestIpAddr OBJECT-TYPE 1304 SYNTAX InetAddress (SIZE(4|16)) 1305 MAX-ACCESS read-only 1306 STATUS current 1307 DESCRIPTION 1308 "loadngRoutingSetDestIpAddrType is the address 1309 of the destination, either the address of an 1310 interface of a destination LOADng Router, or 1311 the address of an interface reachable via the 1312 destination LOADng Router, but which is outside 1313 the routing domain." 1314 REFERENCE 1315 "RFC XXXX - The Lightweight On-demand Ad hoc 1316 Distance-vector Routing Protocol - Next Generation (LOADng), 1317 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1318 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1319 Lys, T., and J. Dean, July 2013" 1320 ::= { loadngRoutingSetEntry 3 } 1322 loadngRoutingSetNextIpAddrType OBJECT-TYPE 1323 SYNTAX InetAddressType 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "The type of the loadngRoutingSetNextIpAddr 1328 in the InetAddress MIB (RFC 4001). 1330 Only the values 'ipv4(1)' and 1331 'ipv6(2)' are supported." 1332 REFERENCE 1333 "RFC XXXX - The Lightweight On-demand Ad hoc 1334 Distance-vector Routing Protocol - Next Generation (LOADng), 1335 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1336 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1337 Lys, T., and J. Dean, July 2013" 1338 ::= { loadngRoutingSetEntry 4 } 1340 loadngRoutingSetNextIpAddr OBJECT-TYPE 1341 SYNTAX InetAddress (SIZE(4|16)) 1342 MAX-ACCESS read-only 1343 STATUS current 1344 DESCRIPTION 1345 "loadngRoutingSetNextIpAddr is the 1346 address of the next hop on the selected 1347 route to the destination." 1348 REFERENCE 1349 "RFC XXXX - The Lightweight On-demand Ad hoc 1350 Distance-vector Routing Protocol - Next Generation (LOADng), 1351 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1352 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1353 Lys, T., and J. Dean, July 2013" 1354 ::= { loadngRoutingSetEntry 5 } 1356 loadngRoutingSetMetric OBJECT-TYPE 1357 SYNTAX Unsigned32 1358 MAX-ACCESS read-only 1359 STATUS current 1360 DESCRIPTION 1361 "loadngRoutingSetMetric is the metric associated with 1362 the selected route to the destination with address 1363 R_dest_addr." 1364 REFERENCE 1365 "RFC XXXX - The Lightweight On-demand Ad hoc 1366 Distance-vector Routing Protocol - Next Generation (LOADng), 1367 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1368 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1369 Lys, T., and J. Dean, July 2013" 1370 ::= { loadngRoutingSetEntry 6 } 1372 loadngRoutingSetMetricType OBJECT-TYPE 1373 SYNTAX Integer32 1374 MAX-ACCESS read-only 1375 STATUS current 1376 DESCRIPTION 1377 "loadngRoutingSetMetricType specifies the metric 1378 type for this Routing Tuple - in other words, how 1379 R_metric is defined and calculated." 1380 REFERENCE 1381 "RFC XXXX - The Lightweight On-demand Ad hoc 1382 Distance-vector Routing Protocol - Next Generation (LOADng), 1383 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1384 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1385 Lys, T., and J. Dean, July 2013" 1386 ::= { loadngRoutingSetEntry 8 } 1388 loadngRoutingSetHopCount OBJECT-TYPE 1389 SYNTAX Integer32 (0..255) 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "loadngRoutingSetHopCount is the hop count of the 1394 selected route to the destination with address 1395 R_dest_addr." 1396 REFERENCE 1397 "RFC XXXX - The Lightweight On-demand Ad hoc 1398 Distance-vector Routing Protocol - Next Generation (LOADng), 1399 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1400 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1401 Lys, T., and J. Dean, July 2013" 1402 ::= { loadngRoutingSetEntry 9 } 1404 loadngRoutingSetSeqnum OBJECT-TYPE 1405 SYNTAX Integer32 (-1..65535) 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "loadngRoutingSetSeqnum is the value of the 1410 field of the RREQ or RREP which installed 1411 or last updated this tuple. For the routing 1412 tuples installed by previous hop information of 1413 RREQ or RREP, loadngRoutingSetSeqnum must be 1414 set to -1. 1416 Sequence numbers are used in LOADng 1417 for the purpose of discarding 'old' information, 1418 i.e., messages received out of order. However 1419 with a limited number of bits for representing 1420 sequence numbers, wrap-around (that the sequence 1421 number is incremented from the maximum possible 1422 value to zero) will occur. To prevent this from 1423 interfering with the operation of this protocol, 1424 LOADng implementations observe the following when 1425 determining the ordering of sequence numbers. 1427 In LOADng, MAXVALUE designates one more than the 1428 largest possible value for a sequence number. 1429 For a 16 bit sequence number MAXVALUE is 65536. 1431 The sequence number S1 is said to be 'greater than' 1432 the sequence number S2 if: 1434 o S1 > S2 AND S1 - S2 < MAXVALUE/2 OR 1436 o S2 > S1 AND S2 - S1 > MAXVALUE/2 1438 When sequence numbers S1 and S2 differ by MAXVALUE/2 1439 their ordering cannot be determined. In this case, 1440 which should not occur, either ordering may be 1441 assumed. 1443 Thus when comparing two messages, it is possible 1444 - even in the presence of wrap-around - to determine 1445 which message contains the most recent information." 1446 REFERENCE 1447 "RFC XXXX - The Lightweight On-demand Ad hoc 1448 Distance-vector Routing Protocol - Next Generation (LOADng), 1449 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1450 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1451 Lys, T., and J. Dean, July 2013" 1452 ::= { loadngRoutingSetEntry 10 } 1453 loadngRoutingSetBidirectional OBJECT-TYPE 1454 SYNTAX TruthValue 1455 MAX-ACCESS read-only 1456 STATUS current 1457 DESCRIPTION 1458 "loadngRoutingSetBidirectional is a boolean 1459 flag, which specifies if the routing tuple 1460 is verified as representing a bi-directional 1461 route. Data traffic should only be routed 1462 through a routing tuple with R_bidirectional 1463 flag equals 'true', unless the router is 1464 configured as accepting routes without 1465 bi-directionality verification explicitly by 1466 setting the USE_BIDIRECTIONAL_LINK_ONLY to 'false'." 1467 REFERENCE 1468 "RFC XXXX - The Lightweight On-demand Ad hoc 1469 Distance-vector Routing Protocol - Next Generation (LOADng), 1470 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1471 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1472 Lys, T., and J. Dean, July 2013" 1473 ::= { loadngRoutingSetEntry 11 } 1475 loadngRoutingSetLocalIfaceIpAddrType OBJECT-TYPE 1476 SYNTAX InetAddressType 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "The type of the loadngRoutingSetLocalIfaceIpAddr 1481 in the InetAddress MIB (RFC 4001). 1483 Only the values 'ipv4(1)' and 1484 'ipv6(2)' are supported." 1485 REFERENCE 1486 "RFC XXXX - The Lightweight On-demand Ad hoc 1487 Distance-vector Routing Protocol - Next Generation (LOADng), 1488 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1489 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1490 Lys, T., and J. Dean, July 2013" 1491 ::= { loadngRoutingSetEntry 12 } 1493 loadngRoutingSetLocalIfaceIpAddr OBJECT-TYPE 1494 SYNTAX InetAddress (SIZE(4|16)) 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 "loadngRoutingSetLocalIfaceIpAddr is the address 1499 of the local interface, through which the 1500 destination can be reached." 1501 REFERENCE 1502 "RFC XXXX - The Lightweight On-demand Ad hoc 1503 Distance-vector Routing Protocol - Next Generation (LOADng), 1504 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1505 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1506 Lys, T., and J. Dean, July 2013" 1507 ::= { loadngRoutingSetEntry 13 } 1509 loadngRoutingSetValidTime OBJECT-TYPE 1510 SYNTAX TimeStamp 1511 MAX-ACCESS read-only 1512 STATUS current 1513 DESCRIPTION 1514 "loadngRoutingSetValidTime specifies the value 1515 of sysUptime when this entry should expire and be 1516 removed from the loadngRoutingSetTable." 1517 REFERENCE 1518 "RFC XXXX - The Lightweight On-demand Ad hoc 1519 Distance-vector Routing Protocol - Next Generation (LOADng), 1520 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1521 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1522 Lys, T., and J. Dean, July 2013" 1523 ::= { loadngRoutingSetEntry 14 } 1525 -- 1526 -- Pending Acknowledgment Set 1527 -- 1529 loadngPendingAckSetTable OBJECT-TYPE 1530 SYNTAX SEQUENCE OF LoadngPendingAckSetEntry 1531 MAX-ACCESS not-accessible 1532 STATUS current 1533 DESCRIPTION 1534 "The Pending Acknowledgment Set contains 1535 information about RREPs which have been 1536 transmitted with the ackrequired flag set, 1537 and for which an RREP_ACK has not yet been 1538 received. It consists of Pending Acknowledgment 1539 Tuples." 1540 REFERENCE 1541 "RFC XXXX - The Lightweight On-demand Ad hoc 1542 Distance-vector Routing Protocol - Next Generation (LOADng), 1543 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1544 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1545 Lys, T., and J. Dean, July 2013" 1546 ::= { loadngStateObjGrp 4 } 1547 loadngPendingAckSetEntry OBJECT-TYPE 1548 SYNTAX LoadngPendingAckSetEntry 1549 MAX-ACCESS not-accessible 1550 STATUS current 1551 DESCRIPTION 1552 "A router's Pending Acknowledgment Set 1553 consists of Pending Acknowledgment Tuples: 1555 (P_next_hop, P_originator, P_seq_num, 1556 R_ack_received, P_ack_timeout)" 1557 REFERENCE 1558 "RFC XXXX - The Lightweight On-demand Ad hoc 1559 Distance-vector Routing Protocol - Next Generation (LOADng), 1560 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1561 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1562 Lys, T., and J. Dean, July 2013" 1563 INDEX { loadngPendingAckSetIndex } 1564 ::= { loadngPendingAckSetTable 1 } 1566 LoadngPendingAckSetEntry ::= 1567 SEQUENCE { 1568 loadngPendingAckSetIndex 1569 Integer32, 1570 loadngPendingAckSetNextIpAddrType 1571 InetAddressType, 1572 loadngPendingAckSetNextIpAddr 1573 InetAddress, 1574 loadngPendingAckSetOrigIpAddrType 1575 InetAddressType, 1576 loadngPendingAckSetOrigIpAddr 1577 InetAddress, 1578 loadngPendingAckSetSeqnum 1579 Integer32, 1580 loadngPendingAckSetAckReceived 1581 TruthValue, 1582 loadngPendingAckSetAckTimeout 1583 TimeStamp 1584 } 1586 loadngPendingAckSetIndex OBJECT-TYPE 1587 SYNTAX Integer32 (0..65535) 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "The index for this table." 1592 REFERENCE 1593 "RFC XXXX - The Lightweight On-demand Ad hoc 1594 Distance-vector Routing Protocol - Next Generation (LOADng), 1595 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1596 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1597 Lys, T., and J. Dean, July 2013" 1598 ::= { loadngPendingAckSetEntry 1 } 1600 loadngPendingAckSetNextIpAddrType OBJECT-TYPE 1601 SYNTAX InetAddressType 1602 MAX-ACCESS read-only 1603 STATUS current 1604 DESCRIPTION 1605 "The type of the loadngPendingAckSetNextIpAddr 1606 in the InetAddress MIB (RFC 4001). 1608 Only the values 'ipv4(1)' and 1609 'ipv6(2)' are supported." 1610 REFERENCE 1611 "RFC XXXX - The Lightweight On-demand Ad hoc 1612 Distance-vector Routing Protocol - Next Generation (LOADng), 1613 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1614 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1615 Lys, T., and J. Dean, July 2013" 1616 ::= { loadngPendingAckSetEntry 2 } 1618 loadngPendingAckSetNextIpAddr OBJECT-TYPE 1619 SYNTAX InetAddress (SIZE(4|16)) 1620 MAX-ACCESS read-only 1621 STATUS current 1622 DESCRIPTION 1623 "loadngPendingAckSetNextIpAddr is the address 1624 of the neighbor interface to which the RREP 1625 was sent. " 1626 REFERENCE 1627 "RFC XXXX - The Lightweight On-demand Ad hoc 1628 Distance-vector Routing Protocol - Next Generation (LOADng), 1629 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1630 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1631 Lys, T., and J. Dean, July 2013" 1632 ::= { loadngPendingAckSetEntry 3 } 1634 loadngPendingAckSetOrigIpAddrType OBJECT-TYPE 1635 SYNTAX InetAddressType 1636 MAX-ACCESS read-only 1637 STATUS current 1638 DESCRIPTION 1639 "The type of the loadngPendingAckSetOrigIpAddr 1640 in the InetAddress MIB (RFC 4001). 1642 Only the values 'ipv4(1)' and 1643 'ipv6(2)' are supported." 1644 REFERENCE 1645 "RFC XXXX - The Lightweight On-demand Ad hoc 1646 Distance-vector Routing Protocol - Next Generation (LOADng), 1647 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1648 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1649 Lys, T., and J. Dean, July 2013" 1650 ::= { loadngPendingAckSetEntry 4 } 1652 loadngPendingAckSetOrigIpAddr OBJECT-TYPE 1653 SYNTAX InetAddress (SIZE(4|16)) 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "loadngPendingAckSetOrigIpAddr is the address 1658 of the originator of the RREP." 1659 REFERENCE 1660 "RFC XXXX - The Lightweight On-demand Ad hoc 1661 Distance-vector Routing Protocol - Next Generation (LOADng), 1662 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1663 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1664 Lys, T., and J. Dean, July 2013" 1665 ::= { loadngPendingAckSetEntry 5 } 1667 loadngPendingAckSetSeqnum OBJECT-TYPE 1668 SYNTAX Integer32 (0..65535) 1669 MAX-ACCESS read-only 1670 STATUS current 1671 DESCRIPTION 1672 "loadngPendingAckSetSeqnum corresponds to the 1673 field of the sent RREP." 1674 REFERENCE 1675 "RFC XXXX - The Lightweight On-demand Ad hoc 1676 Distance-vector Routing Protocol - Next Generation (LOADng), 1677 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1678 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1679 Lys, T., and J. Dean, July 2013" 1680 ::= { loadngPendingAckSetEntry 6 } 1682 loadngPendingAckSetAckReceived OBJECT-TYPE 1683 SYNTAX TruthValue 1684 MAX-ACCESS read-only 1685 STATUS current 1686 DESCRIPTION 1687 "loadngPendingAckSetAckReceived is a boolean flag, 1688 which specifies the tuple has been acknowledged 1689 by a corresponding RREP_ACK message." 1690 REFERENCE 1691 "RFC XXXX - The Lightweight On-demand Ad hoc 1692 Distance-vector Routing Protocol - Next Generation (LOADng), 1693 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1694 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1695 Lys, T., and J. Dean, July 2013" 1696 ::= { loadngPendingAckSetEntry 7 } 1698 loadngPendingAckSetAckTimeout OBJECT-TYPE 1699 SYNTAX TimeStamp 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "loadngPendingAckSetAckTimeout specifies the value 1704 of sysUptime when this entry should expire and be 1705 removed from the loadngPendingAckSetTable." 1706 REFERENCE 1707 "RFC XXXX - The Lightweight On-demand Ad hoc 1708 Distance-vector Routing Protocol - Next Generation (LOADng), 1709 Clausen, T., Colin de Verdiere, A., Yi, J., Niktash, A., 1710 Igarashi, Y., Satoh, H., Herberg, U., Lavenu, C., 1711 Lys, T., and J. Dean, July 2013" 1712 ::= { loadngPendingAckSetEntry 8 } 1714 -- 1715 -- loadngConformance information 1716 -- 1718 loadngCompliances OBJECT IDENTIFIER ::= { loadngConformance 1 } 1719 loadngMIBGroups OBJECT IDENTIFIER ::= { loadngConformance 2 } 1721 -- Compliance Statements 1722 loadngBasicCompliance MODULE-COMPLIANCE 1723 STATUS current 1724 DESCRIPTION 1725 "The basic implementation requirements for 1726 managed network entities that implement 1727 LOADng." 1728 MODULE -- this module 1729 MANDATORY-GROUPS { loadngConfigurationGroup } 1730 ::= { loadngCompliances 1 } 1732 loadngFullCompliance MODULE-COMPLIANCE 1733 STATUS current 1734 DESCRIPTION 1735 "The full implementation requirements for 1736 managed network entities that implement 1737 LOADng." 1738 MODULE -- this module 1739 MANDATORY-GROUPS { loadngConfigurationGroup, 1740 loadngStateGroup } 1741 ::= { loadngCompliances 2 } 1743 -- 1744 -- Units of Conformance 1745 -- 1747 loadngConfigurationGroup OBJECT-GROUP 1748 OBJECTS { 1749 loadngNetTraversalTime, 1750 loadngRREQRetries, 1751 loadngRREQMinInterval, 1752 loadngRHoldTime, 1753 loadngMaxDist, 1754 loadngBHoldTime, 1755 loadngRREPAckRequired, 1756 loadngRREPAckTimeout, 1757 loadngUseBidirectionalLinkOnly, 1758 loadngRreqMaxJitter, 1759 loadngMaxHopLimit, 1760 loadngIfRowStatus, 1761 loadngLibLocalIfSetIfIndex, 1762 loadngLibLocalIfSetIpAddrType, 1763 loadngLibLocalIfSetRowStatus 1764 } 1765 STATUS current 1766 DESCRIPTION 1767 "Set of LOADng configuration objects implemented 1768 in this module." 1769 ::= { loadngMIBGroups 2 } 1771 loadngStateGroup OBJECT-GROUP 1772 OBJECTS { 1773 loadngUpTime, 1774 loadngBlacklistedNeighborSetIpAddrType, 1775 loadngBlacklistedNeighborSetIpAddr, 1776 loadngBlacklistedNeighborSetBTime, 1777 loadngRoutingSetDestIpAddrType, 1778 loadngRoutingSetDestIpAddr, 1779 loadngRoutingSetNextIpAddrType, 1780 loadngRoutingSetNextIpAddr, 1781 loadngRoutingSetMetric, 1782 loadngRoutingSetMetricType, 1783 loadngRoutingSetHopCount, 1784 loadngRoutingSetSeqnum, 1785 loadngRoutingSetBidirectional, 1786 loadngRoutingSetLocalIfaceIpAddrType, 1787 loadngRoutingSetLocalIfaceIpAddr, 1788 loadngRoutingSetValidTime, 1789 loadngPendingAckSetNextIpAddrType, 1790 loadngPendingAckSetNextIpAddr, 1791 loadngPendingAckSetOrigIpAddrType, 1792 loadngPendingAckSetOrigIpAddr, 1793 loadngPendingAckSetSeqnum, 1794 loadngPendingAckSetAckReceived, 1795 loadngPendingAckSetAckTimeout, 1796 loadngLibLocalIfSetIpAddr, 1797 loadngLibDestaddressetIpAddr, 1798 loadngLibDestaddressetIpAddrType 1799 } 1800 STATUS current 1801 DESCRIPTION 1802 "Set of LOADng state objects implemented 1803 in this module." 1804 ::= { loadngMIBGroups 3 } 1806 END 1808 8. Security Considerations 1810 This MIB module defines objects for the configuration and monitoring 1811 of LOADng [LOADng]. 1813 There are a number of management objects defined in this MIB module 1814 with a MAX-ACCESS clause of read-write and/or read-create. Such 1815 objects may be considered sensitive or vulnerable in some network 1816 environments. The support for SET operations in a non-secure 1817 environment without proper protection can have a negative effect on 1818 network operations. These are the tables and objects and their 1819 sensitivity/vulnerability: 1821 o loadngNetTraversalTime - this writable object controls the maximum 1822 time that a packet is expected to take when traversing from one 1823 end of the network to the other. If set too low, a router will 1824 not wait long enough until receiving an RREP as response to an 1825 RREQ. Therefore, all route requests may fail and render LOADng 1826 useless. 1828 o loadngRREQRetries - this writable object controls how many RREQs 1829 may be sent until an RREP must have been received or the route 1830 discovery is considered failed. If set too low in very lossy 1831 networks, route discovery may fail for destinations (which 1832 otherwise would have succeeded, had the value been higher). If 1833 set too high, a router may send unnecessary many RREQs, draining 1834 energy from the router and consuming bandwidth. 1836 o loadngRREQMinInterval- this writable object controls the minimum 1837 interval between two successive RREQs. If set too low, a 1838 malicious node (host or router) may request routes for many 1839 destinations, resulting in many RREQs, which drain energy from the 1840 router and consume bandwidth. 1842 o loadngRHoldTime - this writable object controls how long a Routing 1843 Tuple is hold in the Routing Set. If set too low, a router may not 1844 keep routes long enough, and may therefore frequently rediscover 1845 the same routes to a destination, resulting in bandwidth 1846 consumption and energy drain. 1848 o loadngRREPAckTimeout - this writable object controls how long a 1849 router waits before expecting an RREP_ACK. If set too low, and if 1850 RREP_ACKs are required, the router may list the neighbor as 1851 unidirectional and may therefore not use it for routing. 1853 o loadngBHoldTime - this writable object controls how long a 1854 Blacklisted Neighbor Tuples is hold in the Blacklisted Neighbor 1855 Set. If set too high, a neighbor router may be blocked for a long 1856 time, even though it may have become reachable bidirectionally in 1857 the meantime. 1859 o loadngRREPAckRequired - this writable object controls whether 1860 RREP_ACKs are required for verification of bidirectionality. If 1861 disabled in a lossy environment, and if bidirectionality is not 1862 verified by other means, unidirectional routes may be discovered 1863 to destinations. 1865 o loadngMaxDist - this writable object controls the maximum distance 1866 of a router in the routing domain. If set too low, destinations 1867 may be ignored to which otherwise a path could be established by 1868 LOADng. 1870 Some of the readable objects in this MIB module (i.e., objects with a 1871 MAX-ACCESS other than not-accessible) may be considered sensitive or 1872 vulnerable in some network environments. It is thus important to 1873 control even GET and/or NOTIFY access to these objects and possibly 1874 to even encrypt the values of these objects when sending them over 1875 the network via SNMP. These are the tables and objects and their 1876 sensitivity/vulnerability: 1878 o loadngRoutingSetTable - The table contains information on 1879 destinations in the routing domain, specifically their IP address 1880 in the loadngRoutingSetDestIpAddr object. This information 1881 provides an adversary broad information on the members of the 1882 routing domain, located within this single table. This 1883 information can be use to expedite attacks on the other members of 1884 the routing domain without having to go through a laborious 1885 discovery process on their own. This object is the index into the 1886 table, and has a MAX-ACCESS of 'not-accessible'. However, this 1887 information can be exposed using SNMP operations. 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 there is no control as to who on the secure network is allowed to 1892 access and GET/SET (read/change/create/delete) the objects in this 1893 MIB module. 1895 Implementations SHOULD provide the security features described by the 1896 SNMPv3 framework (see [RFC3410]), and implementations claiming 1897 compliance to the SNMPv3 standard MUST include full support for 1898 authentication and privacy via the User-based Security Model (USM) 1899 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1900 MAY also provide support for the Transport Security Model (TSM) 1901 [RFC5591] in combination with a secure transport such as SSH 1902 [RFC5592] or TLS/DTLS [RFC6353]. 1904 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1905 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1906 enable cryptographic security. It is then a customer/operator 1907 responsibility to ensure that the SNMP entity giving access to an 1908 instance of this MIB module is properly configured to give access to 1909 the objects only to those principals (users) that have legitimate 1910 rights to indeed GET or SET (change/create/delete) them. 1912 9. IANA Considerations 1914 The MIB module in this document uses the following IANA-assigned 1915 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 1917 Descriptor OBJECT IDENTIFIER value 1918 ---------- ----------------------- 1919 LOADng-MIB { mib-2 XXXX } 1920 IANA EDITOR NOTE: please assign XXXX 1922 10. Acknowledgements 1924 This MIB document uses the template authored by D. Harrington which 1925 is based on contributions from the MIB Doctors, especially Juergen 1926 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 1928 11. References 1930 11.1. Normative References 1932 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1933 Requirement Levels", BCP 14, RFC 2119, March 1997. 1935 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1936 Schoenwaelder, Ed., "Structure of Management Information 1937 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1939 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1940 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1941 STD 58, RFC 2579, April 1999. 1943 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1944 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1945 April 1999. 1947 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1948 MIB", RFC 2863, June 2000. 1950 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 1951 Simple Network Management Protocol (SNMP)", STD 62, 1952 RFC 3418, December 2002. 1954 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1955 Schoenwaelder, "Textual Conventions for Internet Network 1956 Addresses", RFC 4001, February 2005. 1958 [LOADng] Clausen, T., Colin de Verdiere, A., Niktash, A., Igarashi, 1959 Y., Satoh, H., Herberg, U., Lavenu, C., Lys, T., and J. 1960 Dean, "The Lightweight On-demand Ad hoc Distance-vector 1961 Routing Protocol - Next Generation (LOADng)", work in 1962 progress draft-clausen-lln-loadng-09, July 2013. 1964 11.2. Informative References 1966 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1967 "Introduction and Applicability Statements for Internet- 1968 Standard Management Framework", RFC 3410, December 2002. 1970 [RFC3561] Perkins, C., Belding-Royer, E., and S. Das, "Ad hoc On- 1971 Demand Distance Vector (AODV) Routing", RFC 3561, 1972 July 2003. 1974 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 1975 (USM) for version 3 of the Simple Network Management 1976 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 1978 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 1979 Advanced Encryption Standard (AES) Cipher Algorithm in the 1980 SNMP User-based Security Model", RFC 3826, June 2004. 1982 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 1983 for the Simple Network Management Protocol (SNMP)", 1984 RFC 5591, June 2009. 1986 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1987 Shell Transport Model for the Simple Network Management 1988 Protocol (SNMP)", RFC 5592, June 2009. 1990 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1991 Model for the Simple Network Management Protocol (SNMP)", 1992 RFC 6353, July 2011. 1994 Appendix A. 1996 *********************************************************** 1997 * Note to the RFC Editor (to be removed prior to * 1998 * publication) * 1999 * * 2000 * The reference to RFCXXXX within the DESCRIPTION clauses * 2001 * of the MIB module point to this draft or to the LOADng * 2002 * document and are to be assigned by the RFC Editor. * 2003 *********************************************************** 2005 Authors' Addresses 2007 Ulrich Herberg 2008 Fujitsu Laboratories of America 2009 1240 East Arques Avenue 2010 Sunnyvale, CA 94085 2011 USA 2013 EMail: ulrich@herberg.name 2014 URI: http://www.herberg.name/ 2015 Robert G. Cole 2016 US Army CERDEC 2017 6010 Frankford Road, Bldg 6010 2018 Aberdeen Proving Ground, Maryland 21005 2019 USA 2021 Phone: +1 443 395 8744 2022 EMail: robert.g.cole@us.army.mil 2023 URI: http://www.cs.jhu.edu/~rgcole/ 2025 Thomas Heide Clausen 2026 LIX, Ecole Polytechnique 2028 Phone: +33 6 6058 9349 2029 EMail: T.Clausen@computer.org 2030 URI: http://www.ThomasClausen.org/