idnits 2.17.1 draft-ietf-manet-smf-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1092 has weird spacing: '...(1) and ipv6(...' == 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. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: o 'smfCfgIpv6Dpd' - this writable configuration object sets the duplicate packet detection method for forwarding of IPv6 multicast packets. Since IPv6 SMF does specifies an option header, the interoperability constraints are not as loose as in the IPv4 version, and forwarders SHOULD not operate with mixed H-DPD and I-DPD modes. Hence the value for this object SHOULD be consistently set within the forwarders comprising the MANET, else inconsistent forwarding may result unnecessary multicast packet dropping. -- The document date (January 20, 2014) is 3720 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'SMF' is mentioned on line 486, but not defined == Missing Reference: 'RFC3626' is mentioned on line 2835, but not defined == Missing Reference: 'RFC5614' is mentioned on line 2841, but not defined Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force R. Cole 3 Internet-Draft US Army CERDEC 4 Intended status: Experimental J. Macker 5 Expires: July 24, 2014 B. Adamson 6 Naval Research Laboratory 7 January 20, 2014 9 Definition of Managed Objects for the Manet Simplified Multicast 10 Framework Relay Set Process 11 draft-ietf-manet-smf-mib-09 13 Abstract 15 This memo defines a portion of the Management Information Base (MIB) 16 for use with network management protocols in the Internet community. 17 In particular, it describes objects for configuring aspects of the 18 Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc 19 Networks (MANETs). The SMF-MIB module also reports state 20 information, performance information, and notifications. In addition 21 to configuration, the additional state and performance information is 22 useful to operators troubleshooting multicast forwarding problems. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on July 24, 2014. 41 Copyright Notice 43 Copyright (c) 2014 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. The Internet-Standard Management Framework . . . . . . . . . . 3 60 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 63 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 65 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 66 5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6 67 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7 68 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7 69 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7 70 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8 71 5.7. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 72 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 73 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 74 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 75 6.3. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10 76 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 77 8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 78 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 54 79 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 80 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 56 81 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 56 82 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56 83 13.1. Normative References . . . . . . . . . . . . . . . . . . . 56 84 13.2. Informative References . . . . . . . . . . . . . . . . . . 57 85 Appendix A. Appendix A: . . . . . . . . . . . . . . . . . . . . . 58 86 Appendix B. Appendix B: . . . . . . . . . . . . . . . . . . . . . 60 87 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 63 89 1. Introduction 91 This memo defines a portion of the Management Information Base (MIB) 92 for use with network management protocols in the Internet community. 93 In particular, it describes objects for configuring aspects of a 94 process implementing Simplified Multicast Forwarding (SMF) [RFC6621] 95 for Mobile Ad-Hoc Networks (MANETs). SMF provides multicast 96 Duplicate Packet Detection (DPD) and supports algorithms for 97 constructing an estimate of a MANET Minimum Connected Dominating Set 98 (MCDS) for efficient multicast forwarding. The SMF-MIB module also 99 reports state information, performance information, and 100 notifications. In addition to configuration, this additional state 101 and performance information is useful to operators troubleshooting 102 multicast forwarding problems. 104 2. The Internet-Standard Management Framework 106 For a detailed overview of the documents that describe the current 107 Internet-Standard Management Framework, please refer to section 7 of 108 RFC 3410 [RFC3410]. 110 Managed objects are accessed via a virtual information store, termed 111 the Management Information Base or MIB. MIB objects are generally 112 accessed through the Simple Network Management Protocol (SNMP). 113 Objects in the MIB are defined using the mechanisms defined in the 114 Structure of Management Information (SMI). This memo specifies a MIB 115 module that is compliant to the SMIv2, which is described in STD 58, 116 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 117 [RFC2580]. 119 3. Conventions 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 4. Overview 127 SMF provides methods for implementing Duplicate Packet Detection 128 (DPD)-based multicast forwarding with the optional use of Connected 129 Dominating Set (CDS)-based relay sets. The CDS provides a complete 130 connected coverage of the nodes comprising the MANET. The Minimum 131 CDS (MCDS) is the smallest set of MANET nodes (comprising a connected 132 cluster) which cover all the nodes in the cluster with their 133 transmissions. As the density of the MANET nodes increase, the 134 fraction of nodes required in an MCDS decreases. Using the MCDS as a 135 multicast forwarding set then becomes an efficient multicast 136 mechanism for MANETs. 138 Various algorithms for the construction of estimates of the MCDS 139 exist. The Simplified Multicast Framework [RFC6621] describes some 140 of these. It further defines various operational modes for a node 141 which is participating in the collective creation of the MCDS 142 estimates. These modes depend upon the set of related MANET routing 143 and discovery protocols and mechanisms in operation in the specific 144 MANET node. 146 A SMF router's MIB module contains SMF process configuration 147 parameters (e.g. specific CDS algorithm), state information (e.g., 148 current membership in the CDS), performance counters (e.g., packet 149 counters), and notifications. 151 4.1. SMF Management Model 153 This section describes the management model for the SMF node process. 155 Figure 1 (reproduced from Figure 1 of [RFC6621]) shows the 156 relationship between the SMF Relay Set selection algorithm and the 157 related algorithms, processes and protocols running in the MANET 158 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 159 topology information gotten from the MANET Neighborhood Discovery 160 Protocol (NHDP), from the specific MANET routing protocol running on 161 the node, or from Layer 2 information passed up to the higher layer 162 protocol processes. 164 ______________ ____________ 165 | | | | 166 | Neighborhood | | Relay Set | 167 | Discovery |------------->| Selection | 168 | | neighbor | | 169 |______________| info |____________| 170 \ / 171 \ / 172 neighbor\ / forwarding 173 info \ _____________ / status 174 \ | | / 175 `-->| Forwarding |<--' 176 | Process | 177 ----------------->|_____________|-----------------> 178 incoming packet, forwarded packets 179 interface id , and 180 previous hop 182 Figure 1: SMF Router Architecture 184 4.2. Terms 186 The following definitions apply throughout this document: 188 o Configuration Objects - switches, tables, objects which are 189 initialized to default settings or set through the management 190 interfaces such as defined by this MIB module. 192 o Tunable Configuration Objects - objects whose values affect timing 193 or attempt bounds on the SMF Relay Set (RS) process. 195 o State Objects - automatically generated values which define the 196 current operating state of the SMF RS process in the router. 198 o Performance Objects - automatically generated values which help an 199 administrator or automated tool to assess the performance of the 200 CDS multicast process on the router and the overall multicast 201 performance within the MANET routing domain. 203 5. Structure of the MIB Module 205 This section presents the structure of the SMF-MIB module. The 206 objects are arranged into the following groups: 208 o smfMIBNotifications - defines the notifications associated with 209 the SMF process. 211 o smfMIBObjects - defines the objects forming the basis for the SMF- 212 MIB module. These objects are divided up by function into the 213 following groups: 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 process and the resulting multicast performance. 223 * State Group - Contains information describing the current state 224 of the SMF process such as the Neighbor Table. 226 * Performance Group - Contains objects which help to characterize 227 the performance of the SMF process, typically counters for 228 statistical computations. 230 o smfMIBConformance - defines two, i.e., minimal and full, 231 conformance implementations for the SMF-MIB module. 233 5.1. Textual Conventions 235 The textual conventions defined within the SMF-MIB module are: 237 o The SmfStatus is defined within the SMF-MIB module. This contains 238 the current operational status of the SMF process on an interface. 240 The textual conventions defined for the SMF-MIB module and maintained 241 by IANA are: 243 o The IANAsmfOpModeIdTC represents an index that identifies a 244 specific SMF operational mode. This textual convention is 245 maintained by IANA in the IANAsmfOpModeID-MIB. 247 o The IANAsmfRssaIdTC represents an index that identifies, through 248 reference, a specific RSSA available for operation on the device. 249 This textual convention is maintained by IANA in the 250 IANAsmfRssaID-MIB. 252 5.2. The Capabilities Group 254 The SMF device supports a set of capabilities. The list of 255 capabilities which the device can advertise are: 257 o Operational Mode - topology information from NHDP, CDS-aware 258 unicast routing or Cross-layer from Layer 2. 260 o SMF RSSA - the specific RSSA operational on the device. Note that 261 configuration, state and performance objects related to a specific 262 RSSA must be defined within a separate MIB module. 264 5.3. The Configuration Group 266 The SMF device is configured with a set of controls. Some of the 267 prominent configuration controls for the SMF device are: 269 o Operational Mode - determines where topology information is 270 derived from, e.g., NHDP, CDS-aware unicast routing or Cross-layer 271 from Layer 2. 273 o SMF RSSA - the specific RSSA operational on the device. 275 o Duplicate Packet detection for IPv4 - Identification-based or 276 Hash-based DPD. 278 o Duplicate Packet detection for IPv6 - Identification-based or 279 Hash-based DPD. 281 o SMF Type Message TLV - if NHDP mode is selected, then the SMF Type 282 Message TLV MAY be included in the NHDP exchanges. 284 o SMF Address Block TLV - if NHDP mode is selected, then the SMF 285 Address Block TLV SHOULD be included in the NHDP exchanges. 287 5.4. The State Group 289 The State sub-tree reports current state information, e.g., 291 o Node RSSA State - identifies whether the node is currently in or 292 out of the Relay Set. 294 o Neighbors Table - a table containing current one-hop neighbors and 295 their operational RSSA. 297 5.5. The Performance Group 299 The Performance sub-tree reports primarily counters that relate to 300 SMF RSSA performance. The SMF performance counters consists of per 301 node and per interface objects: 303 o Total multicast packets received. 305 o Total multicast packets forwarded. 307 o Total duplicate multicast packets detected. 309 o Per interface statistics table with the following entries: 311 * Multicast packets received. 313 * Multicast packets forwarded. 315 * Duplicate multicast packets detected. 317 5.6. The Notifications Group 319 The Notifications Sub-tree contains the list of notifications 320 supported within the SMF-MIB module and their intended purpose and 321 utility. 323 5.7. Tables and Indexing 325 The SMF-MIB module contains a number of tables which record data 326 related to: 328 o configuration and operation of packet forwarding on the local 329 router, 331 o configuration and operation of local MANET interfaces on the 332 router, and 334 o configuration and operation of various RSSA algorithms for packet 335 forwarding. 337 The SMF-MIB module's tables are indexed via the following constructs: 339 o smfCapabilitiesIndex - the index identifying the combination of 340 SMF mode and SMF RSSA available on this device. 342 o smfCfgAddrForwardingAddrType, smfCfgAddrForwardingAddress and 343 smfCfgAddrForwardingAddrPreficLength - indexes to configured 344 multicast addresses which are forwarded by the SMF process. 346 o smfCfgIfIndex - the IfIndex of the interface on the local router 347 on which SMF is configured. 349 o smfStateNeighborIpAddrType, smfStateNeighborIpAddr, and 350 smfStateNeighborPrefixLen - the interface index set of specific 351 one-hop neighbor nodes to this local router. 353 These tables and their associated indexing are: 355 o smfCapabilitiesTable - identifies the resident set of (SMF 356 Operational Modes, SMF RSSA algorithms) available on this router. 357 This table has 'INDEX { smfCapabilitiesIndex }. 359 o smfCfgAddrForwardingTable - contains information on multicast 360 addresses which are to be forwarded by the SMF process on this 361 device. This table has 'INDEX { smfCfgAddrForwardingAddrType, 362 smfCfgAddrForwardingAddress, smfCfgAddrForwardingAddrPrefixLength 363 }'. 365 o smfCfgInterfaceTable - describes the SMF interfaces on this device 366 that are participating in the SMF packet forwarding process. This 367 table has 'INDEX { smfCfgIfIndex }'. 369 o smfStateNeighborTable - describes the current neighbor nodes, 370 their addresses and the SMF RSSA and the interface on which they 371 can be reached. This table has 'INDEX { 372 smfStateNeighborIpAddrType, smfStateNeighborIpAddr, 373 smfStateNeighborPrefixLen }'. 375 o smfPerfIpv4InterfacePerfTable - contains the IPv4 related SMF 376 statistics per each SMF interface on this device. This table has 377 'INDEX { smfCfgIfIndex }'. 379 o smfPerfIpv6InterfacePerfTable - contains the IPv6 related SMF 380 statistics per each SMF interface on this device. This table has 381 'INDEX { smfCfgIfIndex }'. 383 6. Relationship to Other MIB Modules 385 6.1. Relationship to the SNMPv2-MIB 387 The 'system' group in the SNMPv2-MIB module [RFC3418] is defined as 388 being mandatory for all systems, and the objects apply to the entity 389 as a whole. The 'system' group provides identification of the 390 management entity and certain other system-wide data. The SMF-MIB 391 module does not duplicate those objects. 393 6.2. MIB modules required for IMPORTS 395 The textual conventions imported for use in the SMF-MIB module are as 396 follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 397 Counter32, Unsigned32, Integer32 and mib-2 textual conventions are 398 imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 399 and TruthValue textual conventions are imported from RFC 2579 400 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- 401 GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 402 InterfaceIndexOrZero textual convention is imported from RFC 2863 403 [RFC2863]. The SnmpAdminString textual convention is imported from 404 RFC 3411 [RFC3411]. The InetAddress, InetAddressType and 405 InetAddressPrefixLength textual conventions are imported from RFC 406 4001 [RFC4001]. 408 6.3. Relationship to the Future RSSA-MIB Moduless 410 In a sense, the SMF-MIB module is a general front-end to a set of, 411 yet to be developed, RSSA-specific MIB modules. These RSSA-specific 412 MIB modules will define the objects for the configuration, state, 413 performance and notification required for the operation of these 414 specific RSSAs. The SMF-MIB module Capabilities Group allows the 415 remote management station the ability to query the router to discover 416 the set of supported RSSAs. 418 7. Definitions 420 SMF-MIB DEFINITIONS ::= BEGIN 422 IMPORTS 424 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 425 Counter32, Integer32, TimeTicks, experimental 426 FROM SNMPv2-SMI -- [RFC2578] 428 TEXTUAL-CONVENTION, RowStatus, TruthValue 429 FROM SNMPv2-TC -- [RFC2579] 431 MODULE-COMPLIANCE, OBJECT-GROUP, 432 NOTIFICATION-GROUP 433 FROM SNMPv2-CONF -- [RFC2580] 435 InterfaceIndexOrZero 436 FROM IF-MIB -- [RFC2863] 438 SnmpAdminString 439 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 441 InetAddress, InetAddressType, 442 InetAddressPrefixLength 443 FROM INET-ADDRESS-MIB -- [RFC4001] 445 IANAsmfOpModeIdTC 446 FROM IANAsmfOpModeID-MIB 448 IANAsmfRssaIdTC 449 FROM IANAsmfRssaID-MIB 450 ; 452 smfMIB MODULE-IDENTITY 453 LAST-UPDATED "201309011300Z" -- September 01, 2013 454 ORGANIZATION "IETF MANET Working Group" 455 CONTACT-INFO 456 "WG E-Mail: manet@ietf.org 458 WG Chairs: sratliff@cisco.com 459 jmacker@nrl.navy.mil 461 Editors: Robert G. Cole 462 US Army CERDEC 463 Space and Terrestrial Communications 464 6010 Frankford Road 465 Aberdeen Proving Ground, MD 21005 466 USA 467 +1 443 395-8744 468 robert.g.cole@us.army.mil 470 Joseph Macker 471 Naval Research Laboratory 472 Washington, D.C. 20375 473 USA 474 macker@itd.nrl.navy.mil 476 Brian Adamson 477 Naval Research Laboratory 478 Washington, D.C. 20375 479 USA 480 adamson@itd.nrl.navy.mil" 482 DESCRIPTION 483 "This MIB module contains managed object definitions for 484 the Manet SMF RSSA process defined in: 486 [SMF] Macker, J.(ed.), 487 Simplified Multicast Forwarding, RFC 6621, 488 May 2012. 490 Copyright (C) The IETF Trust (2012). This version 491 of this MIB module is part of RFC xxxx; see the RFC 492 itself for full legal notices." 494 -- Revision History 495 REVISION "201309011300Z" -- September 01, 2013 496 DESCRIPTION 497 "The first version of this MIB module, 498 published as RFC xxxx. 499 " 500 -- RFC-Editor assigns xxxx 501 ::= { experimental xxxx } -- to be assigned by IANA 503 -- 504 -- TEXTUAL CONVENTIONs 505 -- 507 SmfStatus ::= TEXTUAL-CONVENTION 508 STATUS current 509 DESCRIPTION 510 "An indication of the operability of a SMF 511 function or feature. For example, the status 512 of an interface: 'enabled' indicates that 513 this interface is performing SMF functions, 514 and 'disabled' indicates that it is not. 515 Similarly for the status of the device: 516 'enabled' indicates that the device has 517 enabled the SMF functions on the device and 518 'disabled' means that the device and all interfaces 519 have disabled all SMF functions." 520 SYNTAX INTEGER { 521 enabled (1), 522 disabled (2) 523 } 525 -- 526 -- Top-Level Object Identifier Assignments 527 -- 529 smfMIBNotifications OBJECT IDENTIFIER ::= { smfMIB 0 } 530 smfMIBObjects OBJECT IDENTIFIER ::= { smfMIB 1 } 531 smfMIBConformance OBJECT IDENTIFIER ::= { smfMIB 2 } 533 -- 534 -- smfMIBObjects Assignments: 535 -- smfCapabilitiesGroup - 1 536 -- smfConfigurationGroup - 2 537 -- smfStateGroup - 3 538 -- smfPerformanceGroup - 4 539 -- 541 -- 542 -- smfCapabilitiesGroup 543 -- 544 -- This group contains the SMF objects that identify specific 545 -- capabilities within this device related to SMF functions. 546 -- 548 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 550 -- 551 -- SMF Capabilities Table 552 -- 554 smfCapabilitiesTable OBJECT-TYPE 555 SYNTAX SEQUENCE OF SmfCapabilitiesEntry 556 MAX-ACCESS not-accessible 557 STATUS current 558 DESCRIPTION 559 "The smfCapabilitiesTable identifies the 560 resident set of SMF Operational Modes and 561 RSSA combinations that can run on this 562 forwarder." 563 REFERENCE 564 "See Section 7.2. 'Reduced Relay Set Forwarding', 565 Section 8.1.1. 'SMF Message TLV Type', and 566 the Appendices A, B and C in 567 RFC 6621 - Simplified Multicast Forwarding 568 (SMF), Macker, J., May 2012." 569 ::= { smfCapabilitiesGroup 1 } 571 smfCapabilitiesEntry OBJECT-TYPE 572 SYNTAX SmfCapabilitiesEntry 573 MAX-ACCESS not-accessible 574 STATUS current 575 DESCRIPTION 576 "Information about a particular operational 577 mode and RSSA combination. 578 " 579 INDEX { smfCapabilitiesIndex } 580 ::= { smfCapabilitiesTable 1 } 582 SmfCapabilitiesEntry ::= SEQUENCE { 583 smfCapabilitiesIndex Integer32, 584 smfCapabilitiesOpModeID IANAsmfOpModeIdTC, 585 smfCapabilitiesRssaID IANAsmfRssaIdTC 586 } 588 smfCapabilitiesIndex OBJECT-TYPE 589 SYNTAX Integer32 (1..2147483647) 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "The index for this entry; a unique value, 594 greater than zero, for each combination of 595 a particular operational mode and RSSA 596 algorithm available on this device. 597 It is recommended that values are assigned 598 contiguously starting from 1. 600 Rows in this table are automatically 601 populated by the entity's management system 602 on initialization. 604 By default, the agent should support at least the 605 Classical Flooding 'cF' algorithm. All compliant 606 SMF forwarders must support Classical Flooding. 607 Hence, the first entry in this table MUST exist 608 and MUST be defined as: 610 smfCapabilitiesIndex i '1' 611 smfCapabilitiesOpModeID i 'cfOnly(1)' 612 smfCapabilitiesRssaID i 'cF(1)' 614 The value for each combination MUST remain 615 constant at least from one re-initialization 616 of the entity's management system to the 617 next re-initialization." 618 ::= { smfCapabilitiesEntry 1 } 620 smfCapabilitiesOpModeID OBJECT-TYPE 621 SYNTAX IANAsmfOpModeIdTC 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "This object identifies 626 the particular operational mode for this device." 627 ::= { smfCapabilitiesEntry 2 } 629 smfCapabilitiesRssaID OBJECT-TYPE 630 SYNTAX IANAsmfRssaIdTC 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "This object identifies 635 the particular RSSA algorithm in this MIB 636 module. Example RSSAs are found in the 637 appendix of RFC 6621." 638 REFERENCE 639 "See, e.g., Section 8.1.1. 'SMF Message TLV Type', 640 and the Appendices A, B and C in 641 RFC 6621 - Simplified Multicast Forwarding 642 (SMF), Macker, J., May 2012." 643 ::= { smfCapabilitiesEntry 3 } 645 -- 646 -- smfConfigurationGroup 647 -- 648 -- This group contains the SMF objects that configure specific 649 -- options that determine the overall performance and operation 650 -- of the multicast forwarding process for the router device 651 -- and its interfaces. 652 -- 654 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 656 smfCfgAdminStatus OBJECT-TYPE 657 SYNTAX SmfStatus 658 MAX-ACCESS read-write 659 STATUS current 660 DESCRIPTION 661 "The configured status of the SMF process 662 on this device. 'enabled(1)' means that 663 SMF is configured to run on this device. 664 'disabled(2)' mean that the SMF process 665 is configured off. 667 Prior to SNM functions being performed over 668 specific interfaces, this object must first 669 be 'enabled'. If this object is 'disabled', 670 then no SMF functions are being performed on 671 the device and all smfIfAdminStatus objects 672 MUST also be set to 'disabled'. When this 673 object is changed from 'enabled' to 'disabled' 674 by the manager, then all smfIfAdminStatus 675 objects MUST also be automatically set to 676 'disabled' by the agent. 678 The default value for this object SHOULD be 679 'enabled'. 681 This object is persistent and when written 682 the entity SHOULD save the change to 683 non-volatile storage." 684 DEFVAL { enabled } 685 ::= { smfConfigurationGroup 1 } 687 smfCfgSmfSysUpTime OBJECT-TYPE 688 SYNTAX TimeTicks 689 MAX-ACCESS read-only 690 STATUS current 691 DESCRIPTION 692 "The time (in hundredths of a second) since the 693 system SMF process was last re-initialized. 694 The SMF process is re-initialized when the 695 value of the 'smfCfgAdminStatus' object 696 transitions to 'enabled' from either a prior 697 value of 'disabled' or upon initialization 698 of this device." 699 ::= { smfConfigurationGroup 2 } 701 smfCfgRouterIDAddrType OBJECT-TYPE 702 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 703 MAX-ACCESS read-write 704 STATUS current 705 DESCRIPTION 706 "The address type of the address used for 707 SMF ID of this router as specified 708 in the 'smfCfgRouterID' next. 710 Only the values ipv4(1) and ipv6(2) 711 are supported. 713 This object is persistent and when written 714 the entity SHOULD save the change to 715 non-volatile storage." 716 DEFVAL { ipv4 } 717 ::= { smfConfigurationGroup 3 } 719 smfCfgRouterID OBJECT-TYPE 720 SYNTAX InetAddress (SIZE(4|16)) 721 MAX-ACCESS read-write 722 STATUS current 723 DESCRIPTION 724 "The IP address used as the SMF router ID. 725 This can be set by the management station. 726 If not explicitly set, then the device 727 SHOULD select a routable IP address 728 assigned to this router for use as 729 the 'smfCfgRouterID'. 731 The smfCfgRouterID is a logical identification 732 that MUST be consistent across interoperable 733 SMF neighborhoods and it is RECOMMENDED to be 734 chosen as the numerically largest address 735 contained in a node's 'Neighbor Address List' 736 as defined in NHDP. A smfCfgRouterID MUST be 737 unique within the scope of the operating 738 MANET network regardless of the method used 739 for selecting it. 741 This object is persistent and when written 742 the entity SHOULD save the change to 743 non-volatile storage." 744 REFERENCE 745 "See, e.g., 747 Appendix Section A.1. 'E-CDS Relay Set 748 Selection Overview' and 750 Appendix Secdtion C.1. 'MPR-CDS Relay 751 Set Selection Overview' 753 in RFC 6621 - Simplified Multicast Forwarding 754 (SMF), Macker, J., May 2012." 755 ::= { smfConfigurationGroup 4 } 757 smfCfgOperationalMode OBJECT-TYPE 758 SYNTAX Integer32 (1..2147483647) 759 MAX-ACCESS read-write 760 STATUS current 761 DESCRIPTION 762 "The SMF RSS node operational mode and 763 RSSA algorithm combination active on this 764 local forwarder. This object is defined 765 to be equal to the smfCapabilitiesIndex 766 which identifies the specific active 767 operational mode and RSSA. 769 The default value for this object is 770 '1' which corresponds to: 772 smfCapabilitiesOpModeID i 'cfOnly(1)' 773 smfCapabilitiesRssaID i 'cF(1)' 775 This object is persistent and when written 776 the entity SHOULD save the change to 777 non-volatile storage." 778 REFERENCE 779 "See Section 7.2. 'Reduced Relay Set Forwarding', 780 and the Appendices A, B and C in 781 RFC 6621 - Simplified Multicast Forwarding 782 (SMF), Macker, J., May 2012." 783 DEFVAL { 1 } 784 ::= { smfConfigurationGroup 5 } 786 smfCfgRssaMember OBJECT-TYPE 787 SYNTAX INTEGER { 788 potential(1), 789 always(2), 790 never(3) 791 } 792 MAX-ACCESS read-write 793 STATUS current 794 DESCRIPTION 795 "The RSSA downselects a set of forwarders for 796 multicast forwarding. Sometimes it is useful 797 to force an agent to be included or excluded 798 from the resulting RSS. This object is a 799 switch to allow for this behavior. 801 The value 'potential(1)' allows the selected 802 RSSA to determine if this agent is included 803 or excluded from the RSS. 805 The value 'always(2)' forces the selected 806 RSSA include this agent in the RSS. 808 The value 'never(3)' forces the selected 809 RSSA to exclude this agent from the RSS. 811 The default setting for this object is 812 'potential(1)'. Other settings could pose 813 operational risks under certain conditions. 815 This object is persistent and when written 816 the entity SHOULD save the change to 817 non-volatile storage." 818 REFERENCE 819 "See Section 7. 'Relay Set Selection' in 820 RFC 6621 - Simplified Multicast Forwarding 821 (SMF), Macker, J., May 2012." 822 DEFVAL { potential } 824 ::= { smfConfigurationGroup 6 } 826 smfCfgIpv4Dpd OBJECT-TYPE 827 SYNTAX INTEGER { 828 hashBased(1), 829 identificationBased(2) 830 } 831 MAX-ACCESS read-write 832 STATUS current 833 DESCRIPTION 834 "The current method for IPv4 duplicate packet 835 detection. 837 The value 'hashBased(1)' indicates that the 838 routers duplicate packet detection is based 839 upon comparing a hash over the packet fields. 840 This is the default setting for this object. 842 The value 'identificationBased(2)' 843 indicates that the duplicate packet 844 detection relies upon header information 845 in the multicast packets to identify 846 previously received packets. 848 This object is persistent and when written 849 the entity SHOULD save the change to 850 non-volatile storage." 851 REFERENCE 852 "See Section 6.2. 'IPv4 Duplicate Packet 853 Detection' in RFC 6621 - Simplified 854 Multicast Forwarding (SMF), Macker, J., 855 May 2012." 856 DEFVAL { hashBased } 857 ::= { smfConfigurationGroup 7 } 859 smfCfgIpv6Dpd OBJECT-TYPE 860 SYNTAX INTEGER { 861 hashBased(1), 862 identificationBased(2) 863 } 864 MAX-ACCESS read-write 865 STATUS current 866 DESCRIPTION 867 "The current method for IPv6 duplicate packet 868 detection. 870 The values indicate the type of method used 871 for duplicate packet detection as described 872 the previous description for the object 873 `smfCfgIpv4Dpd'. 875 The default value for this object is 876 'hashBased(1)'. 878 This object is persistent and when written 879 the entity SHOULD save the change to 880 non-volatile storage." 881 REFERENCE 882 "See Section 6.1. 'IPv6 Duplicate Packet 883 Detection' in RFC 6621 - Simplified 884 Multicast Forwarding (SMF), Macker, J., 885 May 2012." 886 DEFVAL { hashBased } 887 ::= { smfConfigurationGroup 8 } 889 smfCfgMaxPktLifetime OBJECT-TYPE 890 SYNTAX Integer32 (0..65535) 891 UNITS "Seconds" 892 MAX-ACCESS read-write 893 STATUS current 894 DESCRIPTION 895 "The estimate of the network packet 896 traversal time. 898 This object is persistent and when written 899 the entity SHOULD save the change to 900 non-volatile storage." 901 REFERENCE 902 "See Section 6. 'SMF Duplicate Packet 903 Detection' in RFC 6621 - Simplified 904 Multicast Forwarding (SMF), Macker, J., 905 May 2012." 906 DEFVAL { 60 } 907 ::= { smfConfigurationGroup 9 } 909 smfCfgDpdEntryMaxLifetime OBJECT-TYPE 910 SYNTAX Integer32 (0..65525) 911 UNITS "Seconds" 912 MAX-ACCESS read-write 913 STATUS current 914 DESCRIPTION 915 "The maximum lifetime of a cached DPD 916 record in the local device storage. 918 If the memory is running low prior to the 919 MaxLifetimes being exceeded, the local SMF 920 devices should purge the oldest records first. 922 This object is persistent and when written 923 the entity SHOULD save the change to 924 non-volatile storage." 925 REFERENCE 926 "See Section 6. 'SMF Duplicate Packet 927 Detection' in RFC 6621 - Simplified 928 Multicast Forwarding (SMF), Macker, J., 929 May 2012." 930 DEFVAL { 600 } 931 ::= { smfConfigurationGroup 10 } 933 -- 934 -- Configuration of messages to be included in 935 -- NHDP message exchanges in support of SMF 936 -- operations. 937 -- 939 smfCfgNhdpRssaMesgTLVIncluded OBJECT-TYPE 940 SYNTAX TruthValue 941 MAX-ACCESS read-write 942 STATUS current 943 DESCRIPTION 944 "Indicates whether the associated NHDP messages 945 include the RSSA Message TLV, or not. This 946 is an optional SMF operational setting. 947 The value 'true(1)' indicates that this TLV is 948 included; the value 'false(2)' indicates that it 949 is not included. 951 It is RECOMMENDED that the RSSA Message TLV 952 be included in the NHDP messages. 954 This object is persistent and when written 955 the entity SHOULD save the change to 956 non-volatile storage." 957 REFERENCE 958 "See Section 8.1.1. 'SMF Message TLV Type' in 959 RFC 6621 - Simplified Multicast Forwarding 960 (SMF), Macker, J., May 2012." 961 DEFVAL { true } 962 ::= { smfConfigurationGroup 11 } 964 smfCfgNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 965 SYNTAX TruthValue 966 MAX-ACCESS read-write 967 STATUS current 968 DESCRIPTION 969 "Indicates whether the associated NHDP messages 970 include the RSSA Address Block TLV, or not. 971 This is an optional SMF operational setting. 972 The value 'true(1)' indicates that this TLV is 973 included; the value 'false(2)' indicates that it 974 is not included. 976 The smfCfgNhdpRssaAddrBlockTLVIncluded is optional 977 in all cases as it depends on the existence of 978 an address block which may not be present. 979 If this SMF device is configured with NHDP, 980 then this object SHOULD be set to 'true(1)'. 982 This object is persistent and when written 983 the entity SHOULD save the change to 984 non-volatile storage." 985 REFERENCE 986 "See Section 8.1.2. 'SMF Address Block TLV 987 Type' in RFC 6621 - Simplified Multicast 988 Forwarding (SMF), Macker, J., May 2012." 989 DEFVAL { true } 990 ::= { smfConfigurationGroup 12 } 992 -- 993 -- Table identifying configured multicast addresses to be forwarded. 994 -- 996 smfCfgAddrForwardingTable OBJECT-TYPE 997 SYNTAX SEQUENCE OF SmfCfgAddrForwardingEntry 998 MAX-ACCESS not-accessible 999 STATUS current 1000 DESCRIPTION 1001 "The (conceptual) table containing information on multicast 1002 multicast addresses which are to be forwarded by the SMF 1003 process. This table represents an IP filters table for 1004 forwarding (or not) packets based upon their IP 1005 multicast address. 1007 The SMF process can be configured to forward only those 1008 multicast addresses found within the 1009 smfCfgAddrForwardingTable. As such, addresses which are 1010 to be forwarded by the SMF process MUST be found within 1011 the address ranges configured within this table, unless 1012 this table is empty. 1014 Each row is associated with a range of multicast 1015 addresses, and ranges for different rows must be disjoint. 1016 Different rows MAY share a common 1017 smfCfgAddrForwardingGroupName to administratively 1018 associate different rows. 1020 The objects in this table are persistent and when written 1021 the entity SHOULD save the change to non-volatile storage." 1022 REFERENCE 1023 "See Section 9.1. 'Forwarded Multicast Groups' in 1024 RFC 6621 - Simplified Multicast Forwarding 1025 (SMF), Macker, J., May 2012." 1026 ::= { smfConfigurationGroup 13 } 1028 smfCfgAddrForwardingEntry OBJECT-TYPE 1029 SYNTAX SmfCfgAddrForwardingEntry 1030 MAX-ACCESS not-accessible 1031 STATUS current 1032 DESCRIPTION 1033 "An entry (conceptual row) containing the information on a 1034 particular multicast scope." 1035 INDEX { smfCfgAddrForwardingIndex } 1036 ::= { smfCfgAddrForwardingTable 1 } 1038 SmfCfgAddrForwardingEntry ::= SEQUENCE { 1039 smfCfgAddrForwardingIndex Integer32, 1040 smfCfgAddrForwardingGroupName SnmpAdminString, 1041 smfCfgAddrForwardingAddrType InetAddressType, 1042 smfCfgAddrForwardingAddress InetAddress, 1043 smfCfgAddrForwardingAddrPrefixLength 1044 InetAddressPrefixLength, 1045 smfCfgAddrForwardingStatus RowStatus 1046 } 1048 smfCfgAddrForwardingIndex OBJECT-TYPE 1049 SYNTAX Integer32 (1..2147483647) 1050 MAX-ACCESS not-accessible 1051 STATUS current 1052 DESCRIPTION 1053 "This object identifies an unique entry 1054 for a forwarding group. The index for 1055 this entry is a unique value, 1056 greater than zero, for each row. 1057 It is recommended that values are assigned 1058 contiguously starting from 1. 1060 The value for each row index MUST remain 1061 constant from one re-initialization 1062 of the entity's management system to the 1063 next re-initialization." 1064 ::= { smfCfgAddrForwardingEntry 1 } 1066 smfCfgAddrForwardingGroupName OBJECT-TYPE 1067 SYNTAX SnmpAdminString 1068 MAX-ACCESS read-create 1069 STATUS current 1070 DESCRIPTION 1071 "This object identifies a group name for a set of 1072 row entries in order to administratively associate 1073 a set of address ranges. 1075 If there is no group name or this object is 1076 otherwise not applicable, then this object contains 1077 a zero-length string. 1079 This object is persistent and when written 1080 the entity SHOULD save the change to 1081 non-volatile storage." 1082 ::= { smfCfgAddrForwardingEntry 2 } 1084 smfCfgAddrForwardingAddrType OBJECT-TYPE 1085 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1086 MAX-ACCESS read-create 1087 STATUS current 1088 DESCRIPTION 1089 "The type of the addresses in the multicast 1090 forwarding ranges identified by this table. 1092 Only the values ipv4(1) and ipv6(2) are 1093 supported. 1095 This object is persistent and when written 1096 the entity SHOULD save the change to 1097 non-volatile storage." 1098 ::= { smfCfgAddrForwardingEntry 3 } 1100 smfCfgAddrForwardingAddress OBJECT-TYPE 1101 SYNTAX InetAddress (SIZE(4|16)) 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "The multicast group address which, when 1106 combined with smfCfgAddrForwardingAddrPrefixLength, 1107 gives the group prefix for this forwarding range. 1108 The InetAddressType is given by 1109 smfCfgAddrForwardingAddrType. 1111 This address object is only significant up to 1112 smfCfgAddrForwardingAddrPrefixLength bits. The 1113 remaining address bits are set to zero. This is 1114 especially important for this index field, 1115 Any non-zero bits would signify an entirely 1116 different entry. 1118 Legal values correspond to the subset of address 1119 families for which multicast address allocation 1120 is supported. 1122 This object is persistent and when written 1123 the entity SHOULD save the change to 1124 non-volatile storage." 1125 ::= { smfCfgAddrForwardingEntry 4 } 1127 smfCfgAddrForwardingAddrPrefixLength OBJECT-TYPE 1128 SYNTAX InetAddressPrefixLength 1129 MAX-ACCESS read-create 1130 STATUS current 1131 DESCRIPTION 1132 "The length in bits of the mask which, when 1133 combined with smfCfgAddrForwardingAddress, 1134 gives the group prefix for this forwarding 1135 range. 1137 This object is persistent and when written 1138 the entity SHOULD save the change to 1139 non-volatile storage." 1140 ::= { smfCfgAddrForwardingEntry 5 } 1142 smfCfgAddrForwardingStatus OBJECT-TYPE 1143 SYNTAX RowStatus 1144 MAX-ACCESS read-create 1145 STATUS current 1146 DESCRIPTION 1147 "The status of this row, by which new entries may be 1148 created, or old entries deleted from this table." 1149 ::= { smfCfgAddrForwardingEntry 6 } 1151 -- 1152 -- SMF Interfaces Configuration Table 1153 -- 1155 smfCfgInterfaceTable OBJECT-TYPE 1156 SYNTAX SEQUENCE OF SmfCfgInterfaceEntry 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "The SMF Interface Table describes the SMF 1161 interfaces that are participating in the 1162 SMF packet forwarding process. The ifIndex is 1163 from the interfaces group defined in the 1164 Interfaces Group MIB module (RFC 2863). As such, 1165 this table 'sparse augments' the ifTable 1166 specifically when SMF is to be configured to 1167 operate over this interface. 1169 A conceptual row in this table exists if and only 1170 if either a manager has explicitly created the row 1171 or there is an interface on the managed device 1172 that supports and runs SMF. 1174 The manager can create a row by setting 1175 rowStatus to 'createAndGo' or 'createAndWait'. 1176 Row objects having associated DEFVAL clauses are 1177 automatically defined by the agent with these 1178 values during row creation, unless the manager 1179 explicitly defines these object values during the 1180 row creation. 1182 If the corresponding entry with ifIndex value 1183 is deleted from the Interface Table, then the entry 1184 in this table is automatically deleted and 1185 SMF is disabled on this interface, 1186 and all configuration and state information 1187 related to this interface is to be removed 1188 from memory. 1190 If the value of the smfCfgAdminStatus object is changed 1191 from 'enabled' to 'disabled', then all rows in this 1192 table are to be deleted and all 1193 configuration and state information 1194 related to this interface is to be removed 1195 from memory." 1196 REFERENCE 1197 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1198 K., and F. Kastenholtz, June 2000." 1199 ::= { smfConfigurationGroup 14 } 1201 smfCfgInterfaceEntry OBJECT-TYPE 1202 SYNTAX SmfCfgInterfaceEntry 1203 MAX-ACCESS not-accessible 1204 STATUS current 1205 DESCRIPTION 1206 "The SMF interface entry describes one SMF 1207 interface as indexed by its ifIndex. 1209 The objects in this table are persistent and when 1210 written the device SHOULD save the change to 1211 non-volatile storage. For further information 1212 on the storage behavior for these objects, refer 1213 to the description for the smfCfgIfRowStatus 1214 object." 1215 INDEX { smfCfgIfIndex } 1216 ::= { smfCfgInterfaceTable 1 } 1218 SmfCfgInterfaceEntry ::= 1219 SEQUENCE { 1220 smfCfgIfIndex InterfaceIndexOrZero, 1221 smfCfgIfName SnmpAdminString, 1222 smfCfgIfAdminStatus SmfStatus, 1223 smfCfgIfSmfUpTime TimeTicks, 1224 smfCfgIfRowStatus RowStatus 1225 } 1227 smfCfgIfIndex OBJECT-TYPE 1228 SYNTAX InterfaceIndexOrZero 1229 MAX-ACCESS not-accessible 1230 STATUS current 1231 DESCRIPTION 1232 "The ifIndex for this SMF interface. This value 1233 MUST correspond to an ifIndex referring 1234 to a valid entry in The Interfaces Table. 1235 If the manager attempts to create a row 1236 for which the ifIndex does not exist on the 1237 local device, then the agent SHOULD issue 1238 a return value of 'inconsistentValue' and 1239 the operation SHOULD fail." 1240 REFERENCE 1241 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1242 K., and F. Kastenholtz, June 2000." 1243 ::= { smfCfgInterfaceEntry 1 } 1245 smfCfgIfName OBJECT-TYPE 1246 SYNTAX SnmpAdminString 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "The textual name of the interface. The value of this 1251 object SHOULD be the name of the interface as assigned by 1252 the local device. This can be a text-name, such as 'le0' 1253 or a simple port number, such as '1', 1254 depending on the interface-naming syntax of the device. 1256 If there is no local name or this object is otherwise not 1257 applicable, then this object contains a zero-length string." 1258 ::= { smfCfgInterfaceEntry 2 } 1260 smfCfgIfAdminStatus OBJECT-TYPE 1261 SYNTAX SmfStatus 1262 MAX-ACCESS read-create 1263 STATUS current 1264 DESCRIPTION 1265 "The SMF interface's administrative status. 1266 The value 'enabled' denotes that the interface 1267 is running the SMF forwarding process. 1268 The value 'disabled' denotes that the interface is 1269 currently external to the SMF forwarding process. 1271 The default value for this object is 'enabled(1)'. 1273 This object SHOULD be persistent and when 1274 written the device SHOULD save the change to 1275 non-volatile storage." 1276 DEFVAL { enabled } 1277 ::= { smfCfgInterfaceEntry 3 } 1279 smfCfgIfSmfUpTime OBJECT-TYPE 1280 SYNTAX TimeTicks 1281 MAX-ACCESS read-only 1282 STATUS current 1283 DESCRIPTION 1284 "The time (in hundredths of a second) since 1285 this interface SMF process was last 1286 re-initialized. The interface SMF process 1287 is re-initialized when the corresponding 1288 'smfCfgIfRowStatus' object transits to 1289 the active(1) state." 1290 ::= { smfCfgInterfaceEntry 4 } 1292 smfCfgIfRowStatus OBJECT-TYPE 1293 SYNTAX RowStatus 1294 MAX-ACCESS read-create 1295 STATUS current 1296 DESCRIPTION 1297 "This object permits management of the table 1298 by facilitating actions such as row creation, 1299 construction, and destruction. The value of 1300 this object has no effect on whether other 1301 objects in this conceptual row can be 1302 modified. 1304 An entry may not exist in the active(1) state unless all 1305 objects in the entry have a defined appropriate value. For 1306 objects with DEFVAL clauses, the management station 1307 does not need to specify the value of this object in order 1308 for the row to transit to the active(1) state; the default 1309 value for this object is used. For objects that do not 1310 have DEFVAL clauses, then the network manager MUST 1311 specify the value of this object prior to this row 1312 transitioning to the active(1) state. 1314 When this object transitions to active(1), all objects 1315 in this row SHOULD be written to non-volatile (stable) 1316 storage. Read-create objects in this row MAY be modified. 1317 When an object in a row with smfCfgIfRowStatus of active(1) 1318 is changed, then the updated value MUST be reflected in SMF 1319 and this new object value MUST be written to non-volatile 1320 storage. 1322 If this object is not equal to active(1), all associated 1323 entries in the smfPerfIpv4InterfacePerfTable and the 1324 smfPerfIpv6InterfacePerfTable MUST be deleted." 1325 ::= { smfCfgInterfaceEntry 5 } 1327 -- 1328 -- smfStateGroup 1329 -- 1330 -- Contains information describing the current state of the SMF 1331 -- process such as the current inclusion in the RS or not. 1332 -- 1334 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1336 smfStateNodeRsStatusIncluded OBJECT-TYPE 1337 SYNTAX TruthValue 1338 MAX-ACCESS read-only 1339 STATUS current 1340 DESCRIPTION 1341 "The current status of the SMF node in the context of 1342 the MANETs relay set. A value of 'true(1)' indicates 1343 that the node is currently part of the MANET Relay 1344 Set. A value of 'false(2)' indicates that the node 1345 is currently not part of the MANET Relay Set." 1346 REFERENCE 1347 "See Section 7. 'Relay Set Selection' in 1348 RFC 6621 - Simplified Multicast Forwarding 1349 (SMF), Macker, J., May 2012." 1350 ::= { smfStateGroup 1 } 1352 smfStateDpdMemoryOverflow OBJECT-TYPE 1353 SYNTAX Counter32 1354 UNITS "DPD Records" 1355 MAX-ACCESS read-only 1356 STATUS current 1357 DESCRIPTION 1358 "The number of DPD records that had to be flushed to 1359 prevent memory overruns for caching of these records. 1360 The number of records to be flushed upon a buffer 1361 overflow is an implementation specific decision. 1363 There is the potential for a counter discontinuity 1364 in this object if the system SMF process had been 1365 disabled and later enabled. In order to check for 1366 the occurrence of such a discontinuity when monitoring 1367 this counter object, it is recommended that the 1368 smfCfgSmfSysUpTime object also be monitored." 1369 REFERENCE 1370 "See Section 6. 'SMF Duplicate Packet 1371 Detection' in RFC 6621 - Simplified 1372 Multicast Forwarding (SMF), Macker, J., 1373 May 2012." 1374 ::= { smfStateGroup 2 } 1376 -- 1377 -- SMF Neighbor Table 1378 -- 1380 smfStateNeighborTable OBJECT-TYPE 1381 SYNTAX SEQUENCE OF SmfStateNeighborEntry 1382 MAX-ACCESS not-accessible 1383 STATUS current 1384 DESCRIPTION 1385 "The SMF StateNeighborTable describes the 1386 current one-hop neighbor nodes, their address 1387 and SMF RSSA and the interface on which 1388 they can be reached." 1389 REFERENCE 1390 "See Section 7. 'SMF Neighborhood Discovery' and 1391 Section 8.1. 'SMF Relay Algorithm TLV 1392 Types' in RFC 6621 - Simplified Multicast 1393 Forwarding (SMF), Macker, J., May 2012." 1394 ::= { smfStateGroup 3 } 1395 smfStateNeighborEntry OBJECT-TYPE 1396 SYNTAX SmfStateNeighborEntry 1397 MAX-ACCESS not-accessible 1398 STATUS current 1399 DESCRIPTION 1400 "The SMF Neighbor Table contains the 1401 set of one-hop neighbors, the interface 1402 they are reachable on and the SMF RSSA 1403 they are currently running." 1404 INDEX { smfStateNeighborIpAddrType, 1405 smfStateNeighborIpAddr, 1406 smfStateNeighborPrefixLen } 1407 ::= { smfStateNeighborTable 1 } 1409 SmfStateNeighborEntry ::= 1410 SEQUENCE { 1411 smfStateNeighborIpAddrType InetAddressType, 1412 smfStateNeighborIpAddr InetAddress, 1413 smfStateNeighborPrefixLen InetAddressPrefixLength, 1414 smfStateNeighborRSSA IANAsmfRssaIdTC, 1415 smfStateNeighborNextHopInterface InterfaceIndexOrZero 1416 } 1418 smfStateNeighborIpAddrType OBJECT-TYPE 1419 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1420 MAX-ACCESS not-accessible 1421 STATUS current 1422 DESCRIPTION 1423 "The one-hop neighbor IP address type. 1425 Only the values 'ipv4(1)' and 1426 'ipv6(2)' are supported." 1427 ::= { smfStateNeighborEntry 1 } 1429 smfStateNeighborIpAddr OBJECT-TYPE 1430 SYNTAX InetAddress (SIZE(4|16)) 1431 MAX-ACCESS not-accessible 1432 STATUS current 1433 DESCRIPTION 1434 "The one-hop neighbor Inet IPv4 or IPv6 1435 address. 1437 Only IPv4 and IPv6 addresses 1438 are supported." 1439 ::= { smfStateNeighborEntry 2 } 1441 smfStateNeighborPrefixLen OBJECT-TYPE 1442 SYNTAX InetAddressPrefixLength 1443 UNITS "bits" 1444 MAX-ACCESS not-accessible 1445 STATUS current 1446 DESCRIPTION 1447 "The prefix length. This is a decimal value that 1448 indicates the number of contiguous, higher-order 1449 bits of the address that make up the network 1450 portion of the address." 1451 ::= { smfStateNeighborEntry 3 } 1453 smfStateNeighborRSSA OBJECT-TYPE 1454 SYNTAX IANAsmfRssaIdTC 1455 MAX-ACCESS read-only 1456 STATUS current 1457 DESCRIPTION 1458 "The current RSSA running on the neighbor." 1459 ::= { smfStateNeighborEntry 4 } 1461 smfStateNeighborNextHopInterface OBJECT-TYPE 1462 SYNTAX InterfaceIndexOrZero 1463 MAX-ACCESS read-only 1464 STATUS current 1465 DESCRIPTION 1466 "The interface ifIndex over which the 1467 neighbor is reachable in one-hop." 1468 ::= { smfStateNeighborEntry 6 } 1470 -- 1471 -- SMF Performance Group 1472 -- 1473 -- Contains objects which help to characterize the 1474 -- performance of the SMF RSSA process, such as statistics 1475 -- counters. There are two types of SMF RSSA statistics: 1476 -- global counters and per interface counters. 1477 -- 1479 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1481 smfPerfGobalGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1483 -- 1484 -- IPv4 packet counters 1485 -- 1487 smfPerfIpv4MultiPktsRecvTotal OBJECT-TYPE 1488 SYNTAX Counter32 1489 UNITS "Packets" 1490 MAX-ACCESS read-only 1491 STATUS current 1492 DESCRIPTION 1493 "A counter of the total number of 1494 multicast IPv4 packets received by the 1495 device and delivered to the SMF process. 1497 There is the potential for a counter discontinuity 1498 in this object if the system SMF process had been 1499 disabled and later enabled. In order to check for 1500 the occurrence of such a discontinuity when monitoring 1501 this counter object, it is recommended that the 1502 smfCfgSmfSysUpTime object also be monitored." 1503 ::= { smfPerfGobalGroup 1 } 1505 smfPerfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1506 SYNTAX Counter32 1507 UNITS "Packets" 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "A counter of the total number of 1512 multicast IPv4 packets forwarded by the 1513 device. 1515 There is the potential for a counter discontinuity 1516 in this object if the system SMF process had been 1517 disabled and later enabled. In order to check for 1518 the occurrence of such a discontinuity when monitoring 1519 this counter object, it is recommended that the 1520 smfCfgSmfSysUpTime object also be monitored." 1521 ::= { smfPerfGobalGroup 2 } 1523 smfPerfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1524 SYNTAX Counter32 1525 UNITS "Packets" 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "A counter of the total number of duplicate 1530 multicast IPv4 packets detected by the 1531 device. 1533 There is the potential for a counter discontinuity 1534 in this object if the system SMF process had been 1535 disabled and later enabled. In order to check for 1536 the occurrence of such a discontinuity when monitoring 1537 this counter object, it is recommended that the 1538 smfCfgSmfSysUpTime object also be monitored." 1539 REFERENCE 1540 "See Section 6.2. 'IPv4 Duplicate Packet 1541 Detection' in RFC 6621 - Simplified Multicast 1542 Forwarding (SMF), Macker, J., May 2012." 1543 ::= { smfPerfGobalGroup 3 } 1545 smfPerfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1546 SYNTAX Counter32 1547 UNITS "Packets" 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "A counter of the total number of dropped 1552 multicast IPv4 packets by the 1553 device due to TTL exceeded. 1555 There is the potential for a counter discontinuity 1556 in this object if the system SMF process had been 1557 disabled and later enabled. In order to check for 1558 the occurrence of such a discontinuity when monitoring 1559 this counter object, it is recommended that the 1560 smfCfgSmfSysUpTime object also be monitored." 1561 REFERENCE 1562 "See Section 5. 'SMF Packet Processing and 1563 Forwarding' in RFC 6621 - Simplified 1564 Multicast Forwarding (SMF), Macker, J., 1565 May 2012." 1566 ::= { smfPerfGobalGroup 4 } 1568 smfPerfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1569 SYNTAX Counter32 1570 UNITS "Packets" 1571 MAX-ACCESS read-only 1572 STATUS current 1573 DESCRIPTION 1574 "A counter of the total number of IPv4 packets 1575 recieved which have a TTL larger than that 1576 of a previously received identical packet. 1578 There is the potential for a counter discontinuity 1579 in this object if the system SMF process had been 1580 disabled and later enabled. In order to check for 1581 the occurrence of such a discontinuity when monitoring 1582 this counter object, it is recommended that the 1583 smfCfgSmfSysUpTime object also be monitored." 1584 REFERENCE 1585 "See Section 5. 'SMF Packet Processing and 1586 Forwarding' in RFC 6621 - Simplified Multicast 1587 Forwarding (SMF), Macker, J., May 2012." 1588 ::= { smfPerfGobalGroup 5 } 1590 -- 1591 -- IPv6 packet counters 1592 -- 1594 smfPerfIpv6MultiPktsRecvTotal OBJECT-TYPE 1595 SYNTAX Counter32 1596 UNITS "Packets" 1597 MAX-ACCESS read-only 1598 STATUS current 1599 DESCRIPTION 1600 "A counter of the total number of 1601 multicast IPv6 packets received by the 1602 device and delivered to the SMF process. 1604 There is the potential for a counter discontinuity 1605 in this object if the system SMF process had been 1606 disabled and later enabled. In order to check for 1607 the occurrence of such a discontinuity when monitoring 1608 this counter object, it is recommended that the 1609 smfCfgSmfSysUpTime object also be monitored." 1610 ::= { smfPerfGobalGroup 6 } 1612 smfPerfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1613 SYNTAX Counter32 1614 UNITS "Packets" 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "A counter of the total number of 1619 multicast IPv6 packets forwarded by the 1620 device. 1622 There is the potential for a counter discontinuity 1623 in this object if the system SMF process had been 1624 disabled and later enabled. In order to check for 1625 the occurrence of such a discontinuity when monitoring 1626 this counter object, it is recommended that the 1627 smfCfgSmfSysUpTime object also be monitored." 1628 ::= { smfPerfGobalGroup 7 } 1630 smfPerfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1631 SYNTAX Counter32 1632 UNITS "Packets" 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "A counter of the total number of duplicate 1637 multicast IPv6 packets detected by the 1638 device. 1640 There is the potential for a counter discontinuity 1641 in this object if the system SMF process had been 1642 disabled and later enabled. In order to check for 1643 the occurrence of such a discontinuity when monitoring 1644 this counter object, it is recommended that the 1645 smfCfgSmfSysUpTime object also be monitored." 1646 REFERENCE 1647 "See Section 6.1. 'IPv6 Duplicate Packet 1648 Detection' in RFC 6621 - Simplified Multicast 1649 Forwarding (SMF), Macker, J., May 2012." 1650 ::= { smfPerfGobalGroup 8 } 1652 smfPerfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1653 SYNTAX Counter32 1654 UNITS "Packets" 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "A counter of the total number of dropped 1659 multicast IPv6 packets by the 1660 device due to TTL exceeded. 1662 There is the potential for a counter discontinuity 1663 in this object if the system SMF process had been 1664 disabled and later enabled. In order to check for 1665 the occurrence of such a discontinuity when monitoring 1666 this counter object, it is recommended that the 1667 smfCfgSmfSysUpTime object also be monitored." 1668 REFERENCE 1669 "See Section 5. 'SMF Packet Processing and 1670 Forwarding' in RFC 6621 - Simplified 1671 Multicast Forwarding (SMF), Macker, J., 1672 May 2012." 1673 ::= { smfPerfGobalGroup 9 } 1675 smfPerfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1676 SYNTAX Counter32 1677 UNITS "Packets" 1678 MAX-ACCESS read-only 1679 STATUS current 1680 DESCRIPTION 1681 "A counter of the total number of IPv6 packets 1682 recieved which have a TTL larger than that 1683 of a previously recived identical packet. 1685 There is the potential for a counter discontinuity 1686 in this object if the system SMF process had been 1687 disabled and later enabled. In order to check for 1688 the occurrence of such a discontinuity when monitoring 1689 this counter object, it is recommended that the 1690 smfCfgSmfSysUpTime object also be monitored." 1691 REFERENCE 1692 "See Section 5. 'SMF Packet Processing and 1693 Forwarding' in RFC 6621 - Simplified Multicast 1694 Forwarding (SMF), Macker, J., May 2012." 1695 ::= { smfPerfGobalGroup 10 } 1697 smfPerfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1698 SYNTAX Counter32 1699 UNITS "Packets" 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "A counter of the total number of IPv6 packets 1704 received which required the HAV assist for DPD. 1706 There is the potential for a counter discontinuity 1707 in this object if the system SMF process had been 1708 disabled and later enabled. In order to check for 1709 the occurrence of such a discontinuity when monitoring 1710 this counter object, it is recommended that the 1711 smfCfgSmfSysUpTime object also be monitored." 1712 REFERENCE 1713 "See Section 6.1.1. 'IPv6 SMF_DPD Option Header' 1714 in RFC 6621 - Simplified Multicast Forwarding 1715 (SMF), Macker, J., May 2012." 1716 ::= { smfPerfGobalGroup 11 } 1718 smfPerfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1719 SYNTAX Counter32 1720 UNITS "Packets" 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 "A counter of the total number of IPv6 packets 1725 recieved which the device inserted the 1726 DPD header option. 1728 There is the potential for a counter discontinuity 1729 in this object if the system SMF process had been 1730 disabled and later enabled. In order to check for 1731 the occurrence of such a discontinuity when monitoring 1732 this counter object, it is recommended that the 1733 smfCfgSmfSysUpTime object also be monitored." 1734 REFERENCE 1735 "See Section 6.1.2. 'IPv6 Identification-Based 1736 DPD' in RFC 6621 - Simplified Multicast 1737 Forwarding (SMF), Macker, J., May 2012." 1738 ::= { smfPerfGobalGroup 12 } 1740 -- 1741 -- Per SMF Interface Performance Table 1742 -- 1744 smfPerfInterfaceGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1746 smfPerfIpv4InterfacePerfTable OBJECT-TYPE 1747 SYNTAX SEQUENCE OF SmfPerfIpv4InterfacePerfEntry 1748 MAX-ACCESS not-accessible 1749 STATUS current 1750 DESCRIPTION 1751 "The SMF Interface Performance Table 1752 describes the SMF counters per 1753 interface." 1754 ::= { smfPerfInterfaceGroup 1 } 1756 smfPerfIpv4InterfacePerfEntry OBJECT-TYPE 1757 SYNTAX SmfPerfIpv4InterfacePerfEntry 1758 MAX-ACCESS not-accessible 1759 STATUS current 1760 DESCRIPTION 1761 "The SMF Interface Performance entry 1762 describes the statistics for a particular 1763 node interface." 1764 INDEX { smfCfgIfIndex } 1765 ::= { smfPerfIpv4InterfacePerfTable 1 } 1767 SmfPerfIpv4InterfacePerfEntry ::= 1768 SEQUENCE { 1769 smfPerfIpv4MultiPktsRecvPerIf Counter32, 1770 smfPerfIpv4MultiPktsForwardedPerIf Counter32, 1771 smfPerfIpv4DuplMultiPktsDetectedPerIf Counter32, 1772 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1773 smfPerfIpv4TTLLargerThanPreviousPerIf Counter32 1774 } 1776 smfPerfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1777 SYNTAX Counter32 1778 UNITS "Packets" 1779 MAX-ACCESS read-only 1780 STATUS current 1781 DESCRIPTION 1782 "A counter of the number of multicast IP 1783 packets received by the SMF process on 1784 this device on this interface. 1786 There is the potential for a counter discontinuity 1787 in this object if the system SMF process had been 1788 disabled and later enabled on this interface. 1789 In order to check for the occurrence of such a 1790 discontinuity when monitoring this counter object, 1791 it is recommended that the smfCfgIfSmfUpTime 1792 object also be monitored." 1793 ::= { smfPerfIpv4InterfacePerfEntry 1 } 1795 smfPerfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1796 SYNTAX Counter32 1797 UNITS "Packets" 1798 MAX-ACCESS read-only 1799 STATUS current 1800 DESCRIPTION 1801 "A counter of the number of 1802 multicast IP packets forwarded by the 1803 SMF process on this device 1804 on this interface. 1806 There is the potential for a counter discontinuity 1807 in this object if the system SMF process had been 1808 disabled and later enabled on this interface. 1809 In order to check for the occurrence of such a 1810 discontinuity when monitoring this counter object, 1811 it is recommended that the smfCfgIfSmfUpTime 1812 object also be monitored." 1813 ::= { smfPerfIpv4InterfacePerfEntry 2 } 1815 smfPerfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1816 SYNTAX Counter32 1817 UNITS "Packets" 1818 MAX-ACCESS read-only 1819 STATUS current 1820 DESCRIPTION 1821 "A counter of the number of duplicate 1822 multicast IP packets detected by the 1823 SMF process on this device 1824 on this interface. 1826 There is the potential for a counter discontinuity 1827 in this object if the system SMF process had been 1828 disabled and later enabled on this interface. 1829 In order to check for the occurrence of such a 1830 discontinuity when monitoring this counter object, 1831 it is recommended that the smfCfgIfSmfUpTime 1832 object also be monitored." 1833 ::= { smfPerfIpv4InterfacePerfEntry 3 } 1835 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1836 SYNTAX Counter32 1837 UNITS "Packets" 1838 MAX-ACCESS read-only 1839 STATUS current 1840 DESCRIPTION 1841 "A counter of the total number of dropped 1842 multicast IPv4 packets by the SMF process 1843 on this device on this interface 1844 due to TTL exceeded. 1846 There is the potential for a counter discontinuity 1847 in this object if the system SMF process had been 1848 disabled and later enabled on this interface. 1849 In order to check for the occurrence of such a 1850 discontinuity when monitoring this counter object, 1851 it is recommended that the smfCfgIfSmfUpTime 1852 object also be monitored." 1853 ::= { smfPerfIpv4InterfacePerfEntry 4 } 1855 smfPerfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1856 SYNTAX Counter32 1857 UNITS "Packets" 1858 MAX-ACCESS read-only 1859 STATUS current 1860 DESCRIPTION 1861 "A counter of the total number of IPv4 packets 1862 received by the SMF process on this device 1863 on this interface which have a TTL larger than 1864 that of a previously received identical packet. 1866 There is the potential for a counter discontinuity 1867 in this object if the system SMF process had been 1868 disabled and later enabled on this interface. 1869 In order to check for the occurrence of such a 1870 discontinuity when monitoring this counter object, 1871 it is recommended that the smfCfgIfSmfUpTime 1872 object also be monitored." 1873 ::= { smfPerfIpv4InterfacePerfEntry 5 } 1874 smfPerfIpv6InterfacePerfTable OBJECT-TYPE 1875 SYNTAX SEQUENCE OF SmfPerfIpv6InterfacePerfEntry 1876 MAX-ACCESS not-accessible 1877 STATUS current 1878 DESCRIPTION 1879 "The SMF Interface Performance Table 1880 describes the SMF counters per 1881 interface." 1882 ::= { smfPerfInterfaceGroup 2 } 1884 smfPerfIpv6InterfacePerfEntry OBJECT-TYPE 1885 SYNTAX SmfPerfIpv6InterfacePerfEntry 1886 MAX-ACCESS not-accessible 1887 STATUS current 1888 DESCRIPTION 1889 "The SMF Interface Performance entry 1890 describes the counters for a particular 1891 node interface." 1892 INDEX { smfCfgIfIndex } 1893 ::= { smfPerfIpv6InterfacePerfTable 1 } 1895 SmfPerfIpv6InterfacePerfEntry ::= 1896 SEQUENCE { 1897 smfPerfIpv6MultiPktsRecvPerIf Counter32, 1898 smfPerfIpv6MultiPktsForwardedPerIf Counter32, 1899 smfPerfIpv6DuplMultiPktsDetectedPerIf Counter32, 1900 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1901 smfPerfIpv6TTLLargerThanPreviousPerIf Counter32, 1902 smfPerfIpv6HAVAssistsReqdPerIf Counter32, 1903 smfPerfIpv6DpdHeaderInsertionsPerIf Counter32 1904 } 1906 smfPerfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1907 SYNTAX Counter32 1908 UNITS "Packets" 1909 MAX-ACCESS read-only 1910 STATUS current 1911 DESCRIPTION 1912 "A counter of the number of 1913 multicast IP packets received by the 1914 SMF process on this device 1915 on this interface. 1917 There is the potential for a counter discontinuity 1918 in this object if the system SMF process had been 1919 disabled and later enabled on this interface. 1920 In order to check for the occurrence of such a 1921 discontinuity when monitoring this counter object, 1922 it is recommended that the smfCfgIfSmfUpTime 1923 object also be monitored." 1924 ::= { smfPerfIpv6InterfacePerfEntry 1 } 1926 smfPerfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 1927 SYNTAX Counter32 1928 UNITS "Packets" 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "A counter of the number of 1933 multicast IP packets forwarded by the 1934 SMF process on this device 1935 on this interface. 1937 There is the potential for a counter discontinuity 1938 in this object if the system SMF process had been 1939 disabled and later enabled on this interface. 1940 In order to check for the occurrence of such a 1941 discontinuity when monitoring this counter object, 1942 it is recommended that the smfCfgIfSmfUpTime 1943 object also be monitored." 1944 ::= { smfPerfIpv6InterfacePerfEntry 2 } 1946 smfPerfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 1947 SYNTAX Counter32 1948 UNITS "Packets" 1949 MAX-ACCESS read-only 1950 STATUS current 1951 DESCRIPTION 1952 "A counter of the number of duplicate 1953 multicast IP packets detected by the 1954 SMF process on this device 1955 on this interface. 1957 There is the potential for a counter discontinuity 1958 in this object if the system SMF process had been 1959 disabled and later enabled on this interface. 1960 In order to check for the occurrence of such a 1961 discontinuity when monitoring this counter object, 1962 it is recommended that the smfCfgIfSmfUpTime 1963 object also be monitored." 1964 ::= { smfPerfIpv6InterfacePerfEntry 3 } 1966 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1967 SYNTAX Counter32 1968 UNITS "Packets" 1969 MAX-ACCESS read-only 1970 STATUS current 1971 DESCRIPTION 1972 "A counter of the number of dropped 1973 multicast IP packets by the 1974 SMF process on this device 1975 on this interface due to TTL 1976 exceeded. 1978 There is the potential for a counter discontinuity 1979 in this object if the system SMF process had been 1980 disabled and later enabled on this interface. 1981 In order to check for the occurrence of such a 1982 discontinuity when monitoring this counter object, 1983 it is recommended that the smfCfgIfSmfUpTime 1984 object also be monitored." 1985 ::= { smfPerfIpv6InterfacePerfEntry 4 } 1987 smfPerfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 1988 SYNTAX Counter32 1989 UNITS "Packets" 1990 MAX-ACCESS read-only 1991 STATUS current 1992 DESCRIPTION 1993 "A counter of the total number of IPv6 packets 1994 received which have a TTL larger than that 1995 of a previously received identical packet 1996 by the SMF process on this device on this 1997 interface. 1999 There is the potential for a counter discontinuity 2000 in this object if the system SMF process had been 2001 disabled and later enabled on this interface. 2002 In order to check for the occurrence of such a 2003 discontinuity when monitoring this counter object, 2004 it is recommended that the smfCfgIfSmfUpTime 2005 object also be monitored." 2006 ::= { smfPerfIpv6InterfacePerfEntry 5 } 2008 smfPerfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 2009 SYNTAX Counter32 2010 UNITS "Packets" 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "A counter of the total number of IPv6 packets 2015 received by the SMF process on this device 2016 on this interface which required the 2017 HAV assist for DPD. 2019 There is the potential for a counter discontinuity 2020 in this object if the system SMF process had been 2021 disabled and later enabled on this interface. 2022 In order to check for the occurrence of such a 2023 discontinuity when monitoring this counter object, 2024 it is recommended that the smfCfgIfSmfUpTime 2025 object also be monitored." 2026 ::= { smfPerfIpv6InterfacePerfEntry 6 } 2028 smfPerfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 2029 SYNTAX Counter32 2030 UNITS "Packets" 2031 MAX-ACCESS read-only 2032 STATUS current 2033 DESCRIPTION 2034 "A counter of the total number of IPv6 packets 2035 received by the SMF process on this device 2036 on this interface which the device inserted the 2037 DPD header option. 2039 There is the potential for a counter discontinuity 2040 in this object if the system SMF process had been 2041 disabled and later enabled on this interface. 2042 In order to check for the occurrence of such a 2043 discontinuity when monitoring this counter object, 2044 it is recommended that the smfCfgIfSmfUpTime 2045 object also be monitored." 2046 ::= { smfPerfIpv6InterfacePerfEntry 7 } 2048 -- 2049 -- Notifications 2050 -- 2052 smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 0 } 2053 smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 } 2055 -- smfMIBNotifObjects 2057 smfNotifAdminStatusChange NOTIFICATION-TYPE 2058 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2059 -- the notification. 2060 smfCfgRouterID, -- The originator of 2061 -- the notification. 2062 smfCfgAdminStatus -- The new status of the 2063 -- SMF process. 2065 } 2066 STATUS current 2067 DESCRIPTION 2068 "smfCfgAdminStatusChange is a notification sent when a 2069 the 'smfCfgAdminStatus' object changes." 2070 ::= { smfMIBNotifObjects 1 } 2072 smfNotifConfiguredOpModeChange NOTIFICATION-TYPE 2073 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2074 -- the notification. 2075 smfCfgRouterID, -- The originator of 2076 -- the notification. 2077 smfCfgOperationalMode -- The new Operations 2078 -- Mode of the SMF 2079 -- process. 2080 } 2081 STATUS current 2082 DESCRIPTION 2083 "smfNotifConfiguredOpModeChange is a notification 2084 sent when the 'smfCfgOperationalMode' object 2085 changes." 2086 ::= { smfMIBNotifObjects 2 } 2088 smfNotifIfAdminStatusChange NOTIFICATION-TYPE 2089 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2090 -- the notification. 2091 smfCfgRouterID, -- The originator of 2092 -- the notification. 2093 smfCfgIfName, -- The interface whose 2094 -- status has changed. 2095 smfCfgIfAdminStatus -- The new status of the 2096 -- SMF interface. 2097 } 2098 STATUS current 2099 DESCRIPTION 2100 "smfCfgIfAdminStatusChange is a notification sent when a 2101 the 'smfCfgIfAdminStatus' object changes." 2102 ::= { smfMIBNotifObjects 3 } 2104 smfNotifDpdMemoryOverflowEvent NOTIFICATION-TYPE 2105 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2106 -- the notification. 2107 smfCfgRouterID, -- The originator of 2108 -- the notification. 2109 smfStateDpdMemoryOverflow -- The counter of 2110 -- the overflows. 2111 } 2112 STATUS current 2113 DESCRIPTION 2114 "smfNotifDpdMemoryOverflowEvents is sent when the 2115 number of memory overflow events exceeds the 2116 the 'smfNotifDpdMemoryOverflowThreshold' within the 2117 previous number of seconds defined by the 2118 'smfNotifDpdMemoryOverflowWindow'." 2119 ::= { smfMIBNotifObjects 4 } 2121 -- smfMIBNotifControl 2122 smfNotifDpdMemoryOverflowThreshold OBJECT-TYPE 2123 SYNTAX Integer32 (0..255) 2124 UNITS "Events" 2125 MAX-ACCESS read-write 2126 STATUS current 2127 DESCRIPTION 2128 "A threshold value for the 2129 `smfNotifDpdmemoryOverflowEvents' object. 2130 If the number of occurences exceeds 2131 this threshold within the previous 2132 number of seconds 2133 'smfNotifDpdMemoryOverflowWindow', 2134 then the `smfNotifDpdMemoryOverflowEvent' 2135 notification is sent. 2137 The default value for this object is 2138 '1'." 2139 DEFVAL { 1 } 2140 ::= { smfMIBNotifControl 1 } 2142 smfNotifDpdMemoryOverflowWindow OBJECT-TYPE 2143 SYNTAX TimeTicks 2144 MAX-ACCESS read-write 2145 STATUS current 2146 DESCRIPTION 2147 "A time window value for the 2148 `smfNotifDpdmemoryOverflowEvents' object. 2149 If the number of occurences exceeds 2150 the `smfNotifDpdMemoryOverflowThreshold' 2151 within the previous number of seconds 2152 'smfNotifDpdMemoryOverflowWindow', 2153 then the `smfNotifDpdMemoryOverflowEvent' 2154 notification is sent. 2156 The default value for this object is 2157 '1'." 2158 DEFVAL { 1 } 2159 ::= { smfMIBNotifControl 2 } 2161 -- 2162 -- Compliance Statements 2163 -- 2165 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2166 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2168 smfBasicCompliance MODULE-COMPLIANCE 2169 STATUS current 2170 DESCRIPTION "The basic implementation requirements for 2171 managed network entities that implement 2172 the SMF RSSA process." 2173 MODULE -- this module 2174 MANDATORY-GROUPS { smfCapabObjectsGroup, 2175 smfConfigObjectsGroup } 2176 ::= { smfCompliances 1 } 2178 smfFullCompliance MODULE-COMPLIANCE 2179 STATUS current 2180 DESCRIPTION "The full implementation requirements for 2181 managed network entities that implement 2182 the SMF RSSA process." 2183 MODULE -- this module 2184 MANDATORY-GROUPS { smfCapabObjectsGroup, 2185 smfConfigObjectsGroup, 2186 smfStateObjectsGroup, 2187 smfPerfObjectsGroup, 2188 smfNotifObjectsGroup, 2189 smfNotificationsGroup 2190 } 2191 ::= { smfCompliances 2 } 2193 -- 2194 -- Units of Conformance 2195 -- 2197 smfCapabObjectsGroup OBJECT-GROUP 2198 OBJECTS { 2199 smfCapabilitiesOpModeID, 2200 smfCapabilitiesRssaID 2201 } 2202 STATUS current 2203 DESCRIPTION 2204 "Set of SMF configuration objects implemented 2205 in this module." 2207 ::= { smfMIBGroups 1 } 2209 smfConfigObjectsGroup OBJECT-GROUP 2210 OBJECTS { 2211 smfCfgAdminStatus, 2212 smfCfgSmfSysUpTime, 2213 smfCfgRouterIDAddrType, 2214 smfCfgRouterID, 2215 smfCfgOperationalMode, 2216 smfCfgRssaMember, 2217 smfCfgIpv4Dpd, 2218 smfCfgIpv6Dpd, 2219 smfCfgMaxPktLifetime, 2220 smfCfgDpdEntryMaxLifetime, 2221 smfCfgNhdpRssaMesgTLVIncluded, 2222 smfCfgNhdpRssaAddrBlockTLVIncluded, 2224 smfCfgAddrForwardingGroupName, 2225 smfCfgAddrForwardingAddrType, 2226 smfCfgAddrForwardingAddress, 2227 smfCfgAddrForwardingAddrPrefixLength, 2228 smfCfgAddrForwardingStatus, 2230 smfCfgIfName, 2231 smfCfgIfAdminStatus, 2232 smfCfgIfSmfUpTime, 2233 smfCfgIfRowStatus 2234 } 2235 STATUS current 2236 DESCRIPTION 2237 "Set of SMF configuration objects implemented 2238 in this module." 2239 ::= { smfMIBGroups 2 } 2241 smfStateObjectsGroup OBJECT-GROUP 2242 OBJECTS { 2243 smfStateNodeRsStatusIncluded, 2244 smfStateDpdMemoryOverflow, 2246 smfStateNeighborRSSA, 2247 smfStateNeighborNextHopInterface 2248 } 2249 STATUS current 2250 DESCRIPTION 2251 "Set of SMF state objects implemented 2252 in this module." 2253 ::= { smfMIBGroups 3 } 2254 smfPerfObjectsGroup OBJECT-GROUP 2255 OBJECTS { 2256 smfPerfIpv4MultiPktsRecvTotal, 2257 smfPerfIpv4MultiPktsForwardedTotal, 2258 smfPerfIpv4DuplMultiPktsDetectedTotal, 2259 smfPerfIpv4DroppedMultiPktsTTLExceededTotal, 2260 smfPerfIpv4TTLLargerThanPreviousTotal, 2262 smfPerfIpv6MultiPktsRecvTotal, 2263 smfPerfIpv6MultiPktsForwardedTotal, 2264 smfPerfIpv6DuplMultiPktsDetectedTotal, 2265 smfPerfIpv6DroppedMultiPktsTTLExceededTotal, 2266 smfPerfIpv6TTLLargerThanPreviousTotal, 2267 smfPerfIpv6HAVAssistsReqdTotal, 2268 smfPerfIpv6DpdHeaderInsertionsTotal, 2270 smfPerfIpv4MultiPktsRecvPerIf, 2271 smfPerfIpv4MultiPktsForwardedPerIf, 2272 smfPerfIpv4DuplMultiPktsDetectedPerIf, 2273 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf, 2274 smfPerfIpv4TTLLargerThanPreviousPerIf, 2276 smfPerfIpv6MultiPktsRecvPerIf, 2277 smfPerfIpv6MultiPktsForwardedPerIf, 2278 smfPerfIpv6DuplMultiPktsDetectedPerIf, 2279 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf, 2280 smfPerfIpv6TTLLargerThanPreviousPerIf, 2281 smfPerfIpv6HAVAssistsReqdPerIf, 2282 smfPerfIpv6DpdHeaderInsertionsPerIf 2283 } 2284 STATUS current 2285 DESCRIPTION 2286 "Set of SMF performance objects implemented 2287 in this module by total and per interface." 2288 ::= { smfMIBGroups 4 } 2290 smfNotifObjectsGroup OBJECT-GROUP 2291 OBJECTS { 2292 smfNotifDpdMemoryOverflowThreshold, 2293 smfNotifDpdMemoryOverflowWindow 2294 } 2295 STATUS current 2296 DESCRIPTION 2297 "Set of SMF notification control 2298 objects implemented in this module." 2299 ::= { smfMIBGroups 5 } 2301 smfNotificationsGroup NOTIFICATION-GROUP 2302 NOTIFICATIONS { 2303 smfNotifAdminStatusChange, 2304 smfNotifConfiguredOpModeChange, 2305 smfNotifIfAdminStatusChange, 2306 smfNotifDpdMemoryOverflowEvent 2307 } 2308 STATUS current 2309 DESCRIPTION 2310 "Set of SMF notifications implemented 2311 in this module." 2312 ::= { smfMIBGroups 6 } 2314 END 2316 8. Security Considerations 2318 This section discusses security implications of the choices made in 2319 this SMF-MIB module. 2321 There are a number of management objects defined in this MIB module 2322 with a MAX-ACCESS clause of read-write and/or read-create. Such 2323 objects may be considered sensitive or vulnerable in some network 2324 environments. The support for SET operations in a non-secure 2325 environment without proper protection can have a negative effect on 2326 network operations. These are the tables and objects and their 2327 sensitivity/vulnerability: 2329 o 'smfCfgAdminStatus' - this writable configuration object controls 2330 the operational status of the SMF process. If this setting is 2331 configured inconsistently across the MANET multicast domain, then 2332 delivery of multicast data may be inconsistent across the domain; 2333 some nodes may not receive multicast data intended for them. 2335 o 'smfCfgRouterIDAddrType' and 'smfCfgRouterID' - these writable 2336 configuration objects define the ID of the SMF process. These 2337 objects should be configured with a routable address defined on 2338 the local SMF device. The smfCfgRouterID is a logical 2339 identification that MUST be configured as unique across inter- 2340 operating SMF neighborhoods and it is RECOMMENDED to be chosen as 2341 the numerically largest address contained in a node's 'Neighbor 2342 Address List' as defined in NHDP. A smfCfgRouterID MUST be unique 2343 within the scope of the operating MANET network regardless of the 2344 method used for selecting it. If these objects are mis-configured 2345 or configured in-consistently across the MANET, then the ability 2346 of various RSSA algorithms, e.g., ECDS, may be compromised. This 2347 would potentially result in some routers within the MANET not 2348 receiving multicast packets destine to them. Hence, intentionally 2349 mis-configuring these objects could pose a form of Denial-of- 2350 Service (DOS) attack against the MANET. 2352 o 'smfCfgOpMode' - this writable configuration objects define the 2353 operational mode of the SMF process. The operational mode defines 2354 how the SMF process receives its data to form its local estimate 2355 of the CDS. It is recommended that the value for this object be 2356 set consistently across the MANET to ensure proper operation of 2357 the multicast packet forwarding. If the value for this object is 2358 set inconsistently across the MANET, the result may be that 2359 multicast packet delivery will be compromised within the MANET. 2360 Hence, intentionally mis-configuring this object could pose a form 2361 DOS attack against the MANET. 2363 o 'smfCfgRssa' - this writable configuration object sets the 2364 specific Reduced Set Selection Algorithm (RSSA) for the SMF 2365 process. If this object is set inconsistently across the MANET 2366 domain, multicast delivery of data will likely fail. Hence, 2367 intentionally mis-configuring this object could pose a form DOS 2368 attack against the MANET. 2370 o 'smfCfgRssaMember' - this writable configuration object sets the 2371 'interest' of the local SMF node in participating in the CDS. 2372 Setting this object to 'never(3)' on a highly highly connected 2373 device could lead to frequent island formation. Setting this 2374 object to 'always(2)' could support data ex-filtration from the 2375 MANET domain. 2377 o 'smfCfgIpv4Dpd' - this writable configuration object sets the 2378 duplicate packet detection method, i.e., H-DPD or I-DPD, for 2379 forwarding of IPv4 multicast packets. Forwarders may operate with 2380 mixed H-DPD and I-DPD modes as long as they consistently perform 2381 the appropriate DPD routines outlined [RFC6621]. However, it is 2382 RECOMMENDED that a deployment be configured with a common mode for 2383 operational consistency. 2385 o 'smfCfgIpv6Dpd' - this writable configuration object sets the 2386 duplicate packet detection method for forwarding of IPv6 multicast 2387 packets. Since IPv6 SMF does specifies an option header, the 2388 interoperability constraints are not as loose as in the IPv4 2389 version, and forwarders SHOULD not operate with mixed H-DPD and 2390 I-DPD modes. Hence the value for this object SHOULD be 2391 consistently set within the forwarders comprising the MANET, else 2392 inconsistent forwarding may result unnecessary multicast packet 2393 dropping. 2395 o 'smfCfgMaxPktLifetime' - this writable configuration object sets 2396 the estimate of the network packet traversal time. If set too 2397 small, this could lead to poor multicast data delivery ratios 2398 throughout the MANET domain. This could serve as a form of DOS 2399 attack if this object value is set too small. 2401 o 'smfCfgDpdEntryMaxLifetime' - this writable configuration object 2402 sets the maximum lifetime (in seconds) for the cached DPD records 2403 for the combined IPv4 and IPv6 methods. If the memory is running 2404 low prior to the MaxLifetimes being exceeded, the local SMF 2405 devices should purge the oldest records first. If this object 2406 value is set too small, then the effectiveness of the SMF DPD 2407 algorithms may become greatly diminished causing a higher than 2408 necessary packet load on the MANET. 2410 o 'smfCfgNhdpRssaMesgTLVIncluded' - this writable configuration 2411 object indicates whether the associated NHDP messages include the 2412 the RSSA Message TLV, or not. It is highly RECOMMENDED that this 2413 object be set to 'true(1)' when the SMF operation mode is set to 2414 independent as this information will inform the local forwarder of 2415 the RSSA algorithm implemented in neighboring forwarders and is 2416 used to ensure consistent forwarding across the MANET. While it 2417 is possible that SMF neighbors MAY be configured differently with 2418 respect to the RSSA algorithm and still operate cooperatively, but 2419 these cases will vary dependent upon the algorithm types 2420 designated and this situation SHOULD be avoided. 2422 o 'smfCfgNhdpRssaAddrBlockTLVIncluded' - this writable configuration 2423 object indicates whether the associated NHDP messages include the 2424 the RSSA Address Block TLV, or not. The 2425 smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it 2426 depends on the existence of an address block which may not be 2427 present. If this SMF device is configured with NHDP, then this 2428 object should be set to 'true(1)' as this TLV enables CDS relay 2429 algorithm operation and configuration to be shared among 2-hop 2430 neighborhoods. Some relay algorithms require 2-hop neighbor 2431 configuration in order to correctly select relay sets. 2433 o 'smfCfgAddrForwardingTable' - the writable configuration objects 2434 in this table indicate which multicast IP addresses are to be 2435 forwarded by this SMF node. Misconfiguration of rows within this 2436 table can limit the ability of this SMF device to properly forward 2437 multicast data. 2439 o 'smfCfgInterfaceTable' - the writable configuration objects in 2440 this table indicate which SMF node interfaces are participating in 2441 the SMF packet forwarding process. Misconfiguration of rows 2442 within this table can limit the ability of this SMF device to 2443 properly forward multicast data. 2445 Some of the readable objects in this MIB module (i.e., objects with a 2446 MAX-ACCESS other than not-accessible) may be considered sensitive or 2447 vulnerable in some network environments. It is thus important to 2448 control even GET and/or NOTIFY access to these objects and possibly 2449 to even encrypt the values of these objects when sending them over 2450 the network via SNMP. These are the tables and objects and their 2451 sensitivity/vulnerability: 2453 o 'smfNodeRsStatusIncluded' - this readable state object indicates 2454 that this SMF node is part of the CDS, or not. Being part of the 2455 CDS makes this node a distinguished device. It could be exploited 2456 for data ex-filtration, or denial of service attacks. 2458 o 'smfStateNeighborTable' - the readable state objects in this table 2459 indicate current neighbor nodes to this SMF node. Exposing this 2460 information to an attacker could allow the attacker easier access 2461 to the larger MANET domain. 2463 The remainder of the objects in the SMF-MIB module are performance 2464 counter objects. While these give an indication of the activity of 2465 the SMF process on this node, it is not expected that exposing these 2466 values pose a security risk to the MANET network. 2468 SNMP versions prior to SNMPv3 did not include adequate security. 2469 Even if the network itself is secure (for example by using IPSec), 2470 even then, there is no control as to who on the secure network is 2471 allowed to access and GET/SET (read/change/create/delete) the objects 2472 in this MIB module. 2474 Implementations MUST provide the security features described by the 2475 SNMPv3 framework (see [RFC3410] ), including full support for 2476 authentication and privacy via the User-based Security Model (USM) 2477 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2478 MAY also provide support for the Transport Security Model (TSM) 2479 [RFC5591] in combination with a secure transport such as SSH 2480 [RFC5592] or TLS/DTLS [RFC6353]. 2482 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2483 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2484 enable cryptographic security. It is then a customer/operator 2485 responsibility to ensure that the SNMP entity giving access to an 2486 instance of this MIB module is properly configured to give access to 2487 the objects only to those principals (users) that have legitimate 2488 rights to indeed GET or SET (change/create/delete) them. 2490 9. Applicability Statement 2492 This document describes objects for configuring parameters of the 2493 Simplified Multicast Forwarding [RFC6621] process on a Mobile Ad-Hoc 2494 Network (MANET) router. This MIB module, denoted SMF-MIB, also 2495 reports state and performance information and notifications. This 2496 section provides some examples of how this MIB module can be used in 2497 MANET network deployments. A fuller discussion of MANET network 2498 management use cases and challenges will be provided elsewhere. 2500 SMF is designed to allow MANET routers to forward IPv4 and IPv6 2501 packets over the MANET and cover the MANET nodes through the 2502 automatic discovery of efficient estimates of the Minimum Connected 2503 Dominating Set (MCDS) of nodes within the MANET. The MCDS are 2504 estimated using the Relay Set Selection Algorithms (RSSAs) discussed 2505 within this document. In the following, three scenarios are listed 2506 where this MIB module is useful, i.e., 2508 o For a Parking Lot Initial Configuration Situation - it is common 2509 for the vehicles comprising the MANET being forward deployed at a 2510 remote location, e.g., the site of a natural disaster, to be off- 2511 loaded in a parking lot where an initial configuration of the 2512 networking devices is performed. The configuration is loaded into 2513 the devices from a fixed location Network Operation Center (NOC) 2514 at the parking lot and the vehicles are stationary at the parking 2515 lot while the configuration changes are made. Standards-based 2516 methods for configuration management from the co-located NOC are 2517 necessary for this deployment option. The set of interesting 2518 configuration objects for the SMF process are listed within this 2519 MIB module. 2521 o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed 2522 NOC - Here the vehicles carrying the MANET routers carry multiple 2523 wireless interfaces, one of which is a relatively low-bandwidth 2524 on-the-move satellite connection which interconnects a fix NOC to 2525 the nodes of the MANET. Standards-based methods for monitoring 2526 and fault management from the fixed NOC are necessary for this 2527 deployment option. 2529 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 2530 larger vehicles, a hierarchical network management arrangement is 2531 useful. Centralized network management is performed from a fixed 2532 NOC while local management is performed locally from within the 2533 vehicles. Standards-based methods for configuration, monitoring 2534 and fault management are necessary for this deployment option. 2536 Here we provide an example of the simplest of configurations to 2537 establish an operational multicast forwarding capability in a MANET. 2539 This discussion only identifies the configuration necessary through 2540 the SMF-MIB module and assumes that other configuration has occurred. 2541 Assume that the MANET is to support only IPv4 addressing and that the 2542 MANET nodes are to be configured in the context of the Parking Lot 2543 Initialization case above. Then the SMF-MIB module defines ten 2544 configuration OIDs and two configuration tables, i.e., the 2545 smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten 2546 OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL 2547 clauses which allow for a functional configuration of the SMF process 2548 within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the 2549 smfCfgRouterID can be set as, e.g.,: 2551 snmpset [options] .0 a 192.168.1.100 2553 If the smfCfgAddrForwardingTable is left empty, then the SMF local 2554 forwarder will forward all multicast addresses. So this table does 2555 not require configuration if you want to have the MANET forward all 2556 multicast addresses. 2558 All that remains is to configure at least one row in the 2559 smfCfgInterfaceTable. Assume that the node has a wireless interface 2560 with an ='wlan0' and an ='1'. All of the objects in 2561 the rows of the smfCfgInterfaceTable have a DEFVAL clause, hence only 2562 the RowStatus object needs to be set. So the SMF process will be 2563 activated on the 'wlan0' interface by the following network manager 2564 snmpset command: 2566 snmpset [options] .1 i active(1) 2568 At this point, the configured forwarder will begin a Classical 2569 Flooding algorithm to forward all multicast addresses IPv4 packets it 2570 receives. If the 2572 To provide a more efficient multicast forwarding within the MANET, 2573 the network manager could walk the smfCapabilitiesTable to identify 2574 other SMF operational modes, e.g.,: 2576 snmpwalk -c public -v 2c router 2578 SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1 2580 SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2 2582 SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1) 2584 SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2) 2586 SMF-MIB::smfCapabilitiesRssaID.1 = INTEGER: cF(1) 2587 SMF-MIB::smfCapabilitiesRssaID.2 = INTEGER: eCDS(3) 2589 In this example, the forwarding device also supports the Extended 2590 Connected Dominating Set (eCDS) RSSA with the forwarder in the 2591 'independent(2)' operational mode. If the network manager were to 2592 then issue an snmpset, e.g.,: 2594 snmpset [options] .0 i 2 2596 then the local forwarder would switch if forwarding behavior from 2597 Classical Flooding to the more efficient eCDS flooding. 2599 10. IANA Considerations 2601 The MIB module in this document uses the following IANA-assigned 2602 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 2604 Descriptor OBJECT IDENTIFIER value 2605 ---------- ----------------------- 2606 SMF-MIB { experimental XXXX } 2607 IANA EDITOR NOTE: please assign XXXX, and remove this note. 2609 11. Contributors 2611 This MIB document uses the template authored by D. Harrington which 2612 is based on contributions from the MIB Doctors, especially Juergen 2613 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2615 12. Acknowledgements 2617 The authors would like to acknowledge the valuable comments from Sean 2618 Harnedy in the early phases of the development of this MIB module. 2619 The authors would like to thank James Nguyen for his careful review 2620 and comments on this MIB module and his work on the definitions of 2621 the follow on MIB modules to configure specific RSSA algorithms 2622 related to SMF. Further, the authors would like to acknowledge to 2623 work of James Nguyen, Brian Little, Ryan Morgan and Justin Dean on 2624 their software development of the SMF-MIB. 2626 13. References 2628 13.1. Normative References 2630 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2631 MIB", RFC 2863, June 2000. 2633 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2634 Architecture for Describing Simple Network Management 2635 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2636 December 2002. 2638 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 2639 Simple Network Management Protocol (SNMP)", STD 62, 2640 RFC 3418, December 2002. 2642 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2643 Schoenwaelder, "Textual Conventions for Internet Network 2644 Addresses", RFC 4001, February 2005. 2646 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2647 Requirement Levels", BCP 14, RFC 2119, March 1997. 2649 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2650 Schoenwaelder, Ed., "Structure of Management Information 2651 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2653 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2654 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2655 STD 58, RFC 2579, April 1999. 2657 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2658 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2659 April 1999. 2661 [RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621, 2662 May 2012. 2664 13.2. Informative References 2666 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2667 "Introduction and Applicability Statements for Internet- 2668 Standard Management Framework", RFC 3410, December 2002. 2670 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2671 (USM) for version 3 of the Simple Network Management 2672 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 2674 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 2675 Advanced Encryption Standard (AES) Cipher Algorithm in the 2676 SNMP User-based Security Model", RFC 3826, June 2004. 2678 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2679 for the Simple Network Management Protocol (SNMP)", 2680 RFC 5591, June 2009. 2682 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 2683 Shell Transport Model for the Simple Network Management 2684 Protocol (SNMP)", RFC 5592, June 2009. 2686 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 2687 Model for the Simple Network Management Protocol (SNMP)", 2688 RFC 6353, July 2011. 2690 Appendix A. Appendix A: 2692 This appendix contains the IANAsmfOpModeID-MIB module defined by this 2693 specification below. The RFC editor should remove this specification 2694 of the IANAsmfOpModeID-MIB upon publication of the SMF-MIB. Further, 2695 IANA should take over the IANAsmfOpModeID-MIB and to keep it 2696 synchronized with the registry identified below within the 2697 IANAsmfOpModeIdTC TEXTUAL-CONVENTION. 2699 IANAsmfOpModeID-MIB DEFINITIONS ::= BEGIN 2701 IMPORTS 2702 MODULE-IDENTITY, mib-2 2703 FROM SNMPv2-SMI 2704 TEXTUAL-CONVENTION 2705 FROM SNMPv2-TC; 2707 ianasmfOpModeID MODULE-IDENTITY 2708 LAST-UPDATED "201401190000Z" -- January 19, 2014 2709 ORGANIZATION "IANA" 2710 CONTACT-INFO "Internet Assigned Numbers Authority 2712 Postal: ICANN 2713 4676 Admiralty Way, Suite 330 2714 Marina del Rey, CA 90292 2716 Tel: +1 310 823 9358 2717 E-Mail: iana@iana.org" 2718 DESCRIPTION "This MIB module defines the 2719 IANAsmfOpModeIdTC Textual 2720 Convention, and thus the enumerated values of 2721 the smfCapabilitiesOpModeID object defined in 2722 the SMF-MIB." 2723 REVISION "201401190000Z" -- January 19, 2014 2724 DESCRIPTION "Initial version of this MIB as published in 2725 RFC KKKK." 2726 ::= { mib-2 kkkk } 2728 IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION 2729 STATUS current 2730 DESCRIPTION 2731 "An index that identifies through reference to a specific 2732 SMF operations mode. There are basically three styles 2733 of SMF operation with reduced relay sets: 2735 Independent operation 'independent(1)' - 2736 SMF performs its own relay 2737 set selection using information from an associated 2738 MANET NHDP process. 2740 CDS-aware unicast routing operation 'routing(2)'- 2741 a coexistent unicast routing 2742 protocol provides dynamic relay 2743 set state based upon its own control plane 2744 CDS or neighborhood discovery information. 2746 Cross-layer operation 'crossLayer(3)' - 2747 SMF operates using neighborhood 2748 status and triggers from a 2749 cross-layer information base for dynamic relay 2750 set selection and maintenance. 2752 IANA MUST update this textual convention accordingly. 2754 The definition of this textual convention with the 2755 addition of newly assigned values is published 2756 periodically by the IANA, in either the Assigned 2757 Numbers RFC, or some derivative of it specific to 2758 Internet Network Management number assignments. (The 2759 latest arrangements can be obtained by contacting the 2760 IANA.) 2762 Requests for new values should be made to IANA via 2763 email (iana@iana.org)." 2764 REFERENCE 2765 "See Section 7.2. 'Reduced Relay Set Forwarding', 2766 and the Appendices A, B and C in 2767 RFC 6621 - Simplified Multicast Forwarding 2768 (SMF), Macker, J., May 2012." 2769 SYNTAX INTEGER { 2770 independent (1), 2771 routing (2), 2772 crossLayer (3) 2773 -- future (4-255) 2774 } 2776 END 2778 Appendix B. Appendix B: 2780 This appendix contains the IANAsmfRssaID-MIB module defined by this 2781 specification below. The RFC editor should remove this specification 2782 of the IANAsmfRssaID-MIB upon publication of the SMF-MIB. Further, 2783 IANA should take over the IANAsmfRssaID-MIB and to keep it 2784 synchronized with the registry identified below within the 2785 IANAsmfRssaIdTC TEXTUAL-CONVENTION. 2787 IANAsmfRssaID-MIB DEFINITIONS ::= BEGIN 2789 IMPORTS 2790 MODULE-IDENTITY, mib-2 2791 FROM SNMPv2-SMI 2792 TEXTUAL-CONVENTION 2793 FROM SNMPv2-TC; 2795 ianasmfRssaID MODULE-IDENTITY 2796 LAST-UPDATED "201401190000Z" -- January 19, 2014 2797 ORGANIZATION "IANA" 2798 CONTACT-INFO "Internet Assigned Numbers Authority 2800 Postal: ICANN 2801 4676 Admiralty Way, Suite 330 2802 Marina del Rey, CA 90292 2804 Tel: +1 310 823 9358 2805 E-Mail: iana@iana.org" 2806 DESCRIPTION "This MIB module defines the 2807 IANAsmfRssaIdTC Textual 2808 Convention, and thus the enumerated values of 2809 the smfCapabilitiesRssaID object defined in 2810 the SMF-MIB." 2811 REVISION "201401190000Z" -- January 19, 2014 2812 DESCRIPTION "Initial version of this MIB as published in 2813 RFC LLLL." 2815 ::= { mib-2 llll } 2817 IANAsmfRssaIdTC ::= TEXTUAL-CONVENTION 2818 STATUS current 2819 DESCRIPTION 2820 "An index that identifies through reference to a specific 2821 RSSA algorithms. Several are currently defined 2822 in the Appendix A, B and C of RFC 6621. 2824 Examples of RSSA algorithms already identified within 2825 this TC are: 2827 Classical Flooding (cF(1)) - is the standard 2828 flooding algorithm where each node in the next 2829 retransmits the information on each of its interfaces. 2831 Source-Based Multipint Relay (sMPR(2)) - 2832 this algorithm is used by Optimized Link State Routing 2833 (OLSR) and OLSR version 2 (OLSRv2) protocols for the 2834 relay of link state updates and other control 2835 information [RFC3626]. Since each router picks 2836 its neighboring relays independently, sMPR 2837 forwarders depend upon previous hop information 2838 (e.g., source MAC address) to operate correctly. 2840 Extended Connected Dominating Set (eCDS(3)) - 2841 defined in [RFC5614] this algorithm forms a single 2842 CDS mesh for the SMF operating region. Its 2843 packet-forwarding rules are not dependent upon 2844 previous hop knowledge in contrast to sMPR. 2846 Multipoint Relay Connected Dominating Set (mprCDS(4)) - 2847 This algorithm is an extension to the basic sMPR 2848 election algorithm that results in a shared 2849 (non-source-specific) SMF CDS. Thus, its forwarding 2850 rules are not dependent upon previous hop information, 2851 similar to eCDS. 2853 IANA MUST update this textual convention accordingly. 2855 The definition of this textual convention with the 2856 addition of newly assigned values is published 2857 periodically by the IANA, in either the Assigned 2858 Numbers RFC, or some derivative of it specific to 2859 Internet Network Management number assignments. (The 2860 latest arrangements can be obtained by contacting the 2861 IANA.) 2863 Requests for new values should be made to IANA via 2864 email (iana@iana.org)." 2865 REFERENCE 2866 "See, e.g., 2868 Section 8.1.1. 'SMF Message TLV Type', 2869 Appendix A. 'Essential Connecting Dominating Set (E-CDS) 2870 Algorithm', 2871 Appendix B. 'Source-Based Multipoint Relay (S-MPR) 2872 Algorithm', and 2874 Appendix C. 'Multipoint Relay Connected Dominating Set 2875 (MPR-CDS) Algorithm' 2877 in RFC 6621 - Simplified Multicast Forwarding 2878 (SMF), Macker, J., May 2012." 2879 SYNTAX INTEGER { 2880 cF(1), 2881 sMPR(2), 2882 eCDS(3), 2883 mprCDS(4) 2884 -- future(5-127) 2885 -- noStdAction(128-239) 2886 -- experimental(240-255) 2887 } 2889 END 2891 Appendix C. 2893 *************************************************************** 2894 * Note to the RFC Editor (to be removed prior to publication) * 2895 * * 2896 * * 2897 * 1) The reference to RFCXXXX throughout this document point * 2898 * to the current draft-ietf-manet-smf-xx.txt. This needs * 2899 * to be replaced with the XXXX RFC number for the SMF * 2900 * publication. * 2901 * * 2902 * 2) Appendix A contains the IANAsmfOpModeID-MIB * 2903 * module which is defined by this specification in the * 2904 * appendix. The RFC editor should remove this specification * 2905 * of the IANAsmfOpModeID-MIB upon publication of * 2906 * the SMF-MIB. Further, IANA should take over the * 2907 * IANAsmfOpModeID-MIB and keep it synchronized * 2908 * with the registry identified within the contained * 2909 * IANAsmfOpModeIdTC TEXTUAL-CONVENTION. * 2910 * * 2911 * 3) Appendix B contains the IANAsmfRssaID-MIB * 2912 * module which is defined by this specification in the * 2913 * appendix. The RFC editor should remove this specification * 2914 * of the IANAsmfRssaID-MIB upon publication of * 2915 * the SMF-MIB. Further, IANA should take over the * 2916 * IANAsmfRssaID-MIB and keep it synchronized * 2917 * with the registry identified within the contained * 2918 * IANAsmfRssaID TEXTUAL-CONVENTION. * 2919 * * 2920 *************************************************************** 2922 Authors' Addresses 2924 Robert G. Cole 2925 US Army CERDEC 2926 6010 Frankford Road 2927 Aberdeen Proving Ground, Maryland 21005 2928 USA 2930 Phone: +1 443 395 8744 2931 EMail: robert.g.cole@us.army.mil 2932 Joseph Macker 2933 Naval Research Laboratory 2934 Washington, D.C. 20375 2935 USA 2937 EMail: macker@itd.nrl.navy.mil 2939 Brian Adamson 2940 Naval Research Laboratory 2941 Washington, D.C. 20375 2942 USA 2944 EMail: adamson@itd.nrl.navy.mil