idnits 2.17.1 draft-clausen-manet-rfc6779bis-00.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 25, 2014) is 3562 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) -- Obsolete informational reference (is this intentional?): RFC 6779 (Obsoleted by RFC 7939) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group U. Herberg 3 Internet-Draft Fujitsu Laboratories of America 4 Obsoletes: 6779 (if approved) R. Cole 5 Intended status: Standards Track US Army CERDEC 6 Expires: January 26, 2015 I. Chakeres 7 Delvin 8 T. Clausen 9 LIX, Ecole Polytechnique 10 July 25, 2014 12 Definition of Managed Objects for the Neighborhood Discovery Protocol 13 draft-clausen-manet-rfc6779bis-00 15 Abstract 17 This document revises, extends, and replaces RFC 6779. It defines a 18 portion of the Management Information Base (MIB) for use with network 19 management protocols in the Internet community. In particular, it 20 describes objects for configuring parameters of the Neighborhood 21 Discovery Protocol (NHDP) process on a router. The MIB module 22 defined in this document, denoted NHDP-MIB, also reports state, 23 performance information, and notifications about NHDP. This 24 additional state and performance information is useful to 25 troubleshoot problems and performance issues during neighbor 26 discovery. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on January 26, 2015. 45 Copyright Notice 47 Copyright (c) 2014 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 1.1. Difference from RFC 6779 . . . . . . . . . . . . . . . . . 3 64 2. The Internet-Standard Management Framework . . . . . . . . . . 3 65 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 4.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 70 5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 5 71 5.1.1. Introduction . . . . . . . . . . . . . . . . . . . . . 5 72 5.1.2. Notification Generation . . . . . . . . . . . . . . . 5 73 5.1.3. Limiting Frequency of Notifications . . . . . . . . . 5 74 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 6 75 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7 76 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 7 77 5.5. Tables and Indexing . . . . . . . . . . . . . . . . . . . 7 78 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 79 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 80 6.2. Relationship to Routing Protocol MIB Modules Relying 81 on the NHDP-MIB Module . . . . . . . . . . . . . . . . . . 10 82 6.3. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10 83 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 84 8. Security Considerations . . . . . . . . . . . . . . . . . . . 64 85 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 66 86 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67 87 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 67 88 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 67 89 12.1. Normative References . . . . . . . . . . . . . . . . . . . 67 90 12.2. Informative References . . . . . . . . . . . . . . . . . . 68 92 1. Introduction 94 This document defines a portion of the Management Information Base 95 (MIB) for use with network management protocols in the Internet 96 community. In particular, it describes objects for configuring 97 parameters of the Neighborhood Discovery Protocol (NHDP) [RFC6130] 98 process on a router. The MIB module defined in this document, 99 denoted NHDP-MIB, also reports state, performance information, and 100 notifications about NHDP. This additional state and performance 101 information is useful to troubleshoot problems and performance issues 102 during neighbor discovery. 104 1.1. Difference from RFC 6779 106 This document obsoletes [RFC6779], replacing that document as the 107 specification of the MIB module for [RFC6130]. 109 Specifically, the MIB module for [RFC6130], specified in this 110 document, captures the new information and states for each symmetric 111 2-hop neighbor, recorded in the Neighbor Information Base of a router 112 and to be reflected in the appropriate tables, introduced by 113 [draft-ietf-manet-nhdp-optimization]. 115 2. The Internet-Standard Management Framework 117 For a detailed overview of the documents that describe the current 118 Internet-Standard Management Framework, please refer to section 7 of 119 RFC 3410 [RFC3410]. 121 Managed objects are accessed via a virtual information store, termed 122 the Management Information Base or MIB. MIB objects are generally 123 accessed through the Simple Network Management Protocol (SNMP). 124 Objects in the MIB are defined using the mechanisms defined in the 125 Structure of Management Information (SMI). This memo specifies a MIB 126 module that is compliant to the SMIv2, which is described in STD 58, 127 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 128 [RFC2580]. 130 3. Conventions 132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 134 OPTIONAL" in this document are to be interpreted as described in 135 [RFC2119]. 137 4. Overview 139 [RFC6130] allows a router to discover and track topological 140 information of routers up to two hops away by virtue of exchanging 141 HELLO messages. This information is useful for routers running 142 various routing and multicast flooding protocols developed within the 143 IETF MANET Working Group. 145 4.1. Terms 147 The following definitions apply throughout this document: 149 o Notification Objects - triggers and associated notification 150 messages allowing for asynchronous tracking of pre-defined events 151 on the managed router. 153 o Configuration Objects - switches, tables, and objects that are 154 initialized to default settings or set through the management 155 interface defined by this MIB module. 157 o State Objects - automatically generated values that define the 158 current operating state of the NHDP instance in the router. 160 o Performance Objects - automatically generated values that help an 161 administrator or automated tool to assess the performance of the 162 NHDP instance on the router and the overall discovery performance 163 within the Mobile Ad Hoc Network (MANET). 165 4.2. Notation 167 The same notations as defined in [RFC6130] are used throughout this 168 document. 170 5. Structure of the MIB Module 172 This section presents the structure of the NHDP-MIB module. The MIB 173 module is arranged into the following structure: 175 o nhdpNotifications - objects defining NHDP-MIB notifications. 177 o nhdpObjects - defining objects within this MIB module. The 178 objects are arranged into the following groups: 180 * Configuration Group - defining objects related to the 181 configuration of the NHDP instance on the router. 183 * State Group - defining objects that reflect the current state 184 of the NHDP instance running on the router. 186 * Performance Group - defining objects that are useful to a 187 management station when characterizing the performance of NHDP 188 on the router and in the MANET. 190 o nhdpConformance - defining the minimal and maximal conformance 191 requirements for implementations of this MIB module. 193 5.1. Notifications 195 This section describes the use of notifications and mechanisms to 196 enhance the ability to manage NHDP routing domains. 198 5.1.1. Introduction 200 Notifications can be emitted by a router running an instance of this 201 specification as a reaction to a specific event. This allows a 202 network manager to efficiently determine the source of problems or 203 significant changes of configuration or topology, instead of polling 204 a possibly large number of routers. 206 5.1.2. Notification Generation 208 When an exception event occurs, the application notifies the local 209 agent, which sends a notification to the appropriate SNMP management 210 stations. The message includes the notification type and may include 211 a list of notification-specific variables. Section 7 contains the 212 notification definitions, which includes the variable lists. At 213 least one IP address of the router that originates the notification 214 is included in the variable list so that the network manager may 215 determine the source of the notification. 217 5.1.3. Limiting Frequency of Notifications 219 To limit the frequency of notifications, the following additional 220 mechanisms are suggested, similar to those in [RFC4750]. 222 5.1.3.1. Ignoring Initial Activity 224 The majority of critical events occur when NHDP is first enabled on a 225 router, at which time the symmetric neighbors and two-hop neighbors 226 of the router are discovered. During this initial period, a 227 potential flood of notifications is unnecessary since the events are 228 expected. To avoid unnecessary notifications, a router SHOULD NOT 229 originate expected notifications until a certain time interval has 230 elapsed, which is to be predefined by the network manager. It is 231 RECOMMENDED that this time interval is at least 3 x 232 nhdpHelloInterval, so that symmetric neighbors are discovered. The 233 suppression window for notifications is started when the nhdpIfStatus 234 transitions from its default value of 'false(2)' to 'true(1)'. 236 5.1.3.2. Throttling Notifications 238 The mechanism for throttling the notifications is the same as in 239 [RFC4750] (i.e., the number of transmitted notifications per time is 240 bounded). 242 Appropriate values for the window time and upper bound are to be 243 selected by the network manager and depend on the deployment of the 244 MANET. If NHDP is deployed on a lossy, wireless medium, sending too 245 many notifications in a short time interval may lead to collisions 246 and dropped packets. In particular, in dense deployments of routers 247 running NHDP (i.e., where each router has many neighbors), a change 248 of the local topology may trigger many notifications at the same 249 time. [RFC4750] recommends "7 traps with a window time of 10 250 seconds" as the upper bound. As NHDP is expected to be deployed in 251 more lossy channels than OSPF, it is RECOMMENDED to choose a lower 252 threshold for the number of notifications per time than that. 253 Specifically, it is RECOMMENDED that the threshold value for the 254 objects reflecting the change be set to a value of '10' and the 255 DEFAULT values for these objects within the Notifications Group be 256 set to this value. Further, a time window for the change objects is 257 defined within this MIB module. It is RECOMMENDED that if the number 258 of occurrences exceeds the change threshold within the previous 259 change window, then the notification is to be sent. Furthermore, it 260 is RECOMMENDED that the value for this window be set to at least 5 261 times the nhdpHelloInterval. 263 The following objects are used to define the thresholds and time 264 windows for specific notifications defined in the NHDP-MIB module: 265 nhdpNbrStateChangeThreshold, nhdpNbrStateChangeWindow, 266 nhdp2HopNbrStateChangeThreshold, and nhdp2HopNbrStateChangeWindow. 268 5.1.3.3. One Notification per Event 270 Similar to the mechanism in [RFC4750], only one notification is sent 271 per event. 273 5.2. The Configuration Group 275 The router running NHDP is configured with a set of controls. The 276 authoritative list of configuration controls within the NHDP-MIB 277 module are found within the MIB module itself. Generally, an attempt 278 was made in developing the NHDP-MIB module to support all 279 configuration objects defined in [RFC6130]. For all of the 280 configuration parameters, the same constraints and default values of 281 these parameters as defined in [RFC6130] are followed. Refer to 283 [RFC5148] for guidance on setting jitter-related parameters, e.g., 284 nhdpMaxJitter. 286 5.3. The State Group 288 The State Group reports current state information of a router running 289 NHDP. The NHDP-MIB State Group tables were designed to contain the 290 complete set of state information defined within the information 291 bases specified in Sections 6, 7, and 8 of [RFC6130]. 293 Two constructs, i.e., TEXTUAL-CONVENTIONs, are defined to support the 294 tables in the State Group. NHDP stores and indexes information 295 through sets of (dynamically defined) addresses, i.e., address sets. 296 Within SMIv2, it is not possible to index tables with variably 297 defined address sets. Hence, these TEXTUAL-CONVENTIONs are defined 298 to provide a local mapping between NHDP-managed address sets and 299 SMIv2 table indexing. These constructs are the NeighborIfIndex and 300 NeighborRouterIndex. These are locally (to the router) defined, 301 unique identifiers of virtual neighbors and neighbor interfaces. Due 302 to the nature of NHDP, the local router may have identified distinct 303 address sets but is not able to associate these as a single 304 interface. Hence, two or more NeighborIfIndexes pointing to multiple 305 distinct address sets may, in fact, be related to a common neighbor 306 interface. This ambiguity may also hold with respect to the 307 assignment of the NeighborRouterIndex. The local MIB agent is 308 responsible for managing, aggregating, and retiring the defined 309 indexes and for updating MIB tables using these indexes as the local 310 router learns more about its neighbors' topologies. These constructs 311 are used to define indexes to the appropriate State Group tables and 312 to correlate table entries to address sets, virtual neighbor 313 interfaces, and virtual neighbors within the MANET. 315 5.4. The Performance Group 317 The Performance Group reports values relevant to system performance. 318 Unstable neighbors or 2-hop neighbors and frequent changes of sets 319 can have a negative influence on the performance of NHDP. This MIB 320 module defines several objects that can be polled in order to, e.g., 321 calculate histories or monitor frequencies of changes. This may help 322 the network administrator to determine unusual topology changes or 323 other changes that affect stability and reliability of the MANET. 325 5.5. Tables and Indexing 327 The NHDP-MIB module contains a number of tables that record data 328 related to: 330 o the local router, 332 o a local MANET interface on the router, 334 o other routers that are 1 hop removed from the local router, 336 o interfaces on other routers that are 1 hop removed from the local 337 router, and 339 o other routers that are 2 hops removed from the local router. 341 The NHDP-MIB module's tables are indexed via the following 342 constructs: 344 o nhdpIfIndex - the IfIndex of the local router on which NHDP is 345 configured. 347 o nhdpDiscIfIndex - a locally managed index representing a known 348 interface on a neighboring router. 350 o nhdpDiscRouterIndex - a locally managed index representing an ID 351 of a known neighboring router. 353 These tables and their indexing are: 355 o nhdpInterfaceTable - describes the configuration of the interfaces 356 of this router. This table has INDEX { nhdpIfIndex }. 358 o nhdpLibLocalIfSetTable - records all network addresses that are 359 defined as local interface network addresses on this router. This 360 table has INDEX { nhdpLibLocalIfSetIndex }. 362 o nhdpLibRemovedIfAddrSetTable - records network addresses that were 363 recently used as local interface network addresses on this router 364 but have been removed. This table has INDEX 365 { nhdpLibRemovedIfAddrSetIndex }. 367 o nhdpInterfaceStateTable - records state information related to 368 specific interfaces of this router. This table has INDEX 369 { nhdpIfIndex }. 371 o nhdpDiscIfSetTable - includes the nhdpDiscRouterIndex of the 372 discovered router, the nhdpDiscIfIndex of the discovered 373 interface, and the current set of addresses associated with this 374 neighbor interface. This table has INDEX { nhdpDiscIfSetIndex }. 376 o nhdpIibLinkSetTable - for each local interface, records all links 377 belonging to other routers that are, or recently were, 1-hop 378 neighbors to this router. This table has INDEX { nhdpIfIndex, 379 nhdpDiscIfIndex }. 381 o nhdpIib2HopSetTable - for each local interface, records network 382 addresses (one at a time) of symmetric 2-hop neighbors and the 383 symmetric links to symmetric 1-hop neighbors of this router 384 through which these symmetric 2-hop neighbors can be reached. 385 This table has INDEX { nhdpIfIndex, nhdpDiscIfIndex, 386 nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddress }. 388 o nhdpNibNeighborSetTable - records all network addresses of each 389 1-hop neighbor to this router. This table has INDEX 390 { nhdpDiscRouterIndex }. 392 o nhdpNibLostNeighborSetTable - records network addresses of other 393 routers that were recently symmetric 1-hop neighbors to this 394 router but are now advertised as lost. This table has INDEX 395 { nhdpDiscRouterIndex }. 397 o nhdpInterfacePerfTable - records performance objects that are 398 measured for each local NHDP interface on this router. This table 399 has INDEX { nhdpIfIndex }. 401 o nhdpDiscIfSetPerfTable - records performance objects that are 402 measured for each discovered interface of a neighbor of this 403 router. This table has INDEX { nhdpDiscIfIndex }. 405 o nhdpDiscNeighborSetPerfTable - records performance objects that 406 are measured for discovered neighbors of this router. This table 407 has INDEX { nhdpDiscRouterIndex }. 409 o nhdpIib2HopSetPerfTable - records performance objects that are 410 measured for discovered 2-hop neighbors of this router. This 411 table has INDEX { nhdpDiscRouterIndex }. 413 6. Relationship to Other MIB Modules 415 This section specifies the relationship of the MIB module contained 416 in this document to other standards, particularly to standards 417 containing other MIB modules. MIB modules and specific definitions 418 imported from MIB modules that SHOULD be implemented in conjunction 419 with the MIB module contained within this document are identified in 420 this section. 422 6.1. Relationship to the SNMPv2-MIB 424 The System group in the SNMPv2-MIB module [RFC3418] is defined as 425 being mandatory for all systems, and the objects apply to the entity 426 as a whole. The System group provides identification of the 427 management entity and certain other system-wide data. The NHDP-MIB 428 module does not duplicate those objects. 430 6.2. Relationship to Routing Protocol MIB Modules Relying on the NHDP- 431 MIB Module 433 [RFC6130] allows routing protocols to rely on the neighborhood 434 information that is discovered by means of HELLO message exchange. 435 In order to allow for troubleshooting, fault isolation, and 436 management of such routing protocols through a routing protocol MIB 437 module, it may be desired to align the State Group tables of the 438 NHDP-MIB module and the routing protocol MIB module. This is 439 accomplished through the definition of two TEXTUAL-CONVENTIONs in the 440 NHDP-MIB module: the NeighborIfIndex and the NeighborRouterIndex. 441 These object types are used to develop indexes into common NHDP-MIB 442 module and routing protocol State Group tables. These objects are 443 locally significant but should be locally common to the NHDP-MIB 444 module and the routing protocol MIB module implemented on a common 445 networked router. This will allow for improved cross-referencing of 446 information across the two MIB modules. 448 6.3. MIB Modules Required for IMPORTS 450 The following NHDP-MIB module IMPORTS objects from SNMPv2-SMI 451 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB 452 [RFC2863], INET-ADDRESS-MIB [RFC4001], and FLOAT-TC-MIB [RFC6340]. 454 7. Definitions 456 This section contains the MIB module defined by the specification. 458 NHDP-MIB DEFINITIONS ::= BEGIN 460 -- This MIB module defines objects for the management of 461 -- NHDP (RFC 6130) - The Neighborhood Discovery Protocol, 462 -- Clausen, T., Dearlove, C., and J. Dean, January 2011. 464 IMPORTS 466 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 467 Counter32, Counter64, Integer32, Unsigned32, mib-2, 468 TimeTicks 469 FROM SNMPv2-SMI -- RFC 2578 471 TEXTUAL-CONVENTION, TruthValue, TimeStamp, 472 RowStatus 473 FROM SNMPv2-TC -- RFC 2579 475 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 476 FROM SNMPv2-CONF -- STD 58 478 SnmpAdminString 479 FROM SNMP-FRAMEWORK-MIB -- RFC 3411 481 InetAddressType, InetAddress, 482 InetAddressPrefixLength 483 FROM INET-ADDRESS-MIB -- RFC 4001 485 InterfaceIndex 486 FROM IF-MIB -- RFC 2863 488 Float32TC 489 FROM FLOAT-TC-MIB -- RFC 6340 490 ; 492 nhdpMIB MODULE-IDENTITY 493 LAST-UPDATED "201407251000Z" -- 25 July 2014 494 ORGANIZATION "IETF MANET Working Group" 495 CONTACT-INFO 496 "WG E-Mail: manet@ietf.org 498 WG Chairs: sratliff@cisco.com 499 jmacker@nrl.navy.mil 501 Editors: Ulrich Herberg 502 Fujitsu Laboratories of America 503 1240 E Arques Ave 504 Sunnyvale CA 94085 505 USA 507 ulrich@herberg.name 508 http://www.herberg.name/ 510 Robert G. Cole 511 US Army CERDEC 512 Space and Terrestrial Communications 513 6010 Frankford Street 514 Aberdeen Proving Ground, Maryland 21005 515 USA 516 +1 443 395-8744 518 robert.g.cole@us.army.mil 519 http://www.cs.jhu.edu/~rgcole/ 520 Ian D Chakeres 521 Delvin 522 Ellicott City, Maryland 21042 523 USA 525 ian.chakeres@gmail.com 526 http://www.ianchak.com/ 528 Thomas Heide Clausen 529 Ecole Polytechnique 530 LIX 531 91128 Palaiseau Cedex 532 France 533 Email: T.Clausen@computer.org 534 URI: http://www.thomasclausen.org/" 536 DESCRIPTION 537 "This NHDP-MIB module is applicable to routers 538 implementing the Neighborhood Discovery Protocol 539 defined in RFC 6130. 541 Copyright (c) 2014 IETF Trust and the persons 542 identified as authors of the code. All rights reserved. 544 Redistribution and use in source and binary forms, with 545 or without modification, is permitted pursuant to, and 546 subject to the license terms contained in, the Simplified 547 BSD License set forth in Section 4.c of the IETF Trust's 548 Legal Provisions Relating to IETF Documents 549 (http://trustee.ietf.org/license-info). 551 This version of this MIB module is part of RFC 6779; see 552 the RFC itself for full legal notices." 554 -- revision 555 REVISION "201407251000Z" -- 25 July 2014 556 DESCRIPTION 557 "Updated version of this MIB module, 558 including updates made to NHDP by 559 draft-ietf-manet-nhdp-optimization, 560 published as RFC xxxx." 561 REVISION "201210221000Z" -- 22 October 2012 562 DESCRIPTION 563 "Initial version of this MIB module, 564 published as RFC 6779." 565 ::= { mib-2 213 } 567 -- 568 -- Top-Level Components of this MIB Module 569 -- 570 nhdpNotifications OBJECT IDENTIFIER ::= { nhdpMIB 0 } 571 nhdpObjects OBJECT IDENTIFIER ::= { nhdpMIB 1 } 572 nhdpConformance OBJECT IDENTIFIER ::= { nhdpMIB 2 } 574 -- 575 -- TEXTUAL-CONVENTIONs 576 -- 577 -- Two new TEXTUAL-CONVENTIONs have been defined in 578 -- this MIB module for indexing into the following 579 -- tables and indexing into other tables in other MIB modules. 580 -- This was necessary because NHDP manages and 581 -- indexes based upon dynamic address tuples, i.e., 582 -- address sets, while SMI requires statically 583 -- defined indexes for accessing its table rows. 584 -- The NeighborIfIndex defines a unique (to the local router) 585 -- index referencing a discovered virtual interface on another 586 -- neighbor within the MANET. The NeighborRouterIndex defines a 587 -- unique (to the local router) index referencing a discovered 588 -- virtual neighbor within the MANET. 589 -- 590 -- Due to the nature of NHDP, 591 -- different indexes may be related to common neighbor 592 -- interfaces or common neighbor routers, but the information 593 -- obtained through NHDP has not allowed the local router 594 -- to relate these virtual objects (i.e., interfaces or routers) 595 -- at this point in time. As more topology information 596 -- is gathered by the local router, it may associate 597 -- virtual interfaces or routers and collapse these 598 -- indexes appropriately. 600 -- Multiple addresses can be associated with a 601 -- given NeighborIfIndex. Each NeighborIfIndex is 602 -- associated with a NeighborRouterIndex. Throughout 603 -- the nhdpStateObjGroup, the 604 -- NeighborIfIndex and the NeighborRouterIndex are used 605 -- to define the set of IpAddrs related to a virtual 606 -- neighbor interface or virtual neighbor under discussion. 608 NeighborIfIndex ::= TEXTUAL-CONVENTION 609 DISPLAY-HINT "d" 610 STATUS current 611 DESCRIPTION 612 "An arbitrary, locally unique identifier associated with a 613 virtual interface of a discovered NHDP neighbor. 615 Due to the nature of NHDP, the local router 616 may not know if two distinct addresses belong to the 617 same interface of a neighbor or to two different 618 interfaces. As the local router gains more 619 knowledge of its neighbors, its local view may change, and 620 this table will be updated to reflect the local router's 621 current understanding, associating address sets to neighbor 622 interfaces. The local router identifies a virtual neighbor 623 interface through the receipt of address lists advertised 624 through an NHDP HELLO message. 626 All objects of type NeighborIfIndex are assigned by the agent 627 out of a common number space. 629 The value for each discovered virtual neighbor 630 interface may not remain constant from 631 one re-initialization of the entity's network management 632 agent to the next re-initialization. If the 633 local router gains information associating two virtual 634 interfaces on a neighbor as a common interface, 635 then the agent MUST aggregate the two address sets to 636 a single index chosen from the set of aggregated indexes, 637 and it MUST update all tables in this 638 MIB module that are indexed by indexes 639 of type NeighborIfIndex. It MAY then reuse freed 640 index values following the next agent restart. 642 The specific value is meaningful only within a given SNMP 643 entity." 644 SYNTAX Unsigned32 (1..2147483647) 646 NeighborRouterIndex ::= TEXTUAL-CONVENTION 647 DISPLAY-HINT "d" 648 STATUS current 649 DESCRIPTION 650 "An arbitrary, locally unique identifier associated with a 651 virtual discovered neighbor (one or two hop). Due to the 652 nature of NHDP, the local router may identify 653 multiple virtual neighbors that, in fact, are one and 654 the same. Neighbors that are two hops away with more than 655 one advertised address will exhibit this behavior. As the 656 local router's knowledge of its neighbors' topology 657 increases, the local router will be able to associate 658 multiple virtual neighbor indexes into a single virtual 659 neighbor index chosen from the set of aggregated indexes; 660 it MUST update all tables in this MIB module indexed by these 661 indexes, and it MAY reuse the freed indexes following the 662 next agent re-initialization. 664 All objects of type NeighborRouterIndex are assigned by 665 the agent out of a common number space. 667 The NeighborRouterIndex defines a discovered NHDP peer 668 virtual neighbor of the local router. 669 The value for each discovered virtual neighbor index MUST 670 remain constant at least from one re-initialization of 671 the entity's network management agent to the next 672 re-initialization, except if an application is deleted 673 and re-created. 675 The specific value is meaningful only within a given SNMP 676 entity. A NeighborRouterIndex value MUST NOT be reused 677 until the next agent restart." 678 SYNTAX Unsigned32 (1..2147483647) 680 -- 681 -- nhdpObjects 682 -- 684 -- 1) Configuration Objects Group 685 -- 2) State Objects Group 686 -- 3) Performance Objects Group 688 -- 689 -- nhdpConfigurationObjGrp 690 -- 692 -- Contains the NHDP objects that configure specific options 693 -- that determine the overall performance and operation of 694 -- NHDP. 696 nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 } 698 nhdpInterfaceTable OBJECT-TYPE 699 SYNTAX SEQUENCE OF NhdpInterfaceEntry 700 MAX-ACCESS not-accessible 701 STATUS current 702 DESCRIPTION 703 "The nhdpInterfaceTable describes the 704 configuration of the interfaces of this router 705 that are intended to use MANET control protocols. 706 As such, this table 'sparse augments' the ifTable 707 specifically when NHDP is to be configured to 708 operate over this interface. The interface is 709 identified by the ifIndex from the interfaces 710 group defined in the Interfaces Group MIB module. 712 A conceptual row in this table exists if and only 713 if either a manager has explicitly created the row 714 or there is an interface on the managed device 715 that supports and runs NHDP. 717 The manager can create a row by setting 718 rowStatus to 'createAndGo' or 'createAndWait'. 719 Row objects having associated DEFVAL clauses are 720 automatically defined by the agent with these 721 values during row creation, unless the manager 722 explicitly defines these object values during the 723 row creation. 725 If the corresponding entry with ifIndex value 726 is deleted from the Interface Table, then the entry 727 in this table is automatically deleted, 728 NHDP is disabled on this interface, 729 and all configuration and state information 730 related to this interface is to be removed 731 from memory." 732 REFERENCE 733 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 734 K., and F. Kastenholtz, June 2000" 735 ::= { nhdpConfigurationObjGrp 1 } 737 nhdpInterfaceEntry OBJECT-TYPE 738 SYNTAX NhdpInterfaceEntry 739 MAX-ACCESS not-accessible 740 STATUS current 741 DESCRIPTION 742 "The nhdpInterfaceEntry describes one NHDP 743 local interface configuration as indexed by 744 its ifIndex as defined in the Standard MIB II 745 Interface Table (RFC 2863). 747 The objects in this table are persistent, and when 748 written, the device SHOULD save the change to 749 non-volatile storage. For further information 750 on the storage behavior for these objects, refer 751 to the description for the nhdpIfRowStatus 752 object." 754 INDEX { nhdpIfIndex } 755 ::= { nhdpInterfaceTable 1 } 757 NhdpInterfaceEntry ::= 758 SEQUENCE { 759 nhdpIfIndex 760 InterfaceIndex, 761 nhdpIfName 762 SnmpAdminString, 763 nhdpIfStatus 764 TruthValue, 765 nhdpHelloInterval 766 Unsigned32, 767 nhdpHelloMinInterval 768 Unsigned32, 769 nhdpRefreshInterval 770 Unsigned32, 771 nhdpLHoldTime 772 Unsigned32, 773 nhdpHHoldTime 774 Unsigned32, 775 nhdpHystAcceptQuality 776 Float32TC, 777 nhdpHystRejectQuality 778 Float32TC, 779 nhdpInitialQuality 780 Float32TC, 781 nhdpInitialPending 782 TruthValue, 783 nhdpHpMaxJitter 784 Unsigned32, 785 nhdpHtMaxJitter 786 Unsigned32, 787 nhdpIfRowStatus 788 RowStatus 789 } 791 nhdpIfIndex OBJECT-TYPE 792 SYNTAX InterfaceIndex 793 MAX-ACCESS not-accessible 794 STATUS current 795 DESCRIPTION 796 "This value MUST correspond to an ifIndex referring 797 to a valid entry in the Interfaces Table." 798 REFERENCE 799 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 800 and F. Kastenholtz, June 2000" 801 ::= { nhdpInterfaceEntry 1 } 802 nhdpIfName OBJECT-TYPE 803 SYNTAX SnmpAdminString 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "The textual name of the interface. The value of this 808 object SHOULD be the name of the interface as assigned by 809 the local device. This can be a text-name, such as 'le0' 810 or a simple port number, such as '1', 811 depending on the interface-naming syntax of the device. 813 If there is no local name or this object is otherwise not 814 applicable, then this object contains a zero-length string." 815 ::= { nhdpInterfaceEntry 2 } 817 nhdpIfStatus OBJECT-TYPE 818 SYNTAX TruthValue 819 MAX-ACCESS read-create 820 STATUS current 821 DESCRIPTION 822 "nhdpIfStatus indicates whether this interface is 823 currently running NHDP. A value of 'true(1)' indicates 824 that NHDP is running on this interface. 825 A value of 'false(2)' indicates that NHDP is not 826 currently running on this interface. This corresponds 827 to the I_manet parameter in the Local Interface Set 828 of NHDP." 829 DEFVAL { false } 830 ::= { nhdpInterfaceEntry 3 } 832 -- 833 -- Interface Parameters - Message Intervals 834 -- 836 nhdpHelloInterval OBJECT-TYPE 837 SYNTAX Unsigned32 838 UNITS "milliseconds" 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "nhdpHelloInterval corresponds to 843 HELLO_INTERVAL of NHDP and represents the 844 maximum time between the transmission of two 845 successive HELLO messages on this MANET interface. 847 Guidance for setting this object may be found 848 in Section 5 of the NHDP specification (RFC 6130), 849 which indicates that: 851 o nhdpHelloInterval > 0 852 o nhdpHelloInterval >= nhdpHelloMinInterval" 853 REFERENCE 854 "Section 5 on Protocol Parameters and 855 Constraints of RFC 6130 - Mobile Ad Hoc 856 Network (MANET) Neighborhood Discovery 857 Protocol (NHDP), Clausen, T., Dearlove, 858 C., and J. Dean, April 2011" 859 DEFVAL { 2000 } 860 ::= { nhdpInterfaceEntry 4 } 862 nhdpHelloMinInterval OBJECT-TYPE 863 SYNTAX Unsigned32 864 UNITS "milliseconds" 865 MAX-ACCESS read-create 866 STATUS current 867 DESCRIPTION 868 "nhdpHelloMinInterval corresponds to 869 HELLO_MIN_INTERVAL of NHDP and represents 870 the minimum interval between transmission 871 of two successive HELLO messages on this 872 MANET interface. 874 Guidance for setting this object may be found 875 in Section 5 of the NHDP specification (RFC 6130), 876 which indicates that: 877 o nhdpHelloMinInterval <= nhdpHelloInterval" 878 REFERENCE 879 "Section 5 on Protocol Parameters and 880 Constraints of RFC 6130 - Mobile Ad Hoc Network 881 (MANET) Neighborhood Discovery Protocol (NHDP), 882 Clausen, T., Dearlove, C., and J. Dean, April 2011" 883 DEFVAL { 500 } 884 ::= { nhdpInterfaceEntry 5 } 886 nhdpRefreshInterval OBJECT-TYPE 887 SYNTAX Unsigned32 888 UNITS "milliseconds" 889 MAX-ACCESS read-create 890 STATUS current 891 DESCRIPTION 892 "nhdpRefreshInterval corresponds to 893 REFRESH_INTERVAL of NHDP and represents the 894 maximum interval between advertisements of 895 each 1-hop neighbor network address and its 896 status. Each advertisement is in a HELLO 897 message on this MANET interface. 899 Guidance for setting this object may be found 900 in Section 5 of the NHDP specification (RFC 6130), 901 which indicates that: 902 o nhdpRefreshInterval >= nhdpHelloInterval" 903 REFERENCE 904 "Section 5 on Protocol Parameters and 905 Constraints of RFC 6130 - Mobile Ad Hoc Network 906 (MANET) Neighborhood Discovery Protocol (NHDP), 907 Clausen, T., Dearlove, C., and J. Dean, April 2011" 908 DEFVAL { 2000 } 909 ::= { nhdpInterfaceEntry 6 } 911 -- 912 -- Interface Parameters - Information Validity times 913 -- 915 nhdpLHoldTime OBJECT-TYPE 916 SYNTAX Unsigned32 917 UNITS "milliseconds" 918 MAX-ACCESS read-create 919 STATUS current 920 DESCRIPTION 921 "nhdpLHoldTime corresponds to 922 L_HOLD_TIME of NHDP and represents the period 923 of advertisement, on this MANET interface, of 924 former 1-hop neighbor network addresses as lost 925 in HELLO messages, allowing recipients of these 926 HELLO messages to accelerate removal of this 927 information from their Link Sets. 929 Guidance for setting this object may be found 930 in Section 5 of the NHDP specification (RFC 6130), 931 which indicates that it should be assigned a 932 value significantly greater than the refresh 933 interval held by nhdpRefreshInterval." 934 REFERENCE 935 "Section 5 on Protocol Parameters and 936 Constraints of RFC 6130 - Mobile Ad Hoc Network 937 (MANET) Neighborhood Discovery Protocol (NHDP), 938 Clausen, T., Dearlove, C., and J. Dean, April 2011" 939 DEFVAL { 6000 } 940 ::= { nhdpInterfaceEntry 7 } 942 nhdpHHoldTime OBJECT-TYPE 943 SYNTAX Unsigned32 944 UNITS "milliseconds" 945 MAX-ACCESS read-create 946 STATUS current 947 DESCRIPTION 948 "nhdpHHoldTime corresponds to 949 H_HOLD_TIME of NHDP and is used as the value 950 in the VALIDITY_TIME Message TLV included in all 951 HELLO messages on this MANET interface. It is then 952 used by each router receiving such a HELLO message 953 to indicate the validity of the information taken 954 from that HELLO message and recorded in the receiving 955 router's Information Bases. 957 Guidance for setting this object may be found 958 in Section 5 of the NHDP specification (RFC 6130), 959 which indicates that it should be assigned a 960 value significantly greater than the refresh interval 961 held by nhdpRefreshInterval and must be representable 962 as described in RFC 5497." 963 REFERENCE 964 "Section 5 on Protocol Parameters and 965 Constraints of RFC 6130 - Mobile Ad Hoc Network 966 (MANET) Neighborhood Discovery Protocol (NHDP), 967 Clausen, T., Dearlove, C., and J. Dean, April 2011" 968 DEFVAL { 6000 } 969 ::= { nhdpInterfaceEntry 8 } 971 -- 972 -- Interface Parameters - Link Quality 973 -- 975 nhdpHystAcceptQuality OBJECT-TYPE 976 SYNTAX Float32TC 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "nhdpHystAcceptQuality corresponds to 981 HYST_ACCEPT of NHDP and represents the link 982 quality threshold at or above which a link becomes 983 usable, if it was not already so. 985 Guidance for setting this object may be found 986 in Section 5 of the NHDP specification (RFC 6130), 987 which indicates that: 988 o 0 <= nhdpHystRejectQuality 989 <= nhdpHystAcceptQuality <= 1.0 991 The default value for this object is 1.0. According to 992 RFC 6340: 994 Since these textual conventions are defined in terms 995 of the OCTET STRING type, the SMI's mechanisms for 996 formally setting range constraints are not available. 997 MIB designers using these textual conventions will need 998 to use DESCRIPTION clauses to spell out any applicable 999 range constraints beyond those implied by the underlying 1000 IEEE types. 1001 Therefore, this object does not have a DEFVAL clause." 1002 REFERENCE 1003 "Section 5 on Protocol Parameters and 1004 Constraints of RFC 6130 - Mobile Ad Hoc Network 1005 (MANET) Neighborhood Discovery Protocol (NHDP), 1006 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1007 -- DEFVAL { 1.0 } see DESCRIPTION 1008 ::= { nhdpInterfaceEntry 9 } 1010 nhdpHystRejectQuality OBJECT-TYPE 1011 SYNTAX Float32TC 1012 MAX-ACCESS read-create 1013 STATUS current 1014 DESCRIPTION 1015 "nhdpHystRejectQuality corresponds to 1016 HYST_REJECT of NHDP and represents the 1017 link quality threshold below which a 1018 link becomes unusable, if it was not 1019 already so. 1021 Guidance for setting this object may be found 1022 in Section 5 of the NHDP specification (RFC 6130), 1023 which indicates that: 1024 o 0 <= nhdpHystRejectQuality 1025 <= nhdpHystAcceptQuality <= 1.0 1027 The default value for this object is 0.0. According to 1028 RFC 6340: 1029 Since these textual conventions are defined in terms 1030 of the OCTET STRING type, the SMI's mechanisms for 1031 formally setting range constraints are not available. 1032 MIB designers using these textual conventions will need 1033 to use DESCRIPTION clauses to spell out any applicable 1034 range constraints beyond those implied by the underlying 1035 IEEE types. 1036 Therefore, this object does not have a DEFVAL clause." 1037 REFERENCE 1038 "Section 5 on Protocol Parameters and 1039 Constraints of RFC 6130 - Mobile Ad Hoc Network 1040 (MANET) Neighborhood Discovery Protocol (NHDP), 1041 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1043 -- DEFVAL { 0.0 } see DESCRIPTION 1044 ::= { nhdpInterfaceEntry 10 } 1046 nhdpInitialQuality OBJECT-TYPE 1047 SYNTAX Float32TC 1048 MAX-ACCESS read-create 1049 STATUS current 1050 DESCRIPTION 1051 "nhdpInitialQuality corresponds to 1052 INITIAL_QUALITY of NHDP and represents the 1053 initial quality of a newly identified link. 1055 Guidance for setting this object may be found 1056 in Section 5 of the NHDP specification (RFC 6130), 1057 which indicates that: 1058 o 0 <= nhdpInitialQuality <= 1.0 1060 The default value for this object is 1.0. According to 1061 RFC 6340: 1062 Since these textual conventions are defined in terms 1063 of the OCTET STRING type, the SMI's mechanisms for 1064 formally setting range constraints are not available. 1065 MIB designers using these textual conventions will need 1066 to use DESCRIPTION clauses to spell out any applicable 1067 range constraints beyond those implied by the underlying 1068 IEEE types. 1069 Therefore, this object does not have a DEFVAL clause." 1070 REFERENCE 1071 "Section 5 on Protocol Parameters and 1072 Constraints of RFC 6130 - Mobile Ad Hoc Network 1073 (MANET) Neighborhood Discovery Protocol (NHDP), 1074 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1075 -- DEFVAL { 1.0 } see DESCRIPTION 1076 ::= { nhdpInterfaceEntry 11 } 1078 nhdpInitialPending OBJECT-TYPE 1079 SYNTAX TruthValue 1080 MAX-ACCESS read-create 1081 STATUS current 1082 DESCRIPTION 1083 "nhdpInitialPending corresponds to 1084 INITIAL_PENDING of NHDP. If the value of this object 1085 is 'true(1)', then a newly identified link is considered 1086 pending and is not usable until the link quality 1087 has reached or exceeded the nhdpHystAcceptQuality 1088 threshold. 1090 Guidance for setting this object may be found 1091 in Section 5 of the NHDP specification (RFC 6130), 1092 which indicates that: 1093 o If nhdpInitialQuality >= nhdpHystAcceptQuality, 1094 then nhdpInitialPending := false(2). 1095 o If nhdpInitialQuality < nhdpHystRejectQuality, 1096 then nhdpInitialPending := true(1)." 1097 REFERENCE 1098 "Section 5 on Protocol Parameters and 1099 Constraints of RFC 6130 - Mobile Ad Hoc Network 1100 (MANET) Neighborhood Discovery Protocol (NHDP), 1101 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1102 DEFVAL { false } 1103 ::= { nhdpInterfaceEntry 12 } 1105 -- 1106 -- Interface Parameters - Jitter 1107 -- 1108 nhdpHpMaxJitter OBJECT-TYPE 1109 SYNTAX Unsigned32 1110 UNITS "milliseconds" 1111 MAX-ACCESS read-create 1112 STATUS current 1113 DESCRIPTION 1114 "nhdpHpMaxJitter corresponds to 1115 HP_MAXJITTER of NHDP and represents the 1116 value of MAXJITTER used in RFC 5148 for 1117 periodically generated HELLO messages on 1118 this MANET interface. 1120 Guidance for setting this object may be found 1121 in Section 5 of RFC 5148, which indicates that: 1122 o nhdpHpMaxJitter <= nhdpHelloInterval / 2 1123 o nhdpHpMaxJitter should not be greater 1124 than nhdpHelloInterval / 4 1125 o If nhdpMinHelloInterval > 0, then 1126 nhdpHpMaxJitter <= nhdpHelloMinInterval; and 1127 nhdpHpMaxJitter should not be greater than 1128 nhdpHelloMinInterval / 2" 1129 REFERENCE 1130 "Section 5 of RFC 5148 - Jitter Considerations in 1131 Mobile Ad Hoc Networks (MANETs), 1132 Clausen, T., Dearlove, C., and B. Adamson, February 2008" 1133 DEFVAL { 500 } 1134 ::= { nhdpInterfaceEntry 13 } 1136 nhdpHtMaxJitter OBJECT-TYPE 1137 SYNTAX Unsigned32 1138 UNITS "milliseconds" 1139 MAX-ACCESS read-create 1140 STATUS current 1141 DESCRIPTION 1142 "nhdpHtMaxJitter corresponds to 1143 HT_MAXJITTER of NHDP and represents the 1144 value of MAXJITTER used in RFC 5148 for 1145 externally triggered HELLO messages on this 1146 MANET interface. 1148 Guidance for setting this object may be found 1149 in Section 5 of RFC 5148, which indicates that: 1150 o nhdpHtMaxJitter <= nhdpHelloInterval / 2 1151 o nhdpHtMaxJitter should not be greater 1152 than nhdpHelloInterval / 4 1153 o If nhdpMinHelloInterval > 0, then 1154 nhdpHtMaxJitter <= nhdpHelloMinInterval; and 1155 nhdpHtMaxJitter should not be greater than 1156 nhdpHelloMinInterval / 2" 1157 REFERENCE 1158 "Section 5 of RFC 5148 - Jitter Considerations in 1159 Mobile Ad Hoc Networks (MANETs), 1160 Clausen, T., Dearlove, C., and B. Adamson, February 2008" 1161 DEFVAL { 500 } 1162 ::= { nhdpInterfaceEntry 14 } 1164 nhdpIfRowStatus OBJECT-TYPE 1165 SYNTAX RowStatus 1166 MAX-ACCESS read-create 1167 STATUS current 1168 DESCRIPTION 1169 "This object permits management of the table 1170 by facilitating actions such as row creation, 1171 construction, and destruction. The value of 1172 this object has no effect on whether other 1173 objects in this conceptual row can be 1174 modified. 1176 An entry may not exist in the 'active(1)' state unless all 1177 objects in the entry have a defined appropriate value. For 1178 objects with DEFVAL clauses, the management station 1179 does not need to specify the value of this object in order 1180 for the row to transit to the 'active(1)' state; the default 1181 value for this object is used. For objects that do not 1182 have DEFVAL clauses, then the network manager MUST 1183 specify the value of this object prior to this row 1184 transitioning to the 'active(1)' state. 1186 When this object transitions to 'active(1)', all objects 1187 in this row SHOULD be written to non-volatile (stable) 1188 storage. Read-create objects in this row MAY be modified. 1189 When an object in a row with nhdpIfRowStatus of 'active(1)' 1190 is changed, then the updated value MUST be reflected in NHDP, 1191 and this new object value MUST be written to non-volatile 1192 storage. 1194 If the value of this object is not equal to 'active(1)', 1195 all associated entries in the nhdpLibLocalIfSetTable, 1196 nhdpInterfaceStateTable, nhdpIibLinkSetTable, and 1197 nhdpInterfacePerfTable MUST be deleted." 1198 REFERENCE 1199 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1200 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1201 C., and J. Dean, April 2011" 1202 DEFVAL { active } 1203 ::= { nhdpInterfaceEntry 15 } 1205 -- 1206 -- Router Parameters - Information Validity Time 1207 -- 1208 nhdpNHoldTime OBJECT-TYPE 1209 SYNTAX Unsigned32 1210 UNITS "milliseconds" 1211 MAX-ACCESS read-write 1212 STATUS current 1213 DESCRIPTION 1214 "nhdpNHoldTime corresponds to 1215 N_HOLD_TIME of NHDP and is used as the period 1216 during which former 1-hop neighbor network 1217 addresses are advertised as lost in HELLO 1218 messages, allowing recipients of these HELLO 1219 messages to accelerate removal of this information 1220 from their 2-Hop Sets. 1222 This object is persistent, and when written, 1223 the entity SHOULD save the change to 1224 non-volatile storage." 1225 REFERENCE 1226 "Section 5 on Protocol Parameters and 1227 Constraints of RFC 6130 - Mobile Ad Hoc Network 1228 (MANET) Neighborhood Discovery Protocol (NHDP), 1229 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1230 DEFVAL { 6000 } 1231 ::= { nhdpConfigurationObjGrp 2 } 1232 nhdpIHoldTime OBJECT-TYPE 1233 SYNTAX Unsigned32 1234 UNITS "milliseconds" 1235 MAX-ACCESS read-write 1236 STATUS current 1237 DESCRIPTION 1238 "nhdpIHoldTime corresponds to 1239 I_HOLD_TIME of NHDP and represents the period 1240 for which a recently used local interface network 1241 address is recorded. 1243 This object is persistent, and when written, 1244 the entity SHOULD save the change to 1245 non-volatile storage." 1246 REFERENCE 1247 "Section 5 on Protocol Parameters and 1248 Constraints of RFC 6130 - Mobile Ad Hoc Network 1249 (MANET) Neighborhood Discovery Protocol (NHDP), 1250 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1251 DEFVAL { 6000 } 1252 ::= { nhdpConfigurationObjGrp 3 } 1254 -- A router's Local Information Base (LIB) 1256 -- 1257 -- Local Interface Set Table 1258 -- 1260 nhdpLibLocalIfSetTable OBJECT-TYPE 1261 SYNTAX SEQUENCE OF NhdpLibLocalIfSetEntry 1262 MAX-ACCESS not-accessible 1263 STATUS current 1264 DESCRIPTION 1265 "A router's Local Interface Set records all 1266 network addresses that are defined as local 1267 MANET interface network addresses. 1268 As such, this table 'sparse augments' the 1269 nhdpInterfaceTable when network addresses are 1270 being defined for the interfaces existing within 1271 the nhdpInterfaceTable. The local interface 1272 is defined by the nhdpIfIndex. 1274 The Local Interface Set consists of Local Interface 1275 Address Tuples per MANET interface and their prefix 1276 lengths (in order to determine the network addresses 1277 related to the interface). 1279 A conceptual row in this table exists if and only 1280 if a manager has explicitly created the row. The 1281 manager can create a row by setting rowStatus 1282 to 'createAndGo' or 'createAndWait'. 1284 Further guidance on the addition or removal of 1285 local addresses and network addresses is found 1286 in Section 9 of RFC 6130." 1287 REFERENCE 1288 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1289 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1290 C., and J. Dean, April 2011" 1291 ::= { nhdpConfigurationObjGrp 4 } 1293 nhdpLibLocalIfSetEntry OBJECT-TYPE 1294 SYNTAX NhdpLibLocalIfSetEntry 1295 MAX-ACCESS not-accessible 1296 STATUS current 1297 DESCRIPTION 1298 "A router's Local Interface Set consists 1299 of Configured Interface Address Tuples for each network 1300 interface. 1302 The objects in this table are persistent, and when 1303 written, the device SHOULD save the change to 1304 non-volatile storage. For further information 1305 on the storage behavior for these objects, refer 1306 to the description for the nhdpLibLocalIfSetRowStatus 1307 object." 1308 REFERENCE 1309 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1310 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1311 C., and J. Dean, April 2011" 1312 INDEX { nhdpLibLocalIfSetIndex } 1313 ::= { nhdpLibLocalIfSetTable 1 } 1315 NhdpLibLocalIfSetEntry ::= 1316 SEQUENCE { 1317 nhdpLibLocalIfSetIndex 1318 Integer32, 1319 nhdpLibLocalIfSetIfIndex 1320 InterfaceIndex, 1321 nhdpLibLocalIfSetIpAddrType 1322 InetAddressType, 1323 nhdpLibLocalIfSetIpAddr 1324 InetAddress, 1325 nhdpLibLocalIfSetIpAddrPrefixLen 1326 InetAddressPrefixLength, 1328 nhdpLibLocalIfSetRowStatus 1329 RowStatus 1330 } 1332 nhdpLibLocalIfSetIndex OBJECT-TYPE 1333 SYNTAX Integer32 (0..65535) 1334 MAX-ACCESS not-accessible 1335 STATUS current 1336 DESCRIPTION 1337 "The index for this table. Necessary 1338 because multiple addresses may be associated 1339 with a given nhdpIfIndex." 1340 REFERENCE 1341 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1342 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1343 C., and J. Dean, April 2011" 1344 ::= { nhdpLibLocalIfSetEntry 1 } 1346 nhdpLibLocalIfSetIfIndex OBJECT-TYPE 1347 SYNTAX InterfaceIndex 1348 MAX-ACCESS read-only 1349 STATUS current 1350 DESCRIPTION 1351 "Specifies the local nhdpIfIndex for which this 1352 IP address was added." 1353 REFERENCE 1354 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1355 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1356 C., and J. Dean, April 2011" 1357 ::= { nhdpLibLocalIfSetEntry 2 } 1359 nhdpLibLocalIfSetIpAddrType OBJECT-TYPE 1360 SYNTAX InetAddressType 1361 MAX-ACCESS read-create 1362 STATUS current 1363 DESCRIPTION 1364 "The type of the nhdpLibLocalIfSetIpAddr 1365 in the InetAddress MIB (RFC 4001). 1367 Only the values 'ipv4(1)' and 1368 'ipv6(2)' are supported." 1369 REFERENCE 1370 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1371 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1372 C., and J. Dean, April 2011" 1373 ::= { nhdpLibLocalIfSetEntry 3 } 1375 nhdpLibLocalIfSetIpAddr OBJECT-TYPE 1376 SYNTAX InetAddress (SIZE(4|16)) 1377 MAX-ACCESS read-create 1378 STATUS current 1379 DESCRIPTION 1380 "nhdpLibLocalIfSetIpAddr is an 1381 address of an interface of 1382 this router. 1384 This object is interpreted according to 1385 the setting of nhdpLibLocalIfSetIpAddrType." 1386 REFERENCE 1387 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1388 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1389 C., and J. Dean, April 2011" 1390 ::= { nhdpLibLocalIfSetEntry 4 } 1392 nhdpLibLocalIfSetIpAddrPrefixLen OBJECT-TYPE 1393 SYNTAX InetAddressPrefixLength 1394 MAX-ACCESS read-create 1395 STATUS current 1396 DESCRIPTION 1397 "Indicates the number of leading one bits that 1398 form the mask. The mask is logically ANDed 1399 to the nhdpLibLocalIfSetIpAddr to determine 1400 the address prefix. A row match is true 1401 if the address used as an index falls within 1402 the network address range defined by the 1403 address prefix." 1404 REFERENCE 1405 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1406 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1407 C., and J. Dean, April 2011" 1408 ::= { nhdpLibLocalIfSetEntry 5 } 1410 nhdpLibLocalIfSetRowStatus OBJECT-TYPE 1411 SYNTAX RowStatus 1412 MAX-ACCESS read-create 1413 STATUS current 1414 DESCRIPTION 1415 "This object permits management of the table 1416 by facilitating actions such as row creation, 1417 construction, and destruction. The value of 1418 this object has no effect on whether other 1419 objects in this conceptual row can be 1420 modified. 1422 An entry may not exist in the 'active(1)' state unless all 1423 read-create objects in the entry have a defined 1424 appropriate value. As no objects in this table have 1425 DEFVAL clauses, the management station MUST specify 1426 the values of all read-create objects prior to this row 1427 transitioning to the 'active(1)' state. 1429 When this object transitions to 'active(1)', all objects 1430 in this row SHOULD be written to non-volatile (stable) 1431 storage. Read-create objects in this row MAY be modified. 1432 When an object in a row with nhdpIfRowStatus of 'active(1)' 1433 is changed, then the updated value MUST be reflected in NHDP, 1434 and this new object value MUST be written to non-volatile 1435 storage." 1436 REFERENCE 1437 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1438 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1439 C., and J. Dean, April 2011" 1440 DEFVAL { notReady } 1441 ::= { nhdpLibLocalIfSetEntry 6 } 1443 -- 1444 -- Removed Interface Addr Set Table 1445 -- 1447 nhdpLibRemovedIfAddrSetTable OBJECT-TYPE 1448 SYNTAX SEQUENCE OF NhdpLibRemovedIfAddrSetEntry 1449 MAX-ACCESS not-accessible 1450 STATUS current 1451 DESCRIPTION 1452 "A router's Removed Interface Address Set records 1453 network addresses that were recently used as local 1454 interface network addresses. If a router's interface 1455 network addresses are immutable, then the Removed 1456 Interface Address Set is always empty and may be omitted. 1457 It consists of Removed Interface Address Tuples, one 1458 per network address." 1459 REFERENCE 1460 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1461 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1462 C., and J. Dean, April 2011" 1463 ::= { nhdpConfigurationObjGrp 5 } 1465 nhdpLibRemovedIfAddrSetEntry OBJECT-TYPE 1466 SYNTAX NhdpLibRemovedIfAddrSetEntry 1467 MAX-ACCESS not-accessible 1468 STATUS current 1469 DESCRIPTION 1470 "A router's Removed Interface Address Set consists 1471 of Removed Interface Address Tuples, one per network 1472 address: 1474 (IR_local_iface_addr, IR_time) 1476 The association between these addresses and the 1477 router's Interface is found in the Standard MIB II's 1478 IP address table (RFC 1213)." 1479 REFERENCE 1480 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1481 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1482 C., and J. Dean, April 2011" 1483 INDEX { nhdpLibRemovedIfAddrSetIndex } 1484 ::= { nhdpLibRemovedIfAddrSetTable 1 } 1486 NhdpLibRemovedIfAddrSetEntry ::= 1487 SEQUENCE { 1488 nhdpLibRemovedIfAddrSetIndex 1489 Integer32, 1490 nhdpLibRemovedIfAddrSetIpAddrType 1491 InetAddressType, 1492 nhdpLibRemovedIfAddrSetIpAddr 1493 InetAddress, 1494 nhdpLibRemovedIfAddrSetIpAddrPrefixLen 1495 InetAddressPrefixLength, 1496 nhdpLibRemovedIfAddrSetIfIndex 1497 InterfaceIndex, 1498 nhdpLibRemovedIfAddrSetIRTime 1499 TimeStamp 1500 } 1502 nhdpLibRemovedIfAddrSetIndex OBJECT-TYPE 1503 SYNTAX Integer32 (0..65535) 1504 MAX-ACCESS not-accessible 1505 STATUS current 1506 DESCRIPTION 1507 "The index for this table. Necessary 1508 because multiple addresses may be associated 1509 with a given nhdpIfIndex." 1510 REFERENCE 1511 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1512 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1513 C., and J. Dean, April 2011" 1514 ::= { nhdpLibRemovedIfAddrSetEntry 1 } 1516 nhdpLibRemovedIfAddrSetIpAddrType OBJECT-TYPE 1517 SYNTAX InetAddressType 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "The type of the nhdpLibRemovedIfAddrSetIpAddr 1522 in the InetAddress MIB (RFC 4001). 1524 Only the values 'ipv4(1)' and 1525 'ipv6(2)' are supported." 1526 REFERENCE 1527 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1528 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1529 C., and J. Dean, April 2011" 1530 ::= { nhdpLibRemovedIfAddrSetEntry 2 } 1532 nhdpLibRemovedIfAddrSetIpAddr OBJECT-TYPE 1533 SYNTAX InetAddress (SIZE(4|16)) 1534 MAX-ACCESS read-only 1535 STATUS current 1536 DESCRIPTION 1537 "nhdpLibRemovedIfAddrSetIpAddr is a 1538 recently used address of an interface of 1539 this router." 1540 REFERENCE 1541 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1542 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1543 C., and J. Dean, April 2011" 1544 ::= { nhdpLibRemovedIfAddrSetEntry 3 } 1546 nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE 1547 SYNTAX InetAddressPrefixLength 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "Indicates the number of leading one bits that 1552 form the mask. The mask is logically ANDed 1553 to the nhdpLibRemovedIfAddrSetIpAddr to determine 1554 the address prefix. A row match is true 1555 if the address used as an index falls within 1556 the network address range defined by the 1557 address prefix." 1558 REFERENCE 1559 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1560 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1561 C., and J. Dean, April 2011" 1562 ::= { nhdpLibRemovedIfAddrSetEntry 4 } 1564 nhdpLibRemovedIfAddrSetIfIndex OBJECT-TYPE 1565 SYNTAX InterfaceIndex 1566 MAX-ACCESS read-only 1567 STATUS current 1568 DESCRIPTION 1569 "Specifies the local IfIndex from which this 1570 IP address was recently removed." 1571 REFERENCE 1572 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1573 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1574 C., and J. Dean, April 2011" 1575 ::= { nhdpLibRemovedIfAddrSetEntry 5 } 1577 nhdpLibRemovedIfAddrSetIRTime OBJECT-TYPE 1578 SYNTAX TimeStamp 1579 MAX-ACCESS read-only 1580 STATUS current 1581 DESCRIPTION 1582 "nhdpLibRemovedIfAddrSetIRTime specifies the value 1583 of sysUptime when this entry should expire and be 1584 removed from the nhdpLibRemovedIfAddrSetTable." 1585 REFERENCE 1586 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1587 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1588 C., and J. Dean, April 2011" 1589 ::= { nhdpLibRemovedIfAddrSetEntry 6 } 1591 -- 1592 -- nhdpStateObjGrp 1593 -- 1595 -- Contains information describing the current state of the NHDP 1596 -- process on this router. 1598 nhdpStateObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 2 } 1600 nhdpUpTime OBJECT-TYPE 1601 SYNTAX TimeStamp 1602 MAX-ACCESS read-only 1603 STATUS current 1604 DESCRIPTION 1605 "The value of sysUpTime at the time the current NHDP 1606 process was initialized." 1607 ::= { nhdpStateObjGrp 1 } 1609 nhdpInterfaceStateTable OBJECT-TYPE 1610 SYNTAX SEQUENCE OF NhdpInterfaceStateEntry 1611 MAX-ACCESS not-accessible 1612 STATUS current 1613 DESCRIPTION 1614 "nhdpInterfaceStateTable lists state information 1615 related to specific interfaces of this router. 1616 The value of nhdpIfIndex is an ifIndex from the 1617 interfaces group defined in the Interfaces Group 1618 MIB. 1620 The objects in this table are persistent, and when 1621 written, the entity SHOULD save the change to 1622 non-volatile storage." 1623 REFERENCE 1624 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1625 K., and F. Kastenholtz, June 2000." 1626 ::= { nhdpStateObjGrp 2 } 1628 nhdpInterfaceStateEntry OBJECT-TYPE 1629 SYNTAX NhdpInterfaceStateEntry 1630 MAX-ACCESS not-accessible 1631 STATUS current 1632 DESCRIPTION 1633 "nhdpInterfaceStateEntry describes one NHDP 1634 local interface state as indexed by 1635 its nhdpIfIndex." 1636 INDEX { nhdpIfIndex } 1637 ::= { nhdpInterfaceStateTable 1 } 1639 NhdpInterfaceStateEntry ::= 1640 SEQUENCE { 1641 nhdpIfStateUpTime 1642 TimeStamp 1643 } 1645 nhdpIfStateUpTime OBJECT-TYPE 1646 SYNTAX TimeStamp 1647 MAX-ACCESS read-only 1648 STATUS current 1649 DESCRIPTION 1650 "The value of the sysUpTime when 1651 NHDP was last initialized on this 1652 MANET interface." 1653 ::= { nhdpInterfaceStateEntry 1 } 1655 -- 1656 -- This table allows for the mapping between discovered 1657 -- remote interfaces and routers and their addresses. 1658 -- 1660 nhdpDiscIfSetTable OBJECT-TYPE 1661 SYNTAX SEQUENCE OF NhdpDiscIfSetEntry 1662 MAX-ACCESS not-accessible 1663 STATUS current 1664 DESCRIPTION 1665 "A router's set of discovered interfaces on 1666 neighboring routers." 1667 REFERENCE 1668 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1669 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1670 C., and J. Dean, April 2011" 1671 ::= { nhdpStateObjGrp 3 } 1673 nhdpDiscIfSetEntry OBJECT-TYPE 1674 SYNTAX NhdpDiscIfSetEntry 1675 MAX-ACCESS not-accessible 1676 STATUS current 1677 DESCRIPTION 1678 "The entries include the nhdpDiscRouterIndex of 1679 the discovered router, the nhdpDiscIfIndex 1680 of the discovered interface, and the 1681 current set of addresses associated 1682 with this neighbor interface. The 1683 nhdpDiscIfIndex uniquely identifies 1684 the remote interface address sets 1685 through this table. It does not need 1686 to be unique across the MANET but MUST 1687 be locally unique within this router." 1688 REFERENCE 1689 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1690 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1691 C., and J. Dean, April 2011" 1692 INDEX { nhdpDiscIfSetIndex } 1693 ::= { nhdpDiscIfSetTable 1 } 1695 NhdpDiscIfSetEntry ::= 1696 SEQUENCE { 1697 nhdpDiscIfSetIndex 1698 Integer32, 1699 nhdpDiscIfIndex 1700 NeighborIfIndex, 1701 nhdpDiscRouterIndex 1702 NeighborRouterIndex, 1703 nhdpDiscIfSetIpAddrType 1704 InetAddressType, 1705 nhdpDiscIfSetIpAddr 1706 InetAddress, 1707 nhdpDiscIfSetIpAddrPrefixLen 1708 InetAddressPrefixLength 1709 } 1711 nhdpDiscIfSetIndex OBJECT-TYPE 1712 SYNTAX Integer32 (0..65535) 1713 MAX-ACCESS not-accessible 1714 STATUS current 1715 DESCRIPTION 1716 "The index for this table. Necessary 1717 because multiple addresses may be associated 1718 with a given nhdpDiscIfIndex." 1719 REFERENCE 1720 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1721 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1722 C., and J. Dean, April 2011" 1723 ::= { nhdpDiscIfSetEntry 1 } 1725 nhdpDiscIfIndex OBJECT-TYPE 1726 SYNTAX NeighborIfIndex 1727 MAX-ACCESS read-only 1728 STATUS current 1729 DESCRIPTION 1730 "The NHDP interface index (locally created) 1731 of a neighbor's interface. Used for cross- 1732 indexing into other NHDP tables and other 1733 MIB modules." 1734 REFERENCE 1735 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1736 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1737 C., and J. Dean, April 2011" 1738 ::= { nhdpDiscIfSetEntry 2 } 1740 nhdpDiscRouterIndex OBJECT-TYPE 1741 SYNTAX NeighborRouterIndex 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "The NHDP neighbor index (locally created) 1746 of a neighboring router. Used for cross- 1747 indexing into other NHDP tables and other 1748 MIB modules." 1749 REFERENCE 1750 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1751 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1752 C., and J. Dean, April 2011" 1753 ::= { nhdpDiscIfSetEntry 3 } 1755 nhdpDiscIfSetIpAddrType OBJECT-TYPE 1756 SYNTAX InetAddressType 1757 MAX-ACCESS read-only 1758 STATUS current 1759 DESCRIPTION 1760 "The type of the nhdpDiscIfSetIpAddr 1761 in the InetAddress MIB (RFC 4001). 1763 Only the values 'ipv4(1)' and 1764 'ipv6(2)' are supported." 1765 REFERENCE 1766 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1767 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1768 C., and J. Dean, April 2011" 1769 ::= { nhdpDiscIfSetEntry 4 } 1771 nhdpDiscIfSetIpAddr OBJECT-TYPE 1772 SYNTAX InetAddress (SIZE(4|16)) 1773 MAX-ACCESS read-only 1774 STATUS current 1775 DESCRIPTION 1776 "The nhdpDiscIfSetIpAddr is a 1777 recently used address of a neighbor 1778 of this router." 1779 REFERENCE 1780 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1781 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1782 C., and J. Dean, April 2011" 1783 ::= { nhdpDiscIfSetEntry 5 } 1785 nhdpDiscIfSetIpAddrPrefixLen OBJECT-TYPE 1786 SYNTAX InetAddressPrefixLength 1787 MAX-ACCESS read-only 1788 STATUS current 1789 DESCRIPTION 1790 "Indicates the number of leading one bits that 1791 form the mask. The mask is logically ANDed 1792 to the nhdpDiscIfSetIpAddr to determine 1793 the address prefix. A row match is true 1794 if the address used as an index falls within 1795 the network address range defined by the 1796 address prefix." 1797 REFERENCE 1798 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1799 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1800 C., and J. Dean, April 2011" 1801 ::= { nhdpDiscIfSetEntry 6 } 1803 -- Interface Information Base (IIB) 1805 -- 1806 -- Link Set 1807 -- 1809 nhdpIibLinkSetTable OBJECT-TYPE 1810 SYNTAX SEQUENCE OF NhdpIibLinkSetEntry 1811 MAX-ACCESS not-accessible 1812 STATUS current 1813 DESCRIPTION 1814 "A Link Set of an interface records all links 1815 from other routers that are, or recently 1816 were, 1-hop neighbors." 1817 REFERENCE 1818 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1819 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1820 C., and J. Dean, April 2011" 1821 ::= { nhdpStateObjGrp 4 } 1823 nhdpIibLinkSetEntry OBJECT-TYPE 1824 SYNTAX NhdpIibLinkSetEntry 1825 MAX-ACCESS not-accessible 1826 STATUS current 1827 DESCRIPTION 1828 "A Link Set consists of Link Tuples, each 1829 representing a single link indexed by the 1830 local and remote interface pair: 1832 (L_neighbor_iface_addr_list, L_HEARD_time, 1833 L_SYM_time, L_quality, L_pending, 1834 L_lost, L_time). 1836 The local interface is indexed via the 1837 nhdpIfIndex. The 1-hop interface is 1838 indexed via the nhdpDiscIfIndex. There 1839 SHOULD be an entry in this table for each 1840 local interface and associated 1-hop 1841 neighbor reachable on this local interface. 1843 Note that L_quality is not included in the 1844 entries below, because updates may be 1845 required too frequently." 1846 REFERENCE 1847 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1848 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1849 C., and J. Dean, April 2011" 1850 INDEX { nhdpIfIndex, 1851 nhdpDiscIfIndex } 1852 ::= { nhdpIibLinkSetTable 1 } 1854 NhdpIibLinkSetEntry ::= 1855 SEQUENCE { 1856 nhdpIibLinkSetLHeardTime 1857 TimeStamp, 1858 nhdpIibLinkSetLSymTime 1859 TimeStamp, 1860 nhdpIibLinkSetLPending 1861 TruthValue, 1862 nhdpIibLinkSetLLost 1863 TruthValue, 1864 nhdpIibLinkSetLTime 1865 TimeStamp 1866 } 1868 nhdpIibLinkSetLHeardTime OBJECT-TYPE 1869 SYNTAX TimeStamp 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "nhdpIibLinkSetLHeardTime corresponds 1874 to L_HEARD_time of NHDP and represents the 1875 time up to which the MANET interface of the 1876 1-hop neighbor would be considered heard if 1877 not considering link quality." 1878 REFERENCE 1879 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1880 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1881 C., and J. Dean, April 2011" 1882 ::= { nhdpIibLinkSetEntry 1 } 1884 nhdpIibLinkSetLSymTime OBJECT-TYPE 1885 SYNTAX TimeStamp 1886 MAX-ACCESS read-only 1887 STATUS current 1888 DESCRIPTION 1889 "nhdpIibLinkSetLSymTime corresponds 1890 to L_SYM_time of NHDP and represents the time 1891 up to which the link to the 1-hop neighbor 1892 would be considered symmetric if not considering 1893 link quality." 1894 REFERENCE 1895 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1896 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1897 C., and J. Dean, April 2011" 1898 ::= { nhdpIibLinkSetEntry 2 } 1900 nhdpIibLinkSetLPending OBJECT-TYPE 1901 SYNTAX TruthValue 1902 MAX-ACCESS read-only 1903 STATUS current 1904 DESCRIPTION 1905 "nhdpIibLinkSetLPending corresponds 1906 to L_pending of NHDP and is a boolean flag, 1907 describing if a link is considered pending 1908 (i.e., a candidate, but not yet established, 1909 link)." 1910 REFERENCE 1911 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1912 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1913 C., and J. Dean, April 2011" 1914 ::= { nhdpIibLinkSetEntry 3 } 1916 nhdpIibLinkSetLLost OBJECT-TYPE 1917 SYNTAX TruthValue 1918 MAX-ACCESS read-only 1919 STATUS current 1920 DESCRIPTION 1921 "nhdpIibLinkSetLLost corresponds 1922 to L_lost of NHDP and is a boolean flag, 1923 describing if a link is considered lost due 1924 to low link quality." 1925 REFERENCE 1926 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1927 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1928 C., and J. Dean, April 2011" 1929 ::= { nhdpIibLinkSetEntry 4 } 1931 nhdpIibLinkSetLTime OBJECT-TYPE 1932 SYNTAX TimeStamp 1933 MAX-ACCESS read-only 1934 STATUS current 1935 DESCRIPTION 1936 "nhdpIibLinkSetLTime specifies the value 1937 of sysUptime when this entry should expire and be 1938 removed from the nhdpIibLinkSetTable." 1939 REFERENCE 1940 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1941 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1942 C., and J. Dean, April 2011" 1944 ::= { nhdpIibLinkSetEntry 5 } 1946 -- 1947 -- 2-Hop Set 1948 -- 1949 nhdpIib2HopSetTable OBJECT-TYPE 1950 SYNTAX SEQUENCE OF NhdpIib2HopSetEntry 1951 MAX-ACCESS not-accessible 1952 STATUS current 1953 DESCRIPTION 1954 "A 2-Hop Set of an interface records network 1955 addresses of symmetric 2-hop neighbors and 1956 the symmetric links to symmetric 1-hop neighbors 1957 through which these symmetric 2-hop neighbors 1958 can be reached. It consists of 2-Hop Tuples." 1959 REFERENCE 1960 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1961 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1962 C., and J. Dean, April 2011" 1963 ::= { nhdpStateObjGrp 5 } 1965 nhdpIib2HopSetEntry OBJECT-TYPE 1966 SYNTAX NhdpIib2HopSetEntry 1967 MAX-ACCESS not-accessible 1968 STATUS current 1969 DESCRIPTION 1970 "nhdpIib2HopSetTable consists of 2-Hop Tuples, each 1971 representing a single network address of a symmetric 1972 2-hop neighbor and a single MANET interface of a 1973 symmetric 1-hop neighbor. 1975 (N2_neighbor_iface_addr_list, 1976 N2_2hop_addr, N2_lost, N2_time). 1978 The entries include: 1979 - the 2-hop neighbor addresses 1980 ('N2_neighbor_iface_addr_list'), which 1981 act as the table index, 1982 - the associated symmetric 1-hop 1983 neighbor address set ('N2_2hop_addr'), designated 1984 through nhdpDiscIfIndex, 1985 - a flag indicating if the 1-hop neighbor 1986 through which this 2-hop neighbor is reachable 1987 ('N2_lost') is considered lost due to link quality, 1988 or not, 1989 - and the expiration time ('N2_time'). 1991 The nhdpIfIndex in the INDEX is the interface index of 1992 the local interface through which these 2-hop addresses 1993 are accessible. The nhdpDiscIfIndex in the INDEX 1994 represents the 1-hop neighbor interface through which 1995 these 2-hop neighbor addresses are reachable." 1997 REFERENCE 1998 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1999 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2000 C., and J. Dean, April 2011, 2001 and 2002 draft-ietf-manet-nhdp-optimization-00 - 2003 An Optimization for the MANET Neighborhood Discovery 2004 Protocol (NHDP), Dearlove, C., and T. Clausen, 2005 July 2014" 2006 INDEX { nhdpIfIndex, 2007 nhdpDiscIfIndex, 2008 nhdpIib2HopSetIpAddressType, 2009 nhdpIib2HopSetIpAddress 2010 } 2011 ::= { nhdpIib2HopSetTable 1 } 2013 NhdpIib2HopSetEntry ::= 2014 SEQUENCE { 2015 nhdpIib2HopSetIpAddressType 2016 InetAddressType, 2017 nhdpIib2HopSetIpAddress 2018 InetAddress, 2019 nhdpIib2HopSetIpAddrPrefixLen 2020 InetAddressPrefixLength, 2021 nhdpIib2HopSet1HopIfIndex 2022 NeighborIfIndex, 2023 nhdpIib2HopSetN2Lost 2024 TruthValue, 2025 nhdpIib2HopSetN2Time 2026 TimeStamp 2027 } 2029 nhdpIib2HopSetIpAddressType OBJECT-TYPE 2030 SYNTAX InetAddressType 2031 MAX-ACCESS not-accessible 2032 STATUS current 2033 DESCRIPTION 2034 "The type of the nhdpIib2HopSetIpAddress 2035 in the InetAddress MIB module (RFC 4001). 2037 Only the values 'ipv4(1)' and 2038 'ipv6(2)' are supported." 2040 REFERENCE 2041 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2042 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2043 C., and J. Dean, April 2011" 2044 ::= { nhdpIib2HopSetEntry 1 } 2046 nhdpIib2HopSetIpAddress OBJECT-TYPE 2047 SYNTAX InetAddress (SIZE(4|16)) 2048 MAX-ACCESS not-accessible 2049 STATUS current 2050 DESCRIPTION 2051 "nhdpIib2HopSetIpAddr corresponds 2052 to N2_2hop_addr of NHDP and is a network 2053 address of a symmetric 2-hop neighbor that 2054 has a symmetric link (using any MANET 2055 interface) to the indicated symmetric 2056 1-hop neighbor." 2057 REFERENCE 2058 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2059 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2060 C., and J. Dean, April 2011" 2061 ::= { nhdpIib2HopSetEntry 2 } 2063 nhdpIib2HopSetIpAddrPrefixLen OBJECT-TYPE 2064 SYNTAX InetAddressPrefixLength 2065 MAX-ACCESS read-only 2066 STATUS current 2067 DESCRIPTION 2068 "Indicates the number of leading one bits that 2069 form the mask. The mask is logically ANDed 2070 to the nhdpIib2HopSetIpAddress to determine 2071 the address prefix. A row match is true 2072 if the address used as an index falls within 2073 the network address range defined by the 2074 address prefix." 2075 REFERENCE 2076 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2077 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2078 C., and J. Dean, April 2011" 2079 ::= { nhdpIib2HopSetEntry 3 } 2081 nhdpIib2HopSet1HopIfIndex OBJECT-TYPE 2082 SYNTAX NeighborIfIndex 2083 MAX-ACCESS read-only 2084 STATUS current 2085 DESCRIPTION 2086 "nhdpIib2HopSet1HopIfIndex is 2087 nhdpDiscIfIndex of the 1-hop 2088 neighbor that communicated the ipAddress 2089 of the 2-hop neighbor in this row entry." 2090 REFERENCE 2091 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2092 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2093 C., and J. Dean, April 2011" 2094 ::= { nhdpIib2HopSetEntry 4 } 2096 nhdpIib2HopSetN2Lost OBJECT-TYPE 2097 SYNTAX TruthValue 2098 MAX-ACCESS read-only 2099 STATUS current 2100 DESCRIPTION 2101 "nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and 2102 is a boolean flag, describing if for a 2-Hop Tuple, the 2103 corresponding Link Tuple currently is considered lost 2104 due to link quality." 2106 REFERENCE 2107 "draft-ietf-manet-nhdp-optimization-00 - 2108 An Optimization for the MANET Neighborhood Discovery 2109 Protocol (NHDP), Dearlove, C., and T. Clausen, 2110 July 2014" 2111 ::= {nhdpIib2HopSetEntry 5} 2113 nhdpIib2HopSetN2Time OBJECT-TYPE 2114 SYNTAX TimeStamp 2115 MAX-ACCESS read-only 2116 STATUS current 2117 DESCRIPTION 2118 "nhdpIib2HopSetN2Time specifies the value 2119 of sysUptime when this entry should expire and be 2120 removed from the nhdpIib2HopSetTable." 2121 REFERENCE 2122 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2123 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2124 C., and J. Dean, April 2011" 2125 ::= { nhdpIib2HopSetEntry 6 } 2127 -- 2128 -- Neighbor Information Base (NIB) 2129 -- 2130 -- Each router maintains a Neighbor Information Base 2131 -- that records information about addresses of 2132 -- current and recently symmetric 1-hop neighbors. 2134 -- 2135 -- Neighbor Set 2136 -- 2137 -- The Neighbor Set Table is small because 2138 -- most of the corresponding information is found 2139 -- in the nhdpDiscoveredIfTable above. 2140 -- 2142 nhdpNibNeighborSetTable OBJECT-TYPE 2143 SYNTAX SEQUENCE OF NhdpNibNeighborSetEntry 2144 MAX-ACCESS not-accessible 2145 STATUS current 2146 DESCRIPTION 2147 "A router's Neighbor Set records all 2148 network addresses of each 1-hop 2149 neighbor." 2150 REFERENCE 2151 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2152 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2153 C., and J. Dean, April 2011" 2154 ::= { nhdpStateObjGrp 6 } 2156 nhdpNibNeighborSetEntry OBJECT-TYPE 2157 SYNTAX NhdpNibNeighborSetEntry 2158 MAX-ACCESS not-accessible 2159 STATUS current 2160 DESCRIPTION 2161 "A router's Neighbor Set consists 2162 of Neighbor Tuples, each representing 2163 a single 1-hop neighbor: 2165 (N_neighbor_addr_list, N_symmetric)" 2166 REFERENCE 2167 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2168 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2169 C., and J. Dean, April 2011" 2170 INDEX { nhdpDiscRouterIndex } 2171 ::= { nhdpNibNeighborSetTable 1 } 2173 NhdpNibNeighborSetEntry ::= 2174 SEQUENCE { 2175 nhdpNibNeighborSetNSymmetric 2176 TruthValue 2177 } 2179 nhdpNibNeighborSetNSymmetric OBJECT-TYPE 2180 SYNTAX TruthValue 2181 MAX-ACCESS read-only 2182 STATUS current 2183 DESCRIPTION 2184 "nhdpNibNeighborNSymmetric corresponds 2185 to N_symmetric of NHDP and is a boolean flag, 2186 describing if this is a symmetric 1-hop neighbor." 2187 REFERENCE 2188 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2189 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2190 C., and J. Dean, April 2011" 2191 ::= { nhdpNibNeighborSetEntry 1 } 2193 -- 2194 -- Lost Neighbor Set 2195 -- 2196 nhdpNibLostNeighborSetTable OBJECT-TYPE 2197 SYNTAX SEQUENCE OF NhdpNibLostNeighborSetEntry 2198 MAX-ACCESS not-accessible 2199 STATUS current 2200 DESCRIPTION 2201 "A router's Lost Neighbor Set records network 2202 addresses of routers that were recently 2203 symmetric 1-hop neighbors but are now 2204 advertised as lost." 2205 REFERENCE 2206 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2207 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2208 C., and J. Dean, April 2011" 2209 ::= { nhdpStateObjGrp 7 } 2211 nhdpNibLostNeighborSetEntry OBJECT-TYPE 2212 SYNTAX NhdpNibLostNeighborSetEntry 2213 MAX-ACCESS not-accessible 2214 STATUS current 2215 DESCRIPTION 2216 "A router's Lost Neighbor Set consists of 2217 Lost Neighbor Tuples, each representing a 2218 single such network address: 2220 (NL_neighbor_addr, NL_time)" 2221 REFERENCE 2222 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2223 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2224 C., and J. Dean, April 2011" 2225 INDEX { nhdpDiscRouterIndex } 2226 ::= { nhdpNibLostNeighborSetTable 1 } 2228 NhdpNibLostNeighborSetEntry ::= 2229 SEQUENCE { 2230 nhdpNibLostNeighborSetNLTime 2231 TimeStamp 2232 } 2234 nhdpNibLostNeighborSetNLTime OBJECT-TYPE 2235 SYNTAX TimeStamp 2236 MAX-ACCESS read-only 2237 STATUS current 2238 DESCRIPTION 2239 "nhdpNibLostNeighborSetNLTime 2240 specifies the value of sysUptime when this entry 2241 should expire and be removed from the 2242 nhdpNibLostNeighborSetTable." 2243 REFERENCE 2244 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2245 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2246 C., and J. Dean, April 2011" 2247 ::= { nhdpNibLostNeighborSetEntry 1 } 2249 -- 2250 -- nhdpPerformanceObjGrp 2251 -- 2253 -- Contains objects that help to characterize the performance of 2254 -- the NHDP process, typically counters. 2255 -- 2256 nhdpPerformanceObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 3 } 2258 -- 2259 -- Objects per local interface 2260 -- 2262 nhdpInterfacePerfTable OBJECT-TYPE 2263 SYNTAX SEQUENCE OF NhdpInterfacePerfEntry 2264 MAX-ACCESS not-accessible 2265 STATUS current 2266 DESCRIPTION 2267 "This table summarizes performance objects that are 2268 measured per local NHDP interface." 2269 REFERENCE 2270 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2271 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2272 C., and J. Dean, April 2011" 2273 ::= { nhdpPerformanceObjGrp 1 } 2274 nhdpInterfacePerfEntry OBJECT-TYPE 2275 SYNTAX NhdpInterfacePerfEntry 2276 MAX-ACCESS not-accessible 2277 STATUS current 2278 DESCRIPTION 2279 "A single entry contains performance counters for 2280 a local NHDP interface." 2281 INDEX { nhdpIfIndex } 2282 ::= { nhdpInterfacePerfTable 1 } 2284 NhdpInterfacePerfEntry ::= 2285 SEQUENCE { 2286 nhdpIfHelloMessageXmits 2287 Counter32, 2288 nhdpIfHelloMessageRecvd 2289 Counter32, 2290 nhdpIfHelloMessageXmitAccumulatedSize 2291 Counter64, 2292 nhdpIfHelloMessageRecvdAccumulatedSize 2293 Counter64, 2294 nhdpIfHelloMessageTriggeredXmits 2295 Counter32, 2296 nhdpIfHelloMessagePeriodicXmits 2297 Counter32, 2298 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount 2299 Counter32, 2300 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount 2301 Counter32, 2302 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount 2303 Counter32 2304 } 2306 nhdpIfHelloMessageXmits OBJECT-TYPE 2307 SYNTAX Counter32 2308 UNITS "messages" 2309 MAX-ACCESS read-only 2310 STATUS current 2311 DESCRIPTION 2312 "A counter is incremented each time a HELLO 2313 message has been transmitted on that interface." 2314 ::= { nhdpInterfacePerfEntry 1 } 2316 nhdpIfHelloMessageRecvd OBJECT-TYPE 2317 SYNTAX Counter32 2318 UNITS "messages" 2319 MAX-ACCESS read-only 2320 STATUS current 2321 DESCRIPTION 2322 "A counter is incremented each time a 2323 HELLO message has been received on that interface." 2324 ::= { nhdpInterfacePerfEntry 2 } 2326 nhdpIfHelloMessageXmitAccumulatedSize OBJECT-TYPE 2327 SYNTAX Counter64 2328 UNITS "octets" 2329 MAX-ACCESS read-only 2330 STATUS current 2331 DESCRIPTION 2332 "A counter is incremented by the number of octets in 2333 a HELLO message each time a 2334 HELLO message has been sent." 2335 ::= { nhdpInterfacePerfEntry 3 } 2337 nhdpIfHelloMessageRecvdAccumulatedSize OBJECT-TYPE 2338 SYNTAX Counter64 2339 UNITS "octets" 2340 MAX-ACCESS read-only 2341 STATUS current 2342 DESCRIPTION 2343 "A counter is incremented by the number of octets in 2344 a HELLO message each time a 2345 HELLO message has been received." 2346 ::= { nhdpInterfacePerfEntry 4 } 2348 nhdpIfHelloMessageTriggeredXmits OBJECT-TYPE 2349 SYNTAX Counter32 2350 UNITS "messages" 2351 MAX-ACCESS read-only 2352 STATUS current 2353 DESCRIPTION 2354 "A counter is incremented each time a triggered 2355 HELLO message has been sent." 2356 ::= { nhdpInterfacePerfEntry 5 } 2358 nhdpIfHelloMessagePeriodicXmits OBJECT-TYPE 2359 SYNTAX Counter32 2360 UNITS "messages" 2361 MAX-ACCESS read-only 2362 STATUS current 2363 DESCRIPTION 2364 "A counter is incremented each time a periodic 2365 HELLO message has been sent." 2366 ::= { nhdpInterfacePerfEntry 6 } 2368 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount OBJECT-TYPE 2369 SYNTAX Counter32 2370 UNITS "neighbors" 2371 MAX-ACCESS read-only 2372 STATUS current 2373 DESCRIPTION 2374 "A counter is incremented by the number of advertised 2375 symmetric neighbors in a HELLO each time a HELLO 2376 message has been sent." 2377 ::= { nhdpInterfacePerfEntry 7 } 2379 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount OBJECT-TYPE 2380 SYNTAX Counter32 2381 UNITS "neighbors" 2382 MAX-ACCESS read-only 2383 STATUS current 2384 DESCRIPTION 2385 "A counter is incremented by the number of advertised 2386 heard neighbors in a HELLO each time a HELLO 2387 message has been sent." 2388 ::= { nhdpInterfacePerfEntry 8 } 2390 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount OBJECT-TYPE 2391 SYNTAX Counter32 2392 UNITS "neighbors" 2393 MAX-ACCESS read-only 2394 STATUS current 2395 DESCRIPTION 2396 "A counter is incremented by the number of advertised 2397 lost neighbors in a HELLO each time a HELLO 2398 message has been sent." 2399 ::= { nhdpInterfacePerfEntry 9 } 2401 -- 2402 -- Objects per discovered neighbor interface 2403 -- 2404 nhdpDiscIfSetPerfTable OBJECT-TYPE 2405 SYNTAX SEQUENCE OF NhdpDiscIfSetPerfEntry 2406 MAX-ACCESS not-accessible 2407 STATUS current 2408 DESCRIPTION 2409 "A router's set of performance properties for 2410 each discovered interface of a neighbor." 2411 REFERENCE 2412 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2413 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2414 C., and J. Dean, April 2011" 2415 ::= { nhdpPerformanceObjGrp 2 } 2416 nhdpDiscIfSetPerfEntry OBJECT-TYPE 2417 SYNTAX NhdpDiscIfSetPerfEntry 2418 MAX-ACCESS not-accessible 2419 STATUS current 2420 DESCRIPTION 2421 "There is an entry for each discovered 2422 interface of a neighbor." 2423 REFERENCE 2424 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2425 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2426 C., and J. Dean, April 2011" 2427 INDEX { nhdpDiscIfIndex } 2428 ::= { nhdpDiscIfSetPerfTable 1 } 2430 NhdpDiscIfSetPerfEntry ::= 2431 SEQUENCE { 2432 nhdpDiscIfRecvdPackets 2433 Counter32, 2434 nhdpDiscIfExpectedPackets 2435 Counter32 2436 } 2438 nhdpDiscIfRecvdPackets OBJECT-TYPE 2439 SYNTAX Counter32 2440 UNITS "packets" 2441 MAX-ACCESS read-only 2442 STATUS current 2443 DESCRIPTION 2444 "This counter increments each 2445 time this router receives a packet from that interface 2446 of the neighbor." 2447 REFERENCE 2448 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2449 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2450 C., and J. Dean, April 2011" 2451 ::= { nhdpDiscIfSetPerfEntry 1 } 2453 nhdpDiscIfExpectedPackets OBJECT-TYPE 2454 SYNTAX Counter32 2455 UNITS "packets" 2456 MAX-ACCESS read-only 2457 STATUS current 2458 DESCRIPTION 2459 "This counter increments by the number 2460 of missed packets from this neighbor based 2461 on the packet sequence number each time this 2462 router receives a packet from that interface 2463 of the neighbor." 2465 REFERENCE 2466 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2467 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2468 C., and J. Dean, April 2011" 2469 ::= { nhdpDiscIfSetPerfEntry 2 } 2471 -- 2472 -- Objects concerning the Neighbor Set 2473 -- 2474 nhdpNibNeighborSetChanges OBJECT-TYPE 2475 SYNTAX Counter32 2476 UNITS "changes" 2477 MAX-ACCESS read-only 2478 STATUS current 2479 DESCRIPTION 2480 "This counter increments each time the Neighbor Set changes. 2481 A change occurs whenever a new Neighbor Tuple has been 2482 added, a Neighbor Tuple has been removed, or any entry of 2483 a Neighbor Tuple has been modified." 2484 ::= { nhdpPerformanceObjGrp 3 } 2486 -- 2487 -- Objects per discovered neighbor 2488 -- 2489 nhdpDiscNeighborSetPerfTable OBJECT-TYPE 2490 SYNTAX SEQUENCE OF NhdpDiscNeighborSetPerfEntry 2491 MAX-ACCESS not-accessible 2492 STATUS current 2493 DESCRIPTION 2494 "A router's set of discovered neighbors and 2495 their properties." 2496 REFERENCE 2497 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2498 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2499 C., and J. Dean, April 2011" 2500 ::= { nhdpPerformanceObjGrp 4 } 2502 nhdpDiscNeighborSetPerfEntry OBJECT-TYPE 2503 SYNTAX NhdpDiscNeighborSetPerfEntry 2504 MAX-ACCESS not-accessible 2505 STATUS current 2506 DESCRIPTION 2507 "The entries include the nhdpDiscRouterIndex of 2508 the discovered router as well as performance 2509 objects related to changes of the Neighbor 2510 Set." 2511 REFERENCE 2512 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2513 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2514 C., and J. Dean, April 2011" 2515 INDEX { nhdpDiscRouterIndex } 2516 ::= { nhdpDiscNeighborSetPerfTable 1 } 2518 NhdpDiscNeighborSetPerfEntry ::= 2519 SEQUENCE { 2520 nhdpDiscNeighborNibNeighborSetChanges 2521 Counter32, 2522 nhdpDiscNeighborNibNeighborSetUpTime 2523 TimeStamp, 2524 nhdpDiscNeighborNibNeighborSetReachableLinkChanges 2525 Counter32 2526 } 2528 nhdpDiscNeighborNibNeighborSetChanges OBJECT-TYPE 2529 SYNTAX Counter32 2530 UNITS "changes" 2531 MAX-ACCESS read-only 2532 STATUS current 2533 DESCRIPTION 2534 "This object returns the number of changes 2535 to the given Neighbor Tuple." 2536 REFERENCE 2537 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2538 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2539 C., and J. Dean, April 2011" 2540 ::= { nhdpDiscNeighborSetPerfEntry 1 } 2542 nhdpDiscNeighborNibNeighborSetUpTime OBJECT-TYPE 2543 SYNTAX TimeStamp 2544 MAX-ACCESS read-only 2545 STATUS current 2546 DESCRIPTION 2547 "This object returns the sysUpTime when 2548 the neighbor becomes 'nbrup'. A neighbor is 2549 said to become 'nbrup' if a new nhdpNibNeighborSetEntry 2550 is created for a particular nhdpNibNeighborSetRouterIndex. 2551 It becomes 'nbrdown' if the entry for that neighbor 2552 has been deleted." 2553 REFERENCE 2554 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2555 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2556 C., and J. Dean, April 2011" 2557 ::= { nhdpDiscNeighborSetPerfEntry 2 } 2559 nhdpDiscNeighborNibNeighborSetReachableLinkChanges OBJECT-TYPE 2560 SYNTAX Counter32 2561 UNITS "changes" 2562 MAX-ACCESS read-only 2563 STATUS current 2564 DESCRIPTION 2565 "This object counts each time the neighbor changes 2566 the interface(s) over which it is reachable. 2567 A change in the set of Link Tuples corresponding 2568 to the appropriate Neighbor Tuple is registered, 2569 i.e., a corresponding Link Tuple is added or removed 2570 from the set of all corresponding Link Tuples." 2571 REFERENCE 2572 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2573 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2574 C., and J. Dean, April 2011" 2575 ::= { nhdpDiscNeighborSetPerfEntry 3 } 2577 -- 2578 -- Objects per discovered 2-hop neighbor 2579 -- 2580 nhdpIib2HopSetPerfTable OBJECT-TYPE 2581 SYNTAX SEQUENCE OF NhdpIib2HopSetPerfEntry 2582 MAX-ACCESS not-accessible 2583 STATUS current 2584 DESCRIPTION 2585 "This table contains performance objects per 2586 discovered 2-hop neighbor." 2587 REFERENCE 2588 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2589 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2590 C., and J. Dean, April 2011" 2591 ::= { nhdpPerformanceObjGrp 5 } 2593 nhdpIib2HopSetPerfEntry OBJECT-TYPE 2594 SYNTAX NhdpIib2HopSetPerfEntry 2595 MAX-ACCESS not-accessible 2596 STATUS current 2597 DESCRIPTION 2598 "The entries contain performance objects per 2599 discovered 2-hop neighbor." 2600 REFERENCE 2601 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2602 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2603 C., and J. Dean, April 2011" 2604 INDEX { nhdpDiscRouterIndex } 2605 ::= { nhdpIib2HopSetPerfTable 1 } 2607 NhdpIib2HopSetPerfEntry ::= 2608 SEQUENCE { 2609 nhdpIib2HopSetPerfChanges 2610 Counter32, 2611 nhdpIib2HopSetPerfUpTime 2612 TimeStamp 2613 } 2615 nhdpIib2HopSetPerfChanges OBJECT-TYPE 2616 SYNTAX Counter32 2617 UNITS "changes" 2618 MAX-ACCESS read-only 2619 STATUS current 2620 DESCRIPTION 2621 "This object counts the changes of the union of all 2622 N2_neighbor_iface_addr_list of 2-Hop Tuples with an 2623 N2_2hop_addr equal to one of the given 2-hop 2624 neighbor's addresses." 2625 REFERENCE 2626 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2627 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2628 C., and J. Dean, April 2011" 2629 ::= { nhdpIib2HopSetPerfEntry 1 } 2631 nhdpIib2HopSetPerfUpTime OBJECT-TYPE 2632 SYNTAX TimeStamp 2633 MAX-ACCESS read-only 2634 STATUS current 2635 DESCRIPTION 2636 "This object returns the sysUpTime 2637 when the 2-Hop Tuple 2638 corresponding to the given 2-hop neighbor IP address 2639 was registered in the nhdpIib2HopSetTable." 2640 REFERENCE 2641 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2642 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2643 C., and J. Dean, April 2011" 2644 ::= { nhdpIib2HopSetPerfEntry 2 } 2646 -- 2647 -- nhdpNotifications 2648 -- 2650 nhdpNotificationsObjects OBJECT IDENTIFIER ::= { nhdpNotifications 0 } 2651 nhdpNotificationsControl OBJECT IDENTIFIER ::= { nhdpNotifications 1 } 2652 nhdpNotificationsStates OBJECT IDENTIFIER ::= { nhdpNotifications 2 } 2654 -- nhdpNotificationsObjects 2656 nhdpNbrStateChange NOTIFICATION-TYPE 2657 OBJECTS { nhdpIfName, -- The originator of 2658 -- the notification. 2659 nhdpNbrState -- The new state 2660 } 2661 STATUS current 2662 DESCRIPTION 2663 "nhdpNbrStateChange is a notification sent when 2664 more than nhdpNbrStateChangeThreshold neighbors change 2665 their status (i.e., 'down(0)', 'asymmetric(1)', or 2666 'symmetric(2)') within a time window of 2667 nhdpNbrStateChangeWindow." 2668 ::= { nhdpNotificationsObjects 1 } 2670 nhdp2HopNbrStateChange NOTIFICATION-TYPE 2671 OBJECTS { nhdpIfName, -- The originator 2672 -- of the notification 2673 nhdp2HopNbrState -- The new state 2674 } 2675 STATUS current 2676 DESCRIPTION 2677 "nhdp2HopNbrStateChange is a notification sent 2678 when more than nhdp2HopNbrStateChangeThreshold 2-hop 2679 neighbors change their nhdp2HopNbrState from either: 2680 - 'down(0)' to 'up(1)', or 2681 - 'up(1)' to 'down(0)', or 2682 - 'notconsidered(2)' to 'down(0)', or 2683 - 'down(0)' to 'notconsidered(2)' 2684 within a time window of 2685 nhdp2HopNbrStateChangeWindow." 2686 ::= { nhdpNotificationsObjects 2 } 2688 nhdpIfStateChange NOTIFICATION-TYPE 2689 OBJECTS { nhdpIfName, -- The local interface 2690 nhdpIfStatus -- The new status 2691 } 2692 STATUS current 2693 DESCRIPTION 2694 "nhdpIfStateChange is a notification sent when 2695 nhdpIfStatus has changed on this interface." 2696 ::= { nhdpNotificationsObjects 3 } 2698 -- nhdpNotificationsControl 2700 nhdpNbrStateChangeThreshold OBJECT-TYPE 2701 SYNTAX Integer32 (0..255) 2702 UNITS "changes" 2703 MAX-ACCESS read-write 2704 STATUS current 2705 DESCRIPTION 2706 "A threshold value for the 2707 nhdpNbrStateChange object. If the 2708 number of occurrences exceeds this threshold 2709 within the previous nhdpNbrStateChangeWindow, 2710 then the nhdpNbrStateChange notification 2711 is to be sent. 2713 It is recommended that the value of this 2714 threshold be set to at least 10 and higher 2715 in dense topologies with frequent expected 2716 topology changes." 2717 DEFVAL { 10 } 2718 ::= { nhdpNotificationsControl 1 } 2720 nhdpNbrStateChangeWindow OBJECT-TYPE 2721 SYNTAX TimeTicks 2722 MAX-ACCESS read-write 2723 STATUS current 2724 DESCRIPTION 2725 "A time window for the 2726 nhdpNbrStateChange object. If the 2727 number of occurrences exceeds the 2728 nhdpNbrStateChangeThreshold 2729 within the previous nhdpNbrStateChangeWindow, 2730 then the nhdpNbrStateChange notification 2731 is to be sent. 2733 It is recommended that the value for this 2734 window be set to at least 5 times the 2735 nhdpHelloInterval. 2737 This object represents the time in hundredths 2738 of a second." 2739 DEFVAL { 1000 } 2741 ::= { nhdpNotificationsControl 2 } 2743 nhdp2HopNbrStateChangeThreshold OBJECT-TYPE 2744 SYNTAX Integer32 (0..255) 2745 UNITS "changes" 2746 MAX-ACCESS read-write 2747 STATUS current 2748 DESCRIPTION 2749 "A threshold value for the 2750 nhdp2HopNbrStateChange object. If the 2751 number of occurrences exceeds this threshold 2752 within the previous nhdp2HopNbrStateChangeWindow, 2753 then the nhdp2HopNbrStateChange notification 2754 is to be sent. 2756 It is recommended that the value of this 2757 threshold be set to at least 10 and higher 2758 when topologies are expected to be highly dynamic." 2759 DEFVAL { 10 } 2760 ::= { nhdpNotificationsControl 3 } 2762 nhdp2HopNbrStateChangeWindow OBJECT-TYPE 2763 SYNTAX TimeTicks 2764 MAX-ACCESS read-write 2765 STATUS current 2766 DESCRIPTION 2767 "A time window for the 2768 nhdp2HopNbrStateChange object. If the 2769 number of occurrences exceeds the 2770 nhdp2HopNbrStateChangeThreshold 2771 within the previous nhdp2HopNbrStateChangeWindow, 2772 then the nhdp2HopNbrStateChange notification 2773 is to be sent. 2775 It is recommended that the value for this 2776 window be set to at least 5 times 2777 nhdpHelloInterval. 2779 This object represents the time in hundredths 2780 of a second." 2781 DEFVAL { 1000 } 2782 ::= { nhdpNotificationsControl 4 } 2784 -- nhdpNotificationStates 2786 nhdpNbrState OBJECT-TYPE 2787 SYNTAX INTEGER { 2788 down(0), 2789 asymmetric(1), 2790 symmetric(2) 2791 } 2792 MAX-ACCESS read-only 2793 STATUS current 2794 DESCRIPTION 2795 "NHDP neighbor states. In NHDP, it is not 2796 necessary to remove Protocol Tuples from Protocol Sets 2797 at the exact time indicated, only to behave as if the 2798 Protocol Tuples were removed at that time. This case is 2799 indicated here as 'down(0)', all other cases being 2800 indicated as 'asymmetric(1)' or 'symmetric(2)'. If 'down(0)', 2801 the direct neighbor is also added to the 2802 nhdpNibLostNeighborSetTable." 2803 ::= { nhdpNotificationsStates 1 } 2805 nhdp2HopNbrState OBJECT-TYPE 2806 SYNTAX INTEGER { 2807 down(0), 2808 up(1), 2809 notconsidered(2) 2810 } 2811 MAX-ACCESS read-only 2812 STATUS current 2813 DESCRIPTION 2814 "NHDP 2-hop neighbor states. In NHDP, it is not necessary 2815 to remove Protocol Tuples from Protocol Sets at the 2816 exact time indicated, only to behave as if the Protocol 2817 Tuples were removed at that time. This case is indicated 2818 here as 'down(0)'; otherwise, it is either 'up(1)', if 2819 N2_lost for the 2-Hop Tuple is equal to false, or 2820 'notconsidered(2)' otherwise." 2821 ::= { nhdpNotificationsStates 2 } 2823 -- 2824 -- nhdpConformance information 2825 -- 2827 nhdpCompliances OBJECT IDENTIFIER ::= { nhdpConformance 1 } 2828 nhdpMIBGroups OBJECT IDENTIFIER ::= { nhdpConformance 2 } 2830 -- Compliance Statements 2831 nhdpBasicCompliance MODULE-COMPLIANCE 2832 STATUS current 2833 DESCRIPTION 2834 "The basic implementation requirements for 2835 managed network entities that implement 2836 NHDP." 2837 MODULE -- this module 2838 MANDATORY-GROUPS { nhdpConfigurationGroup } 2839 ::= { nhdpCompliances 1 } 2841 nhdpFullCompliance MODULE-COMPLIANCE 2842 STATUS current 2843 DESCRIPTION 2844 "The full implementation requirements for 2845 managed network entities that implement 2846 NHDP." 2847 MODULE -- this module 2848 MANDATORY-GROUPS { nhdpConfigurationGroup, 2849 nhdpStateGroup, 2850 nhdpNotificationObjectGroup, 2851 nhdpNotificationGroup, 2852 nhdpPerformanceGroup 2853 } 2854 ::= { nhdpCompliances 2 } 2856 -- 2857 -- Units of Conformance 2858 -- 2860 nhdpConfigurationGroup OBJECT-GROUP 2861 OBJECTS { 2862 nhdpIfName, 2863 nhdpIfStatus, 2864 nhdpHelloInterval, 2865 nhdpHelloMinInterval, 2866 nhdpRefreshInterval, 2867 nhdpLHoldTime, 2868 nhdpHHoldTime, 2869 nhdpHystAcceptQuality, 2870 nhdpHystRejectQuality, 2871 nhdpInitialQuality, 2872 nhdpInitialPending, 2873 nhdpHpMaxJitter, 2874 nhdpHtMaxJitter, 2875 nhdpNHoldTime, 2876 nhdpIHoldTime, 2877 nhdpIfRowStatus, 2878 nhdpLibLocalIfSetIfIndex, 2879 nhdpLibLocalIfSetIpAddrType, 2880 nhdpLibLocalIfSetIpAddr, 2881 nhdpLibLocalIfSetIpAddrPrefixLen, 2882 nhdpLibLocalIfSetRowStatus, 2883 nhdpLibRemovedIfAddrSetIpAddrType, 2884 nhdpLibRemovedIfAddrSetIpAddr, 2885 nhdpLibRemovedIfAddrSetIpAddrPrefixLen, 2886 nhdpLibRemovedIfAddrSetIfIndex, 2887 nhdpLibRemovedIfAddrSetIRTime 2888 } 2889 STATUS current 2890 DESCRIPTION 2891 "Set of NHDP configuration objects implemented 2892 in this module." 2893 ::= { nhdpMIBGroups 2 } 2895 nhdpStateGroup OBJECT-GROUP 2896 OBJECTS { 2897 nhdpUpTime, 2898 nhdpIfStateUpTime, 2899 nhdpDiscRouterIndex, 2900 nhdpDiscIfIndex, 2901 nhdpDiscIfSetIpAddrType, 2902 nhdpDiscIfSetIpAddr, 2903 nhdpDiscIfSetIpAddrPrefixLen, 2904 nhdpIibLinkSetLHeardTime, 2905 nhdpIibLinkSetLSymTime, 2906 nhdpIibLinkSetLPending, 2907 nhdpIibLinkSetLLost, 2908 nhdpIibLinkSetLTime, 2909 nhdpIib2HopSetIpAddrPrefixLen, 2910 nhdpIib2HopSet1HopIfIndex, 2911 nhdpIib2HopSetN2Time, 2912 nhdpNibNeighborSetNSymmetric, 2913 nhdpNibLostNeighborSetNLTime 2914 } 2915 STATUS current 2916 DESCRIPTION 2917 "Set of NHDP state objects implemented 2918 in this module." 2919 ::= { nhdpMIBGroups 3 } 2921 nhdpPerformanceGroup OBJECT-GROUP 2922 OBJECTS { 2923 nhdpIfHelloMessageXmits, 2924 nhdpIfHelloMessageRecvd, 2925 nhdpIfHelloMessageXmitAccumulatedSize, 2926 nhdpIfHelloMessageRecvdAccumulatedSize, 2927 nhdpIfHelloMessageTriggeredXmits, 2928 nhdpIfHelloMessagePeriodicXmits, 2929 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount, 2930 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount, 2931 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount, 2932 nhdpDiscIfRecvdPackets, 2933 nhdpDiscIfExpectedPackets, 2934 nhdpNibNeighborSetChanges, 2935 nhdpDiscNeighborNibNeighborSetChanges, 2936 nhdpDiscNeighborNibNeighborSetUpTime, 2937 nhdpDiscNeighborNibNeighborSetReachableLinkChanges, 2938 nhdpIib2HopSetPerfChanges, 2939 nhdpIib2HopSetPerfUpTime 2940 } 2941 STATUS current 2942 DESCRIPTION 2943 "Set of NHDP performance objects implemented 2944 in this module." 2945 ::= { nhdpMIBGroups 4 } 2947 nhdpNotificationObjectGroup OBJECT-GROUP 2948 OBJECTS { 2949 nhdpNbrStateChangeThreshold, 2950 nhdpNbrStateChangeWindow, 2951 nhdp2HopNbrStateChangeThreshold, 2952 nhdp2HopNbrStateChangeWindow, 2953 nhdpNbrState, 2954 nhdp2HopNbrState 2955 } 2956 STATUS current 2957 DESCRIPTION 2958 "Set of NHDP notification objects implemented 2959 in this module." 2960 ::= { nhdpMIBGroups 5 } 2962 nhdpNotificationGroup NOTIFICATION-GROUP 2963 NOTIFICATIONS { 2964 nhdpNbrStateChange, 2965 nhdp2HopNbrStateChange, 2966 nhdpIfStateChange 2967 } 2968 STATUS current 2969 DESCRIPTION 2970 "Set of NHDP notifications implemented 2971 in this module." 2972 ::= { nhdpMIBGroups 6 } 2974 END 2976 8. Security Considerations 2978 This MIB module defines objects for the configuration, monitoring, 2979 and notification of the Neighborhood Discovery Protocol [RFC6130]. 2980 NHDP allows routers to acquire topological information up to two hops 2981 away by virtue of exchanging HELLO messages. The information 2982 acquired by NHDP may be used by routing protocols. The neighborhood 2983 information, exchanged between routers using NHDP, serves these 2984 routing protocols as a baseline for calculating paths to all 2985 destinations in the MANET, relay set selection for network-wide 2986 transmissions, etc. 2988 There are a number of management objects defined in this MIB module 2989 with a MAX-ACCESS clause of read-write and/or read-create. Such 2990 objects may be considered sensitive or vulnerable in some network 2991 environments. The support for SET operations in a non-secure 2992 environment without proper protection can have a negative effect on 2993 network operations. These are the tables and objects and their 2994 sensitivity/vulnerability: 2996 o nhdpIfStatus - This writable object turns on or off the NHDP 2997 process for the specified interface. If disabled, higher-level 2998 protocol functions, e.g., routing, would fail, causing network- 2999 wide disruptions. 3001 o nhdpHelloInterval, nhdpHelloMinInterval, and nhdpRefreshInterval - 3002 These writable objects control the rate at which HELLO messages 3003 are sent on an interface. If set at too high a rate, this could 3004 represent a form of denial-of-service (DoS) attack by overloading 3005 interface resources. 3007 o nhdpHystAcceptQuality, nhdpHystRejectQuality, nhdpInitialQuality, 3008 and nhdpInitialPending - These writable objects affect the 3009 perceived quality of the NHDP links and hence the overall 3010 stability of the network. If improperly set, these settings could 3011 result in network-wide disruptions. 3013 o nhdpInterfaceTable - This table contains writable objects that 3014 affect the overall performance and stability of the NHDP process. 3015 Failure of the NHDP process would result in network-wide failure. 3016 Particularly sensitive objects from this table are discussed in 3017 the previous list items. This is the only table in the NHDP-MIB 3018 module with writable objects. 3020 Some of the readable objects in this MIB module (i.e., objects with a 3021 MAX-ACCESS other than not-accessible) may be considered sensitive or 3022 vulnerable in some network environments. It is thus important to 3023 control even GET and/or NOTIFY access to these objects and possibly 3024 to even encrypt the values of these objects when sending them over 3025 the network via SNMP. These are the tables and objects and their 3026 sensitivity/vulnerability: 3028 o nhdpDiscIfSetTable - The object contains information on discovered 3029 neighbors, specifically their IP address in the 3030 nhdpDiscIfSetIpAddr object. This information provides an 3031 adversary broad information on the members of the MANET, located 3032 within this single table. This information can be used to 3033 expedite attacks on the other members of the MANET without having 3034 to go through a laborious discovery process on their own. This 3035 object is the index into the table and has a MAX-ACCESS of 'not- 3036 accessible'. However, this information can be exposed using SNMP 3037 operations. 3039 MANET technology is often deployed to support communications of 3040 emergency services or military tactical applications. In these 3041 applications, it is imperative to maintain the proper operation of 3042 the communications network and to protect sensitive information 3043 related to its operation. Therefore, it is RECOMMENDED to provide 3044 support for the Transport Security Model (TSM) [RFC5591] in 3045 combination with TLS/DTLS [RFC6353]. 3047 SNMP versions prior to SNMPv3 did not include adequate security. 3048 Even if the network itself is secure (for example by using IPsec), 3049 there is no control as to who on the secure network is allowed to 3050 access and GET/SET (read/change/create/delete) the objects in this 3051 MIB module. 3053 Implementations MUST provide the security features described by the 3054 SNMPv3 framework (see [RFC3410]), including full support for 3055 authentication and privacy via the User-based Security Model (USM) 3056 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 3057 MAY also provide support for the Transport Security Model (TSM) 3058 [RFC5591] in combination with a secure transport such as SSH 3059 [RFC5592] or TLS/DTLS [RFC6353]. 3061 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3062 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3063 enable cryptographic security. It is then a customer/operator 3064 responsibility to ensure that the SNMP entity giving access to an 3065 instance of this MIB module is properly configured to give access to 3066 the objects only to those principals (users) that have legitimate 3067 rights to indeed GET or SET (change/create/delete) them. 3069 9. Applicability Statement 3071 This document describes objects for configuring parameters of the 3072 Neighborhood Discovery Protocol [RFC6130] process on a router. This 3073 MIB module, denoted NHDP-MIB, also reports state, performance 3074 information, and notifications. This section provides some examples 3075 of how this MIB module can be used in MANET network deployments. A 3076 fuller discussion of MANET network management use cases and 3077 challenges will be provided elsewhere. 3079 NHDP is designed to allow routers to automatically discover and track 3080 routers one hop remote (denoted "neighbors") and routers two hops 3081 remote (denoted "two-hop neighbors"). This information is used by 3082 other MANET protocols in operation on the router to perform routing, 3083 multicast forwarding, and other functions with ad hoc and mobile 3084 networks. In the following, three example scenarios are listed where 3085 this MIB module is useful: 3087 o For a Parking Lot Initial Configuration Situation - It is common 3088 for the vehicles comprising the MANET being forward deployed at a 3089 remote location, e.g., the site of a natural disaster, to be off- 3090 loaded in a parking lot where an initial configuration of the 3091 networking devices is performed. The configuration is loaded into 3092 the devices from a fixed location Network Operation Center (NOC) 3093 at the parking lot, and the vehicles are stationary at the parking 3094 lot while the configuration changes are made. Standards-based 3095 methods for configuration management from the co-located NOC are 3096 necessary for this deployment option. 3098 o For Mobile Vehicles with Low-Bandwidth Satellite Link to a Fixed 3099 NOC - Here, the vehicles carrying the MANET routers carry multiple 3100 wireless interfaces, one of which is a relatively low-bandwidth, 3101 on-the-move satellite connection that interconnects a fix NOC to 3102 the nodes of the MANET. Standards-based methods for monitoring 3103 and fault management from the fixed NOC are necessary for this 3104 deployment option. 3106 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 3107 larger vehicles, a hierarchical network management arrangement is 3108 useful. Centralized network management is performed from a fixed 3109 NOC while local management is performed locally from within the 3110 vehicles. Standards-based methods for configuration, monitoring, 3111 and fault management are necessary for this deployment option. 3113 10. IANA Considerations 3115 The MIB module in this document uses the following IANA-assigned 3116 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 3118 Descriptor OBJECT IDENTIFIER value 3119 ---------- ----------------------- 3120 NHDP-MIB { mib-2 213 } 3122 11. Acknowledgements 3124 The authors wish to thank Benoit Claise, Justin Dean, Adrian Farrel, 3125 Joel Halpern, Al Morton, and Thomas Nadeau for their detailed reviews 3126 and insightful comments regarding RFC6779 and this document. 3128 This MIB document uses the template authored by D. Harrington, which 3129 is based on contributions from the MIB Doctors, especially Juergen 3130 Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn. 3132 12. References 3134 12.1. Normative References 3136 [RFC2119] Bradner, S., "Key words for use 3137 in RFCs to Indicate Requirement 3138 Levels", BCP 14, RFC 2119, 3139 March 1997. 3141 [RFC2578] McCloghrie, K., Ed., Perkins, 3142 D., Ed., and J. Schoenwaelder, 3143 Ed., "Structure of Management 3144 Information Version 2 (SMIv2)", 3145 STD 58, RFC 2578, April 1999. 3147 [RFC2579] McCloghrie, K., Ed., Perkins, 3148 D., Ed., and J. Schoenwaelder, 3149 Ed., "Textual Conventions for 3150 SMIv2", STD 58, RFC 2579, 3151 April 1999. 3153 [RFC2580] McCloghrie, K., Perkins, D., 3154 and J. Schoenwaelder, 3155 "Conformance Statements for 3156 SMIv2", STD 58, RFC 2580, 3157 April 1999. 3159 [RFC2863] McCloghrie, K. and F. 3160 Kastenholz, "The Interfaces 3161 Group MIB", RFC 2863, 3162 June 2000. 3164 [RFC3418] Presuhn, R., "Management 3165 Information Base (MIB) for the 3166 Simple Network Management 3167 Protocol (SNMP)", STD 62, 3168 RFC 3418, December 2002. 3170 [RFC4001] Daniele, M., Haberman, B., 3171 Routhier, S., and J. 3172 Schoenwaelder, "Textual 3173 Conventions for Internet 3174 Network Addresses", RFC 4001, 3175 February 2005. 3177 [RFC6130] Clausen, T., Dearlove, C., and 3178 J. Dean, "Mobile Ad Hoc Network 3179 (MANET) Neighborhood Discovery 3180 Protocol (NHDP)", RFC 6130, 3181 April 2011. 3183 [RFC6340] Presuhn, R., "Textual 3184 Conventions for the 3185 Representation of Floating- 3186 Point Numbers", RFC 6340, 3187 August 2011. 3189 [draft-ietf-manet-nhdp-optimization] Dearlove, C. and T. Clausen, 3190 "An Optimization for the MANET 3191 Neighborhood Discovery Protocol 3192 (NHDP)", work in progress draft 3193 -ietf-manet-nhdp-optimization- 3194 00, July 2014. 3196 12.2. Informative References 3198 [RFC3410] Case, J., Mundy, R., Partain, 3199 D., and B. Stewart, 3200 "Introduction and Applicability 3201 Statements for Internet- 3202 Standard Management Framework", 3203 RFC 3410, December 2002. 3205 [RFC3414] Blumenthal, U. and B. Wijnen, 3206 "User-based Security Model 3207 (USM) for version 3 of the 3208 Simple Network Management 3209 Protocol (SNMPv3)", STD 62, 3210 RFC 3414, December 2002. 3212 [RFC3826] Blumenthal, U., Maino, F., and 3213 K. McCloghrie, "The Advanced 3214 Encryption Standard (AES) 3215 Cipher Algorithm in the SNMP 3216 User-based Security Model", 3217 RFC 3826, June 2004. 3219 [RFC4750] Joyal, D., Galecki, P., 3220 Giacalone, S., Coltun, R., and 3221 F. Baker, "OSPF Version 2 3222 Management Information Base", 3223 RFC 4750, December 2006. 3225 [RFC5148] Clausen, T., Dearlove, C., and 3226 B. Adamson, "Jitter 3227 Considerations in Mobile Ad Hoc 3228 Networks (MANETs)", RFC 5148, 3229 February 2008. 3231 [RFC5591] Harrington, D. and W. Hardaker, 3232 "Transport Security Model for 3233 the Simple Network Management 3234 Protocol (SNMP)", RFC 5591, 3235 June 2009. 3237 [RFC5592] Harrington, D., Salowey, J., 3238 and W. Hardaker, "Secure Shell 3239 Transport Model for the Simple 3240 Network Management Protocol 3241 (SNMP)", RFC 5592, June 2009. 3243 [RFC6353] Hardaker, W., "Transport Layer 3244 Security (TLS) Transport Model 3245 for the Simple Network 3246 Management Protocol (SNMP)", 3247 RFC 6353, July 2011. 3249 [RFC6779] Herberg, U., Cole, R., and I. 3250 Chakeres, "Definition of 3251 Managed Objects for the 3252 Neighborhood Discovery 3253 Protocol", RFC 6779, 3254 October 2012. 3256 Authors' Addresses 3258 Ulrich Herberg 3259 Fujitsu Laboratories of America 3260 1240 E Arques Ave 3261 Sunnyvale 94085 3262 United States 3264 EMail: ulrich@herberg.name 3265 URI: http://www.herberg.name/ 3267 Robert G. Cole 3268 US Army CERDEC 3269 Space and Terrestrial Communications 3270 6010 Frankford Road 3271 Aberdeen Proving Ground, Maryland 21005 3272 United States 3274 Phone: +1 443 395-8744 3275 EMail: robert.g.cole@us.army.mil 3276 URI: http://www.cs.jhu.edu/~rgcole/ 3278 Ian D Chakeres 3279 Delvin 3280 Ellicott City, Maryland 21042 3281 United States 3283 EMail: ian.chakeres@gmail.com 3284 URI: http://www.ianchak.com/ 3286 Thomas Heide Clausen 3287 LIX, Ecole Polytechnique 3289 Phone: +33 6 6058 9349 3290 EMail: T.Clausen@computer.org 3291 URI: http://www.ThomasClausen.org/