idnits 2.17.1 draft-ietf-manet-smf-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1507 has weird spacing: '...s state table...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (December 1, 2012) is 4163 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'SMF' is mentioned on line 986, but not defined Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force R. Cole 3 Internet-Draft US Army CERDEC 4 Intended status: Experimental J. Macker 5 Expires: June 4, 2013 B. Adamson 6 Naval Research Laboratory 7 December 1, 2012 9 Definition of Managed Objects for the Manet Simplified Multicast 10 Framework Relay Set Process 11 draft-ietf-manet-smf-mib-06 13 Abstract 15 This memo defines a portion of the Management Information Base (MIB) 16 for use with network management protocols in the Internet community. 17 In particular, it describes objects for configuring aspects of the 18 Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc 19 Networks (MANETs). The SMF-MIB also reports state information, 20 performance metrics, and notifications. In addition to 21 configuration, the additional state and performance information is 22 useful to operators troubleshooting multicast forwarding problems. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on June 4, 2013. 41 Copyright Notice 43 Copyright (c) 2012 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. The Internet-Standard Management Framework . . . . . . . . . . 3 60 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 63 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 65 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 66 5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6 67 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7 68 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7 69 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7 70 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8 71 5.7. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 72 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 73 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 74 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 75 6.3. Relationship to the Future RSSA-MIBs . . . . . . . . . . . 10 76 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 77 8. Security Considerations . . . . . . . . . . . . . . . . . . . 52 78 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 55 79 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 80 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 57 81 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 57 82 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57 83 13.1. Normative References . . . . . . . . . . . . . . . . . . . 57 84 13.2. Informative References . . . . . . . . . . . . . . . . . . 58 85 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 58 86 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 60 87 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 60 89 1. Introduction 91 This memo defines a portion of the Management Information Base (MIB) 92 for use with network management protocols in the Internet community. 93 In particular, it describes objects for configuring aspects of a 94 process implementing Simplified Multicast Forwarding (SMF) [RFC6621] 95 for Mobile Ad-Hoc Networks (MANETs). SMF provides multicast 96 Duplicate Packet Detection (DPD) and supports algorithms for 97 constructing an estimate of a MANET Minimum Connected Dominating Set 98 (MCDS) for efficient multicast forwarding. The SMF-MIB also reports 99 state information, performance metrics, and notifications. In 100 addition to configuration, this additional state and performance 101 information is useful to operators troubleshooting multicast 102 forwarding problems. 104 2. The Internet-Standard Management Framework 106 For a detailed overview of the documents that describe the current 107 Internet-Standard Management Framework, please refer to section 7 of 108 RFC 3410 [RFC3410]. 110 Managed objects are accessed via a virtual information store, termed 111 the Management Information Base or MIB. MIB objects are generally 112 accessed through the Simple Network Management Protocol (SNMP). 113 Objects in the MIB are defined using the mechanisms defined in the 114 Structure of Management Information (SMI). This memo specifies a MIB 115 module that is compliant to the SMIv2, which is described in STD 58, 116 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 117 [RFC2580]. 119 3. Conventions 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 4. Overview 127 SMF provides methods for implementing DPD-based multicast forwarding 128 with the optional use of Connected Dominating Set (CDS)-based relay 129 sets. The CDS provides a complete connected coverage of the nodes 130 comprising the MANET. The MCDS is the smallest set of MANET nodes 131 (comprising a connected cluster) which cover all the nodes in the 132 cluster with their transmissions. As the density of the MANET nodes 133 increase, the fraction of nodes required in an MCDS decreases. Using 134 the MCDS as a multicast forwarding set then becomes an efficient 135 multicast mechanism for MANETs. 137 Various algorithms for the construction of estimates of the MCDS 138 exist. The Simplified Multicast Framework [RFC6621] describes some 139 of these. It further defines various operational modes for a node 140 which is participating in the collective creation of the MCDS 141 estimates. These modes depend upon the set of related MANET routing 142 and discovery protocols and mechanisms in operation in the specific 143 MANET node. 145 A SMF router's MIB contains SMF process configuration parameters 146 (e.g. specific CDS algorithm), state information (e.g., current 147 membership in the CDS), performance counters (e.g., packet counters), 148 and notifications. 150 4.1. SMF Management Model 152 This section describes the management model for the SMF node process. 154 Figure 1 (reproduced from Figure 4 of [RFC6621]) shows the 155 relationship between the SMF Relay Set selection algorithm and the 156 related algorithms, processes and protocols running in the MANET 157 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 158 topology information gotten from the MANET Neighborhood Discovery 159 Protocol (NHDP), from the specific MANET routing protocol running on 160 the node, or from Layer 2 information passed up to the higher layer 161 protocol processes. 163 ______________ ____________ 164 | | | | 165 | Neighborhood | | Relay Set | 166 | Discovery |------------->| Selection | 167 | Protocol | neighbor | Algorithm | 168 |______________| info |____________| 169 \ / 170 \ / 171 neighbor\ / forwarding 172 info* \ _____________ / status 173 \ | | / 174 `-->| Forwarding |<--' 175 | Process | 176 ----------------->|_____________|-----------------> 177 incoming packet, forwarded packets 178 interface id*, and 179 previous hop* 181 Figure 1: SMF Node Architecture 183 4.2. Terms 185 The following definitions apply throughout this document: 187 o Configuration Objects - switches, tables, objects which are 188 initialized to default settings or set through the management 189 interface defined by this MIB. 191 o Tunable Configuration Objects - objects whose values affect timing 192 or attempt bounds on the SMF RS process. 194 o State Objects - automatically generated values which define the 195 current operating state of the SMF RS process in the router. 197 o Performance Objects - automatically generated values which help an 198 administrator or automated tool to assess the performance of the 199 CDS multicast process on the router and the overall multicast 200 performance within the MANET routing domain. 202 5. Structure of the MIB Module 204 This section presents the structure of the SMF-MIB module. The 205 objects are arranged into the following groups: 207 o smfMIBNotifications - defines the notifications associated with 208 the SMF-MIB. 210 o smfMIBObjects - defines the objects forming the basis for the SMF- 211 MIB. These objects are divided up by function into the following 212 groups: 214 * Capabilities Group - This group contains the SMF objects that 215 the device uses to advertise its local capabilities with 216 respect to, e.g., the supported RSSAs. 218 * Configuration Group - This group contains the SMF objects that 219 configure specific options that determine the overall operation 220 of the SMF RSSA and the resulting multicast performance. 222 * State Group - Contains information describing the current state 223 of the SMF RSSA process such as the Neighbor Table. 225 * Performance Group - Contains objects which help to characterize 226 the performance of the SMF RSSA process, typically statistics 227 counters. 229 o smfMIBConformance - defines minimal and full conformance of 230 implementations to this SMF-MIB. 232 5.1. Textual Conventions 234 The textual conventions defined within the SMF-MIB are as follows: 236 o The SmfStatus is defined within the SMF-MIB. This contains the 237 current operational status of the SMF process on an interface. 239 o The SmfOpModeID represents an index that identifies a specific SMF 240 operational mode. 242 o The SmfRssaID represents an index that identifies, through 243 reference, a specific RSSA available for operation on the device. 245 5.2. The Capabilities Group 247 The SMF device supports a set of capabilities. The list of 248 capabilities which the device can advertise are: 250 o Operational Mode - topology information from NHDP, CDS-aware 251 unicast routing or Cross-layer from Layer 2. 253 o SMF RSSA - the specific RSSA operational on the device. Note that 254 configuration, state and performance objects related to a specific 255 RSSA must be defined within another separate MIB. 257 5.3. The Configuration Group 259 The SMF device is configured with a set of controls. Some of the 260 prominent configuration controls for the SMF device follow: 262 o Operational Mode - topology information from NHDP, CDS-aware 263 unicast routing or Cross-layer from Layer 2. 265 o SMF RSSA - the specific RSSA operational on the device. 267 o Duplicate Packet detection for IPv4 - Identification-based or 268 Hash-based DPD. 270 o Duplicate Packet detection for IPv6 - Identification-based or 271 Hash-based DPD. 273 o SMF Type Message TLV - if NHDP mode is selected, then is the SMF 274 Type Message TLV may be included in the NHDP exchanges. 276 o SMF Address Block TLV - if NHDP mode is selected, then is the SMF 277 Address Block TLV should be included in the NHDP exchanges. 279 5.4. The State Group 281 The State sub-tree reports current state information, e.g., 283 o Node RSSA State - is the node currently in or out of the Relay 284 Set. 286 o Neighbors Table - a table containing current neighbors and their 287 operational RSSA. 289 5.5. The Performance Group 291 The Performance sub-tree reports primarily counters that relate to 292 SMF RSSA performance. The SMF performance counters consists of per 293 node and per interface objects: 295 o Total multicast packets received. 297 o Total multicast packets forwarded. 299 o Total duplicate multicast packets detected. 301 o Per interface statistics table with the following entries: 303 * Multicast packets received. 305 * Multicast packets forwarded. 307 * Duplicate multicast packets detected. 309 5.6. The Notifications Group 311 The Notifications Sub-tree contains the list of notifications 312 supported within the SMF-MIB and their intended purpose or utility. 314 5.7. Tables and Indexing 316 The SMF-MIB module contains a number of tables which record data 317 related to: 319 o configuration and operation of packet forwarding the local router, 321 o configuration and operation of local MANET interfaces on the 322 router, and 324 o configuration and operation of various RSSA algorithms for packet 325 forwarding. 327 The SMF-MIB module's tables are indexed via the following constructs: 329 o smfOpModeCapabilitiesID - which is the index for each of the SMF 330 modes. 332 o smfRssaCapabilitiesID - which is the index for each of the RSSAs 333 supported by this specific device. 335 o smfConfiguredAddrForwardingAddrType and 336 smfConfiguredAddrForwardingFirstAddr - indexes to multicast 337 addresses which are forwarded by the SMF process. 339 o smfIfIndex - which is the IfIndex of the local router on which SMF 340 is configured. 342 o smfDiscoveredAddrForwardingAddrType and 343 smfDiscoveredAddrForwardingFirstAddr - indexes to discovered 344 multicast addresses which are forwarded by the SMF process. 346 o smfNeighborIpAddrType, smfNeighborIpAddr, and smfNeighborPrefixLen 347 - which is the index set of interface specific neighbor nodes to 348 this SMF device. 350 These tables and their indexing are: 352 o smfOpModeCapabilitiesTable - identifies the resident set of SMF 353 Operational Modes on this router. This table has 'INDEX { 354 smfOpModeCapabilitiesID }. 356 o smfRssaCapabilitiesTable - contains reference to the specific set 357 of RSSAs currently supported on this device. This table has 358 'INDEX { smfRssaCapabilitiesID }'. 360 o smfConfiguredAddrForwardingTable - contains information on 361 multicast addresses which are to be forwarded by the SMF process 362 on this device. This table has 'INDEX { 363 smfConfiguredAddrForwardingAddrType, 364 smfConfiguredAddrForwardingFirstAddr }'. 366 o smfInterfaceTable - describes the SMF interfaces on this device 367 that are participating in the SMF packet forwarding process. This 368 table has 'INDEX { smfIfIndex }'. 370 o smfDiscoveredAddrForwardingTable - contains discovered address for 371 SMF packet forwarding. This table has 'INDEX { 372 smfDiscoveredAddrForwardingAddrType, 373 smfDiscoveredAddrForwardingFirstAddr }'. 375 o smfNeighborTable - describes the current neighbor nodes, their 376 addresses and the SMF RSSA and the interface on which they can be 377 reached. This table has 'INDEX { smfNeighborIpAddrType, 378 smfNeighborIpAddr, smfNeighborPrefixLen }'. 380 o smfIpv4InterfaceTable - contains the IPv4 related SMF statistics 381 per each SMF interface on this device. This table has 'INDEX { 382 smfIfIndex }'. 384 o smfIpv6InterfaceTable - contains the IPv6 related SMF statistics 385 per each SMF interface on this device. This table has 'INDEX { 386 smfIfIndex }'. 388 6. Relationship to Other MIB Modules 390 6.1. Relationship to the SNMPv2-MIB 392 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 393 mandatory for all systems, and the objects apply to the entity as a 394 whole. The 'system' group provides identification of the management 395 entity and certain other system-wide data. The SMF-MIB does not 396 duplicate those objects. 398 6.2. MIB modules required for IMPORTS 400 The textual conventions imported for use in the SMF-MIB are as 401 follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 402 Counter32, Unsigned32, Integer32 and mib-2 textual conventions are 403 imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 404 and TruthValue textual conventions are imported from RFC 2579 405 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- 406 GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 407 InterfaceIndexOrZero textual convention is imported from RFC 2863 408 [RFC2863]. The SnmpAdminString textual convention is imported from 409 RFC 3411 [RFC3411]. The InetAddress, InetAddressType and 410 InetAddressPrefixLength textual conventions are imported from RFC 411 4001 [RFC4001]. 413 6.3. Relationship to the Future RSSA-MIBs 415 In a sense, the SMF-MIB is a general front-end to a set of, yet to be 416 developed, RSSA-specific MIBs. These RSSA-specific MIBs will define 417 the objects for the configuration, state, performance and 418 notification objects required for the operation of these specific 419 RSSAs. The SMF-MIB Capabilities Group allows the remote management 420 station the ability to query the router to discover the set of 421 supported RSSAs. 423 7. Definitions 425 SMF-MIB DEFINITIONS ::= BEGIN 427 IMPORTS 429 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 430 Counter32, Integer32, TimeTicks, experimental 431 FROM SNMPv2-SMI -- [RFC2578] 433 TEXTUAL-CONVENTION, RowStatus, TruthValue, 434 DisplayString 435 FROM SNMPv2-TC -- [RFC2579] 437 MODULE-COMPLIANCE, OBJECT-GROUP, 438 NOTIFICATION-GROUP 439 FROM SNMPv2-CONF -- [RFC2580] 441 InterfaceIndexOrZero 442 FROM IF-MIB -- [RFC2863] 444 SnmpAdminString 445 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 447 InetAddress, InetAddressType, 448 InetAddressPrefixLength 449 FROM INET-ADDRESS-MIB -- [RFC4001] 450 ; 452 smfMIB MODULE-IDENTITY 453 LAST-UPDATED "201212011300Z" -- December 01, 2012 454 ORGANIZATION "IETF MANET Working Group" 455 CONTACT-INFO 456 "WG E-Mail: manet@ietf.org 458 WG Chairs: sratliff@cisco.com 459 jmacker@nrl.navy.mil 461 Editors: Robert G. Cole 462 US Army CERDEC 463 Space and Terrestrial Communications 464 6010 Frankford Road 465 Aberdeen Proving Ground, MD 21005 466 USA 467 +1 443 395-8744 468 robert.g.cole@us.army.mil 469 http://www.cs.jhu.edu/~rgcole/ 471 Joseph Macker 472 Naval Research Laboratory 473 Washington, D.C. 20375 474 USA 475 macker@itd.nrl.navy.mil 477 Brian Adamson 478 Naval Research Laboratory 479 Washington, D.C. 20375 480 USA 481 adamson@itd.nrl.navy.mil 482 " 484 DESCRIPTION 485 "This MIB module contains managed object definitions for 486 the Manet SMF RSSA process defined in: 488 [SMF] Macker, J.(ed.), 489 Simplified Multicast Forwarding, RFC XXXX, 490 July 2012. 492 Copyright (C) The IETF Trust (2008). This version 493 of this MIB module is part of RFC xxxx; see the RFC 494 itself for full legal notices." 496 -- Revision History 497 REVISION "201212011300Z" -- December 01, 2012 498 DESCRIPTION 499 "Updated 9th revision of the 500 draft of this MIB module published as 501 draft-ietf-manet-smf-mib-06.txt. The changes 502 made in this revision to the SMF-MIB include: 503 - None. Only changes to the surrounding 504 textual material associated with this 505 MIB module." 506 REVISION "201211051300Z" -- November 05, 2012 507 DESCRIPTION 508 "Updated 8th revision of the 509 draft of this MIB module published as 510 draft-ietf-manet-smf-mib-05.txt. The changes 511 made in this revision include: 512 - Updated the smfInterfaceTable to reflect a 513 sparse augmentation of the ifTable. 514 - Added text discussing the tables and their 515 indexing. 516 - Added Applicability Statement. 517 - Checked/updated DEFVAL, REFERENCES, 518 UNITS and SIZE cluases in the MIB." 519 REVISION "201205281300Z" -- May 28, 2012 520 DESCRIPTION 521 "Updated 7th revision of the 522 draft of this MIB module published as 523 draft-ietf-manet-smf-mib-04.txt. The changes 524 made in this revision include: 525 - Removed the bitmap switch in the notifications 526 control group. 527 - Moved the notification Objects group up 528 to support reverse-mapping between SNMPv1 529 traps and SNMPv2 nootifications. 530 - Removed reference to the notifications 531 state group. 532 - Replaced smfIfIndex with smfIfName in 533 notifications. 534 " 535 REVISION "201110021300Z" -- October 02, 2011 536 DESCRIPTION 537 "Updated 6th revision of the 538 draft of this MIB module published as 539 draft-ietf-manet-smf-mib-03.txt. The changes 540 made in this revision include: 541 - Added some notes to the MIB module 542 - Clarified and defined default settings 543 " 544 REVISION "201101161300Z" -- January 16, 2011 545 DESCRIPTION 546 "Updated 5th revision of the 547 draft of this MIB module published as 548 draft-ietf-manet-smf-mib-02.txt. The changes 549 made in this revision include: 550 - Added the Notification Group and cleaned 551 up the Conformance section 552 - Completed the TEXTUAL CONVENTION for the 553 smfOpMode. 554 - Completed the Description clauses of 555 several objects within the MIB. 556 - Removed the routerPriority object. 557 - Added the definition of a smfRouterID 558 object and associated smfRouterIDAddrType 559 object. 560 " 561 REVISION "200910261300Z" -- October 26, 2009 562 DESCRIPTION 563 "Updated draft of this MIB module published as 564 draft-ietf-manet-smf-mib-01.txt. A few changes 565 were made in the development of this draft. 566 Specifically, the following changes were made: 567 - Updated the textual material, included 568 section on IMPORTS, relationship to other 569 MIBs, etc. 570 " 571 REVISION "200904211300Z" -- April 21, 2009 572 DESCRIPTION 573 "Updated draft of this MIB module published as 574 draft-ietf-manet-smf-mib-00.txt. A few changes 575 were made in the development of this draft. 576 Specifically, the following changes were made: 577 - Removed the smfGatewayFilterTable from this 578 draft. It is a useful construct, e.g., 579 an IPTABLES-MIB, but might best be handled 580 as a seperate MIB and worked within a 581 security focused working group. 582 - Removed the smfReportsGroup. This capability 583 is being replaced with a new and more general 584 method for offline reporting. This is being 585 worked as a new MIB module refered to as the 586 REPORT-MIB. 587 - Rev'd as a new MANET WG document. 589 " 590 REVISION "200902271300Z" -- February 27, 2009 591 DESCRIPTION 592 "Updated draft of this MIB module published as 593 draft-cole-manet-smf-mib-02.txt. Fairly extensive 594 revisions and additions to this MIB were made 595 in this version. Specifically, the following 596 changes were made in development of this version: 597 - added a Capabilities Group within the Objects 598 Group to allow the device to report supported 599 capabilities, e.g., RSSAs supported. 600 - added administrative status objects for device 601 and interfaces 602 - added multicast address forwarding tables, both 603 for configured (within Configuration Group) and 604 discovered (within the State Group). 605 - added additional Performance counters related 606 to DPD functions. 607 - Split up the performance counters into IPv4 608 and IPv6, for both global and per interface 609 statistics. 610 - Split out the reports capability into a seperate 611 Reports Group under the Objects Group. 612 " 613 REVISION "200811031300Z" -- November 03, 2008 614 DESCRIPTION 615 "Updated draft of this MIB module published as 616 draft-cole-manet-smf-mib-01.txt. Added gateway filter 617 table and reports capabilities following rmon." 618 REVISION "200807071200Z" -- July 07, 2008 619 DESCRIPTION 620 "Initial draft of this MIB module published as 621 draft-cole-manet-smf-mib-00.txt." 622 -- RFC-Editor assigns XXXX 623 ::= { experimental 998 } -- to be assigned by IANA 625 -- 626 -- TEXTUAL CONVENTIONs 627 -- 629 SmfStatus ::= TEXTUAL-CONVENTION 630 STATUS current 631 DESCRIPTION 632 "An indication of the operability of a SMF 633 function or feature. For example, the status 634 of an interface: 'enabled' indicates that 635 it is performing SMF functions, 636 and 'disabled' indicates that it is not." 637 SYNTAX INTEGER { 638 enabled (1), 639 disabled (2) 640 } 642 SmfOpModeID ::= TEXTUAL-CONVENTION 643 STATUS current 644 DESCRIPTION 645 "An index that identifies through reference to a specific 646 SMF operations mode. There are basically three styles 647 of SMF operation with reduced relay sets: 649 Independent operation - SMF performs its own relay 650 set selection using information from an associated 651 MANET NHDP process. 653 CDS-aware unicast routing operation - a coexistent 654 unicast routing protocol provides dynamic relay 655 set state based upon its own control plane 656 CDS or neighborhood discovery information. 658 Cross-layer operation - SMF operates using 659 neighborhood status and triggers from a 660 cross-layer information base for dynamic relay 661 set selection and maintenance." 662 REFERENCE 663 "Simplified Multicast Forwarding for MANET 664 (SMF), Macker, J., July 2012." 665 SYNTAX INTEGER { 666 independent (1), 667 routing (2), 668 crossLayer (3) 669 -- future (4-255) 670 } 672 SmfRssaID ::= TEXTUAL-CONVENTION 673 STATUS current 674 DESCRIPTION 675 "An index that identifies through reference to a specific 676 RSSA algorithms. Several are currently defined 677 in the appendix of SMF (RFC XXXX)." 678 REFERENCE 679 "Simplified Multicast Forwarding for MANET 680 (SMF), Macker, J., July 2012." 681 SYNTAX INTEGER { 682 cF(1), 683 sMPR(2), 684 eCDS(3), 685 mprCDS(4) 686 -- future(5-127) 687 -- noStdAction(128-239) 688 -- experimental(240-255) 689 } 691 -- 692 -- Top-Level Object Identifier Assignments 693 -- 695 smfMIBNotifications OBJECT IDENTIFIER ::= { smfMIB 0 } 696 smfMIBObjects OBJECT IDENTIFIER ::= { smfMIB 1 } 697 smfMIBConformance OBJECT IDENTIFIER ::= { smfMIB 2 } 699 -- 700 -- smfMIBObjects Assignments: 701 -- smfCapabilitiesGroup - 1 702 -- smfConfigurationGroup - 2 703 -- smfStateGroup - 3 704 -- smfPerformanceGroup - 4 705 -- 707 -- 708 -- smfCapabilitiesGroup 709 -- 710 -- This group contains the SMF objects that identify specific 711 -- capabilities within this device related to SMF functions. 712 -- 714 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 716 -- 717 -- SMF Operational Mode Capabilities Table 718 -- 720 smfOpModeCapabilitiesTable OBJECT-TYPE 721 SYNTAX SEQUENCE OF SmfOpModeCapabilitiesEntry 722 MAX-ACCESS not-accessible 723 STATUS current 724 DESCRIPTION 725 "The smfOpModeCapabilitiesTable identifies the 726 resident set of SMF Operational Modes on this 727 router." 728 REFERENCE 729 "Simplified Multicast Forwarding for MANET 730 (SMF), Macker, J., July 2012." 731 ::= { smfCapabilitiesGroup 1 } 733 smfOpModeCapabilitiesEntry OBJECT-TYPE 734 SYNTAX SmfOpModeCapabilitiesEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "Information about a particular operational 739 mode. 740 " 741 INDEX { smfOpModeCapabilitiesID } 742 ::= { smfOpModeCapabilitiesTable 1 } 744 SmfOpModeCapabilitiesEntry ::= SEQUENCE { 745 smfOpModeCapabilitiesID SmfOpModeID, 746 smfOpModeCapabilitiesName SnmpAdminString, 747 smfOpModeCapabilitiesReference SnmpAdminString 748 } 750 smfOpModeCapabilitiesID OBJECT-TYPE 751 SYNTAX SmfOpModeID 752 MAX-ACCESS not-accessible 753 STATUS current 754 DESCRIPTION 755 "The index for this entry. This object identifies 756 the particular operational mode for this device." 757 ::= { smfOpModeCapabilitiesEntry 1 } 759 smfOpModeCapabilitiesName OBJECT-TYPE 760 SYNTAX SnmpAdminString 761 MAX-ACCESS read-only 762 STATUS current 763 DESCRIPTION 764 "The textual name of this operational 765 mode. Current operational modes include: 766 Independent Mode, 767 CDS-aware Routing Mode, and 768 Cross-layer Mode. 769 Others may be defined 770 in future revisions of [SMF]." 771 ::= { smfOpModeCapabilitiesEntry 2 } 773 smfOpModeCapabilitiesReference OBJECT-TYPE 774 SYNTAX SnmpAdminString 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "This object contains a reference to the document 779 that defines this operational mode." 780 ::= { smfOpModeCapabilitiesEntry 3 } 782 -- 783 -- SMF RSSA Capabilities Table 784 -- 786 smfRssaCapabilitiesTable OBJECT-TYPE 787 SYNTAX SEQUENCE OF SmfRssaCapabilitiesEntry 788 MAX-ACCESS not-accessible 789 STATUS current 790 DESCRIPTION 791 "The smfRssaCapabilitiesTable contains 792 reference to the specific set of RSSAs 793 currently supported on this device. 794 " 795 REFERENCE 796 "Simplified Multicast Forwarding for MANET 797 (SMF), Macker, J., July 2012." 798 ::= { smfCapabilitiesGroup 2 } 800 smfRssaCapabilitiesEntry OBJECT-TYPE 801 SYNTAX SmfRssaCapabilitiesEntry 802 MAX-ACCESS not-accessible 803 STATUS current 804 DESCRIPTION 805 "Information about a particular RSSA 806 algorithm." 807 INDEX { smfRssaCapabilitiesID } 808 ::= { smfRssaCapabilitiesTable 1 } 810 SmfRssaCapabilitiesEntry ::= SEQUENCE { 811 smfRssaCapabilitiesID SmfRssaID, 812 smfRssaCapabilitiesName SnmpAdminString, 813 smfRssaCapabilitiesReference SnmpAdminString 814 } 816 smfRssaCapabilitiesID OBJECT-TYPE 817 SYNTAX SmfRssaID 818 MAX-ACCESS not-accessible 819 STATUS current 820 DESCRIPTION 821 "The index for this entry. This object identifies 822 the particular RSSA algorithm in this MIB 823 module. Example RSSAs are found in the 824 appendix of [SMF]. 826 By default, the agent should support at least the 827 Classical Flooding algorithm. All compliant 828 SMF forwarders must support Classical Flooding. 829 Hence, at least one entry in this table must 830 exist." 831 ::= { smfRssaCapabilitiesEntry 1 } 833 smfRssaCapabilitiesName OBJECT-TYPE 834 SYNTAX SnmpAdminString 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION 838 "The textual name of this RSSA algorithm. 839 Currently defined names are: 840 Classical Flooding - cF, 841 Source-based MultiPoint 842 Relay - sMPR, 843 Essential Connecting Dominating 844 Set - eCDS, 845 MultiPoint Relay Connected 846 Dominating Set - mprCDS. 847 " 848 ::= { smfRssaCapabilitiesEntry 2 } 850 smfRssaCapabilitiesReference OBJECT-TYPE 851 SYNTAX SnmpAdminString 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "This object contains a published reference 856 to the document that defines this algorithm. 857 " 858 ::= { smfRssaCapabilitiesEntry 3 } 860 -- 861 -- smfConfigurationGroup 862 -- 863 -- This group contains the SMF objects that configure specific 864 -- options that determine the overall performance and operation 865 -- of the multicast forwarding process for the router device 866 -- and its interfaces. 868 -- 870 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 872 smfAdminStatus OBJECT-TYPE 873 SYNTAX SmfStatus 874 MAX-ACCESS read-write 875 STATUS current 876 DESCRIPTION 877 "The configured status of the SMF process 878 on this device. Enabled(1) means that 879 SMF is configured to run on this device. 880 Disabled(2) mean that the SMF process 881 is configured off. 883 This object is persistent and when written 884 the entity SHOULD save the change to 885 non-volatile storage. 886 " 887 ::= { smfConfigurationGroup 1 } 889 smfRouterIDAddrType OBJECT-TYPE 890 SYNTAX InetAddressType 891 MAX-ACCESS read-write 892 STATUS current 893 DESCRIPTION 894 "The address type of the address used for 895 SMF ID of this router as specified 896 in the 'smfRouterID' next. 898 Only the values ipv4(1) and ipv6(2) 899 are supported. 901 This can be set by the management station, 902 the smfRouterID must be a routable address 903 assigned to this router. If the management 904 station does not assign this value, then the 905 router should choose the highest routable 906 IP address assigned to this router. 908 This object is persistent and when written 909 the entity SHOULD save the change to 910 non-volatile storage." 911 DEFVAL { ipv4 } 912 ::= { smfConfigurationGroup 2 } 914 smfRouterID OBJECT-TYPE 915 SYNTAX InetAddress (SIZE(4|16)) 916 MAX-ACCESS read-write 917 STATUS current 918 DESCRIPTION 919 "The IP address used as the SMF router ID. 920 This can be set by the management station. 921 If not explicitly set, then the device 922 should select a routable IP address 923 assigned to this router for use as 924 the 'smfRouterID'. 926 The smfRouterID is a logical identification 927 that MUST be consistent across interoperable 928 SMF neighborhoods and it is RECOMMENDED to be 929 chosen as the numerically largest address 930 contained in a node's 'Neighbor Address List' 931 as defined in NHDP. A smfRouterID MUST be 932 unique within the scope of the operating 933 MANET network regardless of the method used 934 for selecting it. 936 This object is persistent and when written 937 the entity SHOULD save the change to 938 non-volatile storage." 939 REFERENCE 940 "Simplified Multicast Forwarding for MANET 941 (SMF), Macker, J., July 2012." 942 ::= { smfConfigurationGroup 3 } 944 smfConfiguredOpMode OBJECT-TYPE 945 SYNTAX INTEGER { 946 withNHDP(1), 947 cdsAwareRouting(2), 948 crossLayer(3), 949 other(4) 950 } 951 MAX-ACCESS read-write 952 STATUS current 953 DESCRIPTION 954 "The SMF RSS node operational mode as defined 955 in the TEXTUAL CONVENTION for `SmfOpModeID' 956 and in [SMF].. 958 The value withNHDP(1) indicates Independent 959 Mode of operation. 961 The value cdsAwareRouting(2) indicates 962 CDS-aware Routing Mode of operation. 964 The value crossLayer(3) indicates 965 Cross-layer Mode of operation. 967 The default value for this object is 968 withNHDP(1). 970 This object is persistent and when written 971 the entity SHOULD save the change to 972 non-volatile storage." 973 REFERENCE 974 "Simplified Multicast Forwarding for MANET 975 (SMF), Macker, J., July 2012." 976 DEFVAL { withNHDP } 977 ::= { smfConfigurationGroup 4 } 979 smfConfiguredRssa OBJECT-TYPE 980 SYNTAX SmfRssaID 981 MAX-ACCESS read-write 982 STATUS current 983 DESCRIPTION 984 "The SMF RSS currently operational algorithm 985 as defined in the TEXTUAL CONVENTION for 986 `SmfRssaID' and in [SMF]. 988 The deflaut value for this object is 989 cF(1), i.e., Classical Flooding. 991 This object is persistent and when written 992 the entity SHOULD save the change to 993 non-volatile storage." 994 REFERENCE 995 "Simplified Multicast Forwarding for MANET 996 (SMF), Macker, J., July 2012." 997 DEFVAL { cF } 998 ::= { smfConfigurationGroup 5 } 1000 smfRssaMember OBJECT-TYPE 1001 SYNTAX INTEGER { 1002 potential(1), 1003 always(2), 1004 never(3) 1005 } 1006 MAX-ACCESS read-write 1007 STATUS current 1008 DESCRIPTION 1009 "The RSSA downselects a set of forwarders for 1010 multicast forwarding. Sometimes it is useful 1011 to force an agent to be included or excluded 1012 from the resulting RSS. This object is a 1013 switch to allow for this behavior. 1015 The value potential(1) allows the selected 1016 RSSA to determine if this agent is included 1017 or excluded from the RSS. 1019 The value always(1) forces the selected 1020 RSSA include this agent in the RSS. 1022 The value never(3) forces the selected 1023 RSSA to exclude this agent from the RSS. 1025 The default setting for this object is 1026 'potential(1)'. Other settings could pose 1027 operational risks under certain conditions. 1029 This object is persistent and when written 1030 the entity SHOULD save the change to 1031 non-volatile storage." 1032 REFERENCE 1033 "Simplified Multicast Forwarding for MANET 1034 (SMF), Macker, J., July 2012." 1035 DEFVAL { potential } 1036 ::= { smfConfigurationGroup 6 } 1038 smfIpv4Dpd OBJECT-TYPE 1039 SYNTAX INTEGER { 1040 hashBased(1), 1041 identificationBased(2) 1042 } 1043 MAX-ACCESS read-write 1044 STATUS current 1045 DESCRIPTION 1046 "The current method for IPv4 duplicate packet 1047 detection. 1049 The value hashBased(1) indicates that the 1050 routers duplicate packet detection is based 1051 upon comparing a hash over the packet fields. 1052 This is the default setting for this object. 1054 The value identificationBased(2) 1055 indicates that the duplicate packet 1056 detection relies upon header information 1057 in the multicast packets to identify 1058 previously received packets. 1060 This object is persistent and when written 1061 the entity SHOULD save the change to 1062 non-volatile storage." 1063 REFERENCE 1064 "Simplified Multicast Forwarding for MANET 1065 (SMF), Macker, J., July 2012." 1066 DEFVAL { hashBased } 1067 ::= { smfConfigurationGroup 7 } 1069 smfIpv6Dpd OBJECT-TYPE 1070 SYNTAX INTEGER { 1071 hashBased(1), 1072 identificationBased(2) 1073 } 1074 MAX-ACCESS read-write 1075 STATUS current 1076 DESCRIPTION 1077 "The current method for IPv6 duplicate packet 1078 detection. 1080 The values indicate the type of method used 1081 for duplicate packet detection as described 1082 the previous description for the object 1083 `smfIpv4Dpd'. 1085 The default value for this object is 1086 hashBased(1). 1088 This object is persistent and when written 1089 the entity SHOULD save the change to 1090 non-volatile storage." 1091 REFERENCE 1092 "Simplified Multicast Forwarding for MANET 1093 (SMF), Macker, J., July 2012." 1094 DEFVAL { hashBased } 1095 ::= { smfConfigurationGroup 8 } 1097 smfMaxPktLifetime OBJECT-TYPE 1098 SYNTAX Integer32 (0..65535) 1099 UNITS "Seconds" 1100 MAX-ACCESS read-write 1101 STATUS current 1102 DESCRIPTION 1103 "The estimate of the network packet 1104 traversal time. 1106 This object is persistent and when written 1107 the entity SHOULD save the change to 1108 non-volatile storage." 1109 REFERENCE 1110 "Simplified Multicast Forwarding for MANET 1111 (SMF), Macker, J., July 2012." 1112 DEFVAL { 60 } 1113 ::= { smfConfigurationGroup 9 } 1115 smfDpdMaxMemorySize OBJECT-TYPE 1116 SYNTAX Integer32 (0..65535) 1117 UNITS "Kilo-Bytes" 1118 MAX-ACCESS read-write 1119 STATUS current 1120 DESCRIPTION 1121 "The locally reserved memory for storage 1122 of cached DPD records for both IPv4 and 1123 IPv6 methods. 1125 The local SMF device should protect itself 1126 against the SNMP manager from requesting 1127 too large a memory value. If this is the case, 1128 an error indication should be returned in response 1129 to the SNMP SET request. 1131 This object is persistent and when written 1132 the entity SHOULD save the change to 1133 non-volatile storage." 1134 REFERENCE 1135 "Simplified Multicast Forwarding for MANET 1136 (SMF), Macker, J., July 2012." 1137 DEFVAL { 1024 } 1138 ::= { smfConfigurationGroup 10 } 1140 smfDpdEntryMaxLifetime OBJECT-TYPE 1141 SYNTAX Integer32 (0..65525) 1142 UNITS "Seconds" 1143 MAX-ACCESS read-write 1144 STATUS current 1145 DESCRIPTION 1146 "The maximum lifetime of a cached DPD 1147 record in the local device storage. 1149 If the memory is running low prior to the 1150 MaxLifetimes being exceeded, the local SMF 1151 devices should purge the oldest records first. 1153 This object is persistent and when written 1154 the entity SHOULD save the change to 1155 non-volatile storage." 1157 REFERENCE 1158 "Simplified Multicast Forwarding for MANET 1159 (SMF), Macker, J., July 2012." 1160 DEFVAL { 600 } 1161 ::= { smfConfigurationGroup 11 } 1163 -- 1164 -- Configuration of messages to be included in 1165 -- NHDP message exchanges in support of SMF 1166 -- operations. 1167 -- 1169 smfNhdpRssaMesgTLVIncluded OBJECT-TYPE 1170 SYNTAX TruthValue 1171 MAX-ACCESS read-write 1172 STATUS current 1173 DESCRIPTION 1174 "Indicates whether the associated NHDP messages 1175 include the RSSA Message TLV, or not. This 1176 is an optional SMF operational setting. 1177 The value true(1) indicates that this TLV is 1178 included; the value false(2) indicates that it 1179 is not included. 1181 It is RECOMMENDED that the RSSA Message TLV 1182 be included in the NHDP messages. 1184 This object is persistent and when written 1185 the entity SHOULD save the change to 1186 non-volatile storage." 1187 REFERENCE 1188 "Simplified Multicast Forwarding for MANET 1189 (SMF), Macker, J., July 2012." 1190 DEFVAL { true } 1191 ::= { smfConfigurationGroup 12 } 1193 smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 1194 SYNTAX TruthValue 1195 MAX-ACCESS read-write 1196 STATUS current 1197 DESCRIPTION 1198 "Indicates whether the associated NHDP messages 1199 include the RSSA Address Block TLV, or not. 1200 This is an optional SMF operational setting. 1201 The value true(1) indicates that this TLV is 1202 included; the value false(2) indicates that it 1203 is not included. 1205 The smfNhdpRssaAddrBlockTLVIncluded is optional 1206 in all cases as it depends on the existence of 1207 an address block which may not be present. 1208 If this SMF device is configured with NHDP, 1209 then this object should be set to 'true(1)'. 1211 This object is persistent and when written 1212 the entity SHOULD save the change to 1213 non-volatile storage." 1214 REFERENCE 1215 "Simplified Multicast Forwarding for MANET 1216 (SMF), Macker, J., July 2012." 1217 DEFVAL { true } 1218 ::= { smfConfigurationGroup 13 } 1220 -- 1221 -- Table identifying configured multicast addresses to be forwarded. 1222 -- 1224 smfConfiguredAddrForwardingTable OBJECT-TYPE 1225 SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry 1226 MAX-ACCESS not-accessible 1227 STATUS current 1228 DESCRIPTION 1229 "The (conceptual) table containing information on multicast 1230 addresses which are to be forwarded by the SMF process. 1232 Entries in this table are configured. As well, addresses 1233 to be forwarded by the SMF device can be dynamically 1234 discovered by other means. The corresponding state 1235 table, smfDiscoveredAddrForwardingTable, contains 1236 these additional, dynamically discovered address for 1237 forwarding. 1239 Each row is associated with a range of multicast 1240 addresses, and ranges for different rows must be disjoint. 1242 The objects in this table are persistent and when written 1243 the entity SHOULD save the change to 1244 non-volatile storage." 1245 REFERENCE 1246 "Simplified Multicast Forwarding for MANET 1247 (SMF), Macker, J., July 2012." 1248 ::= { smfConfigurationGroup 15 } 1250 smfConfiguredAddrForwardingEntry OBJECT-TYPE 1251 SYNTAX SmfConfiguredAddrForwardingEntry 1252 MAX-ACCESS not-accessible 1253 STATUS current 1254 DESCRIPTION 1255 "An entry (conceptual row) containing the information on a 1256 particular multicast scope." 1257 INDEX { smfConfiguredAddrForwardingAddrType, 1258 smfConfiguredAddrForwardingFirstAddr } 1259 ::= { smfConfiguredAddrForwardingTable 1 } 1261 SmfConfiguredAddrForwardingEntry ::= SEQUENCE { 1262 smfConfiguredAddrForwardingAddrType InetAddressType, 1263 smfConfiguredAddrForwardingFirstAddr InetAddress, 1264 smfConfiguredAddrForwardingLastAddr InetAddress, 1265 smfConfiguredAddrForwardingStatus RowStatus 1266 } 1268 smfConfiguredAddrForwardingAddrType OBJECT-TYPE 1269 SYNTAX InetAddressType 1270 MAX-ACCESS not-accessible 1271 STATUS current 1272 DESCRIPTION 1273 "The type of the addresses in the multicast forwarding 1274 range. Legal values correspond to the subset of 1275 address families for which multicast address allocation 1276 is supported. 1278 Only the values ipv4(1) and 1279 ipv6(2) are supported." 1280 ::= { smfConfiguredAddrForwardingEntry 1 } 1282 smfConfiguredAddrForwardingFirstAddr OBJECT-TYPE 1283 SYNTAX InetAddress (SIZE(4|16)) 1284 MAX-ACCESS not-accessible 1285 STATUS current 1286 DESCRIPTION 1287 "The first address in the multicast scope range. The type 1288 of this address is determined by the value of the 1289 smfConfiguredAddrForwardingAddrType object." 1290 ::= { smfConfiguredAddrForwardingEntry 2 } 1292 smfConfiguredAddrForwardingLastAddr OBJECT-TYPE 1293 SYNTAX InetAddress (SIZE(4|16)) 1294 MAX-ACCESS read-create 1295 STATUS current 1296 DESCRIPTION 1297 "The last address in the multicast scope range. 1298 The type of this address is determined by the 1299 value of the smfConfiguredAddrForwardingAddrType 1300 object." 1301 ::= { smfConfiguredAddrForwardingEntry 3 } 1303 smfConfiguredAddrForwardingStatus OBJECT-TYPE 1304 SYNTAX RowStatus 1305 MAX-ACCESS read-create 1306 STATUS current 1307 DESCRIPTION 1308 "The status of this row, by which new entries may be 1309 created, or old entries deleted from this table. If write 1310 access is supported, the other writable objects in this 1311 table may be modified even while the status is `active'." 1312 ::= { smfConfiguredAddrForwardingEntry 4 } 1314 -- 1315 -- SMF Interfaces Configuration Table 1316 -- 1318 smfInterfaceTable OBJECT-TYPE 1319 SYNTAX SEQUENCE OF SmfInterfaceEntry 1320 MAX-ACCESS not-accessible 1321 STATUS current 1322 DESCRIPTION 1323 "The SMF Interface Table describes the SMF 1324 interfaces that are participating in the 1325 SMF packet forwarding process. The ifIndex is 1326 from the interfaces group defined in the 1327 Interfaces Group MIB (RFC 2863). As such, 1328 this table 'sparse augments' the ifTable 1329 specifically when SMF is to be configured to 1330 operate over this interface. 1332 A conceptual row in this table exists if and only 1333 if either a manager has explicitly created the row 1334 or there is an interface on the managed device 1335 that supports and runs SMF. 1337 The manager can create a row by setting 1338 rowStatus to 'createAndGo' or 'createAndWait'. 1339 Row objects having associated DEFVAL clauses are 1340 automatically defined by the agent with these 1341 values during row creation, unless the manager 1342 explicitly defines these object values during the 1343 row creation. 1345 If the corresponding entry with ifIndex value 1346 is deleted from the Interface Table, then the entry 1347 in this table is automatically deleted and 1348 SMF is disabled on this interface, 1349 and all configuration and state information 1350 related to this interface is to be removed 1351 from memory." 1352 REFERENCE 1353 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1354 K., and F. Kastenholtz, June 2000." 1355 ::= { smfConfigurationGroup 16 } 1357 smfInterfaceEntry OBJECT-TYPE 1358 SYNTAX SmfInterfaceEntry 1359 MAX-ACCESS not-accessible 1360 STATUS current 1361 DESCRIPTION 1362 "The SMF interface entry describes one SMF 1363 interface as indexed by its ifIndex. 1365 The objects in this table are persistent and when 1366 written the device SHOULD save the change to 1367 non-volatile storage. For further information 1368 on the storage behavior for these objects, refer 1369 to the description for the smfIfRowStatus 1370 object." 1371 INDEX { smfIfIndex } 1372 ::= { smfInterfaceTable 1 } 1374 SmfInterfaceEntry ::= 1375 SEQUENCE { 1376 smfIfIndex InterfaceIndexOrZero, 1377 smfIfName DisplayString, 1378 smfIfAdminStatus SmfStatus, 1379 smfIfRowStatus RowStatus 1380 } 1382 smfIfIndex OBJECT-TYPE 1383 SYNTAX InterfaceIndexOrZero 1384 MAX-ACCESS not-accessible 1385 STATUS current 1386 DESCRIPTION 1387 "The ifIndex for this SMF interface. This value 1388 MUST correspond to an ifIndex referring 1389 to a valid entry in The Interfaces Table." 1390 REFERENCE 1391 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1392 K., and F. Kastenholtz, June 2000." 1394 ::= { smfInterfaceEntry 1 } 1396 smfIfName OBJECT-TYPE 1397 SYNTAX DisplayString 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION 1401 "The textual name of the interface. The value of this 1402 object should be the name of the interface as assigned by 1403 the local device and should be suitable for use in commands 1404 entered at the device's `console'. This might be a text 1405 name, such as `le0' or a simple port number, such as `1', 1406 depending on the interface naming syntax of the device. 1408 If there is no local name, or this object is otherwise not 1409 applicable, then this object contains a zero-length string." 1410 ::= { smfInterfaceEntry 2 } 1412 smfIfAdminStatus OBJECT-TYPE 1413 SYNTAX SmfStatus 1414 MAX-ACCESS read-create 1415 STATUS current 1416 DESCRIPTION 1417 "The SMF interface's administrative status. 1418 The value 'enabled' denotes that the interface 1419 is running the SMF forwarding process. 1420 The value 'disabled' denotes that the interface is 1421 external to the SMF forwarding process. 1422 " 1423 ::= { smfInterfaceEntry 3 } 1425 smfIfRowStatus OBJECT-TYPE 1426 SYNTAX RowStatus 1427 MAX-ACCESS read-create 1428 STATUS current 1429 DESCRIPTION 1430 "This object permits management of the table 1431 by facilitating actions such as row creation, 1432 construction, and destruction. The value of 1433 this object has no effect on whether other 1434 objects in this conceptual row can be 1435 modified. 1437 An entry may not exist in the active(1) state unless all 1438 objects in the entry have a defined appropriate value. For 1439 objects with DEFVAL clauses, the management station 1440 does not need to specify the value of this object in order 1441 for the row to transit to the active(1) state; the default 1442 value for this object is used. For objects that do not 1443 have DEFVAL clauses, then the network manager MUST 1444 specify the value of this object prior to this row 1445 transitioning to the active(1) state. 1447 When this object transitions to active(1), all objects 1448 in this row SHOULD be written to non-volatile (stable) 1449 storage. Read-create objects in this row MAY be modified. 1450 When an object in a row with smfIfRowStatus of active(1) 1451 is changed, then the updated value MUST be reflected in SMF 1452 and this new object value MUST be written to non-volatile 1453 storage. 1455 If this object is not equal to active(1), all associated 1456 entries in the smfIpv4InterfaceperfTable and the 1457 smfIpv6InterfacePerfTable MUST be deleted." 1458 ::= { smfInterfaceEntry 4 } 1460 -- 1461 -- smfStateGroup 1462 -- 1463 -- Contains information describing the current state of the SMF 1464 -- process such as the current inclusion in the RS or not. 1465 -- 1467 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1469 smfNodeRsStatusIncluded OBJECT-TYPE 1470 SYNTAX TruthValue 1471 MAX-ACCESS read-only 1472 STATUS current 1473 DESCRIPTION 1474 "The current status of the SMF node in the context of 1475 the MANETs relay set. A value of true(1) indicates 1476 that the node is currently part of the MANET Relay 1477 Set. A value of false(2) indicates that the node 1478 is currently not part of the MANET Relay Set." 1479 REFERENCE 1480 "Simplified Multicast Forwarding for MANET 1481 (SMF), Macker, J., July 2012." 1482 ::= { smfStateGroup 1 } 1484 smfDpdMemoryOverflow OBJECT-TYPE 1485 SYNTAX Counter32 1486 MAX-ACCESS read-only 1487 STATUS current 1488 DESCRIPTION 1489 "The number of times that the memory for caching 1490 records for DPD overran and records had to be flushed. 1491 The number of records to be flushed upon a buffer 1492 overflow is an implementation specific decision." 1493 REFERENCE 1494 "Simplified Multicast Forwarding for MANET 1495 (SMF), Macker, J., July 2012." 1496 ::= { smfStateGroup 2 } 1498 -- 1499 -- Dynamically Discovered Multicast Addr Table 1500 -- 1502 smfDiscoveredAddrForwardingTable OBJECT-TYPE 1503 SYNTAX SEQUENCE OF SmfDiscoveredAddrForwardingEntry 1504 MAX-ACCESS not-accessible 1505 STATUS current 1506 DESCRIPTION 1507 "This state table, smfDiscoveredAddrForwardingTable 1508 contains additional, dynamically discovered address 1509 for forwarding. 1511 Each row is associated with a range of 1512 multicast addresses, and ranges for different rows 1513 must be disjoint." 1514 REFERENCE 1515 "Simplified Multicast Forwarding for MANET 1516 (SMF), Macker, J., July 2012." 1517 ::= { smfStateGroup 3 } 1519 smfDiscoveredAddrForwardingEntry OBJECT-TYPE 1520 SYNTAX SmfDiscoveredAddrForwardingEntry 1521 MAX-ACCESS not-accessible 1522 STATUS current 1523 DESCRIPTION 1524 "An entry (conceptual row) containing the information on a 1525 particular multicast scope." 1526 INDEX { smfDiscoveredAddrForwardingAddrType, 1527 smfDiscoveredAddrForwardingFirstAddr } 1528 ::= { smfDiscoveredAddrForwardingTable 1 } 1530 SmfDiscoveredAddrForwardingEntry ::= SEQUENCE { 1531 smfDiscoveredAddrForwardingAddrType InetAddressType, 1532 smfDiscoveredAddrForwardingFirstAddr InetAddress, 1533 smfDiscoveredAddrForwardingLastAddr InetAddress 1534 } 1535 smfDiscoveredAddrForwardingAddrType OBJECT-TYPE 1536 SYNTAX InetAddressType 1537 MAX-ACCESS not-accessible 1538 STATUS current 1539 DESCRIPTION 1540 "The type of the addresses in the multicast forwarding 1541 range. Legal values correspond to the subset of 1542 address families for which multicast address allocation 1543 is supported. 1545 Only the values ipv4(1) and 1546 ipv6(2) are supported." 1547 ::= { smfDiscoveredAddrForwardingEntry 1 } 1549 smfDiscoveredAddrForwardingFirstAddr OBJECT-TYPE 1550 SYNTAX InetAddress (SIZE(4|16)) 1551 MAX-ACCESS not-accessible 1552 STATUS current 1553 DESCRIPTION 1554 "The first address in the multicast scope range. The type 1555 of this address is determined by the value of the 1556 smfConfiguredAddrForwardingAddrType object." 1557 ::= { smfDiscoveredAddrForwardingEntry 2 } 1559 smfDiscoveredAddrForwardingLastAddr OBJECT-TYPE 1560 SYNTAX InetAddress (SIZE(4|16)) 1561 MAX-ACCESS read-create 1562 STATUS current 1563 DESCRIPTION 1564 "The last address in the multicast scope range. 1565 The type of this address is determined by the 1566 value of the smfConfiguredAddrForwardingAddrType 1567 object." 1568 ::= { smfDiscoveredAddrForwardingEntry 3 } 1570 -- 1571 -- SMF Neighbor Table 1572 -- 1574 smfNeighborTable OBJECT-TYPE 1575 SYNTAX SEQUENCE OF SmfNeighborEntry 1576 MAX-ACCESS not-accessible 1577 STATUS current 1578 DESCRIPTION 1579 "The SMF NeighborTable describes the 1580 current neighbor nodes, their address 1581 and SMF RSSA and the interface on which 1582 they can be reached." 1583 REFERENCE 1584 "Simplified Multicast Forwarding for MANET 1585 (SMF), Macker, J., July 2012. 1586 Section 7: SMF Neighborhood Discovery 1587 Requirements." 1588 ::= { smfStateGroup 4 } 1590 smfNeighborEntry OBJECT-TYPE 1591 SYNTAX SmfNeighborEntry 1592 MAX-ACCESS not-accessible 1593 STATUS current 1594 DESCRIPTION 1595 "The SMF Neighbor Table contains the 1596 set of one-hop neighbors, the interface 1597 they are reachable on and the SMF RSSA 1598 they are currently running." 1599 INDEX { smfNeighborIpAddrType, 1600 smfNeighborIpAddr, 1601 smfNeighborPrefixLen } 1602 ::= { smfNeighborTable 1 } 1604 SmfNeighborEntry ::= 1605 SEQUENCE { 1606 smfNeighborIpAddrType InetAddressType, 1607 smfNeighborIpAddr InetAddress, 1608 smfNeighborPrefixLen InetAddressPrefixLength, 1609 smfNeighborRSSA SmfRssaID, 1610 smfNeighborNextHopInterface InterfaceIndexOrZero 1611 } 1613 smfNeighborIpAddrType OBJECT-TYPE 1614 SYNTAX InetAddressType 1615 MAX-ACCESS not-accessible 1616 STATUS current 1617 DESCRIPTION 1618 "The neighbor IP address type. 1620 Only the values ipv4(1) and 1621 ipv6(2) are supported." 1622 ::= { smfNeighborEntry 1 } 1624 smfNeighborIpAddr OBJECT-TYPE 1625 SYNTAX InetAddress (SIZE(4|16)) 1626 MAX-ACCESS not-accessible 1627 STATUS current 1628 DESCRIPTION 1629 "The neighbor Inet IPv4 or IPv6 address." 1631 ::= { smfNeighborEntry 2 } 1633 smfNeighborPrefixLen OBJECT-TYPE 1634 SYNTAX InetAddressPrefixLength 1635 MAX-ACCESS not-accessible 1636 STATUS current 1637 DESCRIPTION 1638 "The prefix length. This is a decimal value that 1639 indicates the number of contiguous, higher-order 1640 bits of the address that make up the network 1641 portion of the address." 1642 ::= { smfNeighborEntry 3 } 1644 smfNeighborRSSA OBJECT-TYPE 1645 SYNTAX SmfRssaID 1646 MAX-ACCESS read-only 1647 STATUS current 1648 DESCRIPTION 1649 "The current RSSA running on the neighbor. 1650 The list is identical to that described 1651 above for the smfRssa object." 1652 ::= { smfNeighborEntry 4 } 1654 smfNeighborNextHopInterface OBJECT-TYPE 1655 SYNTAX InterfaceIndexOrZero 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "The interface ifIndex over which the 1660 neighbor is reachable in one-hop." 1661 ::= { smfNeighborEntry 5 } 1663 -- 1664 -- SMF Performance Group 1665 -- 1666 -- Contains objects which help to characterize the 1667 -- performance of the SMF RSSA process, such as statistics 1668 -- counters. There are two types of SMF RSSA statistics: 1669 -- global counters and per interface counters. 1670 -- 1672 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1674 smfGlobalPerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1675 -- 1676 -- IPv4 packet counters 1677 -- 1679 smfIpv4MultiPktsRecvTotal OBJECT-TYPE 1680 SYNTAX Counter32 1681 MAX-ACCESS read-only 1682 STATUS current 1683 DESCRIPTION 1684 "A counter of the total number of 1685 multicast IPv4 packets received by the 1686 device." 1687 REFERENCE 1688 "Simplified Multicast Forwarding for MANET 1689 (SMF), Macker, J., July 2012." 1690 ::= { smfGlobalPerfGroup 1 } 1692 smfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1693 SYNTAX Counter32 1694 MAX-ACCESS read-only 1695 STATUS current 1696 DESCRIPTION 1697 "A counter of the total number of 1698 multicast IPv4 packets forwarded by the 1699 device." 1700 REFERENCE 1701 "Simplified Multicast Forwarding for MANET 1702 (SMF), Macker, J., July 2012." 1703 ::= { smfGlobalPerfGroup 2 } 1705 smfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1706 SYNTAX Counter32 1707 MAX-ACCESS read-only 1708 STATUS current 1709 DESCRIPTION 1710 "A counter of the total number of duplicate 1711 multicast IPv4 packets detected by the 1712 device." 1713 REFERENCE 1714 "Simplified Multicast Forwarding for MANET 1715 (SMF), Macker, J., July 2012." 1716 ::= { smfGlobalPerfGroup 3 } 1718 smfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1719 SYNTAX Counter32 1720 MAX-ACCESS read-only 1721 STATUS current 1722 DESCRIPTION 1723 "A counter of the total number of dropped 1724 multicast IPv4 packets by the 1725 device due to TTL exceeded." 1726 REFERENCE 1727 "Simplified Multicast Forwarding for MANET 1728 (SMF), Macker, J., July 2012." 1729 ::= { smfGlobalPerfGroup 4 } 1731 smfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1732 SYNTAX Counter32 1733 MAX-ACCESS read-only 1734 STATUS current 1735 DESCRIPTION 1736 "A counter of the total number of IPv4 packets 1737 recieved which have a TTL larger than that 1738 of a previously received identical packet." 1739 REFERENCE 1740 "Simplified Multicast Forwarding for MANET 1741 (SMF), Macker, J., July 2012." 1742 ::= { smfGlobalPerfGroup 5 } 1744 -- 1745 -- IPv6 packet counters 1746 -- 1748 smfIpv6MultiPktsRecvTotal OBJECT-TYPE 1749 SYNTAX Counter32 1750 MAX-ACCESS read-only 1751 STATUS current 1752 DESCRIPTION 1753 "A counter of the total number of 1754 multicast IPv6 packets received by the 1755 device." 1756 REFERENCE 1757 "Simplified Multicast Forwarding for MANET 1758 (SMF), Macker, J., July 2012." 1759 ::= { smfGlobalPerfGroup 6 } 1761 smfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1762 SYNTAX Counter32 1763 MAX-ACCESS read-only 1764 STATUS current 1765 DESCRIPTION 1766 "A counter of the total number of 1767 multicast IPv6 packets forwarded by the 1768 device." 1769 REFERENCE 1770 "Simplified Multicast Forwarding for MANET 1771 (SMF), Macker, J., July 2012." 1772 ::= { smfGlobalPerfGroup 7 } 1774 smfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1775 SYNTAX Counter32 1776 MAX-ACCESS read-only 1777 STATUS current 1778 DESCRIPTION 1779 "A counter of the total number of duplicate 1780 multicast IPv6 packets detected by the 1781 device." 1782 REFERENCE 1783 "Simplified Multicast Forwarding for MANET 1784 (SMF), Macker, J., July 2012." 1785 ::= { smfGlobalPerfGroup 8 } 1787 smfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1788 SYNTAX Counter32 1789 MAX-ACCESS read-only 1790 STATUS current 1791 DESCRIPTION 1792 "A counter of the total number of dropped 1793 multicast IPv6 packets by the 1794 device due to TTL exceeded." 1795 REFERENCE 1796 "Simplified Multicast Forwarding for MANET 1797 (SMF), Macker, J., July 2012." 1798 ::= { smfGlobalPerfGroup 9 } 1800 smfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1801 SYNTAX Counter32 1802 MAX-ACCESS read-only 1803 STATUS current 1804 DESCRIPTION 1805 "A counter of the total number of IPv6 packets 1806 recieved which have a TTL larger than that 1807 of a previously recived identical packet." 1808 REFERENCE 1809 "Simplified Multicast Forwarding for MANET 1810 (SMF), Macker, J., July 2012." 1811 ::= { smfGlobalPerfGroup 10 } 1813 smfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1814 SYNTAX Counter32 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "A counter of the total number of IPv6 packets 1819 recieved which required the HAV assist for DPD." 1820 REFERENCE 1821 "Simplified Multicast Forwarding for MANET 1822 (SMF), Macker, J., July 2012." 1823 ::= { smfGlobalPerfGroup 11 } 1825 smfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1826 SYNTAX Counter32 1827 MAX-ACCESS read-only 1828 STATUS current 1829 DESCRIPTION 1830 "A counter of the total number of IPv6 packets 1831 recieved which the device inserted the 1832 DPD header option." 1833 REFERENCE 1834 "Simplified Multicast Forwarding for MANET 1835 (SMF), Macker, J., July 2012." 1836 ::= { smfGlobalPerfGroup 12 } 1838 -- 1839 -- Per SMF Interface Performance Table 1840 -- 1842 smfInterfacePerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1844 smfIpv4InterfacePerfTable OBJECT-TYPE 1845 SYNTAX SEQUENCE OF SmfIpv4InterfacePerfEntry 1846 MAX-ACCESS not-accessible 1847 STATUS current 1848 DESCRIPTION 1849 "The SMF Interface Performance Table 1850 describes the SMF statistics per 1851 interface." 1852 REFERENCE 1853 "Simplified Multicast Forwarding for MANET 1854 (SMF), Macker, J., July 2012." 1855 ::= { smfInterfacePerfGroup 1 } 1857 smfIpv4InterfacePerfEntry OBJECT-TYPE 1858 SYNTAX SmfIpv4InterfacePerfEntry 1859 MAX-ACCESS not-accessible 1860 STATUS current 1861 DESCRIPTION 1862 "The SMF Interface Performance entry 1863 describes the statistics for a particular 1864 node interface." 1865 INDEX { smfIfIndex } 1867 ::= { smfIpv4InterfacePerfTable 1 } 1869 SmfIpv4InterfacePerfEntry ::= 1870 SEQUENCE { 1871 smfIpv4MultiPktsRecvPerIf Counter32, 1872 smfIpv4MultiPktsForwardedPerIf Counter32, 1873 smfIpv4DuplMultiPktsDetectedPerIf Counter32, 1874 smfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1875 smfIpv4TTLLargerThanPreviousPerIf Counter32 1876 } 1878 smfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1879 SYNTAX Counter32 1880 MAX-ACCESS read-only 1881 STATUS current 1882 DESCRIPTION 1883 "A counter of the number of 1884 multicast IP packets received by the 1885 device on this interface." 1886 ::= { smfIpv4InterfacePerfEntry 1 } 1888 smfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1889 SYNTAX Counter32 1890 MAX-ACCESS read-only 1891 STATUS current 1892 DESCRIPTION 1893 "A counter of the number of 1894 multicast IP packets forwarded by the 1895 device on this interface." 1896 ::= { smfIpv4InterfacePerfEntry 2 } 1898 smfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1899 SYNTAX Counter32 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "A counter of the number of duplicate 1904 multicast IP packets detected by the 1905 device on this interface." 1906 ::= { smfIpv4InterfacePerfEntry 3 } 1908 smfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1909 SYNTAX Counter32 1910 MAX-ACCESS read-only 1911 STATUS current 1912 DESCRIPTION 1913 "A counter of the total number of dropped 1914 multicast IPv4 packets by the 1915 device due to TTL exceeded." 1916 ::= { smfIpv4InterfacePerfEntry 4 } 1918 smfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1919 SYNTAX Counter32 1920 MAX-ACCESS read-only 1921 STATUS current 1922 DESCRIPTION 1923 "A counter of the total number of IPv4 packets 1924 recieved which have a TTL larger than that 1925 of a previously recived identical packet. 1926 " 1927 ::= { smfIpv4InterfacePerfEntry 5 } 1929 smfIpv6InterfacePerfTable OBJECT-TYPE 1930 SYNTAX SEQUENCE OF SmfIpv6InterfacePerfEntry 1931 MAX-ACCESS not-accessible 1932 STATUS current 1933 DESCRIPTION 1934 "The SMF Interface Performance Table 1935 describes the SMF statistics per 1936 interface." 1937 REFERENCE 1938 "Simplified Multicast Forwarding for MANET 1939 (SMF), Macker, J., July 2012." 1940 ::= { smfInterfacePerfGroup 2 } 1942 smfIpv6InterfacePerfEntry OBJECT-TYPE 1943 SYNTAX SmfIpv6InterfacePerfEntry 1944 MAX-ACCESS not-accessible 1945 STATUS current 1946 DESCRIPTION 1947 "The SMF Interface Performance entry 1948 describes the statistics for a particular 1949 node interface." 1950 INDEX { smfIfIndex } 1951 ::= { smfIpv6InterfacePerfTable 1 } 1953 SmfIpv6InterfacePerfEntry ::= 1954 SEQUENCE { 1955 smfIpv6MultiPktsRecvPerIf Counter32, 1956 smfIpv6MultiPktsForwardedPerIf Counter32, 1957 smfIpv6DuplMultiPktsDetectedPerIf Counter32, 1958 smfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1959 smfIpv6TTLLargerThanPreviousPerIf Counter32, 1960 smfIpv6HAVAssistsReqdPerIf Counter32, 1961 smfIpv6DpdHeaderInsertionsPerIf Counter32 1962 } 1964 smfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1965 SYNTAX Counter32 1966 MAX-ACCESS read-only 1967 STATUS current 1968 DESCRIPTION 1969 "A counter of the number of 1970 multicast IP packets received by the 1971 device on this interface." 1972 ::= { smfIpv6InterfacePerfEntry 1 } 1974 smfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 1975 SYNTAX Counter32 1976 MAX-ACCESS read-only 1977 STATUS current 1978 DESCRIPTION 1979 "A counter of the number of 1980 multicast IP packets forwarded by the 1981 device on this interface." 1982 ::= { smfIpv6InterfacePerfEntry 2 } 1984 smfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 1985 SYNTAX Counter32 1986 MAX-ACCESS read-only 1987 STATUS current 1988 DESCRIPTION 1989 "A counter of the number of duplicate 1990 multicast IP packets detected by the 1991 device on this interface." 1992 ::= { smfIpv6InterfacePerfEntry 3 } 1994 smfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1995 SYNTAX Counter32 1996 MAX-ACCESS read-only 1997 STATUS current 1998 DESCRIPTION 1999 "A counter of the number of dropped 2000 multicast IP packets by the 2001 device on this interface due to TTL 2002 exceeded." 2003 ::= { smfIpv6InterfacePerfEntry 4 } 2005 smfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 2006 SYNTAX Counter32 2007 MAX-ACCESS read-only 2008 STATUS current 2009 DESCRIPTION 2010 "A counter of the total number of IPv6 packets 2011 recieved which have a TTL larger than that 2012 of a previously recived identical packet." 2013 ::= { smfIpv6InterfacePerfEntry 5 } 2015 smfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 2016 SYNTAX Counter32 2017 MAX-ACCESS read-only 2018 STATUS current 2019 DESCRIPTION 2020 "A counter of the total number of IPv6 packets 2021 recieved which required the HAV assist for DPD." 2022 ::= { smfIpv6InterfacePerfEntry 6 } 2024 smfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 2025 SYNTAX Counter32 2026 MAX-ACCESS read-only 2027 STATUS current 2028 DESCRIPTION 2029 "A counter of the total number of IPv6 packets 2030 recieved which the device inserted the 2031 DPD header option." 2032 ::= { smfIpv6InterfacePerfEntry 7 } 2034 -- 2035 -- Notifications 2036 -- 2038 smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 0 } 2039 smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 } 2041 -- smfMIBNotifObjects 2043 smfAdminStatusChange NOTIFICATION-TYPE 2044 OBJECTS { smfRouterIDAddrType, -- The originator of 2045 -- the notification. 2046 smfRouterID, -- The originator of 2047 -- the notification. 2048 smfAdminStatus -- The new status of the 2049 -- SMF process. 2050 } 2051 STATUS current 2052 DESCRIPTION 2053 "smfAdminStatusChange is a notification sent when a 2054 the 'smfAdminStatus' object changes." 2056 ::= { smfMIBNotifObjects 1 } 2058 smfConfiguredOpModeChange NOTIFICATION-TYPE 2059 OBJECTS { smfRouterIDAddrType, -- The originator of 2060 -- the notification. 2061 smfRouterID, -- The originator of 2062 -- the notification. 2063 smfConfiguredOpMode -- The new Operations 2064 -- Mode of the SMF 2065 -- process. 2066 } 2067 STATUS current 2068 DESCRIPTION 2069 "smfConfiguredOpModeChange is a notification 2070 sent when a the 'smfConfiguredOpMode' object 2071 changes." 2072 ::= { smfMIBNotifObjects 2 } 2074 smfConfiguredRssaChange NOTIFICATION-TYPE 2075 OBJECTS { smfRouterIDAddrType, -- The originator of 2076 -- the notification. 2077 smfRouterID, -- The originator of 2078 -- the notification. 2079 smfConfiguredRssa -- The new RSSA for 2080 -- the SMF process. 2081 } 2082 STATUS current 2083 DESCRIPTION 2084 "smfAdminStatusChange is a notification sent when a 2085 the 'smfConfiguredRssa' object changes." 2086 ::= { smfMIBNotifObjects 3 } 2088 smfIfAdminStatusChange NOTIFICATION-TYPE 2089 OBJECTS { smfRouterIDAddrType, -- The originator of 2090 -- the notification. 2091 smfRouterID, -- The originator of 2092 -- the notification. 2093 smfIfName, -- The interface whose 2094 -- status has changed. 2095 smfIfAdminStatus -- The new status of the 2096 -- SMF interface. 2097 } 2098 STATUS current 2099 DESCRIPTION 2100 "smfIfAdminStatusChange is a notification sent when a 2101 the 'smfIfAdminStatus' object changes." 2102 ::= { smfMIBNotifObjects 4 } 2104 smfDpdMemoryOverflowEvent NOTIFICATION-TYPE 2105 OBJECTS { smfRouterIDAddrType, -- The originator of 2106 -- the notification. 2107 smfRouterID, -- The originator of 2108 -- the notification. 2109 smfDpdMemoryOverflow -- The counter of 2110 -- the overflows. 2111 } 2112 STATUS current 2113 DESCRIPTION 2114 "smfDpdMemoryOverflowEvents is sent when the 2115 number of memory overflow events exceeds the 2116 the 'smfDpdMemoryOverflowThreshold' within the 2117 previous number of seconds defined by the 2118 'smfDpdMemoryOverflowWindow'." 2119 ::= { smfMIBNotifObjects 5 } 2121 smfIpv4DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE 2122 OBJECTS { smfRouterIDAddrType, -- The originator of 2123 -- the notification. 2124 smfRouterID, -- The originator of 2125 -- the notification. 2126 smfIpv4DuplMultiPktsDetectedTotal 2127 -- The counter of detected 2128 -- duplicates. 2129 } 2130 STATUS current 2131 DESCRIPTION 2132 "smfIpv4DuplMultiPktsDetectedTotal is a 2133 notification sent when the number of 2134 IPv4 duplicate packets detected exceeds the 2135 'smfIpv4DuplMultiPktsDetectedTotalThreshold' 2136 during the previous number of seconds 2137 'smfIpv4DuplPktsDetectedTotalWindow'." 2138 ::= { smfMIBNotifObjects 6 } 2140 smfIpv6DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE 2141 OBJECTS { smfRouterIDAddrType, -- The originator of 2142 -- the notification. 2143 smfRouterID, -- The originator of 2144 -- the notification. 2145 smfIpv6DuplMultiPktsDetectedTotal 2146 -- The counter of detected 2147 -- duplicates. 2148 } 2149 STATUS current 2150 DESCRIPTION 2151 "smfIpv6DuplMultiPktsDetectedTotal is a 2152 notification sent when the number of 2153 IPv6 duplicate packets detected exceeds the 2154 'smfIpv6DuplMultiPktsDetectedTotalThreshold' 2155 during the previous number of seconds 2156 'smfIpv6DuplPktsDetectedTotalWindow'." 2157 ::= { smfMIBNotifObjects 7 } 2159 -- smfMIBNotifControl 2160 smfDpdMemoryOverflowThreshold OBJECT-TYPE 2161 SYNTAX Integer32 (0..255) 2162 MAX-ACCESS read-write 2163 STATUS current 2164 DESCRIPTION 2165 "A threshold value for the 2166 `smfDpdmemoryOverflowEvents' object. 2167 If the number of occurences exceeds 2168 this threshold within the previous 2169 number of seconds 2170 'smfDpdMemoryOverflowWindow', 2171 then the `smfDpdMemoryOverflowEvent' 2172 notification is sent." 2173 ::= { smfMIBNotifControl 1 } 2175 smfDpdMemoryOverflowWindow OBJECT-TYPE 2176 SYNTAX TimeTicks 2177 MAX-ACCESS read-write 2178 STATUS current 2179 DESCRIPTION 2180 "A time window value for the 2181 `smfDpdmemoryOverflowEvents' object. 2182 If the number of occurences exceeds 2183 the `smfDpdMemoryOverflowThreshold' 2184 within the previous number of seconds 2185 'smfDpdMemoryOverflowWindow', 2186 then the `smfDpdMemoryOverflowEvent' 2187 notification is sent." 2188 ::= { smfMIBNotifControl 2 } 2190 smfIpv4DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE 2191 SYNTAX Integer32 (0..255) 2192 MAX-ACCESS read-write 2193 STATUS current 2194 DESCRIPTION 2195 "A threshold value for the 2196 `smfIpv4DuplMultiPktsDetectedTotal' 2197 object. If the number of occurences 2198 exceeds this threshold within the 2199 previous number of seconds 2200 `smfIpv4DuplMultiPktsDetectedTotalWindow', 2201 then the 2202 `smfIpv4DuplMultiPktsDetectedTotalEvent' 2203 notification is sent." 2204 ::= { smfMIBNotifControl 3 } 2206 smfIpv4DuplMultiPktsDetectedTotalWindow OBJECT-TYPE 2207 SYNTAX TimeTicks 2208 MAX-ACCESS read-write 2209 STATUS current 2210 DESCRIPTION 2211 "A time window value for the 2212 `smfIpv4DuplMultiPktsDetectedTotalEvents' 2213 object. If the number of occurences 2214 exceeds the 2215 `smfIpv4DuplMultiPktsDetectedTotalThreshold' 2216 within the previous number of seconds 2217 'smfIpv4DuplMultiPktsDetectedTotalWindow', 2218 then the 2219 `smfIpv4DuplMultiPktsDetectedTotalEvent' 2220 notification is sent." 2221 ::= { smfMIBNotifControl 4 } 2223 smfIpv6DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE 2224 SYNTAX Integer32 (0..255) 2225 MAX-ACCESS read-write 2226 STATUS current 2227 DESCRIPTION 2228 "A threshold value for the 2229 `smfIpv6DuplMultiPktsDetectedTotal' 2230 object. If the number of occurences 2231 exceeds this threshold within the 2232 previous number of seconds 2233 `smfIpv6DuplMultiPktsDetectedTotalWindow', 2234 then the 2235 `smfIpv6DuplMultiPktsDetectedTotalEvent' 2236 notification is sent." 2237 ::= { smfMIBNotifControl 5 } 2239 smfIpv6DuplMultiPktsDetectedTotalWindow OBJECT-TYPE 2240 SYNTAX TimeTicks 2241 MAX-ACCESS read-write 2242 STATUS current 2243 DESCRIPTION 2244 "A time window value for the 2245 `smfIpv6DuplMultiPktsDetectedTotalEvents' 2246 object. If the number of occurences 2247 exceeds the 2248 `smfIpv6DuplMultiPktsDetectedTotalThreshold' 2249 within the previous number of seconds 2250 'smfIpv6DuplMultiPktsDetectedTotalWindow', 2251 then the 2252 `smfIpv6DuplMultiPktsDetectedTotalEvent' 2253 notification is sent." 2254 ::= { smfMIBNotifControl 6 } 2256 -- 2257 -- Compliance Statements 2258 -- 2260 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2261 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2263 smfBasicCompliance MODULE-COMPLIANCE 2264 STATUS current 2265 DESCRIPTION "The basic implementation requirements for 2266 managed network entities that implement 2267 the SMF RSSA process." 2268 MODULE -- this module 2269 MANDATORY-GROUPS { smfCapabObjectsGroup, 2270 smfConfigObjectsGroup } 2271 ::= { smfCompliances 1 } 2273 smfFullCompliance MODULE-COMPLIANCE 2274 STATUS current 2275 DESCRIPTION "The full implementation requirements for 2276 managed network entities that implement 2277 the SMF RSSA process." 2278 MODULE -- this module 2279 MANDATORY-GROUPS { smfCapabObjectsGroup, 2280 smfConfigObjectsGroup, 2281 smfStateObjectsGroup, 2282 smfPerfObjectsGroup, 2283 smfNotifObjectsGroup, 2284 smfNotificationsGroup 2285 } 2286 ::= { smfCompliances 2 } 2288 -- 2289 -- Units of Conformance 2290 -- 2292 smfCapabObjectsGroup OBJECT-GROUP 2293 OBJECTS { 2294 smfOpModeCapabilitiesName, 2295 smfOpModeCapabilitiesReference, 2297 smfRssaCapabilitiesName, 2298 smfRssaCapabilitiesReference 2299 } 2300 STATUS current 2301 DESCRIPTION 2302 "Set of SMF configuration objects implemented 2303 in this module." 2304 ::= { smfMIBGroups 1 } 2306 smfConfigObjectsGroup OBJECT-GROUP 2307 OBJECTS { 2308 smfAdminStatus, 2309 smfRouterIDAddrType, 2310 smfRouterID, 2311 smfIfName, 2312 smfConfiguredOpMode, 2313 smfConfiguredRssa, 2314 smfRssaMember, 2315 smfIpv4Dpd, 2316 smfIpv6Dpd, 2317 smfMaxPktLifetime, 2318 smfDpdMaxMemorySize, 2319 smfDpdEntryMaxLifetime, 2320 smfNhdpRssaMesgTLVIncluded, 2321 smfNhdpRssaAddrBlockTLVIncluded, 2323 smfConfiguredAddrForwardingLastAddr, 2324 smfConfiguredAddrForwardingStatus, 2326 smfIfAdminStatus, 2327 smfIfRowStatus 2328 } 2329 STATUS current 2330 DESCRIPTION 2331 "Set of SMF configuration objects implemented 2332 in this module." 2333 ::= { smfMIBGroups 2 } 2335 smfStateObjectsGroup OBJECT-GROUP 2336 OBJECTS { 2337 smfNodeRsStatusIncluded, 2338 smfDpdMemoryOverflow, 2340 smfDiscoveredAddrForwardingLastAddr, 2341 smfNeighborRSSA, 2342 smfNeighborNextHopInterface 2343 } 2344 STATUS current 2345 DESCRIPTION 2346 "Set of SMF state objects implemented 2347 in this module." 2348 ::= { smfMIBGroups 3 } 2350 smfPerfObjectsGroup OBJECT-GROUP 2351 OBJECTS { 2352 smfIpv4MultiPktsRecvTotal, 2353 smfIpv4MultiPktsForwardedTotal, 2354 smfIpv4DuplMultiPktsDetectedTotal, 2355 smfIpv4DroppedMultiPktsTTLExceededTotal, 2356 smfIpv4TTLLargerThanPreviousTotal, 2358 smfIpv6MultiPktsRecvTotal, 2359 smfIpv6MultiPktsForwardedTotal, 2360 smfIpv6DuplMultiPktsDetectedTotal, 2361 smfIpv6DroppedMultiPktsTTLExceededTotal, 2362 smfIpv6TTLLargerThanPreviousTotal, 2363 smfIpv6HAVAssistsReqdTotal, 2364 smfIpv6DpdHeaderInsertionsTotal, 2366 smfIpv4MultiPktsRecvPerIf, 2367 smfIpv4MultiPktsForwardedPerIf, 2368 smfIpv4DuplMultiPktsDetectedPerIf, 2369 smfIpv4DroppedMultiPktsTTLExceededPerIf, 2370 smfIpv4TTLLargerThanPreviousPerIf, 2372 smfIpv6MultiPktsRecvPerIf, 2373 smfIpv6MultiPktsForwardedPerIf, 2374 smfIpv6DuplMultiPktsDetectedPerIf, 2375 smfIpv6DroppedMultiPktsTTLExceededPerIf, 2376 smfIpv6TTLLargerThanPreviousPerIf, 2377 smfIpv6HAVAssistsReqdPerIf, 2378 smfIpv6DpdHeaderInsertionsPerIf 2379 } 2380 STATUS current 2381 DESCRIPTION 2382 "Set of SMF performance objects implemented 2383 in this module by total and per interface." 2384 ::= { smfMIBGroups 4 } 2386 smfNotifObjectsGroup OBJECT-GROUP 2387 OBJECTS { 2388 smfDpdMemoryOverflowThreshold, 2389 smfDpdMemoryOverflowWindow, 2390 smfIpv4DuplMultiPktsDetectedTotalThreshold, 2391 smfIpv4DuplMultiPktsDetectedTotalWindow, 2392 smfIpv6DuplMultiPktsDetectedTotalThreshold, 2393 smfIpv6DuplMultiPktsDetectedTotalWindow 2394 } 2395 STATUS current 2396 DESCRIPTION 2397 "Set of SMF notification control 2398 objects implemented in this module." 2399 ::= { smfMIBGroups 5 } 2401 smfNotificationsGroup NOTIFICATION-GROUP 2402 NOTIFICATIONS { 2403 smfAdminStatusChange, 2404 smfConfiguredOpModeChange, 2405 smfConfiguredRssaChange, 2406 smfIfAdminStatusChange, 2407 smfDpdMemoryOverflowEvent, 2408 smfIpv4DuplMultiPktsDetectedTotalEvents, 2409 smfIpv6DuplMultiPktsDetectedTotalEvents 2410 } 2411 STATUS current 2412 DESCRIPTION 2413 "Set of SMF notifications implemented 2414 in this module." 2415 ::= { smfMIBGroups 6 } 2417 END 2419 8. Security Considerations 2421 This section discusses security implications of the choices made in 2422 this SMF-MIB module. 2424 There are a number of management objects defined in this MIB module 2425 with a MAX-ACCESS clause of read-write and/or read-create. Such 2426 objects may be considered sensitive or vulnerable in some network 2427 environments. The support for SET operations in a non-secure 2428 environment without proper protection can have a negative effect on 2429 network operations. These are the tables and objects and their 2430 sensitivity/vulnerability: 2432 o 'smfAdminStatus' - this writable configuration object controls the 2433 operational status of the SMF process. If this setting is 2434 configured inconsistently across the MANET multicast domain, then 2435 delivery of multicast data may be inconsistent across the domain; 2436 some nodes may not receive multicast data intended for them. 2438 o 'smfRouterIDAddrType' and 'smfRouterID' - these writable 2439 configuration objects define the ID of the SMF process. These 2440 objects should be configured with a routable address defined on 2441 the local SMF device. The smfRouterID is a logical identification 2442 that MUST be consistent across inter-operating SMF neighborhoods 2443 and it is RECOMMENDED to be chosen as the numerically largest 2444 address contained in a node's 'Neighbor Address List' as defined 2445 in NHDP. A smfRouterID MUST be unique within the scope of the 2446 operating MANET network regardless of the method used for 2447 selecting it. 2449 o 'smfConfiguredOpMode' - this writable configuration objects define 2450 the operational mode of the SMF process. The operational mode 2451 defines how the SMF process develops its local estimate of the 2452 CDS. 2454 o 'smfConfiguredRssa' - this writable configuration object sets the 2455 specific Reduced Set Selection Algorithm (RSSA) for the SMF 2456 process. If this object is set inconsistently across the MANET 2457 domain, multicast delivery of data will fail. 2459 o 'smfRssaMember' - this writable configuration object sets the 2460 'interest' of the local SMF node in participating in the CDS. 2461 Setting this object to 'never(3)' on a highly highly connected 2462 device could lead to frequent island formation. Setting this 2463 object to 'always(2)' could support data ex-filtration from the 2464 MANET domain. 2466 o 'smfIpv4Dpd' - this writable configuration object sets the 2467 duplicate packet detection method for forwarding of IPv4 multicast 2468 packets. 2470 o 'smfIpv6Dpd' - this writable configuration object sets the 2471 duplicate packet detection method for forwarding of IPv6 multicast 2472 packets. 2474 o 'smfMaxPktLifetime' - this writable configuration object sets the 2475 estimate of the network packet traversal time. If set too small, 2476 this could lead to poor multicast data delivery ratios throughout 2477 the MANET domain. 2479 o 'smfDpdMaxMemorySize' - this writable configuration object sets 2480 the memory storage size (in Kilo-Bytes) for the cached DPD records 2481 for the combined IPv4 and IPv6 methods. If set too small this 2482 could lead to poor performance of the duplicate packet protection 2483 algorithms and lead to inefficient resource, e.g., link, 2484 utilization within the MANET domain. The local SMF device should 2485 protect itself against memory overruns in the event that too large 2486 a setting is requested. 2488 o 'smfDpdEntryMaxLifetime' - this writable configuration object sets 2489 the maximum lifetime (in seconds) for the cached DPD records for 2490 the combined IPv4 and IPv6 methods. If the memory is running low 2491 prior to the MaxLifetimes being exceeded, the local SMF devices 2492 should purge the oldest records first. 2494 o 'smfNhdpRssaMesgTLVIncluded' - this writable configuration object 2495 indicates whether the associated NHDP messages include the the 2496 RSSA Message TLV, or not. It is highly RECOMMENDED that this 2497 object be set to 'true(1)'. 2499 o 'smfNhdpRssaAddrBlockTLVIncluded' - this writable configuration 2500 object indicates whether the associated NHDP messages include the 2501 the RSSA Address Block TLV, or not. The 2502 smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it 2503 depends on the existence of an address block which may not be 2504 present. If this SMF device is configured with NHDP, then this 2505 object should be set to 'true(1)'. 2507 o 'smfConfiguredAddrForwardingTable' - the writable configuration 2508 objects in this table indicate which multicast IP address are to 2509 be forwarded by this SMF node. Misconfiguration of rows within 2510 this table can limit the ability of this SMF device to forward 2511 multicast data. 2513 o 'smfInterfaceTable' - the writable configuration objects in this 2514 table indicate which SMF node interfaces are participating in the 2515 SMF packet forwarding process. Misconfiguration of rows within 2516 this table can limit the ability of this SMF device to forward 2517 multicast data. 2519 Some of the readable objects in this MIB module (i.e., objects with a 2520 MAX-ACCESS other than not-accessible) may be considered sensitive or 2521 vulnerable in some network environments. It is thus important to 2522 control even GET and/or NOTIFY access to these objects and possibly 2523 to even encrypt the values of these objects when sending them over 2524 the network via SNMP. These are the tables and objects and their 2525 sensitivity/vulnerability: 2527 o 'smfNodeRsStatusIncluded' - this readable state object indicates 2528 that this SMF node is part of the CDS, or not. Being part of the 2529 CDS makes this node a distinguished device. It could be exploited 2530 for data ex-filtration, or denial of service attacks. 2532 o 'smfDiscoveredAddrForwardingTable' - the readable state objects in 2533 this table indicate which, dynamically discovered, multicast IP 2534 address are to be forwarded by this SMF node. 2536 o 'smfNeighborTable' - the readable state objects in this table 2537 indicate current neighbor nodes to this SMF node. Exposing this 2538 information to an attacker could allow the attacker easier access 2539 to the larger MANET domain. 2541 The remainder of the objects in the SMF-MIB are performance counter 2542 objects. While these give an indication of the activity of the SMF 2543 process on this node, it is not expected that exposing these values 2544 pose a security risk to the MANET network. 2546 SNMP versions prior to SNMPv3 did not include adequate security. 2547 Even if the network itself is secure (for example by using IPSec), 2548 even then, there is no control as to who on the secure network is 2549 allowed to access and GET/SET (read/change/create/delete) the objects 2550 in this MIB module. 2552 Implementations MUST provide the security features described by the 2553 SNMPv3 framework (see [RFC3410] ), including full support for 2554 authentication and privacy via the User-based Security Model (USM) 2555 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2556 MAY also provide support for the Transport Security Model (TSM) 2557 [RFC5591] in combination with a secure transport such as SSH 2558 [RFC5592] or TLS/DTLS [RFC6353]. 2560 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2561 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2562 enable cryptographic security. It is then a customer/operator 2563 responsibility to ensure that the SNMP entity giving access to an 2564 instance of this MIB module is properly configured to give access to 2565 the objects only to those principals (users) that have legitimate 2566 rights to indeed GET or SET (change/create/delete) them. 2568 9. Applicability Statement 2570 This document describes objects for configuring parameters of the 2571 Simplified Multicast Forwarding [RFC6621] process on a router. This 2572 MIB module, denoted SMF-MIB, also reports state, performance 2573 information and notifications. This sections provides some examples 2574 of how this MIB module can be used in MANET network deployments. A 2575 fuller discussion of MANET network management use cases and 2576 challenges will be provided elsewhere. 2578 SMF is designed to allow routers to forward IPv4 and IPv6 packets 2579 over the MANET and cover the MANET nodes through the automatic 2580 discovery of efficient estimates of the Minimum Connected Dominating 2581 Set (MCDS) of nodes within the MANET. The MCDS are estimated using 2582 the RSSAs discussed within this document. In the following, three 2583 scenarios are listed where this MIB module is useful, i.e., 2585 o For a Parking Lot Initial Configuration Situation - it is common 2586 for the vehicles comprising the MANET being forward deployed at a 2587 remote location, e.g., the site of a natural disaster, to be off- 2588 loaded in a parking lot where an initial configuration of the 2589 networking devices is performed. The configuration is loaded into 2590 the devices from a fixed location Network Operation Center (NOC) 2591 at the parking lot and the vehicles are stationary at the parking 2592 lot while the configuration changes are made. Standards-based 2593 methods for configuration management from the co-located NOC are 2594 necessary for this deployment option. 2596 o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed 2597 NOC - Here the vehicles carrying the MANET routers carry multiple 2598 wireless interfaces, one of which is a relatively low-bandwidth 2599 on-the-move satellite connection which interconnects a fix NOC to 2600 the nodes of the MANET. Standards-based methods for monitoring 2601 and fault management from the fixed NOC are necessary for this 2602 deployment option. 2604 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 2605 larger vehicles, a hierarchical network management arrangement is 2606 useful. Centralized network management is performed from a fixed 2607 NOC while local management is performed locally from within the 2608 vehicles. Standards-based methods for configuration, monitoring 2609 and fault management are necessary for this deployment option. 2611 10. IANA Considerations 2613 The MIB module in this document uses the following IANA-assigned 2614 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 2616 Descriptor OBJECT IDENTIFIER value 2617 ---------- ----------------------- 2618 SMF-MIB { experimental XXXX } 2619 IANA EDITOR NOTE: please assign XXXX 2621 11. Contributors 2623 This MIB document uses the template authored by D. Harrington which 2624 is based on contributions from the MIB Doctors, especially Juergen 2625 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2627 12. Acknowledgements 2629 The authors would like to acknowledge the valuable comments from Sean 2630 Harnedy in the early phases of the development of this MIB-module. 2631 The authors would like to thank James Nguyen for his careful review 2632 and comments on this MIB-module and his work on the definitions of 2633 the follow on MIB-modules to configure specific RSSA algorithms 2634 related to SMF. Further, the authors would like to acknowledge to 2635 work of James Nguyen, Brian Little and Ryan Morgan on their software 2636 development of the SMF-MIB. 2638 13. References 2640 13.1. Normative References 2642 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2643 MIB", RFC 2863, June 2000. 2645 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2646 Architecture for Describing Simple Network Management 2647 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2648 December 2002. 2650 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 2651 Simple Network Management Protocol (SNMP)", STD 62, 2652 RFC 3418, December 2002. 2654 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2655 Schoenwaelder, "Textual Conventions for Internet Network 2656 Addresses", RFC 4001, February 2005. 2658 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2659 Requirement Levels", BCP 14, RFC 2119, March 1997. 2661 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2662 Schoenwaelder, Ed., "Structure of Management Information 2663 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2665 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2666 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2667 STD 58, RFC 2579, April 1999. 2669 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2670 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2671 April 1999. 2673 [RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621, 2674 May 2012. 2676 13.2. Informative References 2678 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2679 "Introduction and Applicability Statements for Internet- 2680 Standard Management Framework", RFC 3410, December 2002. 2682 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2683 (USM) for version 3 of the Simple Network Management 2684 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 2686 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 2687 Advanced Encryption Standard (AES) Cipher Algorithm in the 2688 SNMP User-based Security Model", RFC 3826, June 2004. 2690 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2691 for the Simple Network Management Protocol (SNMP)", 2692 RFC 5591, June 2009. 2694 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 2695 Shell Transport Model for the Simple Network Management 2696 Protocol (SNMP)", RFC 5592, June 2009. 2698 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 2699 Model for the Simple Network Management Protocol (SNMP)", 2700 RFC 6353, July 2011. 2702 Appendix A. Change Log 2704 This section tracks the revision history in the development of this 2705 SMF-MIB. It will be removed from the final version of this document. 2707 These changes were made from draft-ietf-manet-smf-mib-05 to 2708 draft-ietf-manet-smf-mib-06. 2710 1. Only minor editorial and formatting changes were made to this 2711 document revision. No substantive changes were made to the SMF- 2712 MIB module itself. 2714 These changes were made from draft-ietf-manet-smf-mib-04 to 2715 draft-ietf-manet-smf-mib-05. 2717 1. Updated the smfInterfaceTable to reflect that fact that we want 2718 it to 'sparsely augment' the ifTable. 2720 2. Added a section to the text discussing the SMF Tables and their 2721 indexing. 2723 3. Added the section on 'Applicability Statement'. 2725 4. Added/checked for DEFVAL, REFERENCES, UNITS and SIZE clauses 2726 within the MIB. 2728 These changes were made from draft-ietf-manet-smf-mib-03 to 2729 draft-ietf-manet-smf-mib-04. 2731 1. Removed the bitmap switch in the notifications control group. 2733 2. Moved the notification Objects group up to support reverse- 2734 mapping between SNMPv1 traps and SNMPv2 notifications. 2736 3. Removed reference to the notifications state group. 2738 4. Replaced smfIfIndex with smfIfName in notifications. 2740 These changes were made from draft-ietf-manet-smf-mib-02 to 2741 draft-ietf-manet-smf-mib-03. 2743 1. Clarified and added discussion of default values for several of 2744 the configuration objects within the MIB. 2746 2. Added the security section. 2748 These changes were made from draft-ietf-manet-smf-mib-01 to 2749 draft-ietf-manet-smf-mib-02. 2751 1. Added the NotificationGroup to the MIB and updated the 2752 ConformanceGroup. 2754 2. Added the definition of an smfRouterID to the MIB. This is later 2755 used in the Notifications to indicate the origin of the event to 2756 the management station. 2758 3. Removed the Router Priority object as this was used only in the 2759 eCDS algorithm and hence should be contained within the future 2760 eCDS-MIB. 2762 4. Cleaned up the TEXTUAL CONVENTION for the `SmfOpMode'. 2764 5. Filled in some of the missing text in various object 2765 descriptions. 2767 These changes were made from draft-ietf-manet-smf-mib-00 to 2768 draft-ietf-manet-dsmf-mib-01. 2770 1. Editorial changes to the textual material. These included the 2771 addition of the paragraphs on TEXTUAL-CONVENTIONS defined and 2772 imported into this MIB and relationships to other MIBs. 2774 2. Identified those objects in the SMF-MIB requiring non-volatile 2775 storage. 2777 3. Changed the name of the TEXTUAL-CONVENTION 'Status', defined 2778 within this MIB to 'SmfStatus'. 2780 Appendix B. Open Issues 2782 This section contains the set of open issues related to the 2783 development and design of the SMF-MIB. This section will not be 2784 present in the final version of the MIB and will be removed once all 2785 the open issues have been resolved. 2787 1. A careful review by the working group. 2789 Appendix C. 2791 *************************************************************** 2792 * Note to the RFC Editor (to be removed prior to publication) * 2793 * * 2794 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 2795 * of the MIB module point to this draft and are to be * 2796 * assigned by the RFC Editor. * 2797 * * 2798 *************************************************************** 2800 Authors' Addresses 2802 Robert G. Cole 2803 US Army CERDEC 2804 6010 Frankford Road 2805 Aberdeen Proving Ground, Maryland 21005 2806 USA 2808 Phone: +1 443 395 8744 2809 EMail: robert.g.cole@us.army.mil 2810 URI: http://www.cs.jhu.edu/~rgcole/ 2812 Joseph Macker 2813 Naval Research Laboratory 2814 Washington, D.C. 20375 2815 USA 2817 EMail: macker@itd.nrl.navy.mil 2819 Brian Adamson 2820 Naval Research Laboratory 2821 Washington, D.C. 20375 2822 USA 2824 EMail: adamson@itd.nrl.navy.mil