idnits 2.17.1 draft-ietf-manet-smf-mib-13.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 : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 12, 2014) is 3538 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). 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: February 13, 2015 B. Adamson 6 Naval Research Laboratory 7 August 12, 2014 9 Definition of Managed Objects for the Manet Simplified Multicast 10 Framework Relay Set Process 11 draft-ietf-manet-smf-mib-13 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 February 13, 2015. 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. Relationship to the IP-MIB . . . . . . . . . . . . . . . . 9 75 6.3. Relationship to the IPMCAST-MIB . . . . . . . . . . . . . 10 76 6.4. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 77 6.5. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10 78 7. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 11 79 8. IANA-SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . 52 80 9. Security Considerations . . . . . . . . . . . . . . . . . . . 56 81 10. Applicability Statement . . . . . . . . . . . . . . . . . . . 60 82 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 83 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 63 84 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 63 85 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63 86 14.1. Normative References . . . . . . . . . . . . . . . . . . . 63 87 14.2. Informative References . . . . . . . . . . . . . . . . . . 64 88 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 65 90 1. Introduction 92 This memo defines a portion of the Management Information Base (MIB) 93 for use with network management protocols in the Internet community. 94 In particular, it describes objects for configuring aspects of a 95 process implementing Simplified Multicast Forwarding (SMF) [RFC6621] 96 for Mobile Ad-Hoc Networks (MANETs). SMF provides multicast 97 Duplicate Packet Detection (DPD) and supports algorithms for 98 constructing an estimate of a MANET Minimum Connected Dominating Set 99 (MCDS) for efficient multicast forwarding. The SMF-MIB module also 100 reports state information, performance information, and 101 notifications. In addition to configuration, this additional state 102 and performance information is useful to operators troubleshooting 103 multicast forwarding problems. 105 2. The Internet-Standard Management Framework 107 For a detailed overview of the documents that describe the current 108 Internet-Standard Management Framework, please refer to section 7 of 109 RFC 3410 [RFC3410]. 111 Managed objects are accessed via a virtual information store, termed 112 the Management Information Base or MIB. MIB objects are generally 113 accessed through the Simple Network Management Protocol (SNMP). 114 Objects in the MIB are defined using the mechanisms defined in the 115 Structure of Management Information (SMI). This memo specifies a MIB 116 module that is compliant to the SMIv2, which is described in STD 58, 117 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 118 [RFC2580]. 120 3. Conventions 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 124 "OPTIONAL" in this document are to be interpreted as described in RFC 125 2119 [RFC2119]. 127 4. Overview 129 SMF provides methods for implementing Duplicate Packet Detection 130 (DPD)-based multicast forwarding with the optional use of Connected 131 Dominating Set (CDS)-based relay sets. The CDS provides a complete 132 connected coverage of the nodes comprising the MANET. The Minimum 133 CDS (MCDS) is the smallest set of MANET nodes (comprising a connected 134 cluster) which cover all the nodes in the cluster with their 135 transmissions. As the density of the MANET nodes increase, the 136 fraction of nodes required in an MCDS decreases. Using the MCDS as a 137 multicast forwarding set then becomes an efficient multicast 138 mechanism for MANETs. 140 Various algorithms for the construction of estimates of the MCDS 141 exist. The Simplified Multicast Framework [RFC6621] describes some 142 of these. It further defines various operational modes for a node 143 which is participating in the collective creation of the MCDS 144 estimates. These modes depend upon the set of related MANET routing 145 and discovery protocols and mechanisms in operation in the specific 146 MANET node. 148 A SMF router's MIB module contains SMF process configuration 149 parameters (e.g. specific CDS algorithm), state information (e.g., 150 current membership in the CDS), performance counters (e.g., packet 151 counters), and notifications. 153 4.1. SMF Management Model 155 This section describes the management model for the SMF node process. 157 Figure 1 (reproduced from Figure 1 of [RFC6621]) shows the 158 relationship between the SMF Relay Set selection algorithm and the 159 related algorithms, processes and protocols running in the MANET 160 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 161 topology information gotten from the MANET Neighborhood Discovery 162 Protocol (NHDP), from the specific MANET routing protocol running on 163 the node, or from Layer 2 information passed up to the higher layer 164 protocol processes. 166 ______________ ____________ 167 | | | | 168 | Neighborhood | | Relay Set | 169 | Discovery |------------->| Selection | 170 | | neighbor | | 171 |______________| info |____________| 172 \ / 173 \ / 174 neighbor\ / forwarding 175 info \ _____________ / status 176 \ | | / 177 `-->| Forwarding |<--' 178 | Process | 179 ----------------->|_____________|-----------------> 180 incoming packet, forwarded packets 181 interface id , and 182 previous hop 184 Figure 1: SMF Router Architecture 186 4.2. Terms 188 The following definitions apply throughout this document: 190 o Configuration Objects - switches, tables, objects which are 191 initialized to default settings or set through the management 192 interfaces such as defined by this MIB module. 194 o Tunable Configuration Objects - objects whose values affect timing 195 or attempt bounds on the SMF Relay Set (RS) process. 197 o State Objects - automatically generated values which define the 198 current operating state of the SMF RS process in the router. 200 o Performance Objects - automatically generated values which help an 201 administrator or automated tool to assess the performance of the 202 CDS multicast process on the router and the overall multicast 203 performance within the MANET routing domain. 205 5. Structure of the MIB Module 207 This section presents the structure of the SMF-MIB module. The 208 objects are arranged into the following groups: 210 o smfMIBNotifications - defines the notifications associated with 211 the SMF process. 213 o smfMIBObjects - defines the objects forming the basis for the SMF- 214 MIB module. These objects are divided up by function into the 215 following groups: 217 * Capabilities Group - This group contains the SMF objects that 218 the device uses to advertise its local capabilities with 219 respect to, e.g., the supported RSSAs. 221 * Configuration Group - This group contains the SMF objects that 222 configure specific options that determine the overall operation 223 of the SMF process and the resulting multicast performance. 225 * State Group - Contains information describing the current state 226 of the SMF process such as the Neighbor Table. 228 * Performance Group - Contains objects which help to characterize 229 the performance of the SMF process, typically counters for 230 statistical computations. 232 o smfMIBConformance - defines two, i.e., minimal and full, 233 conformance implementations for the SMF-MIB module. 235 5.1. Textual Conventions 237 The textual conventions defined within the SMF-MIB module are: 239 o The SmfStatus is defined within the SMF-MIB module. This contains 240 the current operational status of the SMF process on an interface. 242 The textual conventions defined for the SMF-MIB module and maintained 243 by IANA are: 245 o The IANAsmfOpModeIdTC represents an index that identifies a 246 specific SMF operational mode. This textual convention is 247 maintained by IANA in the IANA-SMF-MIB. 249 o The IANAsmfRssaIdTC represents an index that identifies, through 250 reference, a specific RSSA available for operation on the device. 251 This textual convention is maintained by IANA also in the IANA- 252 SMF-MIB. 254 5.2. The Capabilities Group 256 The SMF device supports a set of capabilities. The list of 257 capabilities which the device can advertise are: 259 o Operational Mode - topology information from NHDP, CDS-aware 260 unicast routing or Cross-layer from Layer 2. 262 o SMF RSSA - the specific RSSA operational on the device. Note that 263 configuration, state and performance objects related to a specific 264 RSSA must be defined within a separate MIB module. 266 5.3. The Configuration Group 268 The SMF device is configured with a set of controls. Some of the 269 prominent configuration controls for the SMF device are: 271 o Operational Mode - determines where topology information is 272 derived from, e.g., NHDP, CDS-aware unicast routing or Cross-layer 273 from Layer 2. 275 o SMF RSSA - the specific RSSA operational on the device. 277 o Duplicate Packet detection for IPv4 - Identification-based or 278 Hash-based DPD. 280 o Duplicate Packet detection for IPv6 - Identification-based or 281 Hash-based DPD. 283 o SMF Type Message TLV - if NHDP mode is selected, then the SMF Type 284 Message TLV MAY be included in the NHDP exchanges. 286 o SMF Address Block TLV - if NHDP mode is selected, then the SMF 287 Address Block TLV SHOULD be included in the NHDP exchanges. 289 o SMF Address Forwarding Table - a table identifying configured 290 multicast addresses to be forwarded by the SMF process. 292 5.4. The State Group 294 The State sub-tree reports current state information, e.g., 296 o Node RSSA State - identifies whether the node is currently in or 297 out of the Relay Set. 299 o Neighbors Table - a table containing current one-hop neighbors and 300 their operational RSSA. 302 5.5. The Performance Group 304 The Performance sub-tree reports primarily counters that relate to 305 SMF RSSA performance. The SMF performance counters consists of per 306 node and per interface objects: 308 o Total multicast packets received. 310 o Total multicast packets forwarded. 312 o Total duplicate multicast packets detected. 314 o Per interface statistics table with the following entries: 316 * Multicast packets received. 318 * Multicast packets forwarded. 320 * Duplicate multicast packets detected. 322 5.6. The Notifications Group 324 The Notifications Sub-tree contains the list of notifications 325 supported within the SMF-MIB module and their intended purpose and 326 utility. 328 5.7. Tables and Indexing 330 The SMF-MIB module contains a number of tables which record data 331 related to: 333 o configuration and operation of packet forwarding on the local 334 router, 336 o configuration and operation of local MANET interfaces on the 337 router, and 339 o configuration and operation of various RSSA algorithms for packet 340 forwarding. 342 The SMF-MIB module's tables are indexed via the following constructs: 344 o smfCapabilitiesIndex - the index identifying the combination of 345 SMF mode and SMF RSSA available on this device. 347 o smfCfgAddrForwardingIndex - the index to configured multicast 348 addresses lists which are forwarded by the SMF process. 350 o smfCfgIfIndex - the IfIndex of the interface on the local router 351 on which SMF is configured. 353 o smfStateNeighborIpAddrType, smfStateNeighborIpAddr, and 354 smfStateNeighborPrefixLen - the interface index set of specific 355 one-hop neighbor nodes to this local router. 357 These tables and their associated indexing are: 359 o smfCapabilitiesTable - identifies the resident set of (SMF 360 Operational Modes, SMF RSSA algorithms) available on this router. 361 This table has 'INDEX { smfCapabilitiesIndex }. 363 o smfCfgAddrForwardingTable - contains information on multicast 364 addresses which are to be forwarded by the SMF process on this 365 device. This table has 'INDEX { smfCfgAddrForwardingIndex }'. 367 o smfCfgInterfaceTable - describes the SMF interfaces on this device 368 that are participating in the SMF packet forwarding process. This 369 table has 'INDEX { smfCfgIfIndex }'. 371 o smfStateNeighborTable - describes the current neighbor nodes, 372 their addresses and the SMF RSSA and the interface on which they 373 can be reached. This table has 'INDEX { 374 smfStateNeighborIpAddrType, smfStateNeighborIpAddr, 375 smfStateNeighborPrefixLen }'. 377 o smfPerfIpv4InterfacePerfTable - contains the IPv4 related SMF 378 statistics per each SMF interface on this device. This table has 379 'INDEX { smfCfgIfIndex }'. 381 o smfPerfIpv6InterfacePerfTable - contains the IPv6 related SMF 382 statistics per each SMF interface on this device. This table has 383 'INDEX { smfCfgIfIndex }'. 385 6. Relationship to Other MIB Modules 387 6.1. Relationship to the SNMPv2-MIB 389 The 'system' group in the SNMPv2-MIB module [RFC3418] is defined as 390 being mandatory for all systems, and the objects apply to the entity 391 as a whole. The 'system' group provides identification of the 392 management entity and certain other system-wide data. The SMF-MIB 393 module does not duplicate those objects. 395 6.2. Relationship to the IP-MIB 397 It is an expectation that SMF devices will implement the standard IP- 398 MIB module [RFC4293]. Exactly how to integrate SMF packet handling 399 and management into the standard IP-MIB module management are part of 400 the experiment. 402 The SMF-MIB module counters within the smfPerformanceGroup count 403 packets handled by the system and interface local SMF process (as 404 discussed above). Not all IP (unicast and multicast) packets on a 405 device interface are handled by the SMF process. So the counters are 406 tracking different packet streams in the IP-MIB and SMF-MIB modules. 408 6.3. Relationship to the IPMCAST-MIB 410 The smfCfgAddrForwardingTable is essentially a filter table (if 411 populated) that identifies addresses/packets to be forwarded via the 412 local SMF flooding process. The RFC 5132 IP Multicast MIB module 413 [RFC5132] manages objects related to standard IP multicast, which 414 could be running in parallel to SMF on the device. 416 RFC 5132 manages traditional IP-based multicast (based upon multicast 417 routing mechanisms). The SMF-MIB module provides management for a 418 MANET subnet-based flooding mechanism which, may be used for 419 multicast transport (through SMF broadcast) depending upon the MANET 420 dynamics and other factors regarding the MANET subnet. Further, they 421 may co-exist in certain MANET deployments using the 422 smfCfgAddrForwardingTable to hand certain IP multicast addresses to 423 the SMF process and other IP multicast packets to be forwarded by 424 other IP routed-based multicast mechanisms. SMF and the associated 425 SMF-MIB module are experimental and these are some of the experiments 426 to be had with SMF and the SMF-MIB module. 428 6.4. MIB modules required for IMPORTS 430 The textual conventions imported for use in the SMF-MIB module are as 431 follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 432 Counter32, Unsigned32, Integer32 and mib-2 textual conventions are 433 imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 434 and TruthValue textual conventions are imported from RFC 2579 435 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- 436 GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 437 InterfaceIndexOrZero textual convention is imported from RFC 2863 438 [RFC2863]. The SnmpAdminString textual convention is imported from 439 RFC 3411 [RFC3411]. The InetAddress, InetAddressType and 440 InetAddressPrefixLength textual conventions are imported from RFC 441 4001 [RFC4001]. 443 6.5. Relationship to the Future RSSA-MIB Moduless 445 In a sense, the SMF-MIB module is a general front-end to a set of, 446 yet to be developed, RSSA-specific MIB modules. These RSSA-specific 447 MIB modules will define the objects for the configuration, state, 448 performance and notification required for the operation of these 449 specific RSSAs. The SMF-MIB module Capabilities Group allows the 450 remote management station the ability to query the router to discover 451 the set of supported RSSAs. 453 7. SMF-MIB Definitions 455 SMF-MIB DEFINITIONS ::= BEGIN 457 IMPORTS 459 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 460 Counter32, Integer32, TimeTicks, experimental 461 FROM SNMPv2-SMI -- [RFC2578] 463 TEXTUAL-CONVENTION, RowStatus, TruthValue 464 FROM SNMPv2-TC -- [RFC2579] 466 MODULE-COMPLIANCE, OBJECT-GROUP, 467 NOTIFICATION-GROUP 468 FROM SNMPv2-CONF -- [RFC2580] 470 InterfaceIndexOrZero, ifName 471 FROM IF-MIB -- [RFC2863] 473 SnmpAdminString 474 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 476 InetAddress, InetAddressType, 477 InetAddressPrefixLength 478 FROM INET-ADDRESS-MIB -- [RFC4001] 480 IANAsmfOpModeIdTC 481 FROM IANA-SMF-MIB 483 IANAsmfRssaIdTC 484 FROM IANA-SMF-MIB 485 ; 487 smfMIB MODULE-IDENTITY 488 LAST-UPDATED "201408121300Z" -- August 12, 2014 489 ORGANIZATION "IETF MANET Working Group" 490 CONTACT-INFO 491 "WG E-Mail: manet@ietf.org 493 WG Chairs: sratliff@cisco.com 494 jmacker@nrl.navy.mil 496 Editors: Robert G. Cole 497 US Army CERDEC 498 Space and Terrestrial Communications 499 6010 Frankford Road 500 Aberdeen Proving Ground, MD 21005 501 USA 502 +1 443 395-8744 503 robert.g.cole@us.army.mil 505 Joseph Macker 506 Naval Research Laboratory 507 Washington, D.C. 20375 508 USA 509 macker@itd.nrl.navy.mil 511 Brian Adamson 512 Naval Research Laboratory 513 Washington, D.C. 20375 514 USA 515 adamson@itd.nrl.navy.mil" 517 DESCRIPTION 518 "This MIB module contains managed object definitions for 519 the Manet SMF RSSA process defined in: 521 Macker, J.(ed.), 522 Simplified Multicast Forwarding, RFC 6621, 523 May 2012. 525 Copyright (C) The IETF Trust (2014). This version 526 of this MIB module is part of RFC xxxx; see the RFC 527 itself for full legal notices." 529 -- Revision History 530 REVISION "201408121300Z" -- August 12, 2014 531 DESCRIPTION 532 "The first version of this MIB module, 533 published as RFC xxxx. 534 " 535 -- RFC-Editor assigns xxxx 536 ::= { experimental xxxx } -- to be assigned by IANA 538 -- 539 -- TEXTUAL CONVENTIONs 540 -- 542 SmfStatus ::= TEXTUAL-CONVENTION 543 STATUS current 544 DESCRIPTION 545 "An indication of the operability of a SMF 546 function or feature. For example, the status 547 of an interface: 'enabled' indicates that 548 this interface is performing SMF functions, 549 and 'disabled' indicates that it is not. 550 Similarly for the status of the device: 551 'enabled' indicates that the device has 552 enabled the SMF functions on the device and 553 'disabled' means that the device and all interfaces 554 have disabled all SMF functions." 555 SYNTAX INTEGER { 556 enabled (1), 557 disabled (2) 558 } 560 -- 561 -- Top-Level Object Identifier Assignments 562 -- 564 smfMIBNotifications OBJECT IDENTIFIER ::= { smfMIB 0 } 565 smfMIBObjects OBJECT IDENTIFIER ::= { smfMIB 1 } 566 smfMIBConformance OBJECT IDENTIFIER ::= { smfMIB 2 } 568 -- 569 -- smfMIBObjects Assignments: 570 -- smfCapabilitiesGroup - 1 571 -- smfConfigurationGroup - 2 572 -- smfStateGroup - 3 573 -- smfPerformanceGroup - 4 574 -- 576 -- 577 -- smfCapabilitiesGroup 578 -- 579 -- This group contains the SMF objects that identify specific 580 -- capabilities within this device related to SMF functions. 581 -- 583 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 585 -- 586 -- SMF Capabilities Table 587 -- 589 smfCapabilitiesTable OBJECT-TYPE 590 SYNTAX SEQUENCE OF SmfCapabilitiesEntry 591 MAX-ACCESS not-accessible 592 STATUS current 593 DESCRIPTION 594 "The smfCapabilitiesTable identifies the 595 resident set of SMF Operational Modes and 596 RSSA combinations that can run on this 597 forwarder." 598 REFERENCE 599 "See Section 7.2. 'Reduced Relay Set Forwarding', 600 Section 8.1.1. 'SMF Message TLV Type', and 601 the Appendices A, B and C in 602 RFC 6621 - Simplified Multicast Forwarding 603 (SMF), Macker, J., May 2012." 604 ::= { smfCapabilitiesGroup 1 } 606 smfCapabilitiesEntry OBJECT-TYPE 607 SYNTAX SmfCapabilitiesEntry 608 MAX-ACCESS not-accessible 609 STATUS current 610 DESCRIPTION 611 "Information about a particular operational 612 mode and RSSA combination. 613 " 614 INDEX { smfCapabilitiesIndex } 615 ::= { smfCapabilitiesTable 1 } 617 SmfCapabilitiesEntry ::= SEQUENCE { 618 smfCapabilitiesIndex Integer32, 619 smfCapabilitiesOpModeID IANAsmfOpModeIdTC, 620 smfCapabilitiesRssaID IANAsmfRssaIdTC 621 } 623 smfCapabilitiesIndex OBJECT-TYPE 624 SYNTAX Integer32 (1..2147483647) 625 MAX-ACCESS not-accessible 626 STATUS current 627 DESCRIPTION 628 "The index for this entry; a unique value, 629 greater than zero, for each combination of 630 a particular operational mode and RSSA 631 algorithm available on this device. 632 It is recommended that values are assigned 633 contiguously starting from 1. 635 Rows in this table are automatically 636 populated by the entity's management system 637 on initialization. 639 By default, the agent should support at least the 640 Classical Flooding 'cF' algorithm. All compliant 641 SMF forwarders must support Classical Flooding. 642 Hence, the first entry in this table MUST exist 643 and MUST be defined as: 645 smfCapabilitiesIndex i '1' 646 smfCapabilitiesOpModeID i 'cfOnly(1)' 647 smfCapabilitiesRssaID i 'cF(1)' 649 The value for each combination MUST remain 650 constant at least from one re-initialization 651 of the entity's management system to the 652 next re-initialization." 653 ::= { smfCapabilitiesEntry 1 } 655 smfCapabilitiesOpModeID OBJECT-TYPE 656 SYNTAX IANAsmfOpModeIdTC 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "This object identifies 661 the particular operational mode for this device." 662 ::= { smfCapabilitiesEntry 2 } 664 smfCapabilitiesRssaID OBJECT-TYPE 665 SYNTAX IANAsmfRssaIdTC 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "This object identifies 670 the particular RSSA algorithm in this MIB 671 module. Example RSSAs are found in the 672 appendix of RFC 6621." 673 REFERENCE 674 "See, e.g., Section 8.1.1. 'SMF Message TLV Type', 675 and the Appendices A, B and C in 676 RFC 6621 - Simplified Multicast Forwarding 677 (SMF), Macker, J., May 2012." 678 ::= { smfCapabilitiesEntry 3 } 680 -- 681 -- smfConfigurationGroup 682 -- 683 -- This group contains the SMF objects that configure specific 684 -- options that determine the overall performance and operation 685 -- of the multicast forwarding process for the router device 686 -- and its interfaces. 687 -- 689 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 691 smfCfgAdminStatus OBJECT-TYPE 692 SYNTAX SmfStatus 693 MAX-ACCESS read-write 694 STATUS current 695 DESCRIPTION 696 "The configured status of the SMF process 697 on this device. 'enabled(1)' means that 698 SMF is configured to run on this device. 699 'disabled(2)' mean that the SMF process 700 is configured off. 702 Prior to SMF functions being performed over 703 specific interfaces, this object must first 704 be 'enabled'. If this object is 'disabled', 705 then no SMF functions are being performed on 706 the device and all smfCfgIfAdminStatus objects 707 MUST also be set to 'disabled'. When this 708 object is changed from 'enabled' to 'disabled' 709 by the manager, then all smfCfgIfAdminStatus 710 objects MUST also be automatically set to 711 'disabled' by the agent. 713 The default value for this object SHOULD be 714 'enabled'. 716 This object is persistent and when written 717 the entity SHOULD save the change to 718 non-volatile storage." 719 DEFVAL { enabled } 720 ::= { smfConfigurationGroup 1 } 722 smfCfgSmfSysUpTime OBJECT-TYPE 723 SYNTAX TimeTicks 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "The time (in hundredths of a second) since the 728 system SMF process was last re-initialized. 729 The SMF process is re-initialized when the 730 value of the 'smfCfgAdminStatus' object 731 transitions to 'enabled' from either a prior 732 value of 'disabled' or upon initialization 733 of this device." 735 ::= { smfConfigurationGroup 2 } 737 smfCfgRouterIDAddrType OBJECT-TYPE 738 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 739 MAX-ACCESS read-write 740 STATUS current 741 DESCRIPTION 742 "The address type of the address used for 743 SMF ID of this router as specified 744 in the 'smfCfgRouterID' next. 746 Only the values ipv4(1) and ipv6(2) 747 are supported. 749 This object is persistent and when written 750 the entity SHOULD save the change to 751 non-volatile storage." 752 DEFVAL { ipv4 } 753 ::= { smfConfigurationGroup 3 } 755 smfCfgRouterID OBJECT-TYPE 756 SYNTAX InetAddress (SIZE(4|16)) 757 MAX-ACCESS read-write 758 STATUS current 759 DESCRIPTION 760 "The IP address used as the SMF router ID. 761 This can be set by the management station. 762 If not explicitly set, then the device 763 SHOULD select a routable IP address 764 assigned to this router for use as 765 the 'smfCfgRouterID'. 767 The smfCfgRouterID is a logical identification 768 that MUST be consistent across interoperable 769 SMF neighborhoods and it is RECOMMENDED to be 770 chosen as the numerically largest address 771 contained in a node's 'Neighbor Address List' 772 as defined in NHDP. A smfCfgRouterID MUST be 773 unique within the scope of the operating 774 MANET network regardless of the method used 775 for selecting it. 777 This object is persistent and when written 778 the entity SHOULD save the change to 779 non-volatile storage." 780 REFERENCE 781 "See, e.g., 782 Appendix Section A.1. 'E-CDS Relay Set 783 Selection Overview' and 785 Appendix Secdtion C.1. 'MPR-CDS Relay 786 Set Selection Overview' 788 in RFC 6621 - Simplified Multicast Forwarding 789 (SMF), Macker, J., May 2012." 790 ::= { smfConfigurationGroup 4 } 792 smfCfgOperationalMode OBJECT-TYPE 793 SYNTAX Integer32 (1..2147483647) 794 MAX-ACCESS read-write 795 STATUS current 796 DESCRIPTION 797 "The SMF RSS node operational mode and 798 RSSA algorithm combination active on this 799 local forwarder. This object is defined 800 to be equal to the smfCapabilitiesIndex 801 which identifies the specific active 802 operational mode and RSSA. 804 The default value for this object is 805 '1' which corresponds to: 807 smfCapabilitiesOpModeID i 'cfOnly(1)' 808 smfCapabilitiesRssaID i 'cF(1)' 810 This object is persistent and when written 811 the entity SHOULD save the change to 812 non-volatile storage." 813 REFERENCE 814 "See Section 7.2. 'Reduced Relay Set Forwarding', 815 and the Appendices A, B and C in 816 RFC 6621 - Simplified Multicast Forwarding 817 (SMF), Macker, J., May 2012." 818 DEFVAL { 1 } 819 ::= { smfConfigurationGroup 5 } 821 smfCfgRssaMember OBJECT-TYPE 822 SYNTAX INTEGER { 823 potential(1), 824 always(2), 825 never(3) 826 } 827 MAX-ACCESS read-write 828 STATUS current 829 DESCRIPTION 830 "The RSSA downselects a set of forwarders for 831 multicast forwarding. Sometimes it is useful 832 to force an agent to be included or excluded 833 from the resulting RSS. This object is a 834 switch to allow for this behavior. 836 The value 'potential(1)' allows the selected 837 RSSA to determine if this agent is included 838 or excluded from the RSS. 840 The value 'always(2)' forces the selected 841 RSSA include this agent in the RSS. 843 The value 'never(3)' forces the selected 844 RSSA to exclude this agent from the RSS. 846 The default setting for this object is 847 'potential(1)'. Other settings could pose 848 operational risks under certain conditions. 850 This object is persistent and when written 851 the entity SHOULD save the change to 852 non-volatile storage." 853 REFERENCE 854 "See Section 7. 'Relay Set Selection' in 855 RFC 6621 - Simplified Multicast Forwarding 856 (SMF), Macker, J., May 2012." 857 DEFVAL { potential } 858 ::= { smfConfigurationGroup 6 } 860 smfCfgIpv4Dpd OBJECT-TYPE 861 SYNTAX INTEGER { 862 hashBased(1), 863 identificationBased(2) 864 } 865 MAX-ACCESS read-write 866 STATUS current 867 DESCRIPTION 868 "The current method for IPv4 duplicate packet 869 detection. 871 The value 'hashBased(1)' indicates that the 872 routers duplicate packet detection is based 873 upon comparing a hash over the packet fields. 874 This is the default setting for this object. 876 The value 'identificationBased(2)' 877 indicates that the duplicate packet 878 detection relies upon header information 879 in the multicast packets to identify 880 previously received packets. 882 This object is persistent and when written 883 the entity SHOULD save the change to 884 non-volatile storage." 885 REFERENCE 886 "See Section 6.2. 'IPv4 Duplicate Packet 887 Detection' in RFC 6621 - Simplified 888 Multicast Forwarding (SMF), Macker, J., 889 May 2012." 890 DEFVAL { hashBased } 891 ::= { smfConfigurationGroup 7 } 893 smfCfgIpv6Dpd OBJECT-TYPE 894 SYNTAX INTEGER { 895 hashBased(1), 896 identificationBased(2) 897 } 898 MAX-ACCESS read-write 899 STATUS current 900 DESCRIPTION 901 "The current method for IPv6 duplicate packet 902 detection. 904 The values indicate the type of method used 905 for duplicate packet detection as described 906 the previous description for the object 907 `smfCfgIpv4Dpd'. 909 The default value for this object is 910 'hashBased(1)'. 912 This object is persistent and when written 913 the entity SHOULD save the change to 914 non-volatile storage." 915 REFERENCE 916 "See Section 6.1. 'IPv6 Duplicate Packet 917 Detection' in RFC 6621 - Simplified 918 Multicast Forwarding (SMF), Macker, J., 919 May 2012." 920 DEFVAL { hashBased } 921 ::= { smfConfigurationGroup 8 } 923 smfCfgMaxPktLifetime OBJECT-TYPE 924 SYNTAX Integer32 (0..65535) 925 UNITS "Seconds" 926 MAX-ACCESS read-write 927 STATUS current 928 DESCRIPTION 929 "The estimate of the network packet 930 traversal time. 932 This object is persistent and when written 933 the entity SHOULD save the change to 934 non-volatile storage." 935 REFERENCE 936 "See Section 6. 'SMF Duplicate Packet 937 Detection' in RFC 6621 - Simplified 938 Multicast Forwarding (SMF), Macker, J., 939 May 2012." 940 DEFVAL { 60 } 941 ::= { smfConfigurationGroup 9 } 943 smfCfgDpdEntryMaxLifetime OBJECT-TYPE 944 SYNTAX Integer32 (0..65525) 945 UNITS "Seconds" 946 MAX-ACCESS read-write 947 STATUS current 948 DESCRIPTION 949 "The maximum lifetime of a cached DPD 950 record in the local device storage. 952 If the memory is running low prior to the 953 MaxLifetime being exceeded, the local SMF 954 devices should purge the oldest records first. 956 This object is persistent and when written 957 the entity SHOULD save the change to 958 non-volatile storage." 959 REFERENCE 960 "See Section 6. 'SMF Duplicate Packet 961 Detection' in RFC 6621 - Simplified 962 Multicast Forwarding (SMF), Macker, J., 963 May 2012." 964 DEFVAL { 600 } 965 ::= { smfConfigurationGroup 10 } 967 -- 968 -- Configuration of messages to be included in 969 -- NHDP message exchanges in support of SMF 970 -- operations. 971 -- 972 smfCfgNhdpRssaMesgTLVIncluded OBJECT-TYPE 973 SYNTAX TruthValue 974 MAX-ACCESS read-write 975 STATUS current 976 DESCRIPTION 977 "Indicates whether the associated NHDP messages 978 include the RSSA Message TLV, or not. This 979 is an optional SMF operational setting. 980 The value 'true(1)' indicates that this TLV is 981 included; the value 'false(2)' indicates that it 982 is not included. 984 It is RECOMMENDED that the RSSA Message TLV 985 be included in the NHDP messages. 987 This object is persistent and when written 988 the entity SHOULD save the change to 989 non-volatile storage." 990 REFERENCE 991 "See Section 8.1.1. 'SMF Message TLV Type' in 992 RFC 6621 - Simplified Multicast Forwarding 993 (SMF), Macker, J., May 2012." 994 DEFVAL { true } 995 ::= { smfConfigurationGroup 11 } 997 smfCfgNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 998 SYNTAX TruthValue 999 MAX-ACCESS read-write 1000 STATUS current 1001 DESCRIPTION 1002 "Indicates whether the associated NHDP messages 1003 include the RSSA Address Block TLV, or not. 1004 This is an optional SMF operational setting. 1005 The value 'true(1)' indicates that this TLV is 1006 included; the value 'false(2)' indicates that it 1007 is not included. 1009 The smfCfgNhdpRssaAddrBlockTLVIncluded is optional 1010 in all cases as it depends on the existence of 1011 an address block which may not be present. 1012 If this SMF device is configured with NHDP, 1013 then this object SHOULD be set to 'true(1)'. 1015 This object is persistent and when written 1016 the entity SHOULD save the change to 1017 non-volatile storage." 1018 REFERENCE 1019 "See Section 8.1.2. 'SMF Address Block TLV 1020 Type' in RFC 6621 - Simplified Multicast 1021 Forwarding (SMF), Macker, J., May 2012." 1022 DEFVAL { true } 1023 ::= { smfConfigurationGroup 12 } 1025 -- 1026 -- Table identifying configured multicast addresses to be forwarded. 1027 -- 1029 smfCfgAddrForwardingTable OBJECT-TYPE 1030 SYNTAX SEQUENCE OF SmfCfgAddrForwardingEntry 1031 MAX-ACCESS not-accessible 1032 STATUS current 1033 DESCRIPTION 1034 "The smfCfgAddrForwardingTable is essentially a filter 1035 table (if populated) that identifies addresses/packets 1036 to be forwarded viaathe local SMF flooding process. 1037 The RFC 5132 IP Multicast MIB module manages objects 1038 related to standard IP multicast, which could be running 1039 in parallel to SMF on the device. 1041 RFC 5132 manages traditional IP-based multicast (based 1042 upon multicast routing mechanisms). The SMF-MIB module 1043 provides management for a MANET subnet-based flooding 1044 mechanism which, may be used for multicast transport 1045 (through SMF broadcast) depending upon the MANET dynamics 1046 and other factors regarding the MANET subnet. Further, 1047 they may co-exist in certain MANET deployments 1048 using the smfCfgAddrForwardingTable to hand certain IP 1049 multicast addresses to the SMF process and other IP 1050 multicast packets to be forwarded by other IP 1051 routed-based multicast mechanisms. SMF and the 1052 associated SMF-MIB module are experimental and these 1053 are some of the experiments to be had with SMF and 1054 the SMF-MIB module. 1056 This is the (conceptual) table containing information on 1057 multicast addresses which are to be forwarded by the SMF 1058 process. This table represents an IP filters table for 1059 forwarding (or not) packets based upon their IP 1060 multicast address. 1062 The SMF process can be configured to forward only those 1063 multicast addresses found within the 1064 smfCfgAddrForwardingTable. As such, addresses which are 1065 to be forwarded by the SMF process MUST be found within 1066 the address ranges configured within this table, unless 1067 this table is empty. 1069 Each row is associated with a range of multicast 1070 addresses, and ranges for different rows must be disjoint. 1071 Different rows MAY share a common 1072 smfCfgAddrForwardingGroupName to administratively 1073 associate different rows. 1075 The objects in this table are persistent and when written 1076 the entity SHOULD save the change to non-volatile storage." 1077 REFERENCE 1078 "See Section 9.1. 'Forwarded Multicast Groups' in 1079 RFC 6621 - Simplified Multicast Forwarding 1080 (SMF), Macker, J., May 2012." 1081 ::= { smfConfigurationGroup 13 } 1083 smfCfgAddrForwardingEntry OBJECT-TYPE 1084 SYNTAX SmfCfgAddrForwardingEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "An entry (conceptual row) containing the information on a 1089 particular multicast scope." 1090 INDEX { smfCfgAddrForwardingIndex } 1091 ::= { smfCfgAddrForwardingTable 1 } 1093 SmfCfgAddrForwardingEntry ::= SEQUENCE { 1094 smfCfgAddrForwardingIndex Integer32, 1095 smfCfgAddrForwardingGroupName SnmpAdminString, 1096 smfCfgAddrForwardingAddrType InetAddressType, 1097 smfCfgAddrForwardingAddress InetAddress, 1098 smfCfgAddrForwardingAddrPrefixLength 1099 InetAddressPrefixLength, 1100 smfCfgAddrForwardingStatus RowStatus 1101 } 1103 smfCfgAddrForwardingIndex OBJECT-TYPE 1104 SYNTAX Integer32 (1..2147483647) 1105 MAX-ACCESS not-accessible 1106 STATUS current 1107 DESCRIPTION 1108 "This object identifies an unique entry 1109 for a forwarding group. The index for 1110 this entry is a unique value, 1111 greater than zero, for each row. 1112 It is recommended that values are assigned 1113 contiguously starting from 1. 1115 The value for each row index MUST remain 1116 constant from one re-initialization 1117 of the entity's management system to the 1118 next re-initialization." 1119 ::= { smfCfgAddrForwardingEntry 1 } 1121 smfCfgAddrForwardingGroupName OBJECT-TYPE 1122 SYNTAX SnmpAdminString 1123 MAX-ACCESS read-create 1124 STATUS current 1125 DESCRIPTION 1126 "This object identifies a group name for a set of 1127 row entries in order to administratively associate 1128 a set of address ranges. 1130 If there is no group name or this object is 1131 otherwise not applicable, then this object contains 1132 a zero-length string. 1134 This object is persistent and when written 1135 the entity SHOULD save the change to 1136 non-volatile storage." 1137 ::= { smfCfgAddrForwardingEntry 2 } 1139 smfCfgAddrForwardingAddrType OBJECT-TYPE 1140 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1141 MAX-ACCESS read-create 1142 STATUS current 1143 DESCRIPTION 1144 "The type of the addresses in the multicast 1145 forwarding ranges identified by this table. 1147 Only the values ipv4(1) and ipv6(2) are 1148 supported. 1150 This object is persistent and when written 1151 the entity SHOULD save the change to 1152 non-volatile storage." 1153 ::= { smfCfgAddrForwardingEntry 3 } 1155 smfCfgAddrForwardingAddress OBJECT-TYPE 1156 SYNTAX InetAddress (SIZE(4|16)) 1157 MAX-ACCESS read-create 1158 STATUS current 1159 DESCRIPTION 1160 "The multicast group address which, when 1161 combined with smfCfgAddrForwardingAddrPrefixLength, 1162 gives the group prefix for this forwarding range. 1164 The InetAddressType is given by 1165 smfCfgAddrForwardingAddrType. 1167 This address object is only significant up to 1168 smfCfgAddrForwardingAddrPrefixLength bits. The 1169 remaining address bits are set to zero. This is 1170 especially important for this index field, 1171 Any non-zero bits would signify an entirely 1172 different entry. 1174 Legal values correspond to the subset of address 1175 families for which multicast address allocation 1176 is supported. 1178 This object is persistent and when written 1179 the entity SHOULD save the change to 1180 non-volatile storage." 1181 ::= { smfCfgAddrForwardingEntry 4 } 1183 smfCfgAddrForwardingAddrPrefixLength OBJECT-TYPE 1184 SYNTAX InetAddressPrefixLength 1185 MAX-ACCESS read-create 1186 STATUS current 1187 DESCRIPTION 1188 "The length in bits of the mask which, when 1189 combined with smfCfgAddrForwardingAddress, 1190 gives the group prefix for this forwarding 1191 range. 1193 This object is persistent and when written 1194 the entity SHOULD save the change to 1195 non-volatile storage." 1196 ::= { smfCfgAddrForwardingEntry 5 } 1198 smfCfgAddrForwardingStatus OBJECT-TYPE 1199 SYNTAX RowStatus 1200 MAX-ACCESS read-create 1201 STATUS current 1202 DESCRIPTION 1203 "The status of this row, by which new entries may be 1204 created, or old entries deleted from this table." 1205 ::= { smfCfgAddrForwardingEntry 6 } 1207 -- 1208 -- SMF Interfaces Configuration Table 1209 -- 1210 smfCfgInterfaceTable OBJECT-TYPE 1211 SYNTAX SEQUENCE OF SmfCfgInterfaceEntry 1212 MAX-ACCESS not-accessible 1213 STATUS current 1214 DESCRIPTION 1215 "The SMF Interface Table describes the SMF 1216 interfaces that are participating in the 1217 SMF packet forwarding process. The ifIndex is 1218 from the interfaces group defined in the 1219 Interfaces Group MIB module (RFC 2863). As such, 1220 this table 'sparse augments' the ifTable 1221 specifically when SMF is to be configured to 1222 operate over this interface. 1224 A conceptual row in this table exists if and only 1225 if either a manager has explicitly created the row 1226 or there is an interface on the managed device 1227 that automatically supports and runs SMF as part 1228 of the device's initialization process. 1230 The manager creates a row in this table by setting 1231 rowStatus to 'createAndGo' or 'createAndWait'. 1232 Row objects having associated DEFVAL clauses are 1233 automatically defined by the agent with these 1234 values during row creation, unless the manager 1235 explicitly defines these object values during the 1236 row creation. 1238 As the smfCfgInterfaceTable sparsely augments the 1239 IfTable. Hence, 1241 + an entry cannot exist in smfCfgInterfaceTable 1242 without a corresponding entry in the ifTable. 1244 + if an entry in the ifTable is removed, the 1245 corresponding entry (if it exists) in the 1246 smfCfgInterfaceTable MUST be removed. 1248 + the smfCfgIfStatus can have a value of 1249 'enabled' or 'disabled' independent of the 1250 current value of the ifAdminStatus of the 1251 corresponding entry in the ifTable. 1253 The values of the objects smfCfgAdminStatus and 1254 smfCfgIfAdminStatus reflect the up-down status of 1255 the SMF process running on the device and on the 1256 specific interfaces respectively. Hence, 1257 + the value of the smfCfgAdminStatus can be 1258 'enabled' or 'disabled' reflecting the current 1259 running status of the SMF process on the device. 1261 + the value of the smfCfgIfAdminStatus can be 1262 'enabled' or 'disabled' if the value of the 1263 smfCfgAdminStatus is set to 'enabled'. 1265 + if the value of the smfCfgAdminStatus is 1266 'disabled', then the corresponding 1267 smfCfgIfAdminStatus objects MUST be set 1268 to 'disabled' in the smfCfgInterfaceTable. 1270 + once the value of the smfCfgAdminStatus changes 1271 from 'disabled' to 'enabled', it is up to the 1272 management system to make the corresponding 1273 changes to the smfCfgIfAdminStatus values 1274 back to 'enabled'. 1275 " 1276 REFERENCE 1277 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1278 K., and F. Kastenholtz, June 2000." 1279 ::= { smfConfigurationGroup 14 } 1281 smfCfgInterfaceEntry OBJECT-TYPE 1282 SYNTAX SmfCfgInterfaceEntry 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 "The SMF interface entry describes one SMF 1287 interface as indexed by its ifIndex. 1289 The objects in this table are persistent and when 1290 written the device SHOULD save the change to 1291 non-volatile storage. For further information 1292 on the storage behavior for these objects, refer 1293 to the description for the smfCfgIfRowStatus 1294 object." 1295 INDEX { smfCfgIfIndex } 1296 ::= { smfCfgInterfaceTable 1 } 1298 SmfCfgInterfaceEntry ::= 1299 SEQUENCE { 1300 smfCfgIfIndex InterfaceIndexOrZero, 1301 smfCfgIfAdminStatus SmfStatus, 1302 smfCfgIfSmfUpTime TimeTicks, 1303 smfCfgIfRowStatus RowStatus 1304 } 1306 smfCfgIfIndex OBJECT-TYPE 1307 SYNTAX InterfaceIndexOrZero 1308 MAX-ACCESS not-accessible 1309 STATUS current 1310 DESCRIPTION 1311 "The ifIndex for this SMF interface. This value 1312 MUST correspond to an ifIndex referring 1313 to a valid entry in The Interfaces Table. 1314 If the manager attempts to create a row 1315 for which the ifIndex does not exist on the 1316 local device, then the agent SHOULD issue 1317 a return value of 'inconsistentValue' and 1318 the operation SHOULD fail." 1319 REFERENCE 1320 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1321 K., and F. Kastenholtz, June 2000." 1322 ::= { smfCfgInterfaceEntry 1 } 1324 smfCfgIfAdminStatus OBJECT-TYPE 1325 SYNTAX SmfStatus 1326 MAX-ACCESS read-create 1327 STATUS current 1328 DESCRIPTION 1329 "The SMF interface's administrative status. 1330 The value 'enabled' denotes that the interface 1331 is running the SMF forwarding process. 1332 The value 'disabled' denotes that the interface is 1333 currently external to the SMF forwarding process. 1335 When the value of the smfCfgAdminStatus is 1336 'disabled', then the corresponding smfCfgIfAdminStatus 1337 objects MUST be set to 'disabled' in the 1338 smfCfgInterfaceTable. 1340 The default value for this object is 'enabled(1)'. 1342 This object SHOULD be persistent and when 1343 written the device SHOULD save the change to 1344 non-volatile storage." 1345 DEFVAL { enabled } 1346 ::= { smfCfgInterfaceEntry 2 } 1348 smfCfgIfSmfUpTime OBJECT-TYPE 1349 SYNTAX TimeTicks 1350 MAX-ACCESS read-only 1351 STATUS current 1352 DESCRIPTION 1353 "The time (in hundredths of a second) since 1354 this interface SMF process was last 1355 re-initialized. The interface SMF process 1356 is re-initialized when the corresponding 1357 'smfCfgIfRowStatus' object transits to 1358 the 'active' state." 1359 ::= { smfCfgInterfaceEntry 3 } 1361 smfCfgIfRowStatus OBJECT-TYPE 1362 SYNTAX RowStatus 1363 MAX-ACCESS read-create 1364 STATUS current 1365 DESCRIPTION 1366 "This object permits management of this table 1367 by facilitating actions such as row creation, 1368 construction, and destruction. The value of 1369 this object has no effect on whether other 1370 objects in this conceptual row can be 1371 modified. 1373 An entry may not exist in the 'active' state unless all 1374 objects in the entry have a defined appropriate value. For 1375 objects with DEFVAL clauses, the management station 1376 does not need to specify the value of these objects in order 1377 for the row to transit to the 'active' state; the default 1378 value for these objects is used. For objects that do not 1379 have DEFVAL clauses, then the network manager MUST 1380 specify the value of these objects prior to this row 1381 transitioning to the 'active' state. 1383 When this object transitions to 'active', all objects 1384 in this row SHOULD be written to non-volatile (stable) 1385 storage. Read-create objects in this row MAY be modified. 1386 When an object in a row with smfCfgIfRowStatus of 'active' 1387 is changed, then the updated value MUST be reflected in SMF 1388 and this new object value MUST be written to non-volatile 1389 storage. 1391 If this object is not equal to 'active', all associated 1392 entries in the smfPerfIpv4InterfacePerfTable and the 1393 smfPerfIpv6InterfacePerfTable MUST be deleted." 1394 ::= { smfCfgInterfaceEntry 4 } 1396 -- 1397 -- smfStateGroup 1398 -- 1399 -- Contains information describing the current state of the SMF 1400 -- process such as the current inclusion in the RS or not. 1402 -- 1404 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1406 smfStateNodeRsStatusIncluded OBJECT-TYPE 1407 SYNTAX TruthValue 1408 MAX-ACCESS read-only 1409 STATUS current 1410 DESCRIPTION 1411 "The current status of the SMF node in the context of 1412 the MANETs relay set. A value of 'true(1)' indicates 1413 that the node is currently part of the MANET Relay 1414 Set. A value of 'false(2)' indicates that the node 1415 is currently not part of the MANET Relay Set." 1416 REFERENCE 1417 "See Section 7. 'Relay Set Selection' in 1418 RFC 6621 - Simplified Multicast Forwarding 1419 (SMF), Macker, J., May 2012." 1420 ::= { smfStateGroup 1 } 1422 smfStateDpdMemoryOverflow OBJECT-TYPE 1423 SYNTAX Counter32 1424 UNITS "DPD Records" 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "The number of DPD records that had to be flushed to 1429 prevent memory overruns for caching of these records. 1430 The number of records to be flushed upon a buffer 1431 overflow is an implementation specific decision. 1433 There is the potential for a counter discontinuity 1434 in this object if the system SMF process had been 1435 disabled and later enabled. In order to check for 1436 the occurrence of such a discontinuity when monitoring 1437 this counter object, it is recommended that the 1438 smfCfgSmfSysUpTime object also be monitored." 1439 REFERENCE 1440 "See Section 6. 'SMF Duplicate Packet 1441 Detection' in RFC 6621 - Simplified 1442 Multicast Forwarding (SMF), Macker, J., 1443 May 2012." 1444 ::= { smfStateGroup 2 } 1446 -- 1447 -- SMF Neighbor Table 1448 -- 1449 smfStateNeighborTable OBJECT-TYPE 1450 SYNTAX SEQUENCE OF SmfStateNeighborEntry 1451 MAX-ACCESS not-accessible 1452 STATUS current 1453 DESCRIPTION 1454 "The SMF StateNeighborTable describes the 1455 current one-hop neighbor nodes, their address 1456 and SMF RSSA and the interface on which 1457 they can be reached." 1458 REFERENCE 1459 "See Section 7. 'SMF Neighborhood Discovery' and 1460 Section 8.1. 'SMF Relay Algorithm TLV 1461 Types' in RFC 6621 - Simplified Multicast 1462 Forwarding (SMF), Macker, J., May 2012." 1463 ::= { smfStateGroup 3 } 1465 smfStateNeighborEntry OBJECT-TYPE 1466 SYNTAX SmfStateNeighborEntry 1467 MAX-ACCESS not-accessible 1468 STATUS current 1469 DESCRIPTION 1470 "The SMF Neighbor Table contains the 1471 set of one-hop neighbors, the interface 1472 they are reachable on and the SMF RSSA 1473 they are currently running." 1474 INDEX { smfStateNeighborIpAddrType, 1475 smfStateNeighborIpAddr, 1476 smfStateNeighborPrefixLen } 1477 ::= { smfStateNeighborTable 1 } 1479 SmfStateNeighborEntry ::= 1480 SEQUENCE { 1481 smfStateNeighborIpAddrType InetAddressType, 1482 smfStateNeighborIpAddr InetAddress, 1483 smfStateNeighborPrefixLen InetAddressPrefixLength, 1484 smfStateNeighborRSSA IANAsmfRssaIdTC, 1485 smfStateNeighborNextHopInterface InterfaceIndexOrZero 1486 } 1488 smfStateNeighborIpAddrType OBJECT-TYPE 1489 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1490 MAX-ACCESS not-accessible 1491 STATUS current 1492 DESCRIPTION 1493 "The one-hop neighbor IP address type. 1495 Only the values 'ipv4(1)' and 1496 'ipv6(2)' are supported." 1498 ::= { smfStateNeighborEntry 1 } 1500 smfStateNeighborIpAddr OBJECT-TYPE 1501 SYNTAX InetAddress (SIZE(4|16)) 1502 MAX-ACCESS not-accessible 1503 STATUS current 1504 DESCRIPTION 1505 "The one-hop neighbor Inet IPv4 or IPv6 1506 address. 1508 Only IPv4 and IPv6 addresses 1509 are supported." 1510 ::= { smfStateNeighborEntry 2 } 1512 smfStateNeighborPrefixLen OBJECT-TYPE 1513 SYNTAX InetAddressPrefixLength 1514 UNITS "bits" 1515 MAX-ACCESS not-accessible 1516 STATUS current 1517 DESCRIPTION 1518 "The prefix length. This is a decimal value that 1519 indicates the number of contiguous, higher-order 1520 bits of the address that make up the network 1521 portion of the address." 1522 ::= { smfStateNeighborEntry 3 } 1524 smfStateNeighborRSSA OBJECT-TYPE 1525 SYNTAX IANAsmfRssaIdTC 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "The current RSSA running on the neighbor." 1530 ::= { smfStateNeighborEntry 4 } 1532 smfStateNeighborNextHopInterface OBJECT-TYPE 1533 SYNTAX InterfaceIndexOrZero 1534 MAX-ACCESS read-only 1535 STATUS current 1536 DESCRIPTION 1537 "The interface ifIndex over which the 1538 neighbor is reachable in one-hop." 1539 ::= { smfStateNeighborEntry 6 } 1541 -- 1542 -- SMF Performance Group 1543 -- 1544 -- Contains objects which help to characterize the 1545 -- performance of the SMF RSSA process, such as statistics 1546 -- counters. There are two types of SMF RSSA statistics: 1547 -- global counters and per interface counters. 1548 -- 1549 -- It is an expectation that SMF devices will 1550 -- implement the standard IP-MIB module RFC4293. 1551 -- Exactly how to integrate SMF packet handling and 1552 -- management into the standard IP-MIB module management 1553 -- are part of the experiment. 1554 -- 1555 -- The SMF-MIB module counters within the 1556 -- smfPerformanceGroup count packets handled by the 1557 -- system and interface local SMF process (as discussed 1558 -- above). Not all IP (unicast and multicast) packets 1559 -- on a device interface are handled by the SMF process. 1560 -- So the counters are tracking different packet streams 1561 -- in the IP-MIB and SMF-MIB modules. 1562 -- 1564 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1566 smfPerfGobalGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1568 -- 1569 -- IPv4 packet counters 1570 -- 1572 smfPerfIpv4MultiPktsRecvTotal OBJECT-TYPE 1573 SYNTAX Counter32 1574 UNITS "Packets" 1575 MAX-ACCESS read-only 1576 STATUS current 1577 DESCRIPTION 1578 "A counter of the total number of 1579 multicast IPv4 packets received by the 1580 device and delivered to the SMF process. 1582 There is the potential for a counter discontinuity 1583 in this object if the system SMF process had been 1584 disabled and later enabled. In order to check for 1585 the occurrence of such a discontinuity when monitoring 1586 this counter object, it is recommended that the 1587 smfCfgSmfSysUpTime object also be monitored." 1588 ::= { smfPerfGobalGroup 1 } 1590 smfPerfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1591 SYNTAX Counter32 1592 UNITS "Packets" 1593 MAX-ACCESS read-only 1594 STATUS current 1595 DESCRIPTION 1596 "A counter of the total number of 1597 multicast IPv4 packets forwarded by the 1598 device. 1600 There is the potential for a counter discontinuity 1601 in this object if the system SMF process had been 1602 disabled and later enabled. In order to check for 1603 the occurrence of such a discontinuity when monitoring 1604 this counter object, it is recommended that the 1605 smfCfgSmfSysUpTime object also be monitored." 1606 ::= { smfPerfGobalGroup 2 } 1608 smfPerfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1609 SYNTAX Counter32 1610 UNITS "Packets" 1611 MAX-ACCESS read-only 1612 STATUS current 1613 DESCRIPTION 1614 "A counter of the total number of duplicate 1615 multicast IPv4 packets detected by the 1616 device. 1618 There is the potential for a counter discontinuity 1619 in this object if the system SMF process had been 1620 disabled and later enabled. In order to check for 1621 the occurrence of such a discontinuity when monitoring 1622 this counter object, it is recommended that the 1623 smfCfgSmfSysUpTime object also be monitored." 1624 REFERENCE 1625 "See Section 6.2. 'IPv4 Duplicate Packet 1626 Detection' in RFC 6621 - Simplified Multicast 1627 Forwarding (SMF), Macker, J., May 2012." 1628 ::= { smfPerfGobalGroup 3 } 1630 smfPerfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1631 SYNTAX Counter32 1632 UNITS "Packets" 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "A counter of the total number of dropped 1637 multicast IPv4 packets by the 1638 device due to TTL exceeded. 1640 There is the potential for a counter discontinuity 1641 in this object if the system SMF process had been 1642 disabled and later enabled. In order to check for 1643 the occurrence of such a discontinuity when monitoring 1644 this counter object, it is recommended that the 1645 smfCfgSmfSysUpTime object also be monitored." 1646 REFERENCE 1647 "See Section 5. 'SMF Packet Processing and 1648 Forwarding' in RFC 6621 - Simplified 1649 Multicast Forwarding (SMF), Macker, J., 1650 May 2012." 1651 ::= { smfPerfGobalGroup 4 } 1653 smfPerfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1654 SYNTAX Counter32 1655 UNITS "Packets" 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "A counter of the total number of IPv4 packets 1660 recieved which have a TTL larger than that 1661 of a previously received identical packet. 1663 There is the potential for a counter discontinuity 1664 in this object if the system SMF process had been 1665 disabled and later enabled. In order to check for 1666 the occurrence of such a discontinuity when monitoring 1667 this counter object, it is recommended that the 1668 smfCfgSmfSysUpTime object also be monitored." 1669 REFERENCE 1670 "See Section 5. 'SMF Packet Processing and 1671 Forwarding' in RFC 6621 - Simplified Multicast 1672 Forwarding (SMF), Macker, J., May 2012." 1673 ::= { smfPerfGobalGroup 5 } 1675 -- 1676 -- IPv6 packet counters 1677 -- 1679 smfPerfIpv6MultiPktsRecvTotal OBJECT-TYPE 1680 SYNTAX Counter32 1681 UNITS "Packets" 1682 MAX-ACCESS read-only 1683 STATUS current 1684 DESCRIPTION 1685 "A counter of the total number of 1686 multicast IPv6 packets received by the 1687 device and delivered to the SMF process. 1689 There is the potential for a counter discontinuity 1690 in this object if the system SMF process had been 1691 disabled and later enabled. In order to check for 1692 the occurrence of such a discontinuity when monitoring 1693 this counter object, it is recommended that the 1694 smfCfgSmfSysUpTime object also be monitored." 1695 ::= { smfPerfGobalGroup 6 } 1697 smfPerfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1698 SYNTAX Counter32 1699 UNITS "Packets" 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "A counter of the total number of 1704 multicast IPv6 packets forwarded by the 1705 device. 1707 There is the potential for a counter discontinuity 1708 in this object if the system SMF process had been 1709 disabled and later enabled. In order to check for 1710 the occurrence of such a discontinuity when monitoring 1711 this counter object, it is recommended that the 1712 smfCfgSmfSysUpTime object also be monitored." 1713 ::= { smfPerfGobalGroup 7 } 1715 smfPerfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1716 SYNTAX Counter32 1717 UNITS "Packets" 1718 MAX-ACCESS read-only 1719 STATUS current 1720 DESCRIPTION 1721 "A counter of the total number of duplicate 1722 multicast IPv6 packets detected by the 1723 device. 1725 There is the potential for a counter discontinuity 1726 in this object if the system SMF process had been 1727 disabled and later enabled. In order to check for 1728 the occurrence of such a discontinuity when monitoring 1729 this counter object, it is recommended that the 1730 smfCfgSmfSysUpTime object also be monitored." 1731 REFERENCE 1732 "See Section 6.1. 'IPv6 Duplicate Packet 1733 Detection' in RFC 6621 - Simplified Multicast 1734 Forwarding (SMF), Macker, J., May 2012." 1735 ::= { smfPerfGobalGroup 8 } 1736 smfPerfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1737 SYNTAX Counter32 1738 UNITS "Packets" 1739 MAX-ACCESS read-only 1740 STATUS current 1741 DESCRIPTION 1742 "A counter of the total number of dropped 1743 multicast IPv6 packets by the 1744 device due to TTL exceeded. 1746 There is the potential for a counter discontinuity 1747 in this object if the system SMF process had been 1748 disabled and later enabled. In order to check for 1749 the occurrence of such a discontinuity when monitoring 1750 this counter object, it is recommended that the 1751 smfCfgSmfSysUpTime object also be monitored." 1752 REFERENCE 1753 "See Section 5. 'SMF Packet Processing and 1754 Forwarding' in RFC 6621 - Simplified 1755 Multicast Forwarding (SMF), Macker, J., 1756 May 2012." 1757 ::= { smfPerfGobalGroup 9 } 1759 smfPerfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1760 SYNTAX Counter32 1761 UNITS "Packets" 1762 MAX-ACCESS read-only 1763 STATUS current 1764 DESCRIPTION 1765 "A counter of the total number of IPv6 packets 1766 recieved which have a TTL larger than that 1767 of a previously recived identical packet. 1769 There is the potential for a counter discontinuity 1770 in this object if the system SMF process had been 1771 disabled and later enabled. In order to check for 1772 the occurrence of such a discontinuity when monitoring 1773 this counter object, it is recommended that the 1774 smfCfgSmfSysUpTime object also be monitored." 1775 REFERENCE 1776 "See Section 5. 'SMF Packet Processing and 1777 Forwarding' in RFC 6621 - Simplified Multicast 1778 Forwarding (SMF), Macker, J., May 2012." 1779 ::= { smfPerfGobalGroup 10 } 1781 smfPerfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1782 SYNTAX Counter32 1783 UNITS "Packets" 1784 MAX-ACCESS read-only 1785 STATUS current 1786 DESCRIPTION 1787 "A counter of the total number of IPv6 packets 1788 received which required the HAV assist for DPD. 1790 There is the potential for a counter discontinuity 1791 in this object if the system SMF process had been 1792 disabled and later enabled. In order to check for 1793 the occurrence of such a discontinuity when monitoring 1794 this counter object, it is recommended that the 1795 smfCfgSmfSysUpTime object also be monitored." 1796 REFERENCE 1797 "See Section 6.1.1. 'IPv6 SMF_DPD Option Header' 1798 in RFC 6621 - Simplified Multicast Forwarding 1799 (SMF), Macker, J., May 2012." 1800 ::= { smfPerfGobalGroup 11 } 1802 smfPerfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1803 SYNTAX Counter32 1804 UNITS "Packets" 1805 MAX-ACCESS read-only 1806 STATUS current 1807 DESCRIPTION 1808 "A counter of the total number of IPv6 packets 1809 recieved which the device inserted the 1810 DPD header option. 1812 There is the potential for a counter discontinuity 1813 in this object if the system SMF process had been 1814 disabled and later enabled. In order to check for 1815 the occurrence of such a discontinuity when monitoring 1816 this counter object, it is recommended that the 1817 smfCfgSmfSysUpTime object also be monitored." 1818 REFERENCE 1819 "See Section 6.1.2. 'IPv6 Identification-Based 1820 DPD' in RFC 6621 - Simplified Multicast 1821 Forwarding (SMF), Macker, J., May 2012." 1822 ::= { smfPerfGobalGroup 12 } 1824 -- 1825 -- Per SMF Interface Performance Table 1826 -- 1828 smfPerfInterfaceGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1830 smfPerfIpv4InterfacePerfTable OBJECT-TYPE 1831 SYNTAX SEQUENCE OF SmfPerfIpv4InterfacePerfEntry 1832 MAX-ACCESS not-accessible 1833 STATUS current 1834 DESCRIPTION 1835 "The SMF Interface Performance Table 1836 describes the SMF counters per 1837 interface." 1838 ::= { smfPerfInterfaceGroup 1 } 1840 smfPerfIpv4InterfacePerfEntry OBJECT-TYPE 1841 SYNTAX SmfPerfIpv4InterfacePerfEntry 1842 MAX-ACCESS not-accessible 1843 STATUS current 1844 DESCRIPTION 1845 "The SMF Interface Performance entry 1846 describes the statistics for a particular 1847 node interface." 1848 INDEX { smfCfgIfIndex } 1849 ::= { smfPerfIpv4InterfacePerfTable 1 } 1851 SmfPerfIpv4InterfacePerfEntry ::= 1852 SEQUENCE { 1853 smfPerfIpv4MultiPktsRecvPerIf Counter32, 1854 smfPerfIpv4MultiPktsForwardedPerIf Counter32, 1855 smfPerfIpv4DuplMultiPktsDetectedPerIf Counter32, 1856 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1857 smfPerfIpv4TTLLargerThanPreviousPerIf Counter32 1858 } 1860 smfPerfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1861 SYNTAX Counter32 1862 UNITS "Packets" 1863 MAX-ACCESS read-only 1864 STATUS current 1865 DESCRIPTION 1866 "A counter of the number of multicast IP 1867 packets received by the SMF process on 1868 this device on this interface. 1870 There is the potential for a counter discontinuity 1871 in this object if the system SMF process had been 1872 disabled and later enabled on this interface. 1873 In order to check for the occurrence of such a 1874 discontinuity when monitoring this counter object, 1875 it is recommended that the smfCfgIfSmfUpTime 1876 object also be monitored." 1877 ::= { smfPerfIpv4InterfacePerfEntry 1 } 1878 smfPerfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1879 SYNTAX Counter32 1880 UNITS "Packets" 1881 MAX-ACCESS read-only 1882 STATUS current 1883 DESCRIPTION 1884 "A counter of the number of 1885 multicast IP packets forwarded by the 1886 SMF process on this device 1887 on this interface. 1889 There is the potential for a counter discontinuity 1890 in this object if the system SMF process had been 1891 disabled and later enabled on this interface. 1892 In order to check for the occurrence of such a 1893 discontinuity when monitoring this counter object, 1894 it is recommended that the smfCfgIfSmfUpTime 1895 object also be monitored." 1896 ::= { smfPerfIpv4InterfacePerfEntry 2 } 1898 smfPerfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1899 SYNTAX Counter32 1900 UNITS "Packets" 1901 MAX-ACCESS read-only 1902 STATUS current 1903 DESCRIPTION 1904 "A counter of the number of duplicate 1905 multicast IP packets detected by the 1906 SMF process on this device 1907 on this interface. 1909 There is the potential for a counter discontinuity 1910 in this object if the system SMF process had been 1911 disabled and later enabled on this interface. 1912 In order to check for the occurrence of such a 1913 discontinuity when monitoring this counter object, 1914 it is recommended that the smfCfgIfSmfUpTime 1915 object also be monitored." 1916 ::= { smfPerfIpv4InterfacePerfEntry 3 } 1918 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1919 SYNTAX Counter32 1920 UNITS "Packets" 1921 MAX-ACCESS read-only 1922 STATUS current 1923 DESCRIPTION 1924 "A counter of the total number of dropped 1925 multicast IPv4 packets by the SMF process 1926 on this device on this interface 1927 due to TTL exceeded. 1929 There is the potential for a counter discontinuity 1930 in this object if the system SMF process had been 1931 disabled and later enabled on this interface. 1932 In order to check for the occurrence of such a 1933 discontinuity when monitoring this counter object, 1934 it is recommended that the smfCfgIfSmfUpTime 1935 object also be monitored." 1936 ::= { smfPerfIpv4InterfacePerfEntry 4 } 1938 smfPerfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1939 SYNTAX Counter32 1940 UNITS "Packets" 1941 MAX-ACCESS read-only 1942 STATUS current 1943 DESCRIPTION 1944 "A counter of the total number of IPv4 packets 1945 received by the SMF process on this device 1946 on this interface which have a TTL larger than 1947 that of a previously received identical packet. 1949 There is the potential for a counter discontinuity 1950 in this object if the system SMF process had been 1951 disabled and later enabled on this interface. 1952 In order to check for the occurrence of such a 1953 discontinuity when monitoring this counter object, 1954 it is recommended that the smfCfgIfSmfUpTime 1955 object also be monitored." 1956 ::= { smfPerfIpv4InterfacePerfEntry 5 } 1958 smfPerfIpv6InterfacePerfTable OBJECT-TYPE 1959 SYNTAX SEQUENCE OF SmfPerfIpv6InterfacePerfEntry 1960 MAX-ACCESS not-accessible 1961 STATUS current 1962 DESCRIPTION 1963 "The SMF Interface Performance Table 1964 describes the SMF counters per 1965 interface." 1966 ::= { smfPerfInterfaceGroup 2 } 1968 smfPerfIpv6InterfacePerfEntry OBJECT-TYPE 1969 SYNTAX SmfPerfIpv6InterfacePerfEntry 1970 MAX-ACCESS not-accessible 1971 STATUS current 1972 DESCRIPTION 1973 "The SMF Interface Performance entry 1974 describes the counters for a particular 1975 node interface." 1976 INDEX { smfCfgIfIndex } 1977 ::= { smfPerfIpv6InterfacePerfTable 1 } 1979 SmfPerfIpv6InterfacePerfEntry ::= 1980 SEQUENCE { 1981 smfPerfIpv6MultiPktsRecvPerIf Counter32, 1982 smfPerfIpv6MultiPktsForwardedPerIf Counter32, 1983 smfPerfIpv6DuplMultiPktsDetectedPerIf Counter32, 1984 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1985 smfPerfIpv6TTLLargerThanPreviousPerIf Counter32, 1986 smfPerfIpv6HAVAssistsReqdPerIf Counter32, 1987 smfPerfIpv6DpdHeaderInsertionsPerIf Counter32 1988 } 1990 smfPerfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1991 SYNTAX Counter32 1992 UNITS "Packets" 1993 MAX-ACCESS read-only 1994 STATUS current 1995 DESCRIPTION 1996 "A counter of the number of 1997 multicast IP packets received by the 1998 SMF process on this device 1999 on this interface. 2001 There is the potential for a counter discontinuity 2002 in this object if the system SMF process had been 2003 disabled and later enabled on this interface. 2004 In order to check for the occurrence of such a 2005 discontinuity when monitoring this counter object, 2006 it is recommended that the smfCfgIfSmfUpTime 2007 object also be monitored." 2008 ::= { smfPerfIpv6InterfacePerfEntry 1 } 2010 smfPerfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 2011 SYNTAX Counter32 2012 UNITS "Packets" 2013 MAX-ACCESS read-only 2014 STATUS current 2015 DESCRIPTION 2016 "A counter of the number of 2017 multicast IP packets forwarded by the 2018 SMF process on this device 2019 on this interface. 2021 There is the potential for a counter discontinuity 2022 in this object if the system SMF process had been 2023 disabled and later enabled on this interface. 2024 In order to check for the occurrence of such a 2025 discontinuity when monitoring this counter object, 2026 it is recommended that the smfCfgIfSmfUpTime 2027 object also be monitored." 2028 ::= { smfPerfIpv6InterfacePerfEntry 2 } 2030 smfPerfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 2031 SYNTAX Counter32 2032 UNITS "Packets" 2033 MAX-ACCESS read-only 2034 STATUS current 2035 DESCRIPTION 2036 "A counter of the number of duplicate 2037 multicast IP packets detected by the 2038 SMF process on this device 2039 on this interface. 2041 There is the potential for a counter discontinuity 2042 in this object if the system SMF process had been 2043 disabled and later enabled on this interface. 2044 In order to check for the occurrence of such a 2045 discontinuity when monitoring this counter object, 2046 it is recommended that the smfCfgIfSmfUpTime 2047 object also be monitored." 2048 ::= { smfPerfIpv6InterfacePerfEntry 3 } 2050 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 2051 SYNTAX Counter32 2052 UNITS "Packets" 2053 MAX-ACCESS read-only 2054 STATUS current 2055 DESCRIPTION 2056 "A counter of the number of dropped 2057 multicast IP packets by the 2058 SMF process on this device 2059 on this interface due to TTL 2060 exceeded. 2062 There is the potential for a counter discontinuity 2063 in this object if the system SMF process had been 2064 disabled and later enabled on this interface. 2065 In order to check for the occurrence of such a 2066 discontinuity when monitoring this counter object, 2067 it is recommended that the smfCfgIfSmfUpTime 2068 object also be monitored." 2070 ::= { smfPerfIpv6InterfacePerfEntry 4 } 2072 smfPerfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 2073 SYNTAX Counter32 2074 UNITS "Packets" 2075 MAX-ACCESS read-only 2076 STATUS current 2077 DESCRIPTION 2078 "A counter of the total number of IPv6 packets 2079 received which have a TTL larger than that 2080 of a previously received identical packet 2081 by the SMF process on this device on this 2082 interface. 2084 There is the potential for a counter discontinuity 2085 in this object if the system SMF process had been 2086 disabled and later enabled on this interface. 2087 In order to check for the occurrence of such a 2088 discontinuity when monitoring this counter object, 2089 it is recommended that the smfCfgIfSmfUpTime 2090 object also be monitored." 2091 ::= { smfPerfIpv6InterfacePerfEntry 5 } 2093 smfPerfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 2094 SYNTAX Counter32 2095 UNITS "Packets" 2096 MAX-ACCESS read-only 2097 STATUS current 2098 DESCRIPTION 2099 "A counter of the total number of IPv6 packets 2100 received by the SMF process on this device 2101 on this interface which required the 2102 HAV assist for DPD. 2104 There is the potential for a counter discontinuity 2105 in this object if the system SMF process had been 2106 disabled and later enabled on this interface. 2107 In order to check for the occurrence of such a 2108 discontinuity when monitoring this counter object, 2109 it is recommended that the smfCfgIfSmfUpTime 2110 object also be monitored." 2111 ::= { smfPerfIpv6InterfacePerfEntry 6 } 2113 smfPerfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 2114 SYNTAX Counter32 2115 UNITS "Packets" 2116 MAX-ACCESS read-only 2117 STATUS current 2118 DESCRIPTION 2119 "A counter of the total number of IPv6 packets 2120 received by the SMF process on this device 2121 on this interface which the device inserted the 2122 DPD header option. 2124 There is the potential for a counter discontinuity 2125 in this object if the system SMF process had been 2126 disabled and later enabled on this interface. 2127 In order to check for the occurrence of such a 2128 discontinuity when monitoring this counter object, 2129 it is recommended that the smfCfgIfSmfUpTime 2130 object also be monitored." 2131 ::= { smfPerfIpv6InterfacePerfEntry 7 } 2133 -- 2134 -- Notifications 2135 -- 2137 smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 0 } 2138 smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 } 2140 -- smfMIBNotifObjects 2142 smfNotifAdminStatusChange NOTIFICATION-TYPE 2143 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2144 -- the notification. 2145 smfCfgRouterID, -- The originator of 2146 -- the notification. 2147 smfCfgAdminStatus -- The new status of the 2148 -- SMF process. 2149 } 2150 STATUS current 2151 DESCRIPTION 2152 "smfCfgAdminStatusChange is a notification sent when a 2153 the 'smfCfgAdminStatus' object changes." 2154 ::= { smfMIBNotifObjects 1 } 2156 smfNotifConfiguredOpModeChange NOTIFICATION-TYPE 2157 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2158 -- the notification. 2159 smfCfgRouterID, -- The originator of 2160 -- the notification. 2161 smfCfgOperationalMode -- The new Operations 2162 -- Mode of the SMF 2163 -- process. 2164 } 2165 STATUS current 2166 DESCRIPTION 2167 "smfNotifConfiguredOpModeChange is a notification 2168 sent when the 'smfCfgOperationalMode' object 2169 changes." 2170 ::= { smfMIBNotifObjects 2 } 2172 smfNotifIfAdminStatusChange NOTIFICATION-TYPE 2173 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2174 -- the notification. 2175 smfCfgRouterID, -- The originator of 2176 -- the notification. 2177 ifName, -- The interface whose 2178 -- status has changed. 2179 smfCfgIfAdminStatus -- The new status of the 2180 -- SMF interface. 2181 } 2182 STATUS current 2183 DESCRIPTION 2184 "smfCfgIfAdminStatusChange is a notification sent when a 2185 the 'smfCfgIfAdminStatus' object changes." 2186 ::= { smfMIBNotifObjects 3 } 2188 smfNotifDpdMemoryOverflowEvent NOTIFICATION-TYPE 2189 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2190 -- the notification. 2191 smfCfgRouterID, -- The originator of 2192 -- the notification. 2193 smfStateDpdMemoryOverflow -- The counter of 2194 -- the overflows. 2195 } 2196 STATUS current 2197 DESCRIPTION 2198 "smfNotifDpdMemoryOverflowEvents is sent when the 2199 number of memory overflow events exceeds the 2200 the 'smfNotifDpdMemoryOverflowThreshold' within the 2201 previous number of seconds defined by the 2202 'smfNotifDpdMemoryOverflowWindow'." 2203 ::= { smfMIBNotifObjects 4 } 2205 -- smfMIBNotifControl 2206 smfNotifDpdMemoryOverflowThreshold OBJECT-TYPE 2207 SYNTAX Integer32 (0..255) 2208 UNITS "Events" 2209 MAX-ACCESS read-write 2210 STATUS current 2211 DESCRIPTION 2212 "A threshold value for the 2213 `smfNotifDpdmemoryOverflowEvents' object. 2214 If the number of occurences exceeds 2215 this threshold within the previous 2216 number of seconds 2217 'smfNotifDpdMemoryOverflowWindow', 2218 then the `smfNotifDpdMemoryOverflowEvent' 2219 notification is sent. 2221 The default value for this object is 2222 '1'." 2223 DEFVAL { 1 } 2224 ::= { smfMIBNotifControl 1 } 2226 smfNotifDpdMemoryOverflowWindow OBJECT-TYPE 2227 SYNTAX TimeTicks 2228 MAX-ACCESS read-write 2229 STATUS current 2230 DESCRIPTION 2231 "A time window value for the 2232 `smfNotifDpdmemoryOverflowEvents' object. 2233 If the number of occurences exceeds 2234 the `smfNotifDpdMemoryOverflowThreshold' 2235 within the previous number of seconds 2236 'smfNotifDpdMemoryOverflowWindow', 2237 then the `smfNotifDpdMemoryOverflowEvent' 2238 notification is sent. 2240 The default value for this object is 2241 '1'." 2242 DEFVAL { 1 } 2243 ::= { smfMIBNotifControl 2 } 2245 -- 2246 -- Compliance Statements 2247 -- 2249 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2250 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2252 smfBasicCompliance MODULE-COMPLIANCE 2253 STATUS current 2254 DESCRIPTION "The basic implementation requirements for 2255 managed network entities that implement 2256 the SMF RSSA process." 2257 MODULE -- this module 2258 MANDATORY-GROUPS { smfCapabObjectsGroup, 2259 smfConfigObjectsGroup } 2260 ::= { smfCompliances 1 } 2262 smfFullCompliance MODULE-COMPLIANCE 2263 STATUS current 2264 DESCRIPTION "The full implementation requirements for 2265 managed network entities that implement 2266 the SMF RSSA process." 2267 MODULE -- this module 2268 MANDATORY-GROUPS { smfCapabObjectsGroup, 2269 smfConfigObjectsGroup, 2270 smfStateObjectsGroup, 2271 smfPerfObjectsGroup, 2272 smfNotifObjectsGroup, 2273 smfNotificationsGroup 2274 } 2275 ::= { smfCompliances 2 } 2277 -- 2278 -- Units of Conformance 2279 -- 2281 smfCapabObjectsGroup OBJECT-GROUP 2282 OBJECTS { 2283 smfCapabilitiesOpModeID, 2284 smfCapabilitiesRssaID 2285 } 2286 STATUS current 2287 DESCRIPTION 2288 "Set of SMF configuration objects implemented 2289 in this module." 2290 ::= { smfMIBGroups 1 } 2292 smfConfigObjectsGroup OBJECT-GROUP 2293 OBJECTS { 2294 smfCfgAdminStatus, 2295 smfCfgSmfSysUpTime, 2296 smfCfgRouterIDAddrType, 2297 smfCfgRouterID, 2298 smfCfgOperationalMode, 2299 smfCfgRssaMember, 2300 smfCfgIpv4Dpd, 2301 smfCfgIpv6Dpd, 2302 smfCfgMaxPktLifetime, 2303 smfCfgDpdEntryMaxLifetime, 2304 smfCfgNhdpRssaMesgTLVIncluded, 2305 smfCfgNhdpRssaAddrBlockTLVIncluded, 2307 smfCfgAddrForwardingGroupName, 2308 smfCfgAddrForwardingAddrType, 2309 smfCfgAddrForwardingAddress, 2310 smfCfgAddrForwardingAddrPrefixLength, 2311 smfCfgAddrForwardingStatus, 2313 smfCfgIfAdminStatus, 2314 smfCfgIfSmfUpTime, 2315 smfCfgIfRowStatus 2316 } 2317 STATUS current 2318 DESCRIPTION 2319 "Set of SMF configuration objects implemented 2320 in this module." 2321 ::= { smfMIBGroups 2 } 2323 smfStateObjectsGroup OBJECT-GROUP 2324 OBJECTS { 2325 smfStateNodeRsStatusIncluded, 2326 smfStateDpdMemoryOverflow, 2328 smfStateNeighborRSSA, 2329 smfStateNeighborNextHopInterface 2330 } 2331 STATUS current 2332 DESCRIPTION 2333 "Set of SMF state objects implemented 2334 in this module." 2335 ::= { smfMIBGroups 3 } 2337 smfPerfObjectsGroup OBJECT-GROUP 2338 OBJECTS { 2339 smfPerfIpv4MultiPktsRecvTotal, 2340 smfPerfIpv4MultiPktsForwardedTotal, 2341 smfPerfIpv4DuplMultiPktsDetectedTotal, 2342 smfPerfIpv4DroppedMultiPktsTTLExceededTotal, 2343 smfPerfIpv4TTLLargerThanPreviousTotal, 2345 smfPerfIpv6MultiPktsRecvTotal, 2346 smfPerfIpv6MultiPktsForwardedTotal, 2347 smfPerfIpv6DuplMultiPktsDetectedTotal, 2348 smfPerfIpv6DroppedMultiPktsTTLExceededTotal, 2349 smfPerfIpv6TTLLargerThanPreviousTotal, 2350 smfPerfIpv6HAVAssistsReqdTotal, 2351 smfPerfIpv6DpdHeaderInsertionsTotal, 2352 smfPerfIpv4MultiPktsRecvPerIf, 2353 smfPerfIpv4MultiPktsForwardedPerIf, 2354 smfPerfIpv4DuplMultiPktsDetectedPerIf, 2355 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf, 2356 smfPerfIpv4TTLLargerThanPreviousPerIf, 2358 smfPerfIpv6MultiPktsRecvPerIf, 2359 smfPerfIpv6MultiPktsForwardedPerIf, 2360 smfPerfIpv6DuplMultiPktsDetectedPerIf, 2361 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf, 2362 smfPerfIpv6TTLLargerThanPreviousPerIf, 2363 smfPerfIpv6HAVAssistsReqdPerIf, 2364 smfPerfIpv6DpdHeaderInsertionsPerIf 2365 } 2366 STATUS current 2367 DESCRIPTION 2368 "Set of SMF performance objects implemented 2369 in this module by total and per interface." 2370 ::= { smfMIBGroups 4 } 2372 smfNotifObjectsGroup OBJECT-GROUP 2373 OBJECTS { 2374 smfNotifDpdMemoryOverflowThreshold, 2375 smfNotifDpdMemoryOverflowWindow 2376 } 2377 STATUS current 2378 DESCRIPTION 2379 "Set of SMF notification control 2380 objects implemented in this module." 2381 ::= { smfMIBGroups 5 } 2383 smfNotificationsGroup NOTIFICATION-GROUP 2384 NOTIFICATIONS { 2385 smfNotifAdminStatusChange, 2386 smfNotifConfiguredOpModeChange, 2387 smfNotifIfAdminStatusChange, 2388 smfNotifDpdMemoryOverflowEvent 2389 } 2390 STATUS current 2391 DESCRIPTION 2392 "Set of SMF notifications implemented 2393 in this module." 2394 ::= { smfMIBGroups 6 } 2396 END 2398 8. IANA-SMF-MIB Definitions 2400 This section contains the IANA-SMF-MIB module. This MIB module 2401 defines two textual conventions for which IANA SHOULD maintain and 2402 keep synchronized with the registry identified below within the 2403 IANAsmfOpModeIdTC and the IANAsmfRssaIdTC TEXTUAL-CONVENTIONs. 2405 The IANAsmfOpModeIdTC defines an index that identifies through 2406 reference to a specific SMF operations mode. The index is an integer 2407 valued named-number enumeration consisting of an integer and label. 2408 IANA is to create and maintain this textual convention. Future 2409 assignments are made to anyone on a first come, first served basis. 2410 There is no substantive review of the request, other than to ensure 2411 that it is well-formed and does not duplicate an existing assignment. 2412 However, requests must include a minimal amount of clerical 2413 information, such as a point of contact (including an email address) 2414 and a brief description of the method being identified as a new SMF 2415 operations mode. 2417 The IANAsmfRssaIdTC defines an index that identifies through 2418 reference to a specific Reduced Set Selection Algorithm (RSSA). The 2419 index is an integer valued named-number enumeration consisting of an 2420 integer and label. IANA is to create and maintain this textual 2421 convention. 2423 Future assignments to the IANAsmfRssaIdTC for the index range 5-127 2424 require an RFC publication (either as an IETF submission or as an RFC 2425 Editor Independent submission [RFC5742]). The type of RFC MUST be 2426 Standards Track. The specific RSSA algorithms MUST be documented in 2427 sufficient detail so that interoperability between independent 2428 implementations is possible. 2430 Future assignments to the IANAsmfRssaIdTC for the index range 128-239 2431 are private or local use only, with the type and purpose defined by 2432 the local site. No attempt is made to prevent multiple sites from 2433 using the same value in different (and incompatible) ways. There is 2434 no need for IANA to review such assignments (since IANA will not 2435 record these) and assignments are not generally useful for broad 2436 interoperability. It is the responsibility of the sites making use 2437 of the Private Use range to ensure that no conflicts occur (within 2438 the intended scope of use). 2440 Future assignments to the IANAsmfRssaIdTC for the index range 240-255 2441 are to facilitate experimentation. These require an RFC publication 2442 (either as an IETF submission or as an RFC Editor Independent 2443 submission [RFC5742]). The type of RFC MUST be Experimental. The 2444 RSSA algorithms MUST be documented in sufficient detail so that 2445 interoperability between independent implementations is possible. 2447 IANA-SMF-MIB DEFINITIONS ::= BEGIN 2449 IMPORTS 2450 MODULE-IDENTITY, mib-2 2451 FROM SNMPv2-SMI 2452 TEXTUAL-CONVENTION 2453 FROM SNMPv2-TC; 2455 ianaSmfMIB MODULE-IDENTITY 2456 LAST-UPDATED "201408121300Z" -- August 12, 2014 2457 ORGANIZATION "IANA" 2458 CONTACT-INFO "Internet Assigned Numbers Authority 2460 Postal: ICANN 2461 4676 Admiralty Way, Suite 330 2462 Marina del Rey, CA 90292 2464 Tel: +1 310 823 9358 2465 E-Mail: iana@iana.org" 2466 DESCRIPTION "This MIB module defines the 2467 IANAsmfOpModeIdTC and IANAsmfRssaIdTC 2468 Textual Conventions, and thus the 2469 enumerated values of the 2470 smfCapabilitiesOpModeID and 2471 smfCapabilitiesRssaID objects defined 2472 in the SMF-MIB." 2473 REVISION "201408121300Z" -- August 12, 2014 2474 DESCRIPTION "Initial version of this MIB as published in 2475 RFC KKKK." 2476 ::= { mib-2 kkkk } 2478 IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION 2479 STATUS current 2480 DESCRIPTION 2481 "An index that identifies through reference to a specific 2482 SMF operations mode. There are basically three styles 2483 of SMF operation with reduced relay sets currently 2484 identified: 2486 Independent operation 'independent(1)' - 2487 SMF performs its own relay 2488 set selection using information from an associated 2489 MANET NHDP process. 2491 CDS-aware unicast routing operation 'routing(2)'- 2492 a coexistent unicast routing 2493 protocol provides dynamic relay 2494 set state based upon its own control plane 2495 CDS or neighborhood discovery information. 2497 Cross-layer operation 'crossLayer(3)' - 2498 SMF operates using neighborhood 2499 status and triggers from a 2500 cross-layer information base for dynamic relay 2501 set selection and maintenance. 2503 IANA MUST update this textual convention accordingly. 2505 The definition of this textual convention with the 2506 addition of newly assigned values is published 2507 periodically by the IANA, in either the Assigned 2508 Numbers RFC, or some derivative of it specific to 2509 Internet Network Management number assignments. (The 2510 latest arrangements can be obtained by contacting the 2511 IANA.) 2513 Requests for new values SHOULD be made to IANA via 2514 email (iana@iana.org)." 2515 REFERENCE 2516 "See Section 7.2. 'Reduced Relay Set Forwarding', 2517 and the Appendices A, B and C in 2518 RFC 6621 - Simplified Multicast Forwarding 2519 (SMF), Macker, J., May 2012." 2520 SYNTAX INTEGER { 2521 independent (1), 2522 routing (2), 2523 crossLayer (3) 2524 -- future (4-255) 2525 } 2527 IANAsmfRssaIdTC ::= TEXTUAL-CONVENTION 2528 STATUS current 2529 DESCRIPTION 2530 "An index that identifies through reference to a specific 2531 RSSA algorithms. Several are currently defined 2532 in the Appendix A, B and C of RFC 6621. 2534 Examples of RSSA algorithms already identified within 2535 this TC are: 2537 Classical Flooding (cF(1)) - is the standard 2538 flooding algorithm where each node in the next 2539 retransmits the information on each of its interfaces. 2541 Source-Based Multipint Relay (sMPR(2)) - 2542 this algorithm is used by Optimized Link State Routing 2543 (OLSR) and OLSR version 2 (OLSRv2) protocols for the 2544 relay of link state updates and other control 2545 information [RFC3626]. Since each router picks 2546 its neighboring relays independently, sMPR 2547 forwarders depend upon previous hop information 2548 (e.g., source MAC address) to operate correctly. 2550 Extended Connected Dominating Set (eCDS(3)) - 2551 defined in [RFC5614] this algorithm forms a single 2552 CDS mesh for the SMF operating region. Its 2553 packet-forwarding rules are not dependent upon 2554 previous hop knowledge in contrast to sMPR. 2556 Multipoint Relay Connected Dominating Set (mprCDS(4)) - 2557 This algorithm is an extension to the basic sMPR 2558 election algorithm that results in a shared 2559 (non-source-specific) SMF CDS. Thus, its forwarding 2560 rules are not dependent upon previous hop information, 2561 similar to eCDS. 2563 IANA MUST update this textual convention accordingly. 2565 The definition of this textual convention with the 2566 addition of newly assigned values is published 2567 periodically by the IANA, in either the Assigned 2568 Numbers RFC, or some derivative of it specific to 2569 Internet Network Management number assignments. (The 2570 latest arrangements can be obtained by contacting the 2571 IANA.) 2573 Requests for new values SHOULD be made to IANA via 2574 email (iana@iana.org)." 2575 REFERENCE 2576 "See, e.g., 2578 Section 8.1.1. 'SMF Message TLV Type', 2579 Appendix A. 'Essential Connecting Dominating Set (E-CDS) 2580 Algorithm', 2581 Appendix B. 'Source-Based Multipoint Relay (S-MPR) 2582 Algorithm', and 2583 Appendix C. 'Multipoint Relay Connected Dominating Set 2584 (MPR-CDS) Algorithm' 2585 in RFC 6621 - Macker, J., `Simplified Multicast 2586 Forwarding (SMF)', May 2012. 2588 RFC 3626 - Clausen, T., and P. Jacquet, `Optimized Link 2589 State Routing Protocol (OLSR)', October 2003. 2591 RFC 5614 - Ogier, R. and P. Spagnolo, `Mobile Ad Hoc 2592 Network (MANET) Extension of OSPF Using Connected 2593 Dominating Set (CDS) Flooding', August 2009. 2594 " 2595 SYNTAX INTEGER { 2596 cF(1), 2597 sMPR(2), 2598 eCDS(3), 2599 mprCDS(4) 2600 -- future(5-127) 2601 -- noStdAction(128-239) 2602 -- experimental(240-255) 2603 } 2605 END 2607 9. Security Considerations 2609 This section discusses security implications of the choices made in 2610 this SMF-MIB module. 2612 There are a number of management objects defined in this MIB module 2613 with a MAX-ACCESS clause of read-write and/or read-create. Such 2614 objects may be considered sensitive or vulnerable in some network 2615 environments. The support for SET operations in a non-secure 2616 environment without proper protection can have a negative effect on 2617 network operations. These are the tables and objects and their 2618 sensitivity/vulnerability: 2620 o 'smfCfgAdminStatus' - this writable configuration object controls 2621 the operational status of the SMF process. If this setting is 2622 configured inconsistently across the MANET multicast domain, then 2623 delivery of multicast data may be inconsistent across the domain; 2624 some nodes may not receive multicast data intended for them. 2626 o 'smfCfgRouterIDAddrType' and 'smfCfgRouterID' - these writable 2627 configuration objects define the ID of the SMF process. These 2628 objects should be configured with a routable address defined on 2629 the local SMF device. The smfCfgRouterID is a logical 2630 identification that MUST be configured as unique across inter- 2631 operating SMF neighborhoods and it is RECOMMENDED to be chosen as 2632 the numerically largest address contained in a node's 'Neighbor 2633 Address List' as defined in NHDP. A smfCfgRouterID MUST be unique 2634 within the scope of the operating MANET network regardless of the 2635 method used for selecting it. If these objects are mis-configured 2636 or configured in-consistently across the MANET, then the ability 2637 of various RSSA algorithms, e.g., ECDS, may be compromised. This 2638 would potentially result in some routers within the MANET not 2639 receiving multicast packets destine to them. Hence, intentionally 2640 mis-configuring these objects could pose a form of Denial-of- 2641 Service (DOS) attack against the MANET. 2643 o 'smfCfgOpMode' - this writable configuration object defines the 2644 operational mode of the SMF process. The operational mode defines 2645 how the SMF process receives its data to form its local estimate 2646 of the CDS. It is recommended that the value for this object be 2647 set consistently across the MANET to ensure proper operation of 2648 the multicast packet forwarding. If the value for this object is 2649 set inconsistently across the MANET, the result may be that 2650 multicast packet delivery will be compromised within the MANET. 2651 Hence, intentionally mis-configuring this object could pose a form 2652 DOS attack against the MANET. 2654 o 'smfCfgRssa' - this writable configuration object sets the 2655 specific Reduced Set Selection Algorithm (RSSA) for the SMF 2656 process. If this object is set inconsistently across the MANET 2657 domain, multicast delivery of data will likely fail. Hence, 2658 intentionally mis-configuring this object could pose a form DOS 2659 attack against the MANET. 2661 o 'smfCfgRssaMember' - this writable configuration object sets the 2662 'interest' of the local SMF node in participating in the CDS. 2663 Setting this object to 'never(3)' on a highly highly connected 2664 device could lead to frequent island formation. Setting this 2665 object to 'always(2)' could support data ex-filtration from the 2666 MANET domain. 2668 o 'smfCfgIpv4Dpd' - this writable configuration object sets the 2669 duplicate packet detection method, i.e., H-DPD or I-DPD, for 2670 forwarding of IPv4 multicast packets. Forwarders may operate with 2671 mixed H-DPD and I-DPD modes as long as they consistently perform 2672 the appropriate DPD routines outlined [RFC6621]. However, it is 2673 RECOMMENDED that a deployment be configured with a common mode for 2674 operational consistency. 2676 o 'smfCfgIpv6Dpd' - this writable configuration object sets the 2677 duplicate packet detection method for forwarding of IPv6 multicast 2678 packets. Since IPv6 SMF does specifies an option header, the 2679 interoperability constraints are not as loose as in the IPv4 2680 version, and forwarders SHOULD NOT operate with mixed H-DPD and 2681 I-DPD modes. Hence the value for this object SHOULD be 2682 consistently set within the forwarders comprising the MANET, else 2683 inconsistent forwarding may result unnecessary multicast packet 2684 dropping. 2686 o 'smfCfgMaxPktLifetime' - this writable configuration object sets 2687 the estimate of the network packet traversal time. If set too 2688 small, this could lead to poor multicast data delivery ratios 2689 throughout the MANET domain. This could serve as a form of DOS 2690 attack if this object value is set too small. 2692 o 'smfCfgDpdEntryMaxLifetime' - this writable configuration object 2693 sets the maximum lifetime (in seconds) for the cached DPD records 2694 for the combined IPv4 and IPv6 methods. If the memory is running 2695 low prior to the MaxLifetime being exceeded, the local SMF devices 2696 should purge the oldest records first. If this object value is 2697 set too small, then the effectiveness of the SMF DPD algorithms 2698 may become greatly diminished causing a higher than necessary 2699 packet load on the MANET. 2701 o 'smfCfgNhdpRssaMesgTLVIncluded' - this writable configuration 2702 object indicates whether the associated NHDP messages include the 2703 RSSA Message TLV, or not. It is highly RECOMMENDED that this 2704 object be set to 'true(1)' when the SMF operation mode is set to 2705 independent as this information will inform the local forwarder of 2706 the RSSA algorithm implemented in neighboring forwarders and is 2707 used to ensure consistent forwarding across the MANET. While it 2708 is possible that SMF neighbors MAY be configured differently with 2709 respect to the RSSA algorithm and still operate cooperatively, but 2710 these cases will vary dependent upon the algorithm types 2711 designated and this situation SHOULD be avoided. 2713 o 'smfCfgNhdpRssaAddrBlockTLVIncluded' - this writable configuration 2714 object indicates whether the associated NHDP messages include the 2715 the RSSA Address Block TLV, or not. The 2716 smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it 2717 depends on the existence of an address block which may not be 2718 present. If this SMF device is configured with NHDP, then this 2719 object should be set to 'true(1)' as this TLV enables CDS relay 2720 algorithm operation and configuration to be shared among 2-hop 2721 neighborhoods. Some relay algorithms require 2-hop neighbor 2722 configuration in order to correctly select relay sets. 2724 o 'smfCfgAddrForwardingTable' - the writable configuration objects 2725 in this table indicate which multicast IP addresses are to be 2726 forwarded by this SMF node. Misconfiguration of rows within this 2727 table can limit the ability of this SMF device to properly forward 2728 multicast data. 2730 o 'smfCfgInterfaceTable' - the writable configuration objects in 2731 this table indicate which SMF node interfaces are participating in 2732 the SMF packet forwarding process. Misconfiguration of rows 2733 within this table can limit the ability of this SMF device to 2734 properly forward multicast data. 2736 Some of the readable objects in this MIB module (i.e., objects with a 2737 MAX-ACCESS other than not-accessible) may be considered sensitive or 2738 vulnerable in some network environments. It is thus important to 2739 control even GET and/or NOTIFY access to these objects and possibly 2740 to even encrypt the values of these objects when sending them over 2741 the network via SNMP. These are the tables and objects and their 2742 sensitivity/vulnerability: 2744 o 'smfNodeRsStatusIncluded' - this readable state object indicates 2745 that this SMF node is part of the CDS, or not. Being part of the 2746 CDS makes this node a distinguished device. It could be exploited 2747 for data ex-filtration, or denial of service attacks. 2749 o 'smfStateNeighborTable' - the readable state objects in this table 2750 indicate current neighbor nodes to this SMF node. Exposing this 2751 information to an attacker could allow the attacker easier access 2752 to the larger MANET domain. 2754 The remainder of the objects in the SMF-MIB module are performance 2755 counter objects. While these give an indication of the activity of 2756 the SMF process on this node, it is not expected that exposing these 2757 values pose a security risk to the MANET network. 2759 SNMP versions prior to SNMPv3 did not include adequate security. 2760 Even if the network itself is secure (for example by using IPSec), 2761 even then, there is no control as to who on the secure network is 2762 allowed to access and GET/SET (read/change/create/delete) the objects 2763 in this MIB module. 2765 Implementations MUST provide the security features described by the 2766 SNMPv3 framework (see [RFC3410] ), including full support for 2767 authentication and privacy via the User-based Security Model (USM) 2768 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2769 MAY also provide support for the Transport Security Model (TSM) 2770 [RFC5591] in combination with a secure transport such as SSH 2771 [RFC5592] or TLS/DTLS [RFC6353]. 2773 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2774 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2775 enable cryptographic security. It is then a customer/operator 2776 responsibility to ensure that the SNMP entity giving access to an 2777 instance of this MIB module is properly configured to give access to 2778 the objects only to those principals (users) that have legitimate 2779 rights to indeed GET or SET (change/create/delete) them. 2781 10. Applicability Statement 2783 This document describes objects for configuring parameters of the 2784 Simplified Multicast Forwarding [RFC6621] process on a Mobile Ad-Hoc 2785 Network (MANET) router. This MIB module, denoted SMF-MIB, also 2786 reports state and performance information and notifications. This 2787 section provides some examples of how this MIB module can be used in 2788 MANET network deployments. A fuller discussion of MANET network 2789 management use cases and challenges will be provided elsewhere. 2791 SMF is designed to allow MANET routers to forward IPv4 and IPv6 2792 packets over the MANET and cover the MANET nodes through the 2793 automatic discovery of efficient estimates of the Minimum Connected 2794 Dominating Set (MCDS) of nodes within the MANET. The MCDS are 2795 estimated using the Relay Set Selection Algorithms (RSSAs) discussed 2796 within this document. In the following, three scenarios are listed 2797 where this MIB module is useful, i.e., 2799 o For a Parking Lot Initial Configuration Situation - it is common 2800 for the vehicles comprising the MANET being forward deployed at a 2801 remote location, e.g., the site of a natural disaster, to be off- 2802 loaded in a parking lot where an initial configuration of the 2803 networking devices is performed. The configuration is loaded into 2804 the devices from a fixed location Network Operation Center (NOC) 2805 at the parking lot and the vehicles are stationary at the parking 2806 lot while the configuration changes are made. Standards-based 2807 methods for configuration management from the co-located NOC are 2808 necessary for this deployment option. The set of interesting 2809 configuration objects for the SMF process are listed within this 2810 MIB module. 2812 o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed 2813 NOC - Here the vehicles carrying the MANET routers carry multiple 2814 wireless interfaces, one of which is a relatively low-bandwidth 2815 on-the-move satellite connection which interconnects a fix NOC to 2816 the nodes of the MANET. Standards-based methods for monitoring 2817 and fault management from the fixed NOC are necessary for this 2818 deployment option. 2820 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 2821 larger vehicles, a hierarchical network management arrangement is 2822 useful. Centralized network management is performed from a fixed 2823 NOC while local management is performed locally from within the 2824 vehicles. Standards-based methods for configuration, monitoring 2825 and fault management are necessary for this deployment option. 2827 Here we provide an example of the simplest of configurations to 2828 establish an operational multicast forwarding capability in a MANET. 2830 This discussion only identifies the configuration necessary through 2831 the SMF-MIB module and assumes that other configuration has occurred. 2832 Assume that the MANET is to support only IPv4 addressing and that the 2833 MANET nodes are to be configured in the context of the Parking Lot 2834 Initialization case above. Then the SMF-MIB module defines ten 2835 configuration OIDs and two configuration tables, i.e., the 2836 smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten 2837 OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL 2838 clauses which allow for a functional configuration of the SMF process 2839 within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the 2840 smfCfgRouterID can be set as, e.g. (assuming the use of the Net-SNMP 2841 toolkit),: 2843 snmpset [options] .0 a 192.0.2.100 2845 If the smfCfgAddrForwardingTable is left empty, then the SMF local 2846 forwarder will forward all multicast addresses. So this table does 2847 not require configuration if you want to have the MANET forward all 2848 multicast addresses. 2850 All that remains is to configure at least one row in the 2851 smfCfgInterfaceTable. Assume that the node has a wireless interface 2852 with an ='wlan0' and an ='1'. All of the objects in 2853 the rows of the smfCfgInterfaceTable have a DEFVAL clause, hence only 2854 the RowStatus object needs to be set. So the SMF process will be 2855 activated on the 'wlan0' interface by the following network manager 2856 snmpset command: 2858 snmpset [options] .1 i active(1) 2860 At this point, the configured forwarder will begin a Classical 2861 Flooding algorithm to forward all multicast addresses IPv4 packets it 2862 receives. 2864 To provide a more efficient multicast forwarding within the MANET, 2865 the network manager could walk the smfCapabilitiesTable to identify 2866 other SMF operational modes, e.g.,: 2868 snmpwalk [options] 2870 SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1 2872 SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2 2874 SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1) 2876 SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2) 2877 SMF-MIB::smfCapabilitiesRssaID.1 = INTEGER: cF(1) 2879 SMF-MIB::smfCapabilitiesRssaID.2 = INTEGER: eCDS(3) 2881 In this example, the forwarding device also supports the Extended 2882 Connected Dominating Set (eCDS) RSSA with the forwarder in the 2883 'independent(2)' operational mode. If the network manager were to 2884 then issue an snmpset, e.g.,: 2886 snmpset [options] .0 i 2 2888 then the local forwarder would switch if forwarding behavior from 2889 Classical Flooding to the more efficient eCDS flooding. 2891 11. IANA Considerations 2893 This document defines two MIB modules: 2895 o SMF-MIB is defined in Section 7 and is an experimental MIB module. 2897 o IANA-SMF-MIB is defined in Section 8 and is an IANA MIB module 2898 that IANA is requested to maintain. 2900 Thus, there are three actions requested of IANA: 2902 1. IANA is requested to allocate an OBJECT IDENTIFIER value and 2903 record it in the SMI Numbers registry in the sub-registry called "SMI 2904 Experimental Codes" under the experimental branch (1.3.6.1.3). 2906 Decimal | Name | Description | Reference 2907 --------+---------+---------------+------------ 2908 xxxx | smfMib | SMF-MIB | [This.I-D] 2910 [RFC Editor Note: Please replace the tag "xxxx" in 2911 this document with the value assigned by IANA and 2912 remove this note.] 2914 2. IANA is requested to allocate an OBJECT IDENTIFIER value and 2915 record it in the SMI Numbers registry in the sub-registry called "SMI 2916 Network Management MGMT Codes Internet-standard MIB" under the mib-2 2917 branch (1.3.6.1.2.1). 2919 Decimal | Name | Description | Reference 2920 --------+---------------+-----------------+------------ 2921 kkkk | ianaSmfMIB | IANA-SMF-MIB | [This.I-D] 2923 [RFC Editor Note: Please replace the tag "kkkk" in 2924 this document with the value assigned by IANA and 2925 remove this note.] 2927 3. IANA is requested to maintain a MIB module called ianaSmfMIB and 2928 populate it with the initial MIB module defined in Section 8 of this 2929 document by creating a new entry in the registry "IANA Maintained 2930 MIBs" called "IANA-SMF-MIB". 2932 12. Contributors 2934 This MIB document uses the template authored by D. Harrington which 2935 is based on contributions from the MIB Doctors, especially Juergen 2936 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2938 13. Acknowledgements 2940 The authors would like to acknowledge the valuable comments from Sean 2941 Harnedy in the early phases of the development of this MIB module. 2942 The authors would like to thank Adrian Farrel, Dan Romascanu, Juergen 2943 Shoenwaelder, Stephen Hanna, and Brian Haberman for their careful 2944 review of this documenti and their insightful comments. We also wish 2945 to thank the entire MANET WG for many reviews of this document. 2946 Further the authors would like to thank James Nguyen for his careful 2947 review and comments on this MIB module and his work on the 2948 definitions of the follow-on MIB modules to configure specific RSSA 2949 algorithms related to SMF. Further, the authors would like to 2950 acknowledge to work of James Nguyen, Brian Little, Ryan Morgan and 2951 Justin Dean on their software development of the SMF-MIB. 2953 14. References 2955 14.1. Normative References 2957 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2958 MIB", RFC 2863, June 2000. 2960 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2961 "Introduction and Applicability Statements for Internet- 2962 Standard Management Framework", RFC 3410, December 2002. 2964 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2965 Architecture for Describing Simple Network Management 2966 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2967 December 2002. 2969 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 2970 Simple Network Management Protocol (SNMP)", STD 62, 2971 RFC 3418, December 2002. 2973 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2974 Schoenwaelder, "Textual Conventions for Internet Network 2975 Addresses", RFC 4001, February 2005. 2977 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2978 Requirement Levels", BCP 14, RFC 2119, March 1997. 2980 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2981 Schoenwaelder, Ed., "Structure of Management Information 2982 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2984 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2985 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2986 STD 58, RFC 2579, April 1999. 2988 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2989 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2990 April 1999. 2992 [RFC3626] Clausen, T. and P. Jacquet, "Optimized Link State Routing 2993 Protocol (OLSR)", RFC 3626, October 2003. 2995 [RFC5742] Alvestrand, H. and R. Housley, "IESG Procedures for 2996 Handling of Independent and IRTF Stream Submissions", 2997 BCP 92, RFC 5742, December 2009. 2999 [RFC5614] Ogier, R. and P. Spagnolo, "Mobile Ad Hoc Network (MANET) 3000 Extension of OSPF Using Connected Dominating Set (CDS) 3001 Flooding", RFC 5614, August 2009. 3003 [RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621, 3004 May 2012. 3006 14.2. Informative References 3008 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 3009 (USM) for version 3 of the Simple Network Management 3010 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 3012 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 3013 Advanced Encryption Standard (AES) Cipher Algorithm in the 3014 SNMP User-based Security Model", RFC 3826, June 2004. 3016 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 3017 for the Simple Network Management Protocol (SNMP)", 3018 STD 78, RFC 5591, June 2009. 3020 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 3021 Shell Transport Model for the Simple Network Management 3022 Protocol (SNMP)", RFC 5592, June 2009. 3024 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 3025 Model for the Simple Network Management Protocol (SNMP)", 3026 STD 78, RFC 6353, July 2011. 3028 [RFC4293] Routhier, S., "Management Information Base for the 3029 Internet Protocol (IP)", RFC 4293, April 2006. 3031 [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 3032 MIB", RFC 5132, December 2007. 3034 Appendix A. 3036 *************************************************************** 3037 * Note to the RFC Editor (to be removed prior to publication) * 3038 * * 3039 * 1) The reference to RFCXXXX throughout this document point * 3040 * to the current draft-ietf-manet-smf-xx.txt. This needs * 3041 * to be replaced with the XXXX RFC number for the SMF * 3042 * publication. * 3043 * * 3044 * 2) This document also contains the IANA-SMF-MIB module * 3045 * which is defined by this specification above. IANA should * 3046 * take over the IANA-SMF-MIB and keep it synchronized with * 3047 * the registries identified within the contained * 3048 * IANAsmfOpModeIdTC and IANAsmfRssaIdTC TEXTUAL-CONVENTIONs. * 3049 * * 3050 *************************************************************** 3052 Authors' Addresses 3054 Robert G. Cole 3055 US Army CERDEC 3056 6010 Frankford Road 3057 Aberdeen Proving Ground, Maryland 21005 3058 USA 3060 Phone: +1 443 395 8744 3061 EMail: robert.g.cole@us.army.mil 3062 Joseph Macker 3063 Naval Research Laboratory 3064 Washington, D.C. 20375 3065 USA 3067 EMail: macker@itd.nrl.navy.mil 3069 Brian Adamson 3070 Naval Research Laboratory 3071 Washington, D.C. 20375 3072 USA 3074 EMail: adamson@itd.nrl.navy.mil