idnits 2.17.1 draft-ietf-manet-smf-mib-11.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 1091 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 (March 23, 2014) is 3687 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: 'RFC3932' is mentioned on line 2397, but not defined ** Obsolete undefined reference: RFC 3932 (Obsoleted by RFC 5742) == Missing Reference: 'RFC3626' is mentioned on line 2499, but not defined == Missing Reference: 'RFC5614' is mentioned on line 2505, but not defined Summary: 1 error (**), 0 flaws (~~), 9 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: September 24, 2014 B. Adamson 6 Naval Research Laboratory 7 March 23, 2014 9 Definition of Managed Objects for the Manet Simplified Multicast 10 Framework Relay Set Process 11 draft-ietf-manet-smf-mib-11 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 September 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. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 10 77 8. IANA-SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . 51 78 9. Security Considerations . . . . . . . . . . . . . . . . . . . 55 79 10. Applicability Statement . . . . . . . . . . . . . . . . . . . 58 80 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 81 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 62 82 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 62 83 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62 84 14.1. Normative References . . . . . . . . . . . . . . . . . . . 62 85 14.2. Informative References . . . . . . . . . . . . . . . . . . 63 86 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 64 88 1. Introduction 90 This memo defines a portion of the Management Information Base (MIB) 91 for use with network management protocols in the Internet community. 92 In particular, it describes objects for configuring aspects of a 93 process implementing Simplified Multicast Forwarding (SMF) [RFC6621] 94 for Mobile Ad-Hoc Networks (MANETs). SMF provides multicast 95 Duplicate Packet Detection (DPD) and supports algorithms for 96 constructing an estimate of a MANET Minimum Connected Dominating Set 97 (MCDS) for efficient multicast forwarding. The SMF-MIB module also 98 reports state information, performance information, and 99 notifications. In addition to configuration, this additional state 100 and performance information is useful to operators troubleshooting 101 multicast forwarding problems. 103 2. The Internet-Standard Management Framework 105 For a detailed overview of the documents that describe the current 106 Internet-Standard Management Framework, please refer to section 7 of 107 RFC 3410 [RFC3410]. 109 Managed objects are accessed via a virtual information store, termed 110 the Management Information Base or MIB. MIB objects are generally 111 accessed through the Simple Network Management Protocol (SNMP). 112 Objects in the MIB are defined using the mechanisms defined in the 113 Structure of Management Information (SMI). This memo specifies a MIB 114 module that is compliant to the SMIv2, which is described in STD 58, 115 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 116 [RFC2580]. 118 3. Conventions 120 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 121 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 122 document are to be interpreted as described in RFC 2119 [RFC2119]. 124 4. Overview 126 SMF provides methods for implementing Duplicate Packet Detection 127 (DPD)-based multicast forwarding with the optional use of Connected 128 Dominating Set (CDS)-based relay sets. The CDS provides a complete 129 connected coverage of the nodes comprising the MANET. The Minimum 130 CDS (MCDS) is the smallest set of MANET nodes (comprising a connected 131 cluster) which cover all the nodes in the cluster with their 132 transmissions. As the density of the MANET nodes increase, the 133 fraction of nodes required in an MCDS decreases. Using the MCDS as a 134 multicast forwarding set then becomes an efficient multicast 135 mechanism for MANETs. 137 Various algorithms for the construction of estimates of the MCDS 138 exist. The Simplified Multicast Framework [RFC6621] describes some 139 of these. It further defines various operational modes for a node 140 which is participating in the collective creation of the MCDS 141 estimates. These modes depend upon the set of related MANET routing 142 and discovery protocols and mechanisms in operation in the specific 143 MANET node. 145 A SMF router's MIB module contains SMF process configuration 146 parameters (e.g. specific CDS algorithm), state information (e.g., 147 current membership in the CDS), performance counters (e.g., packet 148 counters), and notifications. 150 4.1. SMF Management Model 152 This section describes the management model for the SMF node process. 154 Figure 1 (reproduced from Figure 1 of [RFC6621]) shows the 155 relationship between the SMF Relay Set selection algorithm and the 156 related algorithms, processes and protocols running in the MANET 157 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 158 topology information gotten from the MANET Neighborhood Discovery 159 Protocol (NHDP), from the specific MANET routing protocol running on 160 the node, or from Layer 2 information passed up to the higher layer 161 protocol processes. 163 ______________ ____________ 164 | | | | 165 | Neighborhood | | Relay Set | 166 | Discovery |------------->| Selection | 167 | | neighbor | | 168 |______________| info |____________| 169 \ / 170 \ / 171 neighbor\ / forwarding 172 info \ _____________ / status 173 \ | | / 174 `-->| Forwarding |<--' 175 | Process | 176 ----------------->|_____________|-----------------> 177 incoming packet, forwarded packets 178 interface id , and 179 previous hop 181 Figure 1: SMF Router Architecture 183 4.2. Terms 185 The following definitions apply throughout this document: 187 o Configuration Objects - switches, tables, objects which are 188 initialized to default settings or set through the management 189 interfaces such as defined by this MIB module. 191 o Tunable Configuration Objects - objects whose values affect timing 192 or attempt bounds on the SMF Relay Set (RS) process. 194 o State Objects - automatically generated values which define the 195 current operating state of the SMF RS process in the router. 197 o Performance Objects - automatically generated values which help an 198 administrator or automated tool to assess the performance of the 199 CDS multicast process on the router and the overall multicast 200 performance within the MANET routing domain. 202 5. Structure of the MIB Module 204 This section presents the structure of the SMF-MIB module. The 205 objects are arranged into the following groups: 207 o smfMIBNotifications - defines the notifications associated with 208 the SMF process. 210 o smfMIBObjects - defines the objects forming the basis for the SMF- 211 MIB module. These objects are divided up by function into the 212 following groups: 214 * Capabilities Group - This group contains the SMF objects that 215 the device uses to advertise its local capabilities with 216 respect to, e.g., the supported RSSAs. 218 * Configuration Group - This group contains the SMF objects that 219 configure specific options that determine the overall operation 220 of the SMF process and the resulting multicast performance. 222 * State Group - Contains information describing the current state 223 of the SMF process such as the Neighbor Table. 225 * Performance Group - Contains objects which help to characterize 226 the performance of the SMF process, typically counters for 227 statistical computations. 229 o smfMIBConformance - defines two, i.e., minimal and full, 230 conformance implementations for the SMF-MIB module. 232 5.1. Textual Conventions 234 The textual conventions defined within the SMF-MIB module are: 236 o The SmfStatus is defined within the SMF-MIB module. This contains 237 the current operational status of the SMF process on an interface. 239 The textual conventions defined for the SMF-MIB module and maintained 240 by IANA are: 242 o The IANAsmfOpModeIdTC represents an index that identifies a 243 specific SMF operational mode. This textual convention is 244 maintained by IANA in the IANA-SMF-MIB. 246 o The IANAsmfRssaIdTC represents an index that identifies, through 247 reference, a specific RSSA available for operation on the device. 248 This textual convention is maintained by IANA also in the IANA- 249 SMF-MIB. 251 5.2. The Capabilities Group 253 The SMF device supports a set of capabilities. The list of 254 capabilities which the device can advertise are: 256 o Operational Mode - topology information from NHDP, CDS-aware 257 unicast routing or Cross-layer from Layer 2. 259 o SMF RSSA - the specific RSSA operational on the device. Note that 260 configuration, state and performance objects related to a specific 261 RSSA must be defined within a separate MIB module. 263 5.3. The Configuration Group 265 The SMF device is configured with a set of controls. Some of the 266 prominent configuration controls for the SMF device are: 268 o Operational Mode - determines where topology information is 269 derived from, e.g., NHDP, CDS-aware unicast routing or Cross-layer 270 from Layer 2. 272 o SMF RSSA - the specific RSSA operational on the device. 274 o Duplicate Packet detection for IPv4 - Identification-based or 275 Hash-based DPD. 277 o Duplicate Packet detection for IPv6 - Identification-based or 278 Hash-based DPD. 280 o SMF Type Message TLV - if NHDP mode is selected, then the SMF Type 281 Message TLV MAY be included in the NHDP exchanges. 283 o SMF Address Block TLV - if NHDP mode is selected, then the SMF 284 Address Block TLV SHOULD be included in the NHDP exchanges. 286 o SMF Address Forwarding Table - a table identifying configured 287 multicast addresses to be forwarded by the SMF process. 289 5.4. The State Group 291 The State sub-tree reports current state information, e.g., 293 o Node RSSA State - identifies whether the node is currently in or 294 out of the Relay Set. 296 o Neighbors Table - a table containing current one-hop neighbors and 297 their operational RSSA. 299 5.5. The Performance Group 301 The Performance sub-tree reports primarily counters that relate to 302 SMF RSSA performance. The SMF performance counters consists of per 303 node and per interface objects: 305 o Total multicast packets received. 307 o Total multicast packets forwarded. 309 o Total duplicate multicast packets detected. 311 o Per interface statistics table with the following entries: 313 * Multicast packets received. 315 * Multicast packets forwarded. 317 * Duplicate multicast packets detected. 319 5.6. The Notifications Group 321 The Notifications Sub-tree contains the list of notifications 322 supported within the SMF-MIB module and their intended purpose and 323 utility. 325 5.7. Tables and Indexing 327 The SMF-MIB module contains a number of tables which record data 328 related to: 330 o configuration and operation of packet forwarding on the local 331 router, 333 o configuration and operation of local MANET interfaces on the 334 router, and 336 o configuration and operation of various RSSA algorithms for packet 337 forwarding. 339 The SMF-MIB module's tables are indexed via the following constructs: 341 o smfCapabilitiesIndex - the index identifying the combination of 342 SMF mode and SMF RSSA available on this device. 344 o smfCfgAddrForwardingIndex - the index to configured multicast 345 addresses lists which are forwarded by the SMF process. 347 o smfCfgIfIndex - the IfIndex of the interface on the local router 348 on which SMF is configured. 350 o smfStateNeighborIpAddrType, smfStateNeighborIpAddr, and 351 smfStateNeighborPrefixLen - the interface index set of specific 352 one-hop neighbor nodes to this local router. 354 These tables and their associated indexing are: 356 o smfCapabilitiesTable - identifies the resident set of (SMF 357 Operational Modes, SMF RSSA algorithms) available on this router. 358 This table has 'INDEX { smfCapabilitiesIndex }. 360 o smfCfgAddrForwardingTable - contains information on multicast 361 addresses which are to be forwarded by the SMF process on this 362 device. This table has 'INDEX { smfCfgAddrForwardingIndex }'. 364 o smfCfgInterfaceTable - describes the SMF interfaces on this device 365 that are participating in the SMF packet forwarding process. This 366 table has 'INDEX { smfCfgIfIndex }'. 368 o smfStateNeighborTable - describes the current neighbor nodes, 369 their addresses and the SMF RSSA and the interface on which they 370 can be reached. This table has 'INDEX { 371 smfStateNeighborIpAddrType, smfStateNeighborIpAddr, 372 smfStateNeighborPrefixLen }'. 374 o smfPerfIpv4InterfacePerfTable - contains the IPv4 related SMF 375 statistics per each SMF interface on this device. This table has 376 'INDEX { smfCfgIfIndex }'. 378 o smfPerfIpv6InterfacePerfTable - contains the IPv6 related SMF 379 statistics per each SMF interface on this device. This table has 380 'INDEX { smfCfgIfIndex }'. 382 6. Relationship to Other MIB Modules 384 6.1. Relationship to the SNMPv2-MIB 386 The 'system' group in the SNMPv2-MIB module [RFC3418] is defined as 387 being mandatory for all systems, and the objects apply to the entity 388 as a whole. The 'system' group provides identification of the 389 management entity and certain other system-wide data. The SMF-MIB 390 module does not duplicate those objects. 392 6.2. MIB modules required for IMPORTS 394 The textual conventions imported for use in the SMF-MIB module are as 395 follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 396 Counter32, Unsigned32, Integer32 and mib-2 textual conventions are 397 imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 398 and TruthValue textual conventions are imported from RFC 2579 399 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- 400 GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 401 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. SMF-MIB 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 IANA-SMF-MIB 448 IANAsmfRssaIdTC 449 FROM IANA-SMF-MIB 450 ; 452 smfMIB MODULE-IDENTITY 453 LAST-UPDATED "201403231300Z" -- March 23, 2014 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 "201403231300Z" -- March 23, 2014 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 -- 540 -- 541 -- smfCapabilitiesGroup 542 -- 543 -- This group contains the SMF objects that identify specific 544 -- capabilities within this device related to SMF functions. 545 -- 547 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 549 -- 550 -- SMF Capabilities Table 551 -- 553 smfCapabilitiesTable OBJECT-TYPE 554 SYNTAX SEQUENCE OF SmfCapabilitiesEntry 555 MAX-ACCESS not-accessible 556 STATUS current 557 DESCRIPTION 558 "The smfCapabilitiesTable identifies the 559 resident set of SMF Operational Modes and 560 RSSA combinations that can run on this 561 forwarder." 562 REFERENCE 563 "See Section 7.2. 'Reduced Relay Set Forwarding', 564 Section 8.1.1. 'SMF Message TLV Type', and 565 the Appendices A, B and C in 566 RFC 6621 - Simplified Multicast Forwarding 567 (SMF), Macker, J., May 2012." 568 ::= { smfCapabilitiesGroup 1 } 570 smfCapabilitiesEntry OBJECT-TYPE 571 SYNTAX SmfCapabilitiesEntry 572 MAX-ACCESS not-accessible 573 STATUS current 574 DESCRIPTION 575 "Information about a particular operational 576 mode and RSSA combination. 577 " 578 INDEX { smfCapabilitiesIndex } 579 ::= { smfCapabilitiesTable 1 } 581 SmfCapabilitiesEntry ::= SEQUENCE { 582 smfCapabilitiesIndex Integer32, 583 smfCapabilitiesOpModeID IANAsmfOpModeIdTC, 584 smfCapabilitiesRssaID IANAsmfRssaIdTC 585 } 587 smfCapabilitiesIndex OBJECT-TYPE 588 SYNTAX Integer32 (1..2147483647) 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION 592 "The index for this entry; a unique value, 593 greater than zero, for each combination of 594 a particular operational mode and RSSA 595 algorithm available on this device. 596 It is recommended that values are assigned 597 contiguously starting from 1. 599 Rows in this table are automatically 600 populated by the entity's management system 601 on initialization. 603 By default, the agent should support at least the 604 Classical Flooding 'cF' algorithm. All compliant 605 SMF forwarders must support Classical Flooding. 606 Hence, the first entry in this table MUST exist 607 and MUST be defined as: 609 smfCapabilitiesIndex i '1' 610 smfCapabilitiesOpModeID i 'cfOnly(1)' 611 smfCapabilitiesRssaID i 'cF(1)' 613 The value for each combination MUST remain 614 constant at least from one re-initialization 615 of the entity's management system to the 616 next re-initialization." 617 ::= { smfCapabilitiesEntry 1 } 619 smfCapabilitiesOpModeID OBJECT-TYPE 620 SYNTAX IANAsmfOpModeIdTC 621 MAX-ACCESS read-only 622 STATUS current 623 DESCRIPTION 624 "This object identifies 625 the particular operational mode for this device." 626 ::= { smfCapabilitiesEntry 2 } 628 smfCapabilitiesRssaID OBJECT-TYPE 629 SYNTAX IANAsmfRssaIdTC 630 MAX-ACCESS read-only 631 STATUS current 632 DESCRIPTION 633 "This object identifies 634 the particular RSSA algorithm in this MIB 635 module. Example RSSAs are found in the 636 appendix of RFC 6621." 637 REFERENCE 638 "See, e.g., Section 8.1.1. 'SMF Message TLV Type', 639 and the Appendices A, B and C in 640 RFC 6621 - Simplified Multicast Forwarding 641 (SMF), Macker, J., May 2012." 642 ::= { smfCapabilitiesEntry 3 } 644 -- 645 -- smfConfigurationGroup 646 -- 647 -- This group contains the SMF objects that configure specific 648 -- options that determine the overall performance and operation 649 -- of the multicast forwarding process for the router device 650 -- and its interfaces. 651 -- 653 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 655 smfCfgAdminStatus OBJECT-TYPE 656 SYNTAX SmfStatus 657 MAX-ACCESS read-write 658 STATUS current 659 DESCRIPTION 660 "The configured status of the SMF process 661 on this device. 'enabled(1)' means that 662 SMF is configured to run on this device. 663 'disabled(2)' mean that the SMF process 664 is configured off. 666 Prior to SNM functions being performed over 667 specific interfaces, this object must first 668 be 'enabled'. If this object is 'disabled', 669 then no SMF functions are being performed on 670 the device and all smfIfAdminStatus objects 671 MUST also be set to 'disabled'. When this 672 object is changed from 'enabled' to 'disabled' 673 by the manager, then all smfIfAdminStatus 674 objects MUST also be automatically set to 675 'disabled' by the agent. 677 The default value for this object SHOULD be 678 'enabled'. 680 This object is persistent and when written 681 the entity SHOULD save the change to 682 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 } 823 ::= { smfConfigurationGroup 6 } 825 smfCfgIpv4Dpd OBJECT-TYPE 826 SYNTAX INTEGER { 827 hashBased(1), 828 identificationBased(2) 829 } 830 MAX-ACCESS read-write 831 STATUS current 832 DESCRIPTION 833 "The current method for IPv4 duplicate packet 834 detection. 836 The value 'hashBased(1)' indicates that the 837 routers duplicate packet detection is based 838 upon comparing a hash over the packet fields. 839 This is the default setting for this object. 841 The value 'identificationBased(2)' 842 indicates that the duplicate packet 843 detection relies upon header information 844 in the multicast packets to identify 845 previously received packets. 847 This object is persistent and when written 848 the entity SHOULD save the change to 849 non-volatile storage." 850 REFERENCE 851 "See Section 6.2. 'IPv4 Duplicate Packet 852 Detection' in RFC 6621 - Simplified 853 Multicast Forwarding (SMF), Macker, J., 854 May 2012." 855 DEFVAL { hashBased } 856 ::= { smfConfigurationGroup 7 } 858 smfCfgIpv6Dpd OBJECT-TYPE 859 SYNTAX INTEGER { 860 hashBased(1), 861 identificationBased(2) 862 } 863 MAX-ACCESS read-write 864 STATUS current 865 DESCRIPTION 866 "The current method for IPv6 duplicate packet 867 detection. 869 The values indicate the type of method used 870 for duplicate packet detection as described 871 the previous description for the object 872 `smfCfgIpv4Dpd'. 874 The default value for this object is 875 'hashBased(1)'. 877 This object is persistent and when written 878 the entity SHOULD save the change to 879 non-volatile storage." 880 REFERENCE 881 "See Section 6.1. 'IPv6 Duplicate Packet 882 Detection' in RFC 6621 - Simplified 883 Multicast Forwarding (SMF), Macker, J., 884 May 2012." 885 DEFVAL { hashBased } 886 ::= { smfConfigurationGroup 8 } 888 smfCfgMaxPktLifetime OBJECT-TYPE 889 SYNTAX Integer32 (0..65535) 890 UNITS "Seconds" 891 MAX-ACCESS read-write 892 STATUS current 893 DESCRIPTION 894 "The estimate of the network packet 895 traversal time. 897 This object is persistent and when written 898 the entity SHOULD save the change to 899 non-volatile storage." 900 REFERENCE 901 "See Section 6. 'SMF Duplicate Packet 902 Detection' in RFC 6621 - Simplified 903 Multicast Forwarding (SMF), Macker, J., 904 May 2012." 905 DEFVAL { 60 } 906 ::= { smfConfigurationGroup 9 } 908 smfCfgDpdEntryMaxLifetime OBJECT-TYPE 909 SYNTAX Integer32 (0..65525) 910 UNITS "Seconds" 911 MAX-ACCESS read-write 912 STATUS current 913 DESCRIPTION 914 "The maximum lifetime of a cached DPD 915 record in the local device storage. 917 If the memory is running low prior to the 918 MaxLifetime being exceeded, the local SMF 919 devices should purge the oldest records first. 921 This object is persistent and when written 922 the entity SHOULD save the change to 923 non-volatile storage." 924 REFERENCE 925 "See Section 6. 'SMF Duplicate Packet 926 Detection' in RFC 6621 - Simplified 927 Multicast Forwarding (SMF), Macker, J., 928 May 2012." 929 DEFVAL { 600 } 930 ::= { smfConfigurationGroup 10 } 932 -- 933 -- Configuration of messages to be included in 934 -- NHDP message exchanges in support of SMF 935 -- operations. 936 -- 938 smfCfgNhdpRssaMesgTLVIncluded OBJECT-TYPE 939 SYNTAX TruthValue 940 MAX-ACCESS read-write 941 STATUS current 942 DESCRIPTION 943 "Indicates whether the associated NHDP messages 944 include the RSSA Message TLV, or not. This 945 is an optional SMF operational setting. 946 The value 'true(1)' indicates that this TLV is 947 included; the value 'false(2)' indicates that it 948 is not included. 950 It is RECOMMENDED that the RSSA Message TLV 951 be included in the NHDP messages. 953 This object is persistent and when written 954 the entity SHOULD save the change to 955 non-volatile storage." 956 REFERENCE 957 "See Section 8.1.1. 'SMF Message TLV Type' in 958 RFC 6621 - Simplified Multicast Forwarding 959 (SMF), Macker, J., May 2012." 960 DEFVAL { true } 961 ::= { smfConfigurationGroup 11 } 963 smfCfgNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 964 SYNTAX TruthValue 965 MAX-ACCESS read-write 966 STATUS current 967 DESCRIPTION 968 "Indicates whether the associated NHDP messages 969 include the RSSA Address Block TLV, or not. 970 This is an optional SMF operational setting. 971 The value 'true(1)' indicates that this TLV is 972 included; the value 'false(2)' indicates that it 973 is not included. 975 The smfCfgNhdpRssaAddrBlockTLVIncluded is optional 976 in all cases as it depends on the existence of 977 an address block which may not be present. 978 If this SMF device is configured with NHDP, 979 then this object SHOULD be set to 'true(1)'. 981 This object is persistent and when written 982 the entity SHOULD save the change to 983 non-volatile storage." 984 REFERENCE 985 "See Section 8.1.2. 'SMF Address Block TLV 986 Type' in RFC 6621 - Simplified Multicast 987 Forwarding (SMF), Macker, J., May 2012." 988 DEFVAL { true } 989 ::= { smfConfigurationGroup 12 } 991 -- 992 -- Table identifying configured multicast addresses to be forwarded. 993 -- 995 smfCfgAddrForwardingTable OBJECT-TYPE 996 SYNTAX SEQUENCE OF SmfCfgAddrForwardingEntry 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "The (conceptual) table containing information on multicast 1001 multicast addresses which are to be forwarded by the SMF 1002 process. This table represents an IP filters table for 1003 forwarding (or not) packets based upon their IP 1004 multicast address. 1006 The SMF process can be configured to forward only those 1007 multicast addresses found within the 1008 smfCfgAddrForwardingTable. As such, addresses which are 1009 to be forwarded by the SMF process MUST be found within 1010 the address ranges configured within this table, unless 1011 this table is empty. 1013 Each row is associated with a range of multicast 1014 addresses, and ranges for different rows must be disjoint. 1015 Different rows MAY share a common 1016 smfCfgAddrForwardingGroupName to administratively 1017 associate different rows. 1019 The objects in this table are persistent and when written 1020 the entity SHOULD save the change to non-volatile storage." 1021 REFERENCE 1022 "See Section 9.1. 'Forwarded Multicast Groups' in 1023 RFC 6621 - Simplified Multicast Forwarding 1024 (SMF), Macker, J., May 2012." 1025 ::= { smfConfigurationGroup 13 } 1027 smfCfgAddrForwardingEntry OBJECT-TYPE 1028 SYNTAX SmfCfgAddrForwardingEntry 1029 MAX-ACCESS not-accessible 1030 STATUS current 1031 DESCRIPTION 1032 "An entry (conceptual row) containing the information on a 1033 particular multicast scope." 1034 INDEX { smfCfgAddrForwardingIndex } 1035 ::= { smfCfgAddrForwardingTable 1 } 1037 SmfCfgAddrForwardingEntry ::= SEQUENCE { 1038 smfCfgAddrForwardingIndex Integer32, 1039 smfCfgAddrForwardingGroupName SnmpAdminString, 1040 smfCfgAddrForwardingAddrType InetAddressType, 1041 smfCfgAddrForwardingAddress InetAddress, 1042 smfCfgAddrForwardingAddrPrefixLength 1043 InetAddressPrefixLength, 1044 smfCfgAddrForwardingStatus RowStatus 1045 } 1047 smfCfgAddrForwardingIndex OBJECT-TYPE 1048 SYNTAX Integer32 (1..2147483647) 1049 MAX-ACCESS not-accessible 1050 STATUS current 1051 DESCRIPTION 1052 "This object identifies an unique entry 1053 for a forwarding group. The index for 1054 this entry is a unique value, 1055 greater than zero, for each row. 1056 It is recommended that values are assigned 1057 contiguously starting from 1. 1059 The value for each row index MUST remain 1060 constant from one re-initialization 1061 of the entity's management system to the 1062 next re-initialization." 1063 ::= { smfCfgAddrForwardingEntry 1 } 1065 smfCfgAddrForwardingGroupName OBJECT-TYPE 1066 SYNTAX SnmpAdminString 1067 MAX-ACCESS read-create 1068 STATUS current 1069 DESCRIPTION 1070 "This object identifies a group name for a set of 1071 row entries in order to administratively associate 1072 a set of address ranges. 1074 If there is no group name or this object is 1075 otherwise not applicable, then this object contains 1076 a zero-length string. 1078 This object is persistent and when written 1079 the entity SHOULD save the change to 1080 non-volatile storage." 1081 ::= { smfCfgAddrForwardingEntry 2 } 1083 smfCfgAddrForwardingAddrType OBJECT-TYPE 1084 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1085 MAX-ACCESS read-create 1086 STATUS current 1087 DESCRIPTION 1088 "The type of the addresses in the multicast 1089 forwarding ranges identified by this table. 1091 Only the values ipv4(1) and ipv6(2) are 1092 supported. 1094 This object is persistent and when written 1095 the entity SHOULD save the change to 1096 non-volatile storage." 1097 ::= { smfCfgAddrForwardingEntry 3 } 1099 smfCfgAddrForwardingAddress OBJECT-TYPE 1100 SYNTAX InetAddress (SIZE(4|16)) 1101 MAX-ACCESS read-create 1102 STATUS current 1103 DESCRIPTION 1104 "The multicast group address which, when 1105 combined with smfCfgAddrForwardingAddrPrefixLength, 1106 gives the group prefix for this forwarding range. 1107 The InetAddressType is given by 1108 smfCfgAddrForwardingAddrType. 1110 This address object is only significant up to 1111 smfCfgAddrForwardingAddrPrefixLength bits. The 1112 remaining address bits are set to zero. This is 1113 especially important for this index field, 1114 Any non-zero bits would signify an entirely 1115 different entry. 1117 Legal values correspond to the subset of address 1118 families for which multicast address allocation 1119 is supported. 1121 This object is persistent and when written 1122 the entity SHOULD save the change to 1123 non-volatile storage." 1124 ::= { smfCfgAddrForwardingEntry 4 } 1126 smfCfgAddrForwardingAddrPrefixLength OBJECT-TYPE 1127 SYNTAX InetAddressPrefixLength 1128 MAX-ACCESS read-create 1129 STATUS current 1130 DESCRIPTION 1131 "The length in bits of the mask which, when 1132 combined with smfCfgAddrForwardingAddress, 1133 gives the group prefix for this forwarding 1134 range. 1136 This object is persistent and when written 1137 the entity SHOULD save the change to 1138 non-volatile storage." 1139 ::= { smfCfgAddrForwardingEntry 5 } 1141 smfCfgAddrForwardingStatus OBJECT-TYPE 1142 SYNTAX RowStatus 1143 MAX-ACCESS read-create 1144 STATUS current 1145 DESCRIPTION 1146 "The status of this row, by which new entries may be 1147 created, or old entries deleted from this table." 1148 ::= { smfCfgAddrForwardingEntry 6 } 1150 -- 1151 -- SMF Interfaces Configuration Table 1152 -- 1154 smfCfgInterfaceTable OBJECT-TYPE 1155 SYNTAX SEQUENCE OF SmfCfgInterfaceEntry 1156 MAX-ACCESS not-accessible 1157 STATUS current 1158 DESCRIPTION 1159 "The SMF Interface Table describes the SMF 1160 interfaces that are participating in the 1161 SMF packet forwarding process. The ifIndex is 1162 from the interfaces group defined in the 1163 Interfaces Group MIB module (RFC 2863). As such, 1164 this table 'sparse augments' the ifTable 1165 specifically when SMF is to be configured to 1166 operate over this interface. 1168 A conceptual row in this table exists if and only 1169 if either a manager has explicitly created the row 1170 or there is an interface on the managed device 1171 that automatically supports and runs SMF as part 1172 of the device's initialization process. 1174 The smfCfgIfRowStatus controls the creation 1175 of the rows in the smfCfgInterfaceTable. As 1176 this table only 'sparse augments' the ifTable, 1177 rows in the smfCfgInterfaceTable MAY exist 1178 only if a corresponding row exists in the ifTable. 1179 Although the existance of a row in the ifTable 1180 does not imply a corresponding row in the 1181 smfCfgInterfaceTable. However, rows in the 1182 smfCfgInterfaceTable MUST NOT exist if a 1183 corresponding row in the ifTable is 1184 non-existent. 1186 The manager creates a row in this table by setting 1187 rowStatus to 'createAndGo' or 'createAndWait'. 1188 Row objects having associated DEFVAL clauses are 1189 automatically defined by the agent with these 1190 values during row creation, unless the manager 1191 explicitly defines these object values during the 1192 row creation. 1194 The value of the smfCfgIfAdminStatus is independent 1195 of the value of the associated ifAdminStatus. 1196 The value of the smfCfgIfAdminStatus can be 1197 'enabled' or 'disabled' when the value of the 1198 smfCfgAdminStatus is 'enabled'. However, if the 1199 value of the smfCfgAdminStatus is 'disabled', 1200 then all rows in the smfCfgInterfaceTable 1201 MUST be removed. 1203 If the value of smfCfgIfAdminStatus is 'disabled', 1204 then the value of the corresponding 1205 smfCfgIfRowStatus MUST be set to 'notInService'. 1206 While the value of smfCfgIfRowStatus MAY be 1207 'active' or 'notInService' when smfCfgIfAdminStatus 1208 is set to 'enabled', depending on the state of 1209 the other objects in the corresponding row." 1210 REFERENCE 1211 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1212 K., and F. Kastenholtz, June 2000." 1213 ::= { smfConfigurationGroup 14 } 1215 smfCfgInterfaceEntry OBJECT-TYPE 1216 SYNTAX SmfCfgInterfaceEntry 1217 MAX-ACCESS not-accessible 1218 STATUS current 1219 DESCRIPTION 1220 "The SMF interface entry describes one SMF 1221 interface as indexed by its ifIndex. 1223 The objects in this table are persistent and when 1224 written the device SHOULD save the change to 1225 non-volatile storage. For further information 1226 on the storage behavior for these objects, refer 1227 to the description for the smfCfgIfRowStatus 1228 object." 1229 INDEX { smfCfgIfIndex } 1230 ::= { smfCfgInterfaceTable 1 } 1232 SmfCfgInterfaceEntry ::= 1233 SEQUENCE { 1234 smfCfgIfIndex InterfaceIndexOrZero, 1235 smfCfgIfName SnmpAdminString, 1236 smfCfgIfAdminStatus SmfStatus, 1237 smfCfgIfSmfUpTime TimeTicks, 1238 smfCfgIfRowStatus RowStatus 1239 } 1241 smfCfgIfIndex OBJECT-TYPE 1242 SYNTAX InterfaceIndexOrZero 1243 MAX-ACCESS not-accessible 1244 STATUS current 1245 DESCRIPTION 1246 "The ifIndex for this SMF interface. This value 1247 MUST correspond to an ifIndex referring 1248 to a valid entry in The Interfaces Table. 1249 If the manager attempts to create a row 1250 for which the ifIndex does not exist on the 1251 local device, then the agent SHOULD issue 1252 a return value of 'inconsistentValue' and 1253 the operation SHOULD fail." 1254 REFERENCE 1255 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1256 K., and F. Kastenholtz, June 2000." 1258 ::= { smfCfgInterfaceEntry 1 } 1260 smfCfgIfName OBJECT-TYPE 1261 SYNTAX SnmpAdminString 1262 MAX-ACCESS read-only 1263 STATUS current 1264 DESCRIPTION 1265 "The textual name of the interface. The value of this 1266 object SHOULD be the name of the interface as assigned by 1267 the local device. This can be a text-name, such as 'le0' 1268 or a simple port number, such as '1', 1269 depending on the interface-naming syntax of the device. 1271 If there is no local name or this object is otherwise not 1272 applicable, then this object contains a zero-length string." 1273 ::= { smfCfgInterfaceEntry 2 } 1275 smfCfgIfAdminStatus OBJECT-TYPE 1276 SYNTAX SmfStatus 1277 MAX-ACCESS read-create 1278 STATUS current 1279 DESCRIPTION 1280 "The SMF interface's administrative status. 1281 The value 'enabled' denotes that the interface 1282 is running the SMF forwarding process. 1283 The value 'disabled' denotes that the interface is 1284 currently external to the SMF forwarding process. 1286 The value of the smfCfgIfAdminStatus MAY be either 1287 'enabled' or 'disabled' when the value of the 1288 smfCfgAdminStatus object is 'enabled'. When the 1289 value of the smfCfgAdminStatus is 'disabled', then 1290 all rows in this table MUST be removed. 1292 The default value for this object is 'enabled(1)'. 1294 This object SHOULD be persistent and when 1295 written the device SHOULD save the change to 1296 non-volatile storage." 1297 DEFVAL { enabled } 1298 ::= { smfCfgInterfaceEntry 3 } 1300 smfCfgIfSmfUpTime OBJECT-TYPE 1301 SYNTAX TimeTicks 1302 MAX-ACCESS read-only 1303 STATUS current 1304 DESCRIPTION 1305 "The time (in hundredths of a second) since 1306 this interface SMF process was last 1307 re-initialized. The interface SMF process 1308 is re-initialized when the corresponding 1309 'smfCfgIfRowStatus' object transits to 1310 the 'active' state." 1311 ::= { smfCfgInterfaceEntry 4 } 1313 smfCfgIfRowStatus OBJECT-TYPE 1314 SYNTAX RowStatus 1315 MAX-ACCESS read-create 1316 STATUS current 1317 DESCRIPTION 1318 "This object permits management of this table 1319 by facilitating actions such as row creation, 1320 construction, and destruction. The value of 1321 this object has no effect on whether other 1322 objects in this conceptual row can be 1323 modified. 1325 An entry may not exist in the 'active' state unless all 1326 objects in the entry have a defined appropriate value. For 1327 objects with DEFVAL clauses, the management station 1328 does not need to specify the value of this object in order 1329 for the row to transit to the 'active' state; the default 1330 value for this object is used. For objects that do not 1331 have DEFVAL clauses, then the network manager MUST 1332 specify the value of this object prior to this row 1333 transitioning to the 'active' state. 1335 This object should be set to 'active' only if the 1336 corresponding smfCfgIfAdminStatus is set to 'enabled'. 1337 If the smfCfgIfAdminStatus is set to 'disabled', then the 1338 value of the smfCfgIfRowStatus MAY be set to either 1339 'notInService' or 'notReady' depending upon the values 1340 of the other row objects. 1342 Rows in this table SHOULD exist only if the value of 1343 the smfCfgAdminStatus is 'enabled'. If this object 1344 value changes to 'disabled', then all rows in this table 1345 MUST be removed. 1347 When this object transitions to 'active', all objects 1348 in this row SHOULD be written to non-volatile (stable) 1349 storage. Read-create objects in this row MAY be modified. 1350 When an object in a row with smfCfgIfRowStatus of 'active' 1351 is changed, then the updated value MUST be reflected in SMF 1352 and this new object value MUST be written to non-volatile 1353 storage. 1355 If this object is not equal to 'active', all associated 1356 entries in the smfPerfIpv4InterfacePerfTable and the 1357 smfPerfIpv6InterfacePerfTable MUST be deleted." 1358 ::= { smfCfgInterfaceEntry 5 } 1360 -- 1361 -- smfStateGroup 1362 -- 1363 -- Contains information describing the current state of the SMF 1364 -- process such as the current inclusion in the RS or not. 1365 -- 1367 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1369 smfStateNodeRsStatusIncluded OBJECT-TYPE 1370 SYNTAX TruthValue 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "The current status of the SMF node in the context of 1375 the MANETs relay set. A value of 'true(1)' indicates 1376 that the node is currently part of the MANET Relay 1377 Set. A value of 'false(2)' indicates that the node 1378 is currently not part of the MANET Relay Set." 1379 REFERENCE 1380 "See Section 7. 'Relay Set Selection' in 1381 RFC 6621 - Simplified Multicast Forwarding 1382 (SMF), Macker, J., May 2012." 1383 ::= { smfStateGroup 1 } 1385 smfStateDpdMemoryOverflow OBJECT-TYPE 1386 SYNTAX Counter32 1387 UNITS "DPD Records" 1388 MAX-ACCESS read-only 1389 STATUS current 1390 DESCRIPTION 1391 "The number of DPD records that had to be flushed to 1392 prevent memory overruns for caching of these records. 1393 The number of records to be flushed upon a buffer 1394 overflow is an implementation specific decision. 1396 There is the potential for a counter discontinuity 1397 in this object if the system SMF process had been 1398 disabled and later enabled. In order to check for 1399 the occurrence of such a discontinuity when monitoring 1400 this counter object, it is recommended that the 1401 smfCfgSmfSysUpTime object also be monitored." 1403 REFERENCE 1404 "See Section 6. 'SMF Duplicate Packet 1405 Detection' in RFC 6621 - Simplified 1406 Multicast Forwarding (SMF), Macker, J., 1407 May 2012." 1408 ::= { smfStateGroup 2 } 1410 -- 1411 -- SMF Neighbor Table 1412 -- 1414 smfStateNeighborTable OBJECT-TYPE 1415 SYNTAX SEQUENCE OF SmfStateNeighborEntry 1416 MAX-ACCESS not-accessible 1417 STATUS current 1418 DESCRIPTION 1419 "The SMF StateNeighborTable describes the 1420 current one-hop neighbor nodes, their address 1421 and SMF RSSA and the interface on which 1422 they can be reached." 1423 REFERENCE 1424 "See Section 7. 'SMF Neighborhood Discovery' and 1425 Section 8.1. 'SMF Relay Algorithm TLV 1426 Types' in RFC 6621 - Simplified Multicast 1427 Forwarding (SMF), Macker, J., May 2012." 1428 ::= { smfStateGroup 3 } 1430 smfStateNeighborEntry OBJECT-TYPE 1431 SYNTAX SmfStateNeighborEntry 1432 MAX-ACCESS not-accessible 1433 STATUS current 1434 DESCRIPTION 1435 "The SMF Neighbor Table contains the 1436 set of one-hop neighbors, the interface 1437 they are reachable on and the SMF RSSA 1438 they are currently running." 1439 INDEX { smfStateNeighborIpAddrType, 1440 smfStateNeighborIpAddr, 1441 smfStateNeighborPrefixLen } 1442 ::= { smfStateNeighborTable 1 } 1444 SmfStateNeighborEntry ::= 1445 SEQUENCE { 1446 smfStateNeighborIpAddrType InetAddressType, 1447 smfStateNeighborIpAddr InetAddress, 1448 smfStateNeighborPrefixLen InetAddressPrefixLength, 1449 smfStateNeighborRSSA IANAsmfRssaIdTC, 1450 smfStateNeighborNextHopInterface InterfaceIndexOrZero 1451 } 1453 smfStateNeighborIpAddrType OBJECT-TYPE 1454 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1455 MAX-ACCESS not-accessible 1456 STATUS current 1457 DESCRIPTION 1458 "The one-hop neighbor IP address type. 1460 Only the values 'ipv4(1)' and 1461 'ipv6(2)' are supported." 1462 ::= { smfStateNeighborEntry 1 } 1464 smfStateNeighborIpAddr OBJECT-TYPE 1465 SYNTAX InetAddress (SIZE(4|16)) 1466 MAX-ACCESS not-accessible 1467 STATUS current 1468 DESCRIPTION 1469 "The one-hop neighbor Inet IPv4 or IPv6 1470 address. 1472 Only IPv4 and IPv6 addresses 1473 are supported." 1474 ::= { smfStateNeighborEntry 2 } 1476 smfStateNeighborPrefixLen OBJECT-TYPE 1477 SYNTAX InetAddressPrefixLength 1478 UNITS "bits" 1479 MAX-ACCESS not-accessible 1480 STATUS current 1481 DESCRIPTION 1482 "The prefix length. This is a decimal value that 1483 indicates the number of contiguous, higher-order 1484 bits of the address that make up the network 1485 portion of the address." 1486 ::= { smfStateNeighborEntry 3 } 1488 smfStateNeighborRSSA OBJECT-TYPE 1489 SYNTAX IANAsmfRssaIdTC 1490 MAX-ACCESS read-only 1491 STATUS current 1492 DESCRIPTION 1493 "The current RSSA running on the neighbor." 1494 ::= { smfStateNeighborEntry 4 } 1496 smfStateNeighborNextHopInterface OBJECT-TYPE 1497 SYNTAX InterfaceIndexOrZero 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "The interface ifIndex over which the 1502 neighbor is reachable in one-hop." 1503 ::= { smfStateNeighborEntry 6 } 1505 -- 1506 -- SMF Performance Group 1507 -- 1508 -- Contains objects which help to characterize the 1509 -- performance of the SMF RSSA process, such as statistics 1510 -- counters. There are two types of SMF RSSA statistics: 1511 -- global counters and per interface counters. 1512 -- 1514 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1516 smfPerfGobalGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1518 -- 1519 -- IPv4 packet counters 1520 -- 1522 smfPerfIpv4MultiPktsRecvTotal OBJECT-TYPE 1523 SYNTAX Counter32 1524 UNITS "Packets" 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "A counter of the total number of 1529 multicast IPv4 packets received by the 1530 device and delivered to the SMF process. 1532 There is the potential for a counter discontinuity 1533 in this object if the system SMF process had been 1534 disabled and later enabled. In order to check for 1535 the occurrence of such a discontinuity when monitoring 1536 this counter object, it is recommended that the 1537 smfCfgSmfSysUpTime object also be monitored." 1538 ::= { smfPerfGobalGroup 1 } 1540 smfPerfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1541 SYNTAX Counter32 1542 UNITS "Packets" 1543 MAX-ACCESS read-only 1544 STATUS current 1545 DESCRIPTION 1546 "A counter of the total number of 1547 multicast IPv4 packets forwarded by the 1548 device. 1550 There is the potential for a counter discontinuity 1551 in this object if the system SMF process had been 1552 disabled and later enabled. In order to check for 1553 the occurrence of such a discontinuity when monitoring 1554 this counter object, it is recommended that the 1555 smfCfgSmfSysUpTime object also be monitored." 1556 ::= { smfPerfGobalGroup 2 } 1558 smfPerfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1559 SYNTAX Counter32 1560 UNITS "Packets" 1561 MAX-ACCESS read-only 1562 STATUS current 1563 DESCRIPTION 1564 "A counter of the total number of duplicate 1565 multicast IPv4 packets detected by the 1566 device. 1568 There is the potential for a counter discontinuity 1569 in this object if the system SMF process had been 1570 disabled and later enabled. In order to check for 1571 the occurrence of such a discontinuity when monitoring 1572 this counter object, it is recommended that the 1573 smfCfgSmfSysUpTime object also be monitored." 1574 REFERENCE 1575 "See Section 6.2. 'IPv4 Duplicate Packet 1576 Detection' in RFC 6621 - Simplified Multicast 1577 Forwarding (SMF), Macker, J., May 2012." 1578 ::= { smfPerfGobalGroup 3 } 1580 smfPerfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1581 SYNTAX Counter32 1582 UNITS "Packets" 1583 MAX-ACCESS read-only 1584 STATUS current 1585 DESCRIPTION 1586 "A counter of the total number of dropped 1587 multicast IPv4 packets by the 1588 device due to TTL exceeded. 1590 There is the potential for a counter discontinuity 1591 in this object if the system SMF process had been 1592 disabled and later enabled. In order to check for 1593 the occurrence of such a discontinuity when monitoring 1594 this counter object, it is recommended that the 1595 smfCfgSmfSysUpTime object also be monitored." 1596 REFERENCE 1597 "See Section 5. 'SMF Packet Processing and 1598 Forwarding' in RFC 6621 - Simplified 1599 Multicast Forwarding (SMF), Macker, J., 1600 May 2012." 1601 ::= { smfPerfGobalGroup 4 } 1603 smfPerfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1604 SYNTAX Counter32 1605 UNITS "Packets" 1606 MAX-ACCESS read-only 1607 STATUS current 1608 DESCRIPTION 1609 "A counter of the total number of IPv4 packets 1610 recieved which have a TTL larger than that 1611 of a previously received identical packet. 1613 There is the potential for a counter discontinuity 1614 in this object if the system SMF process had been 1615 disabled and later enabled. In order to check for 1616 the occurrence of such a discontinuity when monitoring 1617 this counter object, it is recommended that the 1618 smfCfgSmfSysUpTime object also be monitored." 1619 REFERENCE 1620 "See Section 5. 'SMF Packet Processing and 1621 Forwarding' in RFC 6621 - Simplified Multicast 1622 Forwarding (SMF), Macker, J., May 2012." 1623 ::= { smfPerfGobalGroup 5 } 1625 -- 1626 -- IPv6 packet counters 1627 -- 1629 smfPerfIpv6MultiPktsRecvTotal OBJECT-TYPE 1630 SYNTAX Counter32 1631 UNITS "Packets" 1632 MAX-ACCESS read-only 1633 STATUS current 1634 DESCRIPTION 1635 "A counter of the total number of 1636 multicast IPv6 packets received by the 1637 device and delivered to the SMF process. 1639 There is the potential for a counter discontinuity 1640 in this object if the system SMF process had been 1641 disabled and later enabled. In order to check for 1642 the occurrence of such a discontinuity when monitoring 1643 this counter object, it is recommended that the 1644 smfCfgSmfSysUpTime object also be monitored." 1645 ::= { smfPerfGobalGroup 6 } 1647 smfPerfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1648 SYNTAX Counter32 1649 UNITS "Packets" 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "A counter of the total number of 1654 multicast IPv6 packets forwarded by the 1655 device. 1657 There is the potential for a counter discontinuity 1658 in this object if the system SMF process had been 1659 disabled and later enabled. In order to check for 1660 the occurrence of such a discontinuity when monitoring 1661 this counter object, it is recommended that the 1662 smfCfgSmfSysUpTime object also be monitored." 1663 ::= { smfPerfGobalGroup 7 } 1665 smfPerfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1666 SYNTAX Counter32 1667 UNITS "Packets" 1668 MAX-ACCESS read-only 1669 STATUS current 1670 DESCRIPTION 1671 "A counter of the total number of duplicate 1672 multicast IPv6 packets detected by the 1673 device. 1675 There is the potential for a counter discontinuity 1676 in this object if the system SMF process had been 1677 disabled and later enabled. In order to check for 1678 the occurrence of such a discontinuity when monitoring 1679 this counter object, it is recommended that the 1680 smfCfgSmfSysUpTime object also be monitored." 1681 REFERENCE 1682 "See Section 6.1. 'IPv6 Duplicate Packet 1683 Detection' in RFC 6621 - Simplified Multicast 1684 Forwarding (SMF), Macker, J., May 2012." 1685 ::= { smfPerfGobalGroup 8 } 1687 smfPerfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1688 SYNTAX Counter32 1689 UNITS "Packets" 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "A counter of the total number of dropped 1694 multicast IPv6 packets by the 1695 device due to TTL exceeded. 1697 There is the potential for a counter discontinuity 1698 in this object if the system SMF process had been 1699 disabled and later enabled. In order to check for 1700 the occurrence of such a discontinuity when monitoring 1701 this counter object, it is recommended that the 1702 smfCfgSmfSysUpTime object also be monitored." 1703 REFERENCE 1704 "See Section 5. 'SMF Packet Processing and 1705 Forwarding' in RFC 6621 - Simplified 1706 Multicast Forwarding (SMF), Macker, J., 1707 May 2012." 1708 ::= { smfPerfGobalGroup 9 } 1710 smfPerfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1711 SYNTAX Counter32 1712 UNITS "Packets" 1713 MAX-ACCESS read-only 1714 STATUS current 1715 DESCRIPTION 1716 "A counter of the total number of IPv6 packets 1717 recieved which have a TTL larger than that 1718 of a previously recived identical packet. 1720 There is the potential for a counter discontinuity 1721 in this object if the system SMF process had been 1722 disabled and later enabled. In order to check for 1723 the occurrence of such a discontinuity when monitoring 1724 this counter object, it is recommended that the 1725 smfCfgSmfSysUpTime object also be monitored." 1726 REFERENCE 1727 "See Section 5. 'SMF Packet Processing and 1728 Forwarding' in RFC 6621 - Simplified Multicast 1729 Forwarding (SMF), Macker, J., May 2012." 1730 ::= { smfPerfGobalGroup 10 } 1732 smfPerfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1733 SYNTAX Counter32 1734 UNITS "Packets" 1735 MAX-ACCESS read-only 1736 STATUS current 1737 DESCRIPTION 1738 "A counter of the total number of IPv6 packets 1739 received which required the HAV assist for DPD. 1741 There is the potential for a counter discontinuity 1742 in this object if the system SMF process had been 1743 disabled and later enabled. In order to check for 1744 the occurrence of such a discontinuity when monitoring 1745 this counter object, it is recommended that the 1746 smfCfgSmfSysUpTime object also be monitored." 1747 REFERENCE 1748 "See Section 6.1.1. 'IPv6 SMF_DPD Option Header' 1749 in RFC 6621 - Simplified Multicast Forwarding 1750 (SMF), Macker, J., May 2012." 1751 ::= { smfPerfGobalGroup 11 } 1753 smfPerfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1754 SYNTAX Counter32 1755 UNITS "Packets" 1756 MAX-ACCESS read-only 1757 STATUS current 1758 DESCRIPTION 1759 "A counter of the total number of IPv6 packets 1760 recieved which the device inserted the 1761 DPD header option. 1763 There is the potential for a counter discontinuity 1764 in this object if the system SMF process had been 1765 disabled and later enabled. In order to check for 1766 the occurrence of such a discontinuity when monitoring 1767 this counter object, it is recommended that the 1768 smfCfgSmfSysUpTime object also be monitored." 1769 REFERENCE 1770 "See Section 6.1.2. 'IPv6 Identification-Based 1771 DPD' in RFC 6621 - Simplified Multicast 1772 Forwarding (SMF), Macker, J., May 2012." 1773 ::= { smfPerfGobalGroup 12 } 1775 -- 1776 -- Per SMF Interface Performance Table 1777 -- 1779 smfPerfInterfaceGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1781 smfPerfIpv4InterfacePerfTable OBJECT-TYPE 1782 SYNTAX SEQUENCE OF SmfPerfIpv4InterfacePerfEntry 1783 MAX-ACCESS not-accessible 1784 STATUS current 1785 DESCRIPTION 1786 "The SMF Interface Performance Table 1787 describes the SMF counters per 1788 interface." 1789 ::= { smfPerfInterfaceGroup 1 } 1791 smfPerfIpv4InterfacePerfEntry OBJECT-TYPE 1792 SYNTAX SmfPerfIpv4InterfacePerfEntry 1793 MAX-ACCESS not-accessible 1794 STATUS current 1795 DESCRIPTION 1796 "The SMF Interface Performance entry 1797 describes the statistics for a particular 1798 node interface." 1799 INDEX { smfCfgIfIndex } 1800 ::= { smfPerfIpv4InterfacePerfTable 1 } 1802 SmfPerfIpv4InterfacePerfEntry ::= 1803 SEQUENCE { 1804 smfPerfIpv4MultiPktsRecvPerIf Counter32, 1805 smfPerfIpv4MultiPktsForwardedPerIf Counter32, 1806 smfPerfIpv4DuplMultiPktsDetectedPerIf Counter32, 1807 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1808 smfPerfIpv4TTLLargerThanPreviousPerIf Counter32 1809 } 1811 smfPerfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1812 SYNTAX Counter32 1813 UNITS "Packets" 1814 MAX-ACCESS read-only 1815 STATUS current 1816 DESCRIPTION 1817 "A counter of the number of multicast IP 1818 packets received by the SMF process on 1819 this device on this interface. 1821 There is the potential for a counter discontinuity 1822 in this object if the system SMF process had been 1823 disabled and later enabled on this interface. 1824 In order to check for the occurrence of such a 1825 discontinuity when monitoring this counter object, 1826 it is recommended that the smfCfgIfSmfUpTime 1827 object also be monitored." 1828 ::= { smfPerfIpv4InterfacePerfEntry 1 } 1830 smfPerfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1831 SYNTAX Counter32 1832 UNITS "Packets" 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "A counter of the number of 1837 multicast IP packets forwarded by the 1838 SMF process on this device 1839 on this interface. 1841 There is the potential for a counter discontinuity 1842 in this object if the system SMF process had been 1843 disabled and later enabled on this interface. 1844 In order to check for the occurrence of such a 1845 discontinuity when monitoring this counter object, 1846 it is recommended that the smfCfgIfSmfUpTime 1847 object also be monitored." 1848 ::= { smfPerfIpv4InterfacePerfEntry 2 } 1850 smfPerfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1851 SYNTAX Counter32 1852 UNITS "Packets" 1853 MAX-ACCESS read-only 1854 STATUS current 1855 DESCRIPTION 1856 "A counter of the number of duplicate 1857 multicast IP packets detected by the 1858 SMF process on this device 1859 on this interface. 1861 There is the potential for a counter discontinuity 1862 in this object if the system SMF process had been 1863 disabled and later enabled on this interface. 1864 In order to check for the occurrence of such a 1865 discontinuity when monitoring this counter object, 1866 it is recommended that the smfCfgIfSmfUpTime 1867 object also be monitored." 1868 ::= { smfPerfIpv4InterfacePerfEntry 3 } 1870 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1871 SYNTAX Counter32 1872 UNITS "Packets" 1873 MAX-ACCESS read-only 1874 STATUS current 1875 DESCRIPTION 1876 "A counter of the total number of dropped 1877 multicast IPv4 packets by the SMF process 1878 on this device on this interface 1879 due to TTL exceeded. 1881 There is the potential for a counter discontinuity 1882 in this object if the system SMF process had been 1883 disabled and later enabled on this interface. 1884 In order to check for the occurrence of such a 1885 discontinuity when monitoring this counter object, 1886 it is recommended that the smfCfgIfSmfUpTime 1887 object also be monitored." 1888 ::= { smfPerfIpv4InterfacePerfEntry 4 } 1890 smfPerfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1891 SYNTAX Counter32 1892 UNITS "Packets" 1893 MAX-ACCESS read-only 1894 STATUS current 1895 DESCRIPTION 1896 "A counter of the total number of IPv4 packets 1897 received by the SMF process on this device 1898 on this interface which have a TTL larger than 1899 that of a previously received identical packet. 1901 There is the potential for a counter discontinuity 1902 in this object if the system SMF process had been 1903 disabled and later enabled on this interface. 1904 In order to check for the occurrence of such a 1905 discontinuity when monitoring this counter object, 1906 it is recommended that the smfCfgIfSmfUpTime 1907 object also be monitored." 1908 ::= { smfPerfIpv4InterfacePerfEntry 5 } 1910 smfPerfIpv6InterfacePerfTable OBJECT-TYPE 1911 SYNTAX SEQUENCE OF SmfPerfIpv6InterfacePerfEntry 1912 MAX-ACCESS not-accessible 1913 STATUS current 1914 DESCRIPTION 1915 "The SMF Interface Performance Table 1916 describes the SMF counters per 1917 interface." 1918 ::= { smfPerfInterfaceGroup 2 } 1920 smfPerfIpv6InterfacePerfEntry OBJECT-TYPE 1921 SYNTAX SmfPerfIpv6InterfacePerfEntry 1922 MAX-ACCESS not-accessible 1923 STATUS current 1924 DESCRIPTION 1925 "The SMF Interface Performance entry 1926 describes the counters for a particular 1927 node interface." 1929 INDEX { smfCfgIfIndex } 1930 ::= { smfPerfIpv6InterfacePerfTable 1 } 1932 SmfPerfIpv6InterfacePerfEntry ::= 1933 SEQUENCE { 1934 smfPerfIpv6MultiPktsRecvPerIf Counter32, 1935 smfPerfIpv6MultiPktsForwardedPerIf Counter32, 1936 smfPerfIpv6DuplMultiPktsDetectedPerIf Counter32, 1937 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1938 smfPerfIpv6TTLLargerThanPreviousPerIf Counter32, 1939 smfPerfIpv6HAVAssistsReqdPerIf Counter32, 1940 smfPerfIpv6DpdHeaderInsertionsPerIf Counter32 1941 } 1943 smfPerfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1944 SYNTAX Counter32 1945 UNITS "Packets" 1946 MAX-ACCESS read-only 1947 STATUS current 1948 DESCRIPTION 1949 "A counter of the number of 1950 multicast IP packets received by the 1951 SMF process on this device 1952 on this interface. 1954 There is the potential for a counter discontinuity 1955 in this object if the system SMF process had been 1956 disabled and later enabled on this interface. 1957 In order to check for the occurrence of such a 1958 discontinuity when monitoring this counter object, 1959 it is recommended that the smfCfgIfSmfUpTime 1960 object also be monitored." 1961 ::= { smfPerfIpv6InterfacePerfEntry 1 } 1963 smfPerfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 1964 SYNTAX Counter32 1965 UNITS "Packets" 1966 MAX-ACCESS read-only 1967 STATUS current 1968 DESCRIPTION 1969 "A counter of the number of 1970 multicast IP packets forwarded by the 1971 SMF process on this device 1972 on this interface. 1974 There is the potential for a counter discontinuity 1975 in this object if the system SMF process had been 1976 disabled and later enabled on this interface. 1978 In order to check for the occurrence of such a 1979 discontinuity when monitoring this counter object, 1980 it is recommended that the smfCfgIfSmfUpTime 1981 object also be monitored." 1982 ::= { smfPerfIpv6InterfacePerfEntry 2 } 1984 smfPerfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 1985 SYNTAX Counter32 1986 UNITS "Packets" 1987 MAX-ACCESS read-only 1988 STATUS current 1989 DESCRIPTION 1990 "A counter of the number of duplicate 1991 multicast IP packets detected by the 1992 SMF process on this device 1993 on this interface. 1995 There is the potential for a counter discontinuity 1996 in this object if the system SMF process had been 1997 disabled and later enabled on this interface. 1998 In order to check for the occurrence of such a 1999 discontinuity when monitoring this counter object, 2000 it is recommended that the smfCfgIfSmfUpTime 2001 object also be monitored." 2002 ::= { smfPerfIpv6InterfacePerfEntry 3 } 2004 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 2005 SYNTAX Counter32 2006 UNITS "Packets" 2007 MAX-ACCESS read-only 2008 STATUS current 2009 DESCRIPTION 2010 "A counter of the number of dropped 2011 multicast IP packets by the 2012 SMF process on this device 2013 on this interface due to TTL 2014 exceeded. 2016 There is the potential for a counter discontinuity 2017 in this object if the system SMF process had been 2018 disabled and later enabled on this interface. 2019 In order to check for the occurrence of such a 2020 discontinuity when monitoring this counter object, 2021 it is recommended that the smfCfgIfSmfUpTime 2022 object also be monitored." 2023 ::= { smfPerfIpv6InterfacePerfEntry 4 } 2025 smfPerfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 2026 SYNTAX Counter32 2027 UNITS "Packets" 2028 MAX-ACCESS read-only 2029 STATUS current 2030 DESCRIPTION 2031 "A counter of the total number of IPv6 packets 2032 received which have a TTL larger than that 2033 of a previously received identical packet 2034 by the SMF process on this device on this 2035 interface. 2037 There is the potential for a counter discontinuity 2038 in this object if the system SMF process had been 2039 disabled and later enabled on this interface. 2040 In order to check for the occurrence of such a 2041 discontinuity when monitoring this counter object, 2042 it is recommended that the smfCfgIfSmfUpTime 2043 object also be monitored." 2044 ::= { smfPerfIpv6InterfacePerfEntry 5 } 2046 smfPerfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 2047 SYNTAX Counter32 2048 UNITS "Packets" 2049 MAX-ACCESS read-only 2050 STATUS current 2051 DESCRIPTION 2052 "A counter of the total number of IPv6 packets 2053 received by the SMF process on this device 2054 on this interface which required the 2055 HAV assist for DPD. 2057 There is the potential for a counter discontinuity 2058 in this object if the system SMF process had been 2059 disabled and later enabled on this interface. 2060 In order to check for the occurrence of such a 2061 discontinuity when monitoring this counter object, 2062 it is recommended that the smfCfgIfSmfUpTime 2063 object also be monitored." 2064 ::= { smfPerfIpv6InterfacePerfEntry 6 } 2066 smfPerfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 2067 SYNTAX Counter32 2068 UNITS "Packets" 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "A counter of the total number of IPv6 packets 2073 received by the SMF process on this device 2074 on this interface which the device inserted the 2075 DPD header option. 2077 There is the potential for a counter discontinuity 2078 in this object if the system SMF process had been 2079 disabled and later enabled on this interface. 2080 In order to check for the occurrence of such a 2081 discontinuity when monitoring this counter object, 2082 it is recommended that the smfCfgIfSmfUpTime 2083 object also be monitored." 2084 ::= { smfPerfIpv6InterfacePerfEntry 7 } 2086 -- 2087 -- Notifications 2088 -- 2090 smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 0 } 2091 smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 } 2093 -- smfMIBNotifObjects 2095 smfNotifAdminStatusChange NOTIFICATION-TYPE 2096 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2097 -- the notification. 2098 smfCfgRouterID, -- The originator of 2099 -- the notification. 2100 smfCfgAdminStatus -- The new status of the 2101 -- SMF process. 2102 } 2103 STATUS current 2104 DESCRIPTION 2105 "smfCfgAdminStatusChange is a notification sent when a 2106 the 'smfCfgAdminStatus' object changes." 2107 ::= { smfMIBNotifObjects 1 } 2109 smfNotifConfiguredOpModeChange NOTIFICATION-TYPE 2110 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2111 -- the notification. 2112 smfCfgRouterID, -- The originator of 2113 -- the notification. 2114 smfCfgOperationalMode -- The new Operations 2115 -- Mode of the SMF 2116 -- process. 2117 } 2118 STATUS current 2119 DESCRIPTION 2120 "smfNotifConfiguredOpModeChange is a notification 2121 sent when the 'smfCfgOperationalMode' object 2122 changes." 2123 ::= { smfMIBNotifObjects 2 } 2125 smfNotifIfAdminStatusChange NOTIFICATION-TYPE 2126 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2127 -- the notification. 2128 smfCfgRouterID, -- The originator of 2129 -- the notification. 2130 smfCfgIfName, -- The interface whose 2131 -- status has changed. 2132 smfCfgIfAdminStatus -- The new status of the 2133 -- SMF interface. 2134 } 2135 STATUS current 2136 DESCRIPTION 2137 "smfCfgIfAdminStatusChange is a notification sent when a 2138 the 'smfCfgIfAdminStatus' object changes." 2139 ::= { smfMIBNotifObjects 3 } 2141 smfNotifDpdMemoryOverflowEvent NOTIFICATION-TYPE 2142 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2143 -- the notification. 2144 smfCfgRouterID, -- The originator of 2145 -- the notification. 2146 smfStateDpdMemoryOverflow -- The counter of 2147 -- the overflows. 2148 } 2149 STATUS current 2150 DESCRIPTION 2151 "smfNotifDpdMemoryOverflowEvents is sent when the 2152 number of memory overflow events exceeds the 2153 the 'smfNotifDpdMemoryOverflowThreshold' within the 2154 previous number of seconds defined by the 2155 'smfNotifDpdMemoryOverflowWindow'." 2156 ::= { smfMIBNotifObjects 4 } 2158 -- smfMIBNotifControl 2159 smfNotifDpdMemoryOverflowThreshold OBJECT-TYPE 2160 SYNTAX Integer32 (0..255) 2161 UNITS "Events" 2162 MAX-ACCESS read-write 2163 STATUS current 2164 DESCRIPTION 2165 "A threshold value for the 2166 `smfNotifDpdmemoryOverflowEvents' object. 2167 If the number of occurences exceeds 2168 this threshold within the previous 2169 number of seconds 2170 'smfNotifDpdMemoryOverflowWindow', 2171 then the `smfNotifDpdMemoryOverflowEvent' 2172 notification is sent. 2174 The default value for this object is 2175 '1'." 2176 DEFVAL { 1 } 2177 ::= { smfMIBNotifControl 1 } 2179 smfNotifDpdMemoryOverflowWindow OBJECT-TYPE 2180 SYNTAX TimeTicks 2181 MAX-ACCESS read-write 2182 STATUS current 2183 DESCRIPTION 2184 "A time window value for the 2185 `smfNotifDpdmemoryOverflowEvents' object. 2186 If the number of occurences exceeds 2187 the `smfNotifDpdMemoryOverflowThreshold' 2188 within the previous number of seconds 2189 'smfNotifDpdMemoryOverflowWindow', 2190 then the `smfNotifDpdMemoryOverflowEvent' 2191 notification is sent. 2193 The default value for this object is 2194 '1'." 2195 DEFVAL { 1 } 2196 ::= { smfMIBNotifControl 2 } 2198 -- 2199 -- Compliance Statements 2200 -- 2202 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2203 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2205 smfBasicCompliance MODULE-COMPLIANCE 2206 STATUS current 2207 DESCRIPTION "The basic implementation requirements for 2208 managed network entities that implement 2209 the SMF RSSA process." 2210 MODULE -- this module 2211 MANDATORY-GROUPS { smfCapabObjectsGroup, 2212 smfConfigObjectsGroup } 2213 ::= { smfCompliances 1 } 2215 smfFullCompliance MODULE-COMPLIANCE 2216 STATUS current 2217 DESCRIPTION "The full implementation requirements for 2218 managed network entities that implement 2219 the SMF RSSA process." 2220 MODULE -- this module 2221 MANDATORY-GROUPS { smfCapabObjectsGroup, 2222 smfConfigObjectsGroup, 2223 smfStateObjectsGroup, 2224 smfPerfObjectsGroup, 2225 smfNotifObjectsGroup, 2226 smfNotificationsGroup 2227 } 2228 ::= { smfCompliances 2 } 2230 -- 2231 -- Units of Conformance 2232 -- 2234 smfCapabObjectsGroup OBJECT-GROUP 2235 OBJECTS { 2236 smfCapabilitiesOpModeID, 2237 smfCapabilitiesRssaID 2238 } 2239 STATUS current 2240 DESCRIPTION 2241 "Set of SMF configuration objects implemented 2242 in this module." 2243 ::= { smfMIBGroups 1 } 2245 smfConfigObjectsGroup OBJECT-GROUP 2246 OBJECTS { 2247 smfCfgAdminStatus, 2248 smfCfgSmfSysUpTime, 2249 smfCfgRouterIDAddrType, 2250 smfCfgRouterID, 2251 smfCfgOperationalMode, 2252 smfCfgRssaMember, 2253 smfCfgIpv4Dpd, 2254 smfCfgIpv6Dpd, 2255 smfCfgMaxPktLifetime, 2256 smfCfgDpdEntryMaxLifetime, 2257 smfCfgNhdpRssaMesgTLVIncluded, 2258 smfCfgNhdpRssaAddrBlockTLVIncluded, 2259 smfCfgAddrForwardingGroupName, 2260 smfCfgAddrForwardingAddrType, 2261 smfCfgAddrForwardingAddress, 2262 smfCfgAddrForwardingAddrPrefixLength, 2263 smfCfgAddrForwardingStatus, 2265 smfCfgIfName, 2266 smfCfgIfAdminStatus, 2267 smfCfgIfSmfUpTime, 2268 smfCfgIfRowStatus 2269 } 2270 STATUS current 2271 DESCRIPTION 2272 "Set of SMF configuration objects implemented 2273 in this module." 2274 ::= { smfMIBGroups 2 } 2276 smfStateObjectsGroup OBJECT-GROUP 2277 OBJECTS { 2278 smfStateNodeRsStatusIncluded, 2279 smfStateDpdMemoryOverflow, 2281 smfStateNeighborRSSA, 2282 smfStateNeighborNextHopInterface 2283 } 2284 STATUS current 2285 DESCRIPTION 2286 "Set of SMF state objects implemented 2287 in this module." 2288 ::= { smfMIBGroups 3 } 2290 smfPerfObjectsGroup OBJECT-GROUP 2291 OBJECTS { 2292 smfPerfIpv4MultiPktsRecvTotal, 2293 smfPerfIpv4MultiPktsForwardedTotal, 2294 smfPerfIpv4DuplMultiPktsDetectedTotal, 2295 smfPerfIpv4DroppedMultiPktsTTLExceededTotal, 2296 smfPerfIpv4TTLLargerThanPreviousTotal, 2298 smfPerfIpv6MultiPktsRecvTotal, 2299 smfPerfIpv6MultiPktsForwardedTotal, 2300 smfPerfIpv6DuplMultiPktsDetectedTotal, 2301 smfPerfIpv6DroppedMultiPktsTTLExceededTotal, 2302 smfPerfIpv6TTLLargerThanPreviousTotal, 2303 smfPerfIpv6HAVAssistsReqdTotal, 2304 smfPerfIpv6DpdHeaderInsertionsTotal, 2306 smfPerfIpv4MultiPktsRecvPerIf, 2307 smfPerfIpv4MultiPktsForwardedPerIf, 2308 smfPerfIpv4DuplMultiPktsDetectedPerIf, 2309 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf, 2310 smfPerfIpv4TTLLargerThanPreviousPerIf, 2312 smfPerfIpv6MultiPktsRecvPerIf, 2313 smfPerfIpv6MultiPktsForwardedPerIf, 2314 smfPerfIpv6DuplMultiPktsDetectedPerIf, 2315 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf, 2316 smfPerfIpv6TTLLargerThanPreviousPerIf, 2317 smfPerfIpv6HAVAssistsReqdPerIf, 2318 smfPerfIpv6DpdHeaderInsertionsPerIf 2319 } 2320 STATUS current 2321 DESCRIPTION 2322 "Set of SMF performance objects implemented 2323 in this module by total and per interface." 2324 ::= { smfMIBGroups 4 } 2326 smfNotifObjectsGroup OBJECT-GROUP 2327 OBJECTS { 2328 smfNotifDpdMemoryOverflowThreshold, 2329 smfNotifDpdMemoryOverflowWindow 2330 } 2331 STATUS current 2332 DESCRIPTION 2333 "Set of SMF notification control 2334 objects implemented in this module." 2335 ::= { smfMIBGroups 5 } 2337 smfNotificationsGroup NOTIFICATION-GROUP 2338 NOTIFICATIONS { 2339 smfNotifAdminStatusChange, 2340 smfNotifConfiguredOpModeChange, 2341 smfNotifIfAdminStatusChange, 2342 smfNotifDpdMemoryOverflowEvent 2343 } 2344 STATUS current 2345 DESCRIPTION 2346 "Set of SMF notifications implemented 2347 in this module." 2348 ::= { smfMIBGroups 6 } 2350 END 2352 8. IANA-SMF-MIB Definitions 2354 This section contains the IANA-SMF-MIB module. This MIB module 2355 defines two textual conventions for which IANA SHOULD maintain and 2356 keep synchronized with the registry identified below within the 2357 IANAsmfOpModeIdTC and the IANAsmfRssaIdTC TEXTUAL-CONVENTIONs. 2359 The IANAsmfOpModeIdTC defines an index that identifies through 2360 reference to a specific SMF operations mode. The index is an integer 2361 valued named-number enumeration consisting of an integer and label. 2362 IANA is to create and maintain this textual convention. Future 2363 assignments are made to anyone on a first come, first served basis. 2364 There is no substantive review of the request, other than to ensure 2365 that it is well-formed and does not duplicate an existing assignment. 2366 However, requests must include a minimal amount of clerical 2367 information, such as a point of contact (including an email address) 2368 and a brief description of the method being identified as a new SMF 2369 operations mode. 2371 The IANAsmfRssaIdTC defines an index that identifies through 2372 reference to a specific Reduced Set Selection Algorithm (RSSA). The 2373 index is an integer valued named-number enumeration consisting of an 2374 integer and label. IANA is to create and maintain this textual 2375 convention. 2377 Future assignments to the IANAsmfRssaIdTC for the index range 5-127 2378 require an RFC publication (either as an IETF submission or as an RFC 2379 Editor Independent submission [RFC3932]). The type of RFC MUST be 2380 Standards Track. The specific RSSA algorithms MUST be documented in 2381 sufficient detail so that interoperability between independent 2382 implementations is possible. 2384 Future assignments to the IANAsmfRssaIdTC for the index range 128-239 2385 are private or local use only, with the type and purpose defined by 2386 the local site. No attempt is made to prevent multiple sites from 2387 using the same value in different (and incompatible) ways. There is 2388 no need for IANA to review such assignments (since IANA will not 2389 record these) and assignments are not generally useful for broad 2390 interoperability. It is the responsibility of the sites making use 2391 of the Private Use range to ensure that no conflicts occur (within 2392 the intended scope of use). 2394 Future assignments to the IANAsmfRssaIdTC for the index range 240-255 2395 are to facilitate experimentation. These require an RFC publication 2396 (either as an IETF submission or as an RFC Editor Independent 2397 submission [RFC3932]). The type of RFC MUST be Experimental. The 2398 RSSA algorithms MUST be documented in sufficient detail so that 2399 interoperability between independent implementations is possible. 2401 IANA-SMF-MIB DEFINITIONS ::= BEGIN 2403 IMPORTS 2404 MODULE-IDENTITY, mib-2 2405 FROM SNMPv2-SMI 2406 TEXTUAL-CONVENTION 2407 FROM SNMPv2-TC; 2409 ianaSmfMIB MODULE-IDENTITY 2410 LAST-UPDATED "201403231300Z" -- March 23, 2014 2411 ORGANIZATION "IANA" 2412 CONTACT-INFO "Internet Assigned Numbers Authority 2414 Postal: ICANN 2415 4676 Admiralty Way, Suite 330 2416 Marina del Rey, CA 90292 2418 Tel: +1 310 823 9358 2419 E-Mail: iana@iana.org" 2420 DESCRIPTION "This MIB module defines the 2421 IANAsmfOpModeIdTC and IANAsmfRssaIdTC 2422 Textual Conventions, and thus the 2423 enumerated values of the 2424 smfCapabilitiesOpModeID and 2425 smfCapabilitiesRssaID objects defined 2426 in the SMF-MIB." 2427 REVISION "201403231300Z" -- March 23, 2014 2428 DESCRIPTION "Initial version of this MIB as published in 2429 RFC KKKK." 2430 ::= { mib-2 kkkk } 2432 IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION 2433 STATUS current 2434 DESCRIPTION 2435 "An index that identifies through reference to a specific 2436 SMF operations mode. There are basically three styles 2437 of SMF operation with reduced relay sets currently 2438 identified: 2440 Independent operation 'independent(1)' - 2441 SMF performs its own relay 2442 set selection using information from an associated 2443 MANET NHDP process. 2445 CDS-aware unicast routing operation 'routing(2)'- 2446 a coexistent unicast routing 2447 protocol provides dynamic relay 2448 set state based upon its own control plane 2449 CDS or neighborhood discovery information. 2451 Cross-layer operation 'crossLayer(3)' - 2452 SMF operates using neighborhood 2453 status and triggers from a 2454 cross-layer information base for dynamic relay 2455 set selection and maintenance. 2457 IANA MUST update this textual convention accordingly. 2459 The definition of this textual convention with the 2460 addition of newly assigned values is published 2461 periodically by the IANA, in either the Assigned 2462 Numbers RFC, or some derivative of it specific to 2463 Internet Network Management number assignments. (The 2464 latest arrangements can be obtained by contacting the 2465 IANA.) 2467 Requests for new values SHOULD be made to IANA via 2468 email (iana@iana.org)." 2469 REFERENCE 2470 "See Section 7.2. 'Reduced Relay Set Forwarding', 2471 and the Appendices A, B and C in 2472 RFC 6621 - Simplified Multicast Forwarding 2473 (SMF), Macker, J., May 2012." 2474 SYNTAX INTEGER { 2475 independent (1), 2476 routing (2), 2477 crossLayer (3) 2478 -- future (4-255) 2479 } 2481 IANAsmfRssaIdTC ::= TEXTUAL-CONVENTION 2482 STATUS current 2483 DESCRIPTION 2484 "An index that identifies through reference to a specific 2485 RSSA algorithms. Several are currently defined 2486 in the Appendix A, B and C of RFC 6621. 2488 Examples of RSSA algorithms already identified within 2489 this TC are: 2491 Classical Flooding (cF(1)) - is the standard 2492 flooding algorithm where each node in the next 2493 retransmits the information on each of its interfaces. 2495 Source-Based Multipint Relay (sMPR(2)) - 2496 this algorithm is used by Optimized Link State Routing 2497 (OLSR) and OLSR version 2 (OLSRv2) protocols for the 2498 relay of link state updates and other control 2499 information [RFC3626]. Since each router picks 2500 its neighboring relays independently, sMPR 2501 forwarders depend upon previous hop information 2502 (e.g., source MAC address) to operate correctly. 2504 Extended Connected Dominating Set (eCDS(3)) - 2505 defined in [RFC5614] this algorithm forms a single 2506 CDS mesh for the SMF operating region. Its 2507 packet-forwarding rules are not dependent upon 2508 previous hop knowledge in contrast to sMPR. 2510 Multipoint Relay Connected Dominating Set (mprCDS(4)) - 2511 This algorithm is an extension to the basic sMPR 2512 election algorithm that results in a shared 2513 (non-source-specific) SMF CDS. Thus, its forwarding 2514 rules are not dependent upon previous hop information, 2515 similar to eCDS. 2517 IANA MUST update this textual convention accordingly. 2519 The definition of this textual convention with the 2520 addition of newly assigned values is published 2521 periodically by the IANA, in either the Assigned 2522 Numbers RFC, or some derivative of it specific to 2523 Internet Network Management number assignments. (The 2524 latest arrangements can be obtained by contacting the 2525 IANA.) 2527 Requests for new values SHOULD be made to IANA via 2528 email (iana@iana.org)." 2529 REFERENCE 2530 "See, e.g., 2532 Section 8.1.1. 'SMF Message TLV Type', 2533 Appendix A. 'Essential Connecting Dominating Set (E-CDS) 2534 Algorithm', 2535 Appendix B. 'Source-Based Multipoint Relay (S-MPR) 2536 Algorithm', and 2537 Appendix C. 'Multipoint Relay Connected Dominating Set 2538 (MPR-CDS) Algorithm' 2540 in RFC 6621 - Simplified Multicast Forwarding 2541 (SMF), Macker, J., May 2012." 2542 SYNTAX INTEGER { 2543 cF(1), 2544 sMPR(2), 2545 eCDS(3), 2546 mprCDS(4) 2547 -- future(5-127) 2548 -- noStdAction(128-239) 2549 -- experimental(240-255) 2550 } 2552 END 2554 9. Security Considerations 2556 This section discusses security implications of the choices made in 2557 this SMF-MIB module. 2559 There are a number of management objects defined in this MIB module 2560 with a MAX-ACCESS clause of read-write and/or read-create. Such 2561 objects may be considered sensitive or vulnerable in some network 2562 environments. The support for SET operations in a non-secure 2563 environment without proper protection can have a negative effect on 2564 network operations. These are the tables and objects and their 2565 sensitivity/vulnerability: 2567 o 'smfCfgAdminStatus' - this writable configuration object controls 2568 the operational status of the SMF process. If this setting is 2569 configured inconsistently across the MANET multicast domain, then 2570 delivery of multicast data may be inconsistent across the domain; 2571 some nodes may not receive multicast data intended for them. 2573 o 'smfCfgRouterIDAddrType' and 'smfCfgRouterID' - these writable 2574 configuration objects define the ID of the SMF process. These 2575 objects should be configured with a routable address defined on 2576 the local SMF device. The smfCfgRouterID is a logical 2577 identification that MUST be configured as unique across inter- 2578 operating SMF neighborhoods and it is RECOMMENDED to be chosen as 2579 the numerically largest address contained in a node's 'Neighbor 2580 Address List' as defined in NHDP. A smfCfgRouterID MUST be unique 2581 within the scope of the operating MANET network regardless of the 2582 method used for selecting it. If these objects are mis-configured 2583 or configured in-consistently across the MANET, then the ability 2584 of various RSSA algorithms, e.g., ECDS, may be compromised. This 2585 would potentially result in some routers within the MANET not 2586 receiving multicast packets destine to them. Hence, intentionally 2587 mis-configuring these objects could pose a form of Denial-of- 2588 Service (DOS) attack against the MANET. 2590 o 'smfCfgOpMode' - this writable configuration objects define the 2591 operational mode of the SMF process. The operational mode defines 2592 how the SMF process receives its data to form its local estimate 2593 of the CDS. It is recommended that the value for this object be 2594 set consistently across the MANET to ensure proper operation of 2595 the multicast packet forwarding. If the value for this object is 2596 set inconsistently across the MANET, the result may be that 2597 multicast packet delivery will be compromised within the MANET. 2598 Hence, intentionally mis-configuring this object could pose a form 2599 DOS attack against the MANET. 2601 o 'smfCfgRssa' - this writable configuration object sets the 2602 specific Reduced Set Selection Algorithm (RSSA) for the SMF 2603 process. If this object is set inconsistently across the MANET 2604 domain, multicast delivery of data will likely fail. Hence, 2605 intentionally mis-configuring this object could pose a form DOS 2606 attack against the MANET. 2608 o 'smfCfgRssaMember' - this writable configuration object sets the 2609 'interest' of the local SMF node in participating in the CDS. 2610 Setting this object to 'never(3)' on a highly highly connected 2611 device could lead to frequent island formation. Setting this 2612 object to 'always(2)' could support data ex-filtration from the 2613 MANET domain. 2615 o 'smfCfgIpv4Dpd' - this writable configuration object sets the 2616 duplicate packet detection method, i.e., H-DPD or I-DPD, for 2617 forwarding of IPv4 multicast packets. Forwarders may operate with 2618 mixed H-DPD and I-DPD modes as long as they consistently perform 2619 the appropriate DPD routines outlined [RFC6621]. However, it is 2620 RECOMMENDED that a deployment be configured with a common mode for 2621 operational consistency. 2623 o 'smfCfgIpv6Dpd' - this writable configuration object sets the 2624 duplicate packet detection method for forwarding of IPv6 multicast 2625 packets. Since IPv6 SMF does specifies an option header, the 2626 interoperability constraints are not as loose as in the IPv4 2627 version, and forwarders SHOULD not operate with mixed H-DPD and 2628 I-DPD modes. Hence the value for this object SHOULD be 2629 consistently set within the forwarders comprising the MANET, else 2630 inconsistent forwarding may result unnecessary multicast packet 2631 dropping. 2633 o 'smfCfgMaxPktLifetime' - this writable configuration object sets 2634 the estimate of the network packet traversal time. If set too 2635 small, this could lead to poor multicast data delivery ratios 2636 throughout the MANET domain. This could serve as a form of DOS 2637 attack if this object value is set too small. 2639 o 'smfCfgDpdEntryMaxLifetime' - this writable configuration object 2640 sets the maximum lifetime (in seconds) for the cached DPD records 2641 for the combined IPv4 and IPv6 methods. If the memory is running 2642 low prior to the MaxLifetime being exceeded, the local SMF devices 2643 should purge the oldest records first. If this object value is 2644 set too small, then the effectiveness of the SMF DPD algorithms 2645 may become greatly diminished causing a higher than necessary 2646 packet load on the MANET. 2648 o 'smfCfgNhdpRssaMesgTLVIncluded' - this writable configuration 2649 object indicates whether the associated NHDP messages include the 2650 the RSSA Message TLV, or not. It is highly RECOMMENDED that this 2651 object be set to 'true(1)' when the SMF operation mode is set to 2652 independent as this information will inform the local forwarder of 2653 the RSSA algorithm implemented in neighboring forwarders and is 2654 used to ensure consistent forwarding across the MANET. While it 2655 is possible that SMF neighbors MAY be configured differently with 2656 respect to the RSSA algorithm and still operate cooperatively, but 2657 these cases will vary dependent upon the algorithm types 2658 designated and this situation SHOULD be avoided. 2660 o 'smfCfgNhdpRssaAddrBlockTLVIncluded' - this writable configuration 2661 object indicates whether the associated NHDP messages include the 2662 the RSSA Address Block TLV, or not. The 2663 smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it 2664 depends on the existence of an address block which may not be 2665 present. If this SMF device is configured with NHDP, then this 2666 object should be set to 'true(1)' as this TLV enables CDS relay 2667 algorithm operation and configuration to be shared among 2-hop 2668 neighborhoods. Some relay algorithms require 2-hop neighbor 2669 configuration in order to correctly select relay sets. 2671 o 'smfCfgAddrForwardingTable' - the writable configuration objects 2672 in this table indicate which multicast IP addresses are to be 2673 forwarded by this SMF node. Misconfiguration of rows within this 2674 table can limit the ability of this SMF device to properly forward 2675 multicast data. 2677 o 'smfCfgInterfaceTable' - the writable configuration objects in 2678 this table indicate which SMF node interfaces are participating in 2679 the SMF packet forwarding process. Misconfiguration of rows 2680 within this table can limit the ability of this SMF device to 2681 properly forward multicast data. 2683 Some of the readable objects in this MIB module (i.e., objects with a 2684 MAX-ACCESS other than not-accessible) may be considered sensitive or 2685 vulnerable in some network environments. It is thus important to 2686 control even GET and/or NOTIFY access to these objects and possibly 2687 to even encrypt the values of these objects when sending them over 2688 the network via SNMP. These are the tables and objects and their 2689 sensitivity/vulnerability: 2691 o 'smfNodeRsStatusIncluded' - this readable state object indicates 2692 that this SMF node is part of the CDS, or not. Being part of the 2693 CDS makes this node a distinguished device. It could be exploited 2694 for data ex-filtration, or denial of service attacks. 2696 o 'smfStateNeighborTable' - the readable state objects in this table 2697 indicate current neighbor nodes to this SMF node. Exposing this 2698 information to an attacker could allow the attacker easier access 2699 to the larger MANET domain. 2701 The remainder of the objects in the SMF-MIB module are performance 2702 counter objects. While these give an indication of the activity of 2703 the SMF process on this node, it is not expected that exposing these 2704 values pose a security risk to the MANET network. 2706 SNMP versions prior to SNMPv3 did not include adequate security. 2707 Even if the network itself is secure (for example by using IPSec), 2708 even then, there is no control as to who on the secure network is 2709 allowed to access and GET/SET (read/change/create/delete) the objects 2710 in this MIB module. 2712 Implementations MUST provide the security features described by the 2713 SNMPv3 framework (see [RFC3410] ), including full support for 2714 authentication and privacy via the User-based Security Model (USM) 2715 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2716 MAY also provide support for the Transport Security Model (TSM) 2717 [RFC5591] in combination with a secure transport such as SSH 2718 [RFC5592] or TLS/DTLS [RFC6353]. 2720 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2721 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2722 enable cryptographic security. It is then a customer/operator 2723 responsibility to ensure that the SNMP entity giving access to an 2724 instance of this MIB module is properly configured to give access to 2725 the objects only to those principals (users) that have legitimate 2726 rights to indeed GET or SET (change/create/delete) them. 2728 10. Applicability Statement 2730 This document describes objects for configuring parameters of the 2731 Simplified Multicast Forwarding [RFC6621] process on a Mobile Ad-Hoc 2732 Network (MANET) router. This MIB module, denoted SMF-MIB, also 2733 reports state and performance information and notifications. This 2734 section provides some examples of how this MIB module can be used in 2735 MANET network deployments. A fuller discussion of MANET network 2736 management use cases and challenges will be provided elsewhere. 2738 SMF is designed to allow MANET routers to forward IPv4 and IPv6 2739 packets over the MANET and cover the MANET nodes through the 2740 automatic discovery of efficient estimates of the Minimum Connected 2741 Dominating Set (MCDS) of nodes within the MANET. The MCDS are 2742 estimated using the Relay Set Selection Algorithms (RSSAs) discussed 2743 within this document. In the following, three scenarios are listed 2744 where this MIB module is useful, i.e., 2746 o For a Parking Lot Initial Configuration Situation - it is common 2747 for the vehicles comprising the MANET being forward deployed at a 2748 remote location, e.g., the site of a natural disaster, to be off- 2749 loaded in a parking lot where an initial configuration of the 2750 networking devices is performed. The configuration is loaded into 2751 the devices from a fixed location Network Operation Center (NOC) 2752 at the parking lot and the vehicles are stationary at the parking 2753 lot while the configuration changes are made. Standards-based 2754 methods for configuration management from the co-located NOC are 2755 necessary for this deployment option. The set of interesting 2756 configuration objects for the SMF process are listed within this 2757 MIB module. 2759 o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed 2760 NOC - Here the vehicles carrying the MANET routers carry multiple 2761 wireless interfaces, one of which is a relatively low-bandwidth 2762 on-the-move satellite connection which interconnects a fix NOC to 2763 the nodes of the MANET. Standards-based methods for monitoring 2764 and fault management from the fixed NOC are necessary for this 2765 deployment option. 2767 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 2768 larger vehicles, a hierarchical network management arrangement is 2769 useful. Centralized network management is performed from a fixed 2770 NOC while local management is performed locally from within the 2771 vehicles. Standards-based methods for configuration, monitoring 2772 and fault management are necessary for this deployment option. 2774 Here we provide an example of the simplest of configurations to 2775 establish an operational multicast forwarding capability in a MANET. 2776 This discussion only identifies the configuration necessary through 2777 the SMF-MIB module and assumes that other configuration has occurred. 2778 Assume that the MANET is to support only IPv4 addressing and that the 2779 MANET nodes are to be configured in the context of the Parking Lot 2780 Initialization case above. Then the SMF-MIB module defines ten 2781 configuration OIDs and two configuration tables, i.e., the 2782 smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten 2783 OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL 2784 clauses which allow for a functional configuration of the SMF process 2785 within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the 2786 smfCfgRouterID can be set as, e.g. (assuming the use of the Net-SNMP 2787 toolkit),: 2789 snmpset [options] .0 a 192.168.1.100 2791 If the smfCfgAddrForwardingTable is left empty, then the SMF local 2792 forwarder will forward all multicast addresses. So this table does 2793 not require configuration if you want to have the MANET forward all 2794 multicast addresses. 2796 All that remains is to configure at least one row in the 2797 smfCfgInterfaceTable. Assume that the node has a wireless interface 2798 with an ='wlan0' and an ='1'. All of the objects in 2799 the rows of the smfCfgInterfaceTable have a DEFVAL clause, hence only 2800 the RowStatus object needs to be set. So the SMF process will be 2801 activated on the 'wlan0' interface by the following network manager 2802 snmpset command: 2804 snmpset [options] .1 i active(1) 2806 At this point, the configured forwarder will begin a Classical 2807 Flooding algorithm to forward all multicast addresses IPv4 packets it 2808 receives. 2810 To provide a more efficient multicast forwarding within the MANET, 2811 the network manager could walk the smfCapabilitiesTable to identify 2812 other SMF operational modes, e.g.,: 2814 snmpwalk [options] 2816 SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1 2818 SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2 2820 SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1) 2822 SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2) 2824 SMF-MIB::smfCapabilitiesRssaID.1 = INTEGER: cF(1) 2826 SMF-MIB::smfCapabilitiesRssaID.2 = INTEGER: eCDS(3) 2828 In this example, the forwarding device also supports the Extended 2829 Connected Dominating Set (eCDS) RSSA with the forwarder in the 2830 'independent(2)' operational mode. If the network manager were to 2831 then issue an snmpset, e.g.,: 2833 snmpset [options] .0 i 2 2835 then the local forwarder would switch if forwarding behavior from 2836 Classical Flooding to the more efficient eCDS flooding. 2838 11. IANA Considerations 2840 This document defines two MIB modules: 2842 o SMF-MIB is defined in Section 7 and is an experimental MIB module 2844 o IANA-SMF-MIB is defined in Section 8 and is an IANA MIB module 2845 that IANA is requested to maintain 2847 Thus, there are three actions requested of IANA: 2849 1. IANA is requested to allocate an OBJECT IDENTIFIER value and 2850 record it in the SMI Numbers registry in the sub-registry called "SMI 2851 Experimental Codes" under the experimental branch (1.3.6.1.3). 2853 Decimal | Name | Description | Reference 2854 --------+---------+---------------+------------ 2855 xxxx | smfMib | SMF-MIB | [This.I-D] 2857 [RFC Editor Note: Please replace the tag "xxxx" in 2858 this document with the value assigned by IANA and 2859 remove this note.] 2861 2. IANA is requested to allocate an OBJECT IDENTIFIER value and 2862 record it in the SMI Numbers registry in the sub-registry called "SMI 2863 Network Management MGMT Codes Internet-standard MIB" under the mib-2 2864 branch (1.3.6.1.2.1). 2866 Decimal | Name | Description | Reference 2867 --------+---------------+-----------------+------------ 2868 kkkk | ianaSmfMIB | IANA-SMF-MIB | [This.I-D] 2870 [RFC Editor Note: Please replace the tag "kkkk" in 2871 this document with the value assigned by IANA and 2872 remove this note.] 2874 3. IANA is requested to maintain a MIB module called ianaSmfMIB and 2875 populate it with the initial MIB module defined in Section 8 of this 2876 document by creating a new entry in the registry "IANA Maintained 2877 MIBs" called "IANA-SMF-MIB". 2879 12. Contributors 2881 This MIB document uses the template authored by D. Harrington which 2882 is based on contributions from the MIB Doctors, especially Juergen 2883 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2885 13. Acknowledgements 2887 The authors would like to acknowledge the valuable comments from Sean 2888 Harnedy in the early phases of the development of this MIB module and 2889 from Dan Romascanu in the final reviews of this MIB module. The 2890 authors would like to thank James Nguyen for his careful review and 2891 comments on this MIB module and his work on the definitions of the 2892 follow-on MIB modules to configure specific RSSA algorithms related 2893 to SMF. Further, the authors would like to acknowledge to work of 2894 James Nguyen, Brian Little, Ryan Morgan and Justin Dean on their 2895 software development of the SMF-MIB. 2897 14. References 2899 14.1. Normative References 2901 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2902 MIB", RFC 2863, June 2000. 2904 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2905 Architecture for Describing Simple Network Management 2906 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2907 December 2002. 2909 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 2910 Simple Network Management Protocol (SNMP)", STD 62, 2911 RFC 3418, December 2002. 2913 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2914 Schoenwaelder, "Textual Conventions for Internet Network 2915 Addresses", RFC 4001, February 2005. 2917 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2918 Requirement Levels", BCP 14, RFC 2119, March 1997. 2920 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2921 Schoenwaelder, Ed., "Structure of Management Information 2922 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2924 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2925 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2926 STD 58, RFC 2579, April 1999. 2928 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2929 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2930 April 1999. 2932 [RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621, 2933 May 2012. 2935 14.2. Informative References 2937 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2938 "Introduction and Applicability Statements for Internet- 2939 Standard Management Framework", RFC 3410, December 2002. 2941 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2942 (USM) for version 3 of the Simple Network Management 2943 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 2945 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 2946 Advanced Encryption Standard (AES) Cipher Algorithm in the 2947 SNMP User-based Security Model", RFC 3826, June 2004. 2949 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2950 for the Simple Network Management Protocol (SNMP)", 2951 RFC 5591, June 2009. 2953 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 2954 Shell Transport Model for the Simple Network Management 2955 Protocol (SNMP)", RFC 5592, June 2009. 2957 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 2958 Model for the Simple Network Management Protocol (SNMP)", 2959 RFC 6353, July 2011. 2961 Appendix A. 2963 *************************************************************** 2964 * Note to the RFC Editor (to be removed prior to publication) * 2965 * * 2966 * 1) The reference to RFCXXXX throughout this document point * 2967 * to the current draft-ietf-manet-smf-xx.txt. This needs * 2968 * to be replaced with the XXXX RFC number for the SMF * 2969 * publication. * 2970 * * 2971 * 2) This document also contains the IANA-SMF-MIB module * 2972 * which is defined by this specification above. IANA should * 2973 * take over the IANA-SMF-MIB and keep it synchronized with * 2974 * the registries identified within the contained * 2975 * IANAsmfOpModeIdTC and IANAsmfRssaIdTC TEXTUAL-CONVENTIONs. * 2976 * * 2977 *************************************************************** 2979 Authors' Addresses 2981 Robert G. Cole 2982 US Army CERDEC 2983 6010 Frankford Road 2984 Aberdeen Proving Ground, Maryland 21005 2985 USA 2987 Phone: +1 443 395 8744 2988 EMail: robert.g.cole@us.army.mil 2990 Joseph Macker 2991 Naval Research Laboratory 2992 Washington, D.C. 20375 2993 USA 2995 EMail: macker@itd.nrl.navy.mil 2997 Brian Adamson 2998 Naval Research Laboratory 2999 Washington, D.C. 20375 3000 USA 3002 EMail: adamson@itd.nrl.navy.mil