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