idnits 2.17.1 draft-ietf-manet-smf-mib-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1381 has weird spacing: '...s state table...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (March 21, 2013) is 4048 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'SMF' is mentioned on line 863, but not defined Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force R. Cole 3 Internet-Draft US Army CERDEC 4 Intended status: Experimental J. Macker 5 Expires: September 22, 2013 B. Adamson 6 Naval Research Laboratory 7 March 21, 2013 9 Definition of Managed Objects for the Manet Simplified Multicast 10 Framework Relay Set Process 11 draft-ietf-manet-smf-mib-07 13 Abstract 15 This memo defines a portion of the Management Information Base (MIB) 16 for use with network management protocols in the Internet community. 17 In particular, it describes objects for configuring aspects of the 18 Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc 19 Networks (MANETs). The SMF-MIB also reports state information, 20 performance metrics, and notifications. In addition to 21 configuration, the additional state and performance information is 22 useful to operators troubleshooting multicast forwarding problems. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on September 22, 2013. 41 Copyright Notice 43 Copyright (c) 2013 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. The Internet-Standard Management Framework . . . . . . . . . . 3 60 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 63 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 65 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 66 5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6 67 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7 68 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7 69 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7 70 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8 71 5.7. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 72 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 73 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 74 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 75 6.3. Relationship to the Future RSSA-MIBs . . . . . . . . . . . 10 76 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 77 8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 78 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 53 79 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 80 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 54 81 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 54 82 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54 83 13.1. Normative References . . . . . . . . . . . . . . . . . . . 54 84 13.2. Informative References . . . . . . . . . . . . . . . . . . 55 85 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 56 87 1. Introduction 89 This memo defines a portion of the Management Information Base (MIB) 90 for use with network management protocols in the Internet community. 91 In particular, it describes objects for configuring aspects of a 92 process implementing Simplified Multicast Forwarding (SMF) [RFC6621] 93 for Mobile Ad-Hoc Networks (MANETs). SMF provides multicast 94 Duplicate Packet Detection (DPD) and supports algorithms for 95 constructing an estimate of a MANET Minimum Connected Dominating Set 96 (MCDS) for efficient multicast forwarding. The SMF-MIB also reports 97 state information, performance metrics, and notifications. In 98 addition to configuration, this additional state and performance 99 information is useful to operators troubleshooting multicast 100 forwarding problems. 102 2. The Internet-Standard Management Framework 104 For a detailed overview of the documents that describe the current 105 Internet-Standard Management Framework, please refer to section 7 of 106 RFC 3410 [RFC3410]. 108 Managed objects are accessed via a virtual information store, termed 109 the Management Information Base or MIB. MIB objects are generally 110 accessed through the Simple Network Management Protocol (SNMP). 111 Objects in the MIB are defined using the mechanisms defined in the 112 Structure of Management Information (SMI). This memo specifies a MIB 113 module that is compliant to the SMIv2, which is described in STD 58, 114 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 115 [RFC2580]. 117 3. Conventions 119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 121 document are to be interpreted as described in RFC 2119 [RFC2119]. 123 4. Overview 125 SMF provides methods for implementing DPD-based multicast forwarding 126 with the optional use of Connected Dominating Set (CDS)-based relay 127 sets. The CDS provides a complete connected coverage of the nodes 128 comprising the MANET. The MCDS is the smallest set of MANET nodes 129 (comprising a connected cluster) which cover all the nodes in the 130 cluster with their transmissions. As the density of the MANET nodes 131 increase, the fraction of nodes required in an MCDS decreases. Using 132 the MCDS as a multicast forwarding set then becomes an efficient 133 multicast mechanism for MANETs. 135 Various algorithms for the construction of estimates of the MCDS 136 exist. The Simplified Multicast Framework [RFC6621] describes some 137 of these. It further defines various operational modes for a node 138 which is participating in the collective creation of the MCDS 139 estimates. These modes depend upon the set of related MANET routing 140 and discovery protocols and mechanisms in operation in the specific 141 MANET node. 143 A SMF router's MIB contains SMF process configuration parameters 144 (e.g. specific CDS algorithm), state information (e.g., current 145 membership in the CDS), performance counters (e.g., packet counters), 146 and notifications. 148 4.1. SMF Management Model 150 This section describes the management model for the SMF node process. 152 Figure 1 (reproduced from Figure 4 of [RFC6621]) shows the 153 relationship between the SMF Relay Set selection algorithm and the 154 related algorithms, processes and protocols running in the MANET 155 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 156 topology information gotten from the MANET Neighborhood Discovery 157 Protocol (NHDP), from the specific MANET routing protocol running on 158 the node, or from Layer 2 information passed up to the higher layer 159 protocol processes. 161 ______________ ____________ 162 | | | | 163 | Neighborhood | | Relay Set | 164 | Discovery |------------->| Selection | 165 | Protocol | neighbor | Algorithm | 166 |______________| info |____________| 167 \ / 168 \ / 169 neighbor\ / forwarding 170 info* \ _____________ / status 171 \ | | / 172 `-->| Forwarding |<--' 173 | Process | 174 ----------------->|_____________|-----------------> 175 incoming packet, forwarded packets 176 interface id*, and 177 previous hop* 179 Figure 1: SMF Node Architecture 181 4.2. Terms 183 The following definitions apply throughout this document: 185 o Configuration Objects - switches, tables, objects which are 186 initialized to default settings or set through the management 187 interface defined by this MIB. 189 o Tunable Configuration Objects - objects whose values affect timing 190 or attempt bounds on the SMF RS process. 192 o State Objects - automatically generated values which define the 193 current operating state of the SMF RS process in the router. 195 o Performance Objects - automatically generated values which help an 196 administrator or automated tool to assess the performance of the 197 CDS multicast process on the router and the overall multicast 198 performance within the MANET routing domain. 200 5. Structure of the MIB Module 202 This section presents the structure of the SMF-MIB module. The 203 objects are arranged into the following groups: 205 o smfMIBNotifications - defines the notifications associated with 206 the SMF-MIB. 208 o smfMIBObjects - defines the objects forming the basis for the SMF- 209 MIB. These objects are divided up by function into the following 210 groups: 212 * Capabilities Group - This group contains the SMF objects that 213 the device uses to advertise its local capabilities with 214 respect to, e.g., the supported RSSAs. 216 * Configuration Group - This group contains the SMF objects that 217 configure specific options that determine the overall operation 218 of the SMF RSSA and the resulting multicast performance. 220 * State Group - Contains information describing the current state 221 of the SMF RSSA process such as the Neighbor Table. 223 * Performance Group - Contains objects which help to characterize 224 the performance of the SMF RSSA process, typically statistics 225 counters. 227 o smfMIBConformance - defines minimal and full conformance of 228 implementations to this SMF-MIB. 230 5.1. Textual Conventions 232 The textual conventions defined within the SMF-MIB are as follows: 234 o The SmfStatus is defined within the SMF-MIB. This contains the 235 current operational status of the SMF process on an interface. 237 o The SmfOpModeID represents an index that identifies a specific SMF 238 operational mode. 240 o The SmfRssaID represents an index that identifies, through 241 reference, a specific RSSA available for operation on the device. 243 5.2. The Capabilities Group 245 The SMF device supports a set of capabilities. The list of 246 capabilities which the device can advertise are: 248 o Operational Mode - topology information from NHDP, CDS-aware 249 unicast routing or Cross-layer from Layer 2. 251 o SMF RSSA - the specific RSSA operational on the device. Note that 252 configuration, state and performance objects related to a specific 253 RSSA must be defined within another separate MIB. 255 5.3. The Configuration Group 257 The SMF device is configured with a set of controls. Some of the 258 prominent configuration controls for the SMF device follow: 260 o Operational Mode - topology information from NHDP, CDS-aware 261 unicast routing or Cross-layer from Layer 2. 263 o SMF RSSA - the specific RSSA operational on the device. 265 o Duplicate Packet detection for IPv4 - Identification-based or 266 Hash-based DPD. 268 o Duplicate Packet detection for IPv6 - Identification-based or 269 Hash-based DPD. 271 o SMF Type Message TLV - if NHDP mode is selected, then is the SMF 272 Type Message TLV may be included in the NHDP exchanges. 274 o SMF Address Block TLV - if NHDP mode is selected, then is the SMF 275 Address Block TLV should be included in the NHDP exchanges. 277 5.4. The State Group 279 The State sub-tree reports current state information, e.g., 281 o Node RSSA State - is the node currently in or out of the Relay 282 Set. 284 o Neighbors Table - a table containing current neighbors and their 285 operational RSSA. 287 5.5. The Performance Group 289 The Performance sub-tree reports primarily counters that relate to 290 SMF RSSA performance. The SMF performance counters consists of per 291 node and per interface objects: 293 o Total multicast packets received. 295 o Total multicast packets forwarded. 297 o Total duplicate multicast packets detected. 299 o Per interface statistics table with the following entries: 301 * Multicast packets received. 303 * Multicast packets forwarded. 305 * Duplicate multicast packets detected. 307 5.6. The Notifications Group 309 The Notifications Sub-tree contains the list of notifications 310 supported within the SMF-MIB and their intended purpose or utility. 312 5.7. Tables and Indexing 314 The SMF-MIB module contains a number of tables which record data 315 related to: 317 o configuration and operation of packet forwarding the local router, 319 o configuration and operation of local MANET interfaces on the 320 router, and 322 o configuration and operation of various RSSA algorithms for packet 323 forwarding. 325 The SMF-MIB module's tables are indexed via the following constructs: 327 o smfOpModeCapabilitiesID - which is the index for each of the SMF 328 modes. 330 o smfRssaCapabilitiesID - which is the index for each of the RSSAs 331 supported by this specific device. 333 o smfConfiguredAddrForwardingAddrType and 334 smfConfiguredAddrForwardingFirstAddr - indexes to multicast 335 addresses which are forwarded by the SMF process. 337 o smfIfIndex - which is the IfIndex of the local router on which SMF 338 is configured. 340 o smfDiscoveredAddrForwardingAddrType and 341 smfDiscoveredAddrForwardingFirstAddr - indexes to discovered 342 multicast addresses which are forwarded by the SMF process. 344 o smfNeighborIpAddrType, smfNeighborIpAddr, and smfNeighborPrefixLen 345 - which is the index set of interface specific neighbor nodes to 346 this SMF device. 348 These tables and their indexing are: 350 o smfOpModeCapabilitiesTable - identifies the resident set of SMF 351 Operational Modes on this router. This table has 'INDEX { 352 smfOpModeCapabilitiesID }. 354 o smfRssaCapabilitiesTable - contains reference to the specific set 355 of RSSAs currently supported on this device. This table has 356 'INDEX { smfRssaCapabilitiesID }'. 358 o smfConfiguredAddrForwardingTable - contains information on 359 multicast addresses which are to be forwarded by the SMF process 360 on this device. This table has 'INDEX { 361 smfConfiguredAddrForwardingAddrType, 362 smfConfiguredAddrForwardingFirstAddr }'. 364 o smfInterfaceTable - describes the SMF interfaces on this device 365 that are participating in the SMF packet forwarding process. This 366 table has 'INDEX { smfIfIndex }'. 368 o smfDiscoveredAddrForwardingTable - contains discovered address for 369 SMF packet forwarding. This table has 'INDEX { 370 smfDiscoveredAddrForwardingAddrType, 371 smfDiscoveredAddrForwardingFirstAddr }'. 373 o smfNeighborTable - describes the current neighbor nodes, their 374 addresses and the SMF RSSA and the interface on which they can be 375 reached. This table has 'INDEX { smfNeighborIpAddrType, 376 smfNeighborIpAddr, smfNeighborPrefixLen }'. 378 o smfIpv4InterfaceTable - contains the IPv4 related SMF statistics 379 per each SMF interface on this device. This table has 'INDEX { 380 smfIfIndex }'. 382 o smfIpv6InterfaceTable - contains the IPv6 related SMF statistics 383 per each SMF interface on this device. This table has 'INDEX { 384 smfIfIndex }'. 386 6. Relationship to Other MIB Modules 388 6.1. Relationship to the SNMPv2-MIB 390 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 391 mandatory for all systems, and the objects apply to the entity as a 392 whole. The 'system' group provides identification of the management 393 entity and certain other system-wide data. The SMF-MIB does not 394 duplicate those objects. 396 6.2. MIB modules required for IMPORTS 398 The textual conventions imported for use in the SMF-MIB are as 399 follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 400 Counter32, Unsigned32, Integer32 and mib-2 textual conventions are 401 imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 402 and TruthValue textual conventions are imported from RFC 2579 403 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- 404 GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 405 InterfaceIndexOrZero textual convention is imported from RFC 2863 406 [RFC2863]. The SnmpAdminString textual convention is imported from 407 RFC 3411 [RFC3411]. The InetAddress, InetAddressType and 408 InetAddressPrefixLength textual conventions are imported from RFC 409 4001 [RFC4001]. 411 6.3. Relationship to the Future RSSA-MIBs 413 In a sense, the SMF-MIB is a general front-end to a set of, yet to be 414 developed, RSSA-specific MIBs. These RSSA-specific MIBs will define 415 the objects for the configuration, state, performance and 416 notification objects required for the operation of these specific 417 RSSAs. The SMF-MIB Capabilities Group allows the remote management 418 station the ability to query the router to discover the set of 419 supported RSSAs. 421 7. Definitions 423 SMF-MIB DEFINITIONS ::= BEGIN 425 IMPORTS 427 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 428 Counter32, Integer32, TimeTicks, experimental 429 FROM SNMPv2-SMI -- [RFC2578] 431 TEXTUAL-CONVENTION, RowStatus, TruthValue, 432 DisplayString 433 FROM SNMPv2-TC -- [RFC2579] 435 MODULE-COMPLIANCE, OBJECT-GROUP, 436 NOTIFICATION-GROUP 437 FROM SNMPv2-CONF -- [RFC2580] 439 InterfaceIndexOrZero 440 FROM IF-MIB -- [RFC2863] 442 SnmpAdminString 443 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 445 InetAddress, InetAddressType, 446 InetAddressPrefixLength 447 FROM INET-ADDRESS-MIB -- [RFC4001] 448 ; 450 smfMIB MODULE-IDENTITY 451 LAST-UPDATED "201303201300Z" -- March 20, 2013 452 ORGANIZATION "IETF MANET Working Group" 453 CONTACT-INFO 454 "WG E-Mail: manet@ietf.org 456 WG Chairs: sratliff@cisco.com 457 jmacker@nrl.navy.mil 459 Editors: Robert G. Cole 460 US Army CERDEC 461 Space and Terrestrial Communications 462 6010 Frankford Road 463 Aberdeen Proving Ground, MD 21005 464 USA 465 +1 443 395-8744 466 robert.g.cole@us.army.mil 468 Joseph Macker 469 Naval Research Laboratory 470 Washington, D.C. 20375 471 USA 472 macker@itd.nrl.navy.mil 474 Brian Adamson 475 Naval Research Laboratory 476 Washington, D.C. 20375 477 USA 478 adamson@itd.nrl.navy.mil" 480 DESCRIPTION 481 "This MIB module contains managed object definitions for 482 the Manet SMF RSSA process defined in: 484 [SMF] Macker, J.(ed.), 485 Simplified Multicast Forwarding, RFC XXXX, 486 July 2012. 488 Copyright (C) The IETF Trust (2012). This version 489 of this MIB module is part of RFC xxxx; see the RFC 490 itself for full legal notices." 492 -- Revision History 493 REVISION "201303201300Z" -- March 20, 2013 494 DESCRIPTION 495 "The first version of this MIB module, 496 published as RFC xxxx. 497 " 498 -- RFC-Editor assigns xxxx 499 ::= { experimental xxxx } -- to be assigned by IANA 501 -- 502 -- TEXTUAL CONVENTIONs 503 -- 505 SmfStatus ::= TEXTUAL-CONVENTION 506 STATUS current 507 DESCRIPTION 508 "An indication of the operability of a SMF 509 function or feature. For example, the status 510 of an interface: 'enabled' indicates that 511 it is performing SMF functions, 512 and 'disabled' indicates that it is not." 513 SYNTAX INTEGER { 514 enabled (1), 515 disabled (2) 516 } 518 SmfOpModeID ::= TEXTUAL-CONVENTION 519 STATUS current 520 DESCRIPTION 521 "An index that identifies through reference to a specific 522 SMF operations mode. There are basically three styles 523 of SMF operation with reduced relay sets: 525 Independent operation - SMF performs its own relay 526 set selection using information from an associated 527 MANET NHDP process. 529 CDS-aware unicast routing operation - a coexistent 530 unicast routing protocol provides dynamic relay 531 set state based upon its own control plane 532 CDS or neighborhood discovery information. 534 Cross-layer operation - SMF operates using 535 neighborhood status and triggers from a 536 cross-layer information base for dynamic relay 537 set selection and maintenance." 538 REFERENCE 539 "Simplified Multicast Forwarding for MANET 540 (SMF), Macker, J., July 2012." 541 SYNTAX INTEGER { 542 independent (1), 543 routing (2), 544 crossLayer (3) 545 -- future (4-255) 546 } 548 SmfRssaID ::= TEXTUAL-CONVENTION 549 STATUS current 550 DESCRIPTION 551 "An index that identifies through reference to a specific 552 RSSA algorithms. Several are currently defined 553 in the appendix of SMF (RFC XXXX)." 554 REFERENCE 555 "Simplified Multicast Forwarding for MANET 556 (SMF), Macker, J., July 2012." 557 SYNTAX INTEGER { 558 cF(1), 559 sMPR(2), 560 eCDS(3), 561 mprCDS(4) 562 -- future(5-127) 563 -- noStdAction(128-239) 564 -- experimental(240-255) 565 } 567 -- 568 -- Top-Level Object Identifier Assignments 569 -- 571 smfMIBNotifications OBJECT IDENTIFIER ::= { smfMIB 0 } 572 smfMIBObjects OBJECT IDENTIFIER ::= { smfMIB 1 } 573 smfMIBConformance OBJECT IDENTIFIER ::= { smfMIB 2 } 575 -- 576 -- smfMIBObjects Assignments: 577 -- smfCapabilitiesGroup - 1 578 -- smfConfigurationGroup - 2 579 -- smfStateGroup - 3 580 -- smfPerformanceGroup - 4 581 -- 583 -- 584 -- smfCapabilitiesGroup 585 -- 586 -- This group contains the SMF objects that identify specific 587 -- capabilities within this device related to SMF functions. 588 -- 590 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 592 -- 593 -- SMF Operational Mode Capabilities Table 594 -- 596 smfOpModeCapabilitiesTable OBJECT-TYPE 597 SYNTAX SEQUENCE OF SmfOpModeCapabilitiesEntry 598 MAX-ACCESS not-accessible 599 STATUS current 600 DESCRIPTION 601 "The smfOpModeCapabilitiesTable identifies the 602 resident set of SMF Operational Modes on this 603 router." 604 REFERENCE 605 "Simplified Multicast Forwarding for MANET 606 (SMF), Macker, J., July 2012." 607 ::= { smfCapabilitiesGroup 1 } 609 smfOpModeCapabilitiesEntry OBJECT-TYPE 610 SYNTAX SmfOpModeCapabilitiesEntry 611 MAX-ACCESS not-accessible 612 STATUS current 613 DESCRIPTION 614 "Information about a particular operational 615 mode. 616 " 617 INDEX { smfOpModeCapabilitiesID } 618 ::= { smfOpModeCapabilitiesTable 1 } 620 SmfOpModeCapabilitiesEntry ::= SEQUENCE { 621 smfOpModeCapabilitiesID SmfOpModeID, 622 smfOpModeCapabilitiesName SnmpAdminString, 623 smfOpModeCapabilitiesReference SnmpAdminString 624 } 626 smfOpModeCapabilitiesID OBJECT-TYPE 627 SYNTAX SmfOpModeID 628 MAX-ACCESS not-accessible 629 STATUS current 630 DESCRIPTION 631 "The index for this entry. This object identifies 632 the particular operational mode for this device." 633 ::= { smfOpModeCapabilitiesEntry 1 } 635 smfOpModeCapabilitiesName OBJECT-TYPE 636 SYNTAX SnmpAdminString 637 MAX-ACCESS read-only 638 STATUS current 639 DESCRIPTION 640 "The textual name of this operational 641 mode. Current operational modes include: 642 Independent Mode, 643 CDS-aware Routing Mode, and 644 Cross-layer Mode. 645 Others may be defined 646 in future revisions of [SMF]." 647 ::= { smfOpModeCapabilitiesEntry 2 } 649 smfOpModeCapabilitiesReference OBJECT-TYPE 650 SYNTAX SnmpAdminString 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "This object contains a reference to the document 655 that defines this operational mode." 656 ::= { smfOpModeCapabilitiesEntry 3 } 658 -- 659 -- SMF RSSA Capabilities Table 660 -- 662 smfRssaCapabilitiesTable OBJECT-TYPE 663 SYNTAX SEQUENCE OF SmfRssaCapabilitiesEntry 664 MAX-ACCESS not-accessible 665 STATUS current 666 DESCRIPTION 667 "The smfRssaCapabilitiesTable contains 668 reference to the specific set of RSSAs 669 currently supported on this device. 670 " 671 REFERENCE 672 "Simplified Multicast Forwarding for MANET 673 (SMF), Macker, J., July 2012." 674 ::= { smfCapabilitiesGroup 2 } 676 smfRssaCapabilitiesEntry OBJECT-TYPE 677 SYNTAX SmfRssaCapabilitiesEntry 678 MAX-ACCESS not-accessible 679 STATUS current 680 DESCRIPTION 681 "Information about a particular RSSA 682 algorithm." 683 INDEX { smfRssaCapabilitiesID } 684 ::= { smfRssaCapabilitiesTable 1 } 686 SmfRssaCapabilitiesEntry ::= SEQUENCE { 687 smfRssaCapabilitiesID SmfRssaID, 688 smfRssaCapabilitiesName SnmpAdminString, 689 smfRssaCapabilitiesReference SnmpAdminString 690 } 692 smfRssaCapabilitiesID OBJECT-TYPE 693 SYNTAX SmfRssaID 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "The index for this entry. This object identifies 698 the particular RSSA algorithm in this MIB 699 module. Example RSSAs are found in the 700 appendix of [SMF]. 702 By default, the agent should support at least the 703 Classical Flooding algorithm. All compliant 704 SMF forwarders must support Classical Flooding. 705 Hence, at least one entry in this table must 706 exist." 707 ::= { smfRssaCapabilitiesEntry 1 } 709 smfRssaCapabilitiesName OBJECT-TYPE 710 SYNTAX SnmpAdminString 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "The textual name of this RSSA algorithm. 715 Currently defined names are: 716 Classical Flooding - cF, 717 Source-based MultiPoint 718 Relay - sMPR, 719 Essential Connecting Dominating 720 Set - eCDS, 721 MultiPoint Relay Connected 722 Dominating Set - mprCDS. 723 " 725 ::= { smfRssaCapabilitiesEntry 2 } 727 smfRssaCapabilitiesReference OBJECT-TYPE 728 SYNTAX SnmpAdminString 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "This object contains a published reference 733 to the document that defines this algorithm. 734 " 735 ::= { smfRssaCapabilitiesEntry 3 } 737 -- 738 -- smfConfigurationGroup 739 -- 740 -- This group contains the SMF objects that configure specific 741 -- options that determine the overall performance and operation 742 -- of the multicast forwarding process for the router device 743 -- and its interfaces. 744 -- 746 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 748 smfAdminStatus OBJECT-TYPE 749 SYNTAX SmfStatus 750 MAX-ACCESS read-write 751 STATUS current 752 DESCRIPTION 753 "The configured status of the SMF process 754 on this device. Enabled(1) means that 755 SMF is configured to run on this device. 756 Disabled(2) mean that the SMF process 757 is configured off. 759 This object is persistent and when written 760 the entity SHOULD save the change to 761 non-volatile storage. 762 " 763 ::= { smfConfigurationGroup 1 } 765 smfRouterIDAddrType OBJECT-TYPE 766 SYNTAX InetAddressType 767 MAX-ACCESS read-write 768 STATUS current 769 DESCRIPTION 770 "The address type of the address used for 771 SMF ID of this router as specified 772 in the 'smfRouterID' next. 774 Only the values ipv4(1) and ipv6(2) 775 are supported. 777 This can be set by the management station, 778 the smfRouterID must be a routable address 779 assigned to this router. If the management 780 station does not assign this value, then the 781 router should choose the highest routable 782 IP address assigned to this router. 784 This object is persistent and when written 785 the entity SHOULD save the change to 786 non-volatile storage." 787 DEFVAL { ipv4 } 788 ::= { smfConfigurationGroup 2 } 790 smfRouterID OBJECT-TYPE 791 SYNTAX InetAddress (SIZE(4|16)) 792 MAX-ACCESS read-write 793 STATUS current 794 DESCRIPTION 795 "The IP address used as the SMF router ID. 796 This can be set by the management station. 797 If not explicitly set, then the device 798 should select a routable IP address 799 assigned to this router for use as 800 the 'smfRouterID'. 802 The smfRouterID is a logical identification 803 that MUST be consistent across interoperable 804 SMF neighborhoods and it is RECOMMENDED to be 805 chosen as the numerically largest address 806 contained in a node's 'Neighbor Address List' 807 as defined in NHDP. A smfRouterID MUST be 808 unique within the scope of the operating 809 MANET network regardless of the method used 810 for selecting it. 812 This object is persistent and when written 813 the entity SHOULD save the change to 814 non-volatile storage." 815 REFERENCE 816 "Simplified Multicast Forwarding for MANET 817 (SMF), Macker, J., July 2012." 819 ::= { smfConfigurationGroup 3 } 821 smfConfiguredOpMode OBJECT-TYPE 822 SYNTAX INTEGER { 823 withNHDP(1), 824 cdsAwareRouting(2), 825 crossLayer(3), 826 other(4) 827 } 828 MAX-ACCESS read-write 829 STATUS current 830 DESCRIPTION 831 "The SMF RSS node operational mode as defined 832 in the TEXTUAL CONVENTION for `SmfOpModeID' 833 and in [SMF].. 835 The value withNHDP(1) indicates Independent 836 Mode of operation. 838 The value cdsAwareRouting(2) indicates 839 CDS-aware Routing Mode of operation. 841 The value crossLayer(3) indicates 842 Cross-layer Mode of operation. 844 The default value for this object is 845 withNHDP(1). 847 This object is persistent and when written 848 the entity SHOULD save the change to 849 non-volatile storage." 850 REFERENCE 851 "Simplified Multicast Forwarding for MANET 852 (SMF), Macker, J., July 2012." 853 DEFVAL { withNHDP } 854 ::= { smfConfigurationGroup 4 } 856 smfConfiguredRssa OBJECT-TYPE 857 SYNTAX SmfRssaID 858 MAX-ACCESS read-write 859 STATUS current 860 DESCRIPTION 861 "The SMF RSS currently operational algorithm 862 as defined in the TEXTUAL CONVENTION for 863 `SmfRssaID' and in [SMF]. 865 The deflaut value for this object is 866 cF(1), i.e., Classical Flooding. 868 This object is persistent and when written 869 the entity SHOULD save the change to 870 non-volatile storage." 871 REFERENCE 872 "Simplified Multicast Forwarding for MANET 873 (SMF), Macker, J., July 2012." 874 DEFVAL { cF } 875 ::= { smfConfigurationGroup 5 } 877 smfRssaMember OBJECT-TYPE 878 SYNTAX INTEGER { 879 potential(1), 880 always(2), 881 never(3) 882 } 883 MAX-ACCESS read-write 884 STATUS current 885 DESCRIPTION 886 "The RSSA downselects a set of forwarders for 887 multicast forwarding. Sometimes it is useful 888 to force an agent to be included or excluded 889 from the resulting RSS. This object is a 890 switch to allow for this behavior. 892 The value potential(1) allows the selected 893 RSSA to determine if this agent is included 894 or excluded from the RSS. 896 The value always(1) forces the selected 897 RSSA include this agent in the RSS. 899 The value never(3) forces the selected 900 RSSA to exclude this agent from the RSS. 902 The default setting for this object is 903 'potential(1)'. Other settings could pose 904 operational risks under certain conditions. 906 This object is persistent and when written 907 the entity SHOULD save the change to 908 non-volatile storage." 909 REFERENCE 910 "Simplified Multicast Forwarding for MANET 911 (SMF), Macker, J., July 2012." 912 DEFVAL { potential } 913 ::= { smfConfigurationGroup 6 } 914 smfIpv4Dpd OBJECT-TYPE 915 SYNTAX INTEGER { 916 hashBased(1), 917 identificationBased(2) 918 } 919 MAX-ACCESS read-write 920 STATUS current 921 DESCRIPTION 922 "The current method for IPv4 duplicate packet 923 detection. 925 The value hashBased(1) indicates that the 926 routers duplicate packet detection is based 927 upon comparing a hash over the packet fields. 928 This is the default setting for this object. 930 The value identificationBased(2) 931 indicates that the duplicate packet 932 detection relies upon header information 933 in the multicast packets to identify 934 previously received packets. 936 This object is persistent and when written 937 the entity SHOULD save the change to 938 non-volatile storage." 939 REFERENCE 940 "Simplified Multicast Forwarding for MANET 941 (SMF), Macker, J., July 2012." 942 DEFVAL { hashBased } 943 ::= { smfConfigurationGroup 7 } 945 smfIpv6Dpd OBJECT-TYPE 946 SYNTAX INTEGER { 947 hashBased(1), 948 identificationBased(2) 949 } 950 MAX-ACCESS read-write 951 STATUS current 952 DESCRIPTION 953 "The current method for IPv6 duplicate packet 954 detection. 956 The values indicate the type of method used 957 for duplicate packet detection as described 958 the previous description for the object 959 `smfIpv4Dpd'. 961 The default value for this object is 962 hashBased(1). 964 This object is persistent and when written 965 the entity SHOULD save the change to 966 non-volatile storage." 967 REFERENCE 968 "Simplified Multicast Forwarding for MANET 969 (SMF), Macker, J., July 2012." 970 DEFVAL { hashBased } 971 ::= { smfConfigurationGroup 8 } 973 smfMaxPktLifetime OBJECT-TYPE 974 SYNTAX Integer32 (0..65535) 975 UNITS "Seconds" 976 MAX-ACCESS read-write 977 STATUS current 978 DESCRIPTION 979 "The estimate of the network packet 980 traversal time. 982 This object is persistent and when written 983 the entity SHOULD save the change to 984 non-volatile storage." 985 REFERENCE 986 "Simplified Multicast Forwarding for MANET 987 (SMF), Macker, J., July 2012." 988 DEFVAL { 60 } 989 ::= { smfConfigurationGroup 9 } 991 smfDpdMaxMemorySize OBJECT-TYPE 992 SYNTAX Integer32 (0..65535) 993 UNITS "Kilo-Bytes" 994 MAX-ACCESS read-write 995 STATUS current 996 DESCRIPTION 997 "The locally reserved memory for storage 998 of cached DPD records for both IPv4 and 999 IPv6 methods. 1001 The local SMF device should protect itself 1002 against the SNMP manager from requesting 1003 too large a memory value. If this is the case, 1004 an error indication should be returned in response 1005 to the SNMP SET request. 1007 This object is persistent and when written 1008 the entity SHOULD save the change to 1009 non-volatile storage." 1011 REFERENCE 1012 "Simplified Multicast Forwarding for MANET 1013 (SMF), Macker, J., July 2012." 1014 DEFVAL { 1024 } 1015 ::= { smfConfigurationGroup 10 } 1017 smfDpdEntryMaxLifetime OBJECT-TYPE 1018 SYNTAX Integer32 (0..65525) 1019 UNITS "Seconds" 1020 MAX-ACCESS read-write 1021 STATUS current 1022 DESCRIPTION 1023 "The maximum lifetime of a cached DPD 1024 record in the local device storage. 1026 If the memory is running low prior to the 1027 MaxLifetimes being exceeded, the local SMF 1028 devices should purge the oldest records first. 1030 This object is persistent and when written 1031 the entity SHOULD save the change to 1032 non-volatile storage." 1033 REFERENCE 1034 "Simplified Multicast Forwarding for MANET 1035 (SMF), Macker, J., July 2012." 1036 DEFVAL { 600 } 1037 ::= { smfConfigurationGroup 11 } 1039 -- 1040 -- Configuration of messages to be included in 1041 -- NHDP message exchanges in support of SMF 1042 -- operations. 1043 -- 1045 smfNhdpRssaMesgTLVIncluded OBJECT-TYPE 1046 SYNTAX TruthValue 1047 MAX-ACCESS read-write 1048 STATUS current 1049 DESCRIPTION 1050 "Indicates whether the associated NHDP messages 1051 include the RSSA Message TLV, or not. This 1052 is an optional SMF operational setting. 1053 The value true(1) indicates that this TLV is 1054 included; the value false(2) indicates that it 1055 is not included. 1057 It is RECOMMENDED that the RSSA Message TLV 1058 be included in the NHDP messages. 1060 This object is persistent and when written 1061 the entity SHOULD save the change to 1062 non-volatile storage." 1063 REFERENCE 1064 "Simplified Multicast Forwarding for MANET 1065 (SMF), Macker, J., July 2012." 1066 DEFVAL { true } 1067 ::= { smfConfigurationGroup 12 } 1069 smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 1070 SYNTAX TruthValue 1071 MAX-ACCESS read-write 1072 STATUS current 1073 DESCRIPTION 1074 "Indicates whether the associated NHDP messages 1075 include the RSSA Address Block TLV, or not. 1076 This is an optional SMF operational setting. 1077 The value true(1) indicates that this TLV is 1078 included; the value false(2) indicates that it 1079 is not included. 1081 The smfNhdpRssaAddrBlockTLVIncluded is optional 1082 in all cases as it depends on the existence of 1083 an address block which may not be present. 1084 If this SMF device is configured with NHDP, 1085 then this object should be set to 'true(1)'. 1087 This object is persistent and when written 1088 the entity SHOULD save the change to 1089 non-volatile storage." 1090 REFERENCE 1091 "Simplified Multicast Forwarding for MANET 1092 (SMF), Macker, J., July 2012." 1093 DEFVAL { true } 1094 ::= { smfConfigurationGroup 13 } 1096 -- 1097 -- Table identifying configured multicast addresses to be forwarded. 1098 -- 1100 smfConfiguredAddrForwardingTable OBJECT-TYPE 1101 SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry 1102 MAX-ACCESS not-accessible 1103 STATUS current 1104 DESCRIPTION 1105 "The (conceptual) table containing information on multicast 1106 addresses which are to be forwarded by the SMF process. 1108 Entries in this table are configured. As well, addresses 1109 to be forwarded by the SMF device can be dynamically 1110 discovered by other means. The corresponding state 1111 table, smfDiscoveredAddrForwardingTable, contains 1112 these additional, dynamically discovered address for 1113 forwarding. 1115 Each row is associated with a range of multicast 1116 addresses, and ranges for different rows must be disjoint. 1118 The objects in this table are persistent and when written 1119 the entity SHOULD save the change to 1120 non-volatile storage." 1121 REFERENCE 1122 "Simplified Multicast Forwarding for MANET 1123 (SMF), Macker, J., July 2012." 1124 ::= { smfConfigurationGroup 15 } 1126 smfConfiguredAddrForwardingEntry OBJECT-TYPE 1127 SYNTAX SmfConfiguredAddrForwardingEntry 1128 MAX-ACCESS not-accessible 1129 STATUS current 1130 DESCRIPTION 1131 "An entry (conceptual row) containing the information on a 1132 particular multicast scope." 1133 INDEX { smfConfiguredAddrForwardingAddrType, 1134 smfConfiguredAddrForwardingFirstAddr } 1135 ::= { smfConfiguredAddrForwardingTable 1 } 1137 SmfConfiguredAddrForwardingEntry ::= SEQUENCE { 1138 smfConfiguredAddrForwardingAddrType InetAddressType, 1139 smfConfiguredAddrForwardingFirstAddr InetAddress, 1140 smfConfiguredAddrForwardingLastAddr InetAddress, 1141 smfConfiguredAddrForwardingStatus RowStatus 1142 } 1144 smfConfiguredAddrForwardingAddrType OBJECT-TYPE 1145 SYNTAX InetAddressType 1146 MAX-ACCESS not-accessible 1147 STATUS current 1148 DESCRIPTION 1149 "The type of the addresses in the multicast forwarding 1150 range. Legal values correspond to the subset of 1151 address families for which multicast address allocation 1152 is supported. 1154 Only the values ipv4(1) and 1155 ipv6(2) are supported." 1156 ::= { smfConfiguredAddrForwardingEntry 1 } 1158 smfConfiguredAddrForwardingFirstAddr OBJECT-TYPE 1159 SYNTAX InetAddress (SIZE(4|16)) 1160 MAX-ACCESS not-accessible 1161 STATUS current 1162 DESCRIPTION 1163 "The first address in the multicast scope range. The type 1164 of this address is determined by the value of the 1165 smfConfiguredAddrForwardingAddrType object." 1166 ::= { smfConfiguredAddrForwardingEntry 2 } 1168 smfConfiguredAddrForwardingLastAddr OBJECT-TYPE 1169 SYNTAX InetAddress (SIZE(4|16)) 1170 MAX-ACCESS read-create 1171 STATUS current 1172 DESCRIPTION 1173 "The last address in the multicast scope range. 1174 The type of this address is determined by the 1175 value of the smfConfiguredAddrForwardingAddrType 1176 object." 1177 ::= { smfConfiguredAddrForwardingEntry 3 } 1179 smfConfiguredAddrForwardingStatus OBJECT-TYPE 1180 SYNTAX RowStatus 1181 MAX-ACCESS read-create 1182 STATUS current 1183 DESCRIPTION 1184 "The status of this row, by which new entries may be 1185 created, or old entries deleted from this table. If write 1186 access is supported, the other writable objects in this 1187 table may be modified even while the status is `active'." 1188 ::= { smfConfiguredAddrForwardingEntry 4 } 1190 -- 1191 -- SMF Interfaces Configuration Table 1192 -- 1194 smfInterfaceTable OBJECT-TYPE 1195 SYNTAX SEQUENCE OF SmfInterfaceEntry 1196 MAX-ACCESS not-accessible 1197 STATUS current 1198 DESCRIPTION 1199 "The SMF Interface Table describes the SMF 1200 interfaces that are participating in the 1201 SMF packet forwarding process. The ifIndex is 1202 from the interfaces group defined in the 1203 Interfaces Group MIB (RFC 2863). As such, 1204 this table 'sparse augments' the ifTable 1205 specifically when SMF is to be configured to 1206 operate over this interface. 1208 A conceptual row in this table exists if and only 1209 if either a manager has explicitly created the row 1210 or there is an interface on the managed device 1211 that supports and runs SMF. 1213 The manager can create a row by setting 1214 rowStatus to 'createAndGo' or 'createAndWait'. 1215 Row objects having associated DEFVAL clauses are 1216 automatically defined by the agent with these 1217 values during row creation, unless the manager 1218 explicitly defines these object values during the 1219 row creation. 1221 If the corresponding entry with ifIndex value 1222 is deleted from the Interface Table, then the entry 1223 in this table is automatically deleted and 1224 SMF is disabled on this interface, 1225 and all configuration and state information 1226 related to this interface is to be removed 1227 from memory." 1228 REFERENCE 1229 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1230 K., and F. Kastenholtz, June 2000." 1231 ::= { smfConfigurationGroup 16 } 1233 smfInterfaceEntry OBJECT-TYPE 1234 SYNTAX SmfInterfaceEntry 1235 MAX-ACCESS not-accessible 1236 STATUS current 1237 DESCRIPTION 1238 "The SMF interface entry describes one SMF 1239 interface as indexed by its ifIndex. 1241 The objects in this table are persistent and when 1242 written the device SHOULD save the change to 1243 non-volatile storage. For further information 1244 on the storage behavior for these objects, refer 1245 to the description for the smfIfRowStatus 1246 object." 1247 INDEX { smfIfIndex } 1248 ::= { smfInterfaceTable 1 } 1250 SmfInterfaceEntry ::= 1251 SEQUENCE { 1252 smfIfIndex InterfaceIndexOrZero, 1253 smfIfName DisplayString, 1254 smfIfAdminStatus SmfStatus, 1255 smfIfRowStatus RowStatus 1256 } 1258 smfIfIndex OBJECT-TYPE 1259 SYNTAX InterfaceIndexOrZero 1260 MAX-ACCESS not-accessible 1261 STATUS current 1262 DESCRIPTION 1263 "The ifIndex for this SMF interface. This value 1264 MUST correspond to an ifIndex referring 1265 to a valid entry in The Interfaces Table." 1266 REFERENCE 1267 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1268 K., and F. Kastenholtz, June 2000." 1269 ::= { smfInterfaceEntry 1 } 1271 smfIfName OBJECT-TYPE 1272 SYNTAX DisplayString 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "The textual name of the interface. The value of this 1277 object should be the name of the interface as assigned by 1278 the local device and should be suitable for use in commands 1279 entered at the device's `console'. This might be a text 1280 name, such as `le0' or a simple port number, such as `1', 1281 depending on the interface naming syntax of the device. 1283 If there is no local name, or this object is otherwise not 1284 applicable, then this object contains a zero-length string." 1285 ::= { smfInterfaceEntry 2 } 1287 smfIfAdminStatus OBJECT-TYPE 1288 SYNTAX SmfStatus 1289 MAX-ACCESS read-create 1290 STATUS current 1291 DESCRIPTION 1292 "The SMF interface's administrative status. 1293 The value 'enabled' denotes that the interface 1294 is running the SMF forwarding process. 1295 The value 'disabled' denotes that the interface is 1296 external to the SMF forwarding process. 1297 " 1298 ::= { smfInterfaceEntry 3 } 1300 smfIfRowStatus OBJECT-TYPE 1301 SYNTAX RowStatus 1302 MAX-ACCESS read-create 1303 STATUS current 1304 DESCRIPTION 1305 "This object permits management of the table 1306 by facilitating actions such as row creation, 1307 construction, and destruction. The value of 1308 this object has no effect on whether other 1309 objects in this conceptual row can be 1310 modified. 1312 An entry may not exist in the active(1) state unless all 1313 objects in the entry have a defined appropriate value. For 1314 objects with DEFVAL clauses, the management station 1315 does not need to specify the value of this object in order 1316 for the row to transit to the active(1) state; the default 1317 value for this object is used. For objects that do not 1318 have DEFVAL clauses, then the network manager MUST 1319 specify the value of this object prior to this row 1320 transitioning to the active(1) state. 1322 When this object transitions to active(1), all objects 1323 in this row SHOULD be written to non-volatile (stable) 1324 storage. Read-create objects in this row MAY be modified. 1325 When an object in a row with smfIfRowStatus of active(1) 1326 is changed, then the updated value MUST be reflected in SMF 1327 and this new object value MUST be written to non-volatile 1328 storage. 1330 If this object is not equal to active(1), all associated 1331 entries in the smfIpv4InterfaceperfTable and the 1332 smfIpv6InterfacePerfTable MUST be deleted." 1333 ::= { smfInterfaceEntry 4 } 1335 -- 1336 -- smfStateGroup 1337 -- 1338 -- Contains information describing the current state of the SMF 1339 -- process such as the current inclusion in the RS or not. 1340 -- 1341 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1343 smfNodeRsStatusIncluded OBJECT-TYPE 1344 SYNTAX TruthValue 1345 MAX-ACCESS read-only 1346 STATUS current 1347 DESCRIPTION 1348 "The current status of the SMF node in the context of 1349 the MANETs relay set. A value of true(1) indicates 1350 that the node is currently part of the MANET Relay 1351 Set. A value of false(2) indicates that the node 1352 is currently not part of the MANET Relay Set." 1353 REFERENCE 1354 "Simplified Multicast Forwarding for MANET 1355 (SMF), Macker, J., July 2012." 1356 ::= { smfStateGroup 1 } 1358 smfDpdMemoryOverflow OBJECT-TYPE 1359 SYNTAX Counter32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "The number of times that the memory for caching 1364 records for DPD overran and records had to be flushed. 1365 The number of records to be flushed upon a buffer 1366 overflow is an implementation specific decision." 1367 REFERENCE 1368 "Simplified Multicast Forwarding for MANET 1369 (SMF), Macker, J., July 2012." 1370 ::= { smfStateGroup 2 } 1372 -- 1373 -- Dynamically Discovered Multicast Addr Table 1374 -- 1376 smfDiscoveredAddrForwardingTable OBJECT-TYPE 1377 SYNTAX SEQUENCE OF SmfDiscoveredAddrForwardingEntry 1378 MAX-ACCESS not-accessible 1379 STATUS current 1380 DESCRIPTION 1381 "This state table, smfDiscoveredAddrForwardingTable 1382 contains additional, dynamically discovered address 1383 for forwarding. 1385 Each row is associated with a range of 1386 multicast addresses, and ranges for different rows 1387 must be disjoint." 1388 REFERENCE 1389 "Simplified Multicast Forwarding for MANET 1390 (SMF), Macker, J., July 2012." 1391 ::= { smfStateGroup 3 } 1393 smfDiscoveredAddrForwardingEntry OBJECT-TYPE 1394 SYNTAX SmfDiscoveredAddrForwardingEntry 1395 MAX-ACCESS not-accessible 1396 STATUS current 1397 DESCRIPTION 1398 "An entry (conceptual row) containing the information on a 1399 particular multicast scope." 1400 INDEX { smfDiscoveredAddrForwardingAddrType, 1401 smfDiscoveredAddrForwardingFirstAddr } 1402 ::= { smfDiscoveredAddrForwardingTable 1 } 1404 SmfDiscoveredAddrForwardingEntry ::= SEQUENCE { 1405 smfDiscoveredAddrForwardingAddrType InetAddressType, 1406 smfDiscoveredAddrForwardingFirstAddr InetAddress, 1407 smfDiscoveredAddrForwardingLastAddr InetAddress 1408 } 1410 smfDiscoveredAddrForwardingAddrType OBJECT-TYPE 1411 SYNTAX InetAddressType 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION 1415 "The type of the addresses in the multicast forwarding 1416 range. Legal values correspond to the subset of 1417 address families for which multicast address allocation 1418 is supported. 1420 Only the values ipv4(1) and 1421 ipv6(2) are supported." 1422 ::= { smfDiscoveredAddrForwardingEntry 1 } 1424 smfDiscoveredAddrForwardingFirstAddr OBJECT-TYPE 1425 SYNTAX InetAddress (SIZE(4|16)) 1426 MAX-ACCESS not-accessible 1427 STATUS current 1428 DESCRIPTION 1429 "The first address in the multicast scope range. The type 1430 of this address is determined by the value of the 1431 smfConfiguredAddrForwardingAddrType object." 1432 ::= { smfDiscoveredAddrForwardingEntry 2 } 1434 smfDiscoveredAddrForwardingLastAddr OBJECT-TYPE 1435 SYNTAX InetAddress (SIZE(4|16)) 1436 MAX-ACCESS read-create 1437 STATUS current 1438 DESCRIPTION 1439 "The last address in the multicast scope range. 1440 The type of this address is determined by the 1441 value of the smfConfiguredAddrForwardingAddrType 1442 object." 1443 ::= { smfDiscoveredAddrForwardingEntry 3 } 1445 -- 1446 -- SMF Neighbor Table 1447 -- 1449 smfNeighborTable OBJECT-TYPE 1450 SYNTAX SEQUENCE OF SmfNeighborEntry 1451 MAX-ACCESS not-accessible 1452 STATUS current 1453 DESCRIPTION 1454 "The SMF NeighborTable describes the 1455 current neighbor nodes, their address 1456 and SMF RSSA and the interface on which 1457 they can be reached." 1458 REFERENCE 1459 "Simplified Multicast Forwarding for MANET 1460 (SMF), Macker, J., July 2012. 1461 Section 7: SMF Neighborhood Discovery 1462 Requirements." 1463 ::= { smfStateGroup 4 } 1465 smfNeighborEntry OBJECT-TYPE 1466 SYNTAX SmfNeighborEntry 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 { smfNeighborIpAddrType, 1475 smfNeighborIpAddr, 1476 smfNeighborPrefixLen } 1477 ::= { smfNeighborTable 1 } 1479 SmfNeighborEntry ::= 1480 SEQUENCE { 1481 smfNeighborIpAddrType InetAddressType, 1482 smfNeighborIpAddr InetAddress, 1483 smfNeighborPrefixLen InetAddressPrefixLength, 1484 smfNeighborRSSA SmfRssaID, 1485 smfNeighborNextHopInterface InterfaceIndexOrZero 1486 } 1488 smfNeighborIpAddrType OBJECT-TYPE 1489 SYNTAX InetAddressType 1490 MAX-ACCESS not-accessible 1491 STATUS current 1492 DESCRIPTION 1493 "The neighbor IP address type. 1495 Only the values ipv4(1) and 1496 ipv6(2) are supported." 1497 ::= { smfNeighborEntry 1 } 1499 smfNeighborIpAddr OBJECT-TYPE 1500 SYNTAX InetAddress (SIZE(4|16)) 1501 MAX-ACCESS not-accessible 1502 STATUS current 1503 DESCRIPTION 1504 "The neighbor Inet IPv4 or IPv6 address." 1505 ::= { smfNeighborEntry 2 } 1507 smfNeighborPrefixLen OBJECT-TYPE 1508 SYNTAX InetAddressPrefixLength 1509 MAX-ACCESS not-accessible 1510 STATUS current 1511 DESCRIPTION 1512 "The prefix length. This is a decimal value that 1513 indicates the number of contiguous, higher-order 1514 bits of the address that make up the network 1515 portion of the address." 1516 ::= { smfNeighborEntry 3 } 1518 smfNeighborRSSA OBJECT-TYPE 1519 SYNTAX SmfRssaID 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "The current RSSA running on the neighbor. 1524 The list is identical to that described 1525 above for the smfRssa object." 1526 ::= { smfNeighborEntry 4 } 1528 smfNeighborNextHopInterface OBJECT-TYPE 1529 SYNTAX InterfaceIndexOrZero 1530 MAX-ACCESS read-only 1531 STATUS current 1532 DESCRIPTION 1533 "The interface ifIndex over which the 1534 neighbor is reachable in one-hop." 1535 ::= { smfNeighborEntry 5 } 1537 -- 1538 -- SMF Performance Group 1539 -- 1540 -- Contains objects which help to characterize the 1541 -- performance of the SMF RSSA process, such as statistics 1542 -- counters. There are two types of SMF RSSA statistics: 1543 -- global counters and per interface counters. 1544 -- 1546 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1548 smfGlobalPerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1550 -- 1551 -- IPv4 packet counters 1552 -- 1554 smfIpv4MultiPktsRecvTotal OBJECT-TYPE 1555 SYNTAX Counter32 1556 MAX-ACCESS read-only 1557 STATUS current 1558 DESCRIPTION 1559 "A counter of the total number of 1560 multicast IPv4 packets received by the 1561 device." 1562 REFERENCE 1563 "Simplified Multicast Forwarding for MANET 1564 (SMF), Macker, J., July 2012." 1565 ::= { smfGlobalPerfGroup 1 } 1567 smfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1568 SYNTAX Counter32 1569 MAX-ACCESS read-only 1570 STATUS current 1571 DESCRIPTION 1572 "A counter of the total number of 1573 multicast IPv4 packets forwarded by the 1574 device." 1576 REFERENCE 1577 "Simplified Multicast Forwarding for MANET 1578 (SMF), Macker, J., July 2012." 1579 ::= { smfGlobalPerfGroup 2 } 1581 smfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1582 SYNTAX Counter32 1583 MAX-ACCESS read-only 1584 STATUS current 1585 DESCRIPTION 1586 "A counter of the total number of duplicate 1587 multicast IPv4 packets detected by the 1588 device." 1589 REFERENCE 1590 "Simplified Multicast Forwarding for MANET 1591 (SMF), Macker, J., July 2012." 1592 ::= { smfGlobalPerfGroup 3 } 1594 smfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1595 SYNTAX Counter32 1596 MAX-ACCESS read-only 1597 STATUS current 1598 DESCRIPTION 1599 "A counter of the total number of dropped 1600 multicast IPv4 packets by the 1601 device due to TTL exceeded." 1602 REFERENCE 1603 "Simplified Multicast Forwarding for MANET 1604 (SMF), Macker, J., July 2012." 1605 ::= { smfGlobalPerfGroup 4 } 1607 smfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1608 SYNTAX Counter32 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "A counter of the total number of IPv4 packets 1613 recieved which have a TTL larger than that 1614 of a previously received identical packet." 1615 REFERENCE 1616 "Simplified Multicast Forwarding for MANET 1617 (SMF), Macker, J., July 2012." 1618 ::= { smfGlobalPerfGroup 5 } 1620 -- 1621 -- IPv6 packet counters 1622 -- 1623 smfIpv6MultiPktsRecvTotal OBJECT-TYPE 1624 SYNTAX Counter32 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "A counter of the total number of 1629 multicast IPv6 packets received by the 1630 device." 1631 REFERENCE 1632 "Simplified Multicast Forwarding for MANET 1633 (SMF), Macker, J., July 2012." 1634 ::= { smfGlobalPerfGroup 6 } 1636 smfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1637 SYNTAX Counter32 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "A counter of the total number of 1642 multicast IPv6 packets forwarded by the 1643 device." 1644 REFERENCE 1645 "Simplified Multicast Forwarding for MANET 1646 (SMF), Macker, J., July 2012." 1647 ::= { smfGlobalPerfGroup 7 } 1649 smfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1650 SYNTAX Counter32 1651 MAX-ACCESS read-only 1652 STATUS current 1653 DESCRIPTION 1654 "A counter of the total number of duplicate 1655 multicast IPv6 packets detected by the 1656 device." 1657 REFERENCE 1658 "Simplified Multicast Forwarding for MANET 1659 (SMF), Macker, J., July 2012." 1660 ::= { smfGlobalPerfGroup 8 } 1662 smfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1663 SYNTAX Counter32 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "A counter of the total number of dropped 1668 multicast IPv6 packets by the 1669 device due to TTL exceeded." 1670 REFERENCE 1671 "Simplified Multicast Forwarding for MANET 1672 (SMF), Macker, J., July 2012." 1673 ::= { smfGlobalPerfGroup 9 } 1675 smfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1676 SYNTAX Counter32 1677 MAX-ACCESS read-only 1678 STATUS current 1679 DESCRIPTION 1680 "A counter of the total number of IPv6 packets 1681 recieved which have a TTL larger than that 1682 of a previously recived identical packet." 1683 REFERENCE 1684 "Simplified Multicast Forwarding for MANET 1685 (SMF), Macker, J., July 2012." 1686 ::= { smfGlobalPerfGroup 10 } 1688 smfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1689 SYNTAX Counter32 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "A counter of the total number of IPv6 packets 1694 recieved which required the HAV assist for DPD." 1695 REFERENCE 1696 "Simplified Multicast Forwarding for MANET 1697 (SMF), Macker, J., July 2012." 1698 ::= { smfGlobalPerfGroup 11 } 1700 smfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1701 SYNTAX Counter32 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "A counter of the total number of IPv6 packets 1706 recieved which the device inserted the 1707 DPD header option." 1708 REFERENCE 1709 "Simplified Multicast Forwarding for MANET 1710 (SMF), Macker, J., July 2012." 1711 ::= { smfGlobalPerfGroup 12 } 1713 -- 1714 -- Per SMF Interface Performance Table 1715 -- 1717 smfInterfacePerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1718 smfIpv4InterfacePerfTable OBJECT-TYPE 1719 SYNTAX SEQUENCE OF SmfIpv4InterfacePerfEntry 1720 MAX-ACCESS not-accessible 1721 STATUS current 1722 DESCRIPTION 1723 "The SMF Interface Performance Table 1724 describes the SMF statistics per 1725 interface." 1726 REFERENCE 1727 "Simplified Multicast Forwarding for MANET 1728 (SMF), Macker, J., July 2012." 1729 ::= { smfInterfacePerfGroup 1 } 1731 smfIpv4InterfacePerfEntry OBJECT-TYPE 1732 SYNTAX SmfIpv4InterfacePerfEntry 1733 MAX-ACCESS not-accessible 1734 STATUS current 1735 DESCRIPTION 1736 "The SMF Interface Performance entry 1737 describes the statistics for a particular 1738 node interface." 1739 INDEX { smfIfIndex } 1740 ::= { smfIpv4InterfacePerfTable 1 } 1742 SmfIpv4InterfacePerfEntry ::= 1743 SEQUENCE { 1744 smfIpv4MultiPktsRecvPerIf Counter32, 1745 smfIpv4MultiPktsForwardedPerIf Counter32, 1746 smfIpv4DuplMultiPktsDetectedPerIf Counter32, 1747 smfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1748 smfIpv4TTLLargerThanPreviousPerIf Counter32 1749 } 1751 smfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1752 SYNTAX Counter32 1753 MAX-ACCESS read-only 1754 STATUS current 1755 DESCRIPTION 1756 "A counter of the number of 1757 multicast IP packets received by the 1758 device on this interface." 1759 ::= { smfIpv4InterfacePerfEntry 1 } 1761 smfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1762 SYNTAX Counter32 1763 MAX-ACCESS read-only 1764 STATUS current 1765 DESCRIPTION 1766 "A counter of the number of 1767 multicast IP packets forwarded by the 1768 device on this interface." 1769 ::= { smfIpv4InterfacePerfEntry 2 } 1771 smfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1772 SYNTAX Counter32 1773 MAX-ACCESS read-only 1774 STATUS current 1775 DESCRIPTION 1776 "A counter of the number of duplicate 1777 multicast IP packets detected by the 1778 device on this interface." 1779 ::= { smfIpv4InterfacePerfEntry 3 } 1781 smfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1782 SYNTAX Counter32 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "A counter of the total number of dropped 1787 multicast IPv4 packets by the 1788 device due to TTL exceeded." 1789 ::= { smfIpv4InterfacePerfEntry 4 } 1791 smfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1792 SYNTAX Counter32 1793 MAX-ACCESS read-only 1794 STATUS current 1795 DESCRIPTION 1796 "A counter of the total number of IPv4 packets 1797 recieved which have a TTL larger than that 1798 of a previously recived identical packet. 1799 " 1800 ::= { smfIpv4InterfacePerfEntry 5 } 1802 smfIpv6InterfacePerfTable OBJECT-TYPE 1803 SYNTAX SEQUENCE OF SmfIpv6InterfacePerfEntry 1804 MAX-ACCESS not-accessible 1805 STATUS current 1806 DESCRIPTION 1807 "The SMF Interface Performance Table 1808 describes the SMF statistics per 1809 interface." 1810 REFERENCE 1811 "Simplified Multicast Forwarding for MANET 1812 (SMF), Macker, J., July 2012." 1814 ::= { smfInterfacePerfGroup 2 } 1816 smfIpv6InterfacePerfEntry OBJECT-TYPE 1817 SYNTAX SmfIpv6InterfacePerfEntry 1818 MAX-ACCESS not-accessible 1819 STATUS current 1820 DESCRIPTION 1821 "The SMF Interface Performance entry 1822 describes the statistics for a particular 1823 node interface." 1824 INDEX { smfIfIndex } 1825 ::= { smfIpv6InterfacePerfTable 1 } 1827 SmfIpv6InterfacePerfEntry ::= 1828 SEQUENCE { 1829 smfIpv6MultiPktsRecvPerIf Counter32, 1830 smfIpv6MultiPktsForwardedPerIf Counter32, 1831 smfIpv6DuplMultiPktsDetectedPerIf Counter32, 1832 smfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1833 smfIpv6TTLLargerThanPreviousPerIf Counter32, 1834 smfIpv6HAVAssistsReqdPerIf Counter32, 1835 smfIpv6DpdHeaderInsertionsPerIf Counter32 1836 } 1838 smfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1839 SYNTAX Counter32 1840 MAX-ACCESS read-only 1841 STATUS current 1842 DESCRIPTION 1843 "A counter of the number of 1844 multicast IP packets received by the 1845 device on this interface." 1846 ::= { smfIpv6InterfacePerfEntry 1 } 1848 smfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 1849 SYNTAX Counter32 1850 MAX-ACCESS read-only 1851 STATUS current 1852 DESCRIPTION 1853 "A counter of the number of 1854 multicast IP packets forwarded by the 1855 device on this interface." 1856 ::= { smfIpv6InterfacePerfEntry 2 } 1858 smfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 1859 SYNTAX Counter32 1860 MAX-ACCESS read-only 1861 STATUS current 1862 DESCRIPTION 1863 "A counter of the number of duplicate 1864 multicast IP packets detected by the 1865 device on this interface." 1866 ::= { smfIpv6InterfacePerfEntry 3 } 1868 smfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1869 SYNTAX Counter32 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "A counter of the number of dropped 1874 multicast IP packets by the 1875 device on this interface due to TTL 1876 exceeded." 1877 ::= { smfIpv6InterfacePerfEntry 4 } 1879 smfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 1880 SYNTAX Counter32 1881 MAX-ACCESS read-only 1882 STATUS current 1883 DESCRIPTION 1884 "A counter of the total number of IPv6 packets 1885 recieved which have a TTL larger than that 1886 of a previously recived identical packet." 1887 ::= { smfIpv6InterfacePerfEntry 5 } 1889 smfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 1890 SYNTAX Counter32 1891 MAX-ACCESS read-only 1892 STATUS current 1893 DESCRIPTION 1894 "A counter of the total number of IPv6 packets 1895 recieved which required the HAV assist for DPD." 1896 ::= { smfIpv6InterfacePerfEntry 6 } 1898 smfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 1899 SYNTAX Counter32 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "A counter of the total number of IPv6 packets 1904 recieved which the device inserted the 1905 DPD header option." 1906 ::= { smfIpv6InterfacePerfEntry 7 } 1907 -- 1908 -- Notifications 1909 -- 1911 smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 0 } 1912 smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 } 1914 -- smfMIBNotifObjects 1916 smfAdminStatusChange NOTIFICATION-TYPE 1917 OBJECTS { smfRouterIDAddrType, -- The originator of 1918 -- the notification. 1919 smfRouterID, -- The originator of 1920 -- the notification. 1921 smfAdminStatus -- The new status of the 1922 -- SMF process. 1923 } 1924 STATUS current 1925 DESCRIPTION 1926 "smfAdminStatusChange is a notification sent when a 1927 the 'smfAdminStatus' object changes." 1928 ::= { smfMIBNotifObjects 1 } 1930 smfConfiguredOpModeChange NOTIFICATION-TYPE 1931 OBJECTS { smfRouterIDAddrType, -- The originator of 1932 -- the notification. 1933 smfRouterID, -- The originator of 1934 -- the notification. 1935 smfConfiguredOpMode -- The new Operations 1936 -- Mode of the SMF 1937 -- process. 1938 } 1939 STATUS current 1940 DESCRIPTION 1941 "smfConfiguredOpModeChange is a notification 1942 sent when a the 'smfConfiguredOpMode' object 1943 changes." 1944 ::= { smfMIBNotifObjects 2 } 1946 smfConfiguredRssaChange NOTIFICATION-TYPE 1947 OBJECTS { smfRouterIDAddrType, -- The originator of 1948 -- the notification. 1949 smfRouterID, -- The originator of 1950 -- the notification. 1951 smfConfiguredRssa -- The new RSSA for 1952 -- the SMF process. 1953 } 1955 STATUS current 1956 DESCRIPTION 1957 "smfAdminStatusChange is a notification sent when a 1958 the 'smfConfiguredRssa' object changes." 1959 ::= { smfMIBNotifObjects 3 } 1961 smfIfAdminStatusChange NOTIFICATION-TYPE 1962 OBJECTS { smfRouterIDAddrType, -- The originator of 1963 -- the notification. 1964 smfRouterID, -- The originator of 1965 -- the notification. 1966 smfIfName, -- The interface whose 1967 -- status has changed. 1968 smfIfAdminStatus -- The new status of the 1969 -- SMF interface. 1970 } 1971 STATUS current 1972 DESCRIPTION 1973 "smfIfAdminStatusChange is a notification sent when a 1974 the 'smfIfAdminStatus' object changes." 1975 ::= { smfMIBNotifObjects 4 } 1977 smfDpdMemoryOverflowEvent NOTIFICATION-TYPE 1978 OBJECTS { smfRouterIDAddrType, -- The originator of 1979 -- the notification. 1980 smfRouterID, -- The originator of 1981 -- the notification. 1982 smfDpdMemoryOverflow -- The counter of 1983 -- the overflows. 1984 } 1985 STATUS current 1986 DESCRIPTION 1987 "smfDpdMemoryOverflowEvents is sent when the 1988 number of memory overflow events exceeds the 1989 the 'smfDpdMemoryOverflowThreshold' within the 1990 previous number of seconds defined by the 1991 'smfDpdMemoryOverflowWindow'." 1992 ::= { smfMIBNotifObjects 5 } 1994 smfIpv4DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE 1995 OBJECTS { smfRouterIDAddrType, -- The originator of 1996 -- the notification. 1997 smfRouterID, -- The originator of 1998 -- the notification. 1999 smfIpv4DuplMultiPktsDetectedTotal 2000 -- The counter of detected 2001 -- duplicates. 2002 } 2004 STATUS current 2005 DESCRIPTION 2006 "smfIpv4DuplMultiPktsDetectedTotal is a 2007 notification sent when the number of 2008 IPv4 duplicate packets detected exceeds the 2009 'smfIpv4DuplMultiPktsDetectedTotalThreshold' 2010 during the previous number of seconds 2011 'smfIpv4DuplPktsDetectedTotalWindow'." 2012 ::= { smfMIBNotifObjects 6 } 2014 smfIpv6DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE 2015 OBJECTS { smfRouterIDAddrType, -- The originator of 2016 -- the notification. 2017 smfRouterID, -- The originator of 2018 -- the notification. 2019 smfIpv6DuplMultiPktsDetectedTotal 2020 -- The counter of detected 2021 -- duplicates. 2022 } 2023 STATUS current 2024 DESCRIPTION 2025 "smfIpv6DuplMultiPktsDetectedTotal is a 2026 notification sent when the number of 2027 IPv6 duplicate packets detected exceeds the 2028 'smfIpv6DuplMultiPktsDetectedTotalThreshold' 2029 during the previous number of seconds 2030 'smfIpv6DuplPktsDetectedTotalWindow'." 2031 ::= { smfMIBNotifObjects 7 } 2033 -- smfMIBNotifControl 2034 smfDpdMemoryOverflowThreshold OBJECT-TYPE 2035 SYNTAX Integer32 (0..255) 2036 MAX-ACCESS read-write 2037 STATUS current 2038 DESCRIPTION 2039 "A threshold value for the 2040 `smfDpdmemoryOverflowEvents' object. 2041 If the number of occurences exceeds 2042 this threshold within the previous 2043 number of seconds 2044 'smfDpdMemoryOverflowWindow', 2045 then the `smfDpdMemoryOverflowEvent' 2046 notification is sent." 2047 ::= { smfMIBNotifControl 1 } 2049 smfDpdMemoryOverflowWindow OBJECT-TYPE 2050 SYNTAX TimeTicks 2051 MAX-ACCESS read-write 2052 STATUS current 2053 DESCRIPTION 2054 "A time window value for the 2055 `smfDpdmemoryOverflowEvents' object. 2056 If the number of occurences exceeds 2057 the `smfDpdMemoryOverflowThreshold' 2058 within the previous number of seconds 2059 'smfDpdMemoryOverflowWindow', 2060 then the `smfDpdMemoryOverflowEvent' 2061 notification is sent." 2062 ::= { smfMIBNotifControl 2 } 2064 smfIpv4DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE 2065 SYNTAX Integer32 (0..255) 2066 MAX-ACCESS read-write 2067 STATUS current 2068 DESCRIPTION 2069 "A threshold value for the 2070 `smfIpv4DuplMultiPktsDetectedTotal' 2071 object. If the number of occurences 2072 exceeds this threshold within the 2073 previous number of seconds 2074 `smfIpv4DuplMultiPktsDetectedTotalWindow', 2075 then the 2076 `smfIpv4DuplMultiPktsDetectedTotalEvent' 2077 notification is sent." 2078 ::= { smfMIBNotifControl 3 } 2080 smfIpv4DuplMultiPktsDetectedTotalWindow OBJECT-TYPE 2081 SYNTAX TimeTicks 2082 MAX-ACCESS read-write 2083 STATUS current 2084 DESCRIPTION 2085 "A time window value for the 2086 `smfIpv4DuplMultiPktsDetectedTotalEvents' 2087 object. If the number of occurences 2088 exceeds the 2089 `smfIpv4DuplMultiPktsDetectedTotalThreshold' 2090 within the previous number of seconds 2091 'smfIpv4DuplMultiPktsDetectedTotalWindow', 2092 then the 2093 `smfIpv4DuplMultiPktsDetectedTotalEvent' 2094 notification is sent." 2095 ::= { smfMIBNotifControl 4 } 2097 smfIpv6DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE 2098 SYNTAX Integer32 (0..255) 2099 MAX-ACCESS read-write 2100 STATUS current 2101 DESCRIPTION 2102 "A threshold value for the 2103 `smfIpv6DuplMultiPktsDetectedTotal' 2104 object. If the number of occurences 2105 exceeds this threshold within the 2106 previous number of seconds 2107 `smfIpv6DuplMultiPktsDetectedTotalWindow', 2108 then the 2109 `smfIpv6DuplMultiPktsDetectedTotalEvent' 2110 notification is sent." 2111 ::= { smfMIBNotifControl 5 } 2113 smfIpv6DuplMultiPktsDetectedTotalWindow OBJECT-TYPE 2114 SYNTAX TimeTicks 2115 MAX-ACCESS read-write 2116 STATUS current 2117 DESCRIPTION 2118 "A time window value for the 2119 `smfIpv6DuplMultiPktsDetectedTotalEvents' 2120 object. If the number of occurences 2121 exceeds the 2122 `smfIpv6DuplMultiPktsDetectedTotalThreshold' 2123 within the previous number of seconds 2124 'smfIpv6DuplMultiPktsDetectedTotalWindow', 2125 then the 2126 `smfIpv6DuplMultiPktsDetectedTotalEvent' 2127 notification is sent." 2128 ::= { smfMIBNotifControl 6 } 2130 -- 2131 -- Compliance Statements 2132 -- 2134 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2135 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2137 smfBasicCompliance MODULE-COMPLIANCE 2138 STATUS current 2139 DESCRIPTION "The basic implementation requirements for 2140 managed network entities that implement 2141 the SMF RSSA process." 2142 MODULE -- this module 2143 MANDATORY-GROUPS { smfCapabObjectsGroup, 2144 smfConfigObjectsGroup } 2145 ::= { smfCompliances 1 } 2146 smfFullCompliance MODULE-COMPLIANCE 2147 STATUS current 2148 DESCRIPTION "The full implementation requirements for 2149 managed network entities that implement 2150 the SMF RSSA process." 2151 MODULE -- this module 2152 MANDATORY-GROUPS { smfCapabObjectsGroup, 2153 smfConfigObjectsGroup, 2154 smfStateObjectsGroup, 2155 smfPerfObjectsGroup, 2156 smfNotifObjectsGroup, 2157 smfNotificationsGroup 2158 } 2159 ::= { smfCompliances 2 } 2161 -- 2162 -- Units of Conformance 2163 -- 2165 smfCapabObjectsGroup OBJECT-GROUP 2166 OBJECTS { 2167 smfOpModeCapabilitiesName, 2168 smfOpModeCapabilitiesReference, 2170 smfRssaCapabilitiesName, 2171 smfRssaCapabilitiesReference 2172 } 2173 STATUS current 2174 DESCRIPTION 2175 "Set of SMF configuration objects implemented 2176 in this module." 2177 ::= { smfMIBGroups 1 } 2179 smfConfigObjectsGroup OBJECT-GROUP 2180 OBJECTS { 2181 smfAdminStatus, 2182 smfRouterIDAddrType, 2183 smfRouterID, 2184 smfIfName, 2185 smfConfiguredOpMode, 2186 smfConfiguredRssa, 2187 smfRssaMember, 2188 smfIpv4Dpd, 2189 smfIpv6Dpd, 2190 smfMaxPktLifetime, 2191 smfDpdMaxMemorySize, 2192 smfDpdEntryMaxLifetime, 2193 smfNhdpRssaMesgTLVIncluded, 2194 smfNhdpRssaAddrBlockTLVIncluded, 2196 smfConfiguredAddrForwardingLastAddr, 2197 smfConfiguredAddrForwardingStatus, 2199 smfIfAdminStatus, 2200 smfIfRowStatus 2201 } 2202 STATUS current 2203 DESCRIPTION 2204 "Set of SMF configuration objects implemented 2205 in this module." 2206 ::= { smfMIBGroups 2 } 2208 smfStateObjectsGroup OBJECT-GROUP 2209 OBJECTS { 2210 smfNodeRsStatusIncluded, 2211 smfDpdMemoryOverflow, 2213 smfDiscoveredAddrForwardingLastAddr, 2215 smfNeighborRSSA, 2216 smfNeighborNextHopInterface 2217 } 2218 STATUS current 2219 DESCRIPTION 2220 "Set of SMF state objects implemented 2221 in this module." 2222 ::= { smfMIBGroups 3 } 2224 smfPerfObjectsGroup OBJECT-GROUP 2225 OBJECTS { 2226 smfIpv4MultiPktsRecvTotal, 2227 smfIpv4MultiPktsForwardedTotal, 2228 smfIpv4DuplMultiPktsDetectedTotal, 2229 smfIpv4DroppedMultiPktsTTLExceededTotal, 2230 smfIpv4TTLLargerThanPreviousTotal, 2232 smfIpv6MultiPktsRecvTotal, 2233 smfIpv6MultiPktsForwardedTotal, 2234 smfIpv6DuplMultiPktsDetectedTotal, 2235 smfIpv6DroppedMultiPktsTTLExceededTotal, 2236 smfIpv6TTLLargerThanPreviousTotal, 2237 smfIpv6HAVAssistsReqdTotal, 2238 smfIpv6DpdHeaderInsertionsTotal, 2240 smfIpv4MultiPktsRecvPerIf, 2241 smfIpv4MultiPktsForwardedPerIf, 2242 smfIpv4DuplMultiPktsDetectedPerIf, 2243 smfIpv4DroppedMultiPktsTTLExceededPerIf, 2244 smfIpv4TTLLargerThanPreviousPerIf, 2246 smfIpv6MultiPktsRecvPerIf, 2247 smfIpv6MultiPktsForwardedPerIf, 2248 smfIpv6DuplMultiPktsDetectedPerIf, 2249 smfIpv6DroppedMultiPktsTTLExceededPerIf, 2250 smfIpv6TTLLargerThanPreviousPerIf, 2251 smfIpv6HAVAssistsReqdPerIf, 2252 smfIpv6DpdHeaderInsertionsPerIf 2253 } 2254 STATUS current 2255 DESCRIPTION 2256 "Set of SMF performance objects implemented 2257 in this module by total and per interface." 2258 ::= { smfMIBGroups 4 } 2260 smfNotifObjectsGroup OBJECT-GROUP 2261 OBJECTS { 2262 smfDpdMemoryOverflowThreshold, 2263 smfDpdMemoryOverflowWindow, 2264 smfIpv4DuplMultiPktsDetectedTotalThreshold, 2265 smfIpv4DuplMultiPktsDetectedTotalWindow, 2266 smfIpv6DuplMultiPktsDetectedTotalThreshold, 2267 smfIpv6DuplMultiPktsDetectedTotalWindow 2268 } 2269 STATUS current 2270 DESCRIPTION 2271 "Set of SMF notification control 2272 objects implemented in this module." 2273 ::= { smfMIBGroups 5 } 2275 smfNotificationsGroup NOTIFICATION-GROUP 2276 NOTIFICATIONS { 2277 smfAdminStatusChange, 2278 smfConfiguredOpModeChange, 2279 smfConfiguredRssaChange, 2280 smfIfAdminStatusChange, 2281 smfDpdMemoryOverflowEvent, 2282 smfIpv4DuplMultiPktsDetectedTotalEvents, 2283 smfIpv6DuplMultiPktsDetectedTotalEvents 2284 } 2285 STATUS current 2286 DESCRIPTION 2287 "Set of SMF notifications implemented 2288 in this module." 2289 ::= { smfMIBGroups 6 } 2290 END 2292 8. Security Considerations 2294 This section discusses security implications of the choices made in 2295 this SMF-MIB module. 2297 There are a number of management objects defined in this MIB module 2298 with a MAX-ACCESS clause of read-write and/or read-create. Such 2299 objects may be considered sensitive or vulnerable in some network 2300 environments. The support for SET operations in a non-secure 2301 environment without proper protection can have a negative effect on 2302 network operations. These are the tables and objects and their 2303 sensitivity/vulnerability: 2305 o 'smfAdminStatus' - this writable configuration object controls the 2306 operational status of the SMF process. If this setting is 2307 configured inconsistently across the MANET multicast domain, then 2308 delivery of multicast data may be inconsistent across the domain; 2309 some nodes may not receive multicast data intended for them. 2311 o 'smfRouterIDAddrType' and 'smfRouterID' - these writable 2312 configuration objects define the ID of the SMF process. These 2313 objects should be configured with a routable address defined on 2314 the local SMF device. The smfRouterID is a logical identification 2315 that MUST be consistent across inter-operating SMF neighborhoods 2316 and it is RECOMMENDED to be chosen as the numerically largest 2317 address contained in a node's 'Neighbor Address List' as defined 2318 in NHDP. A smfRouterID MUST be unique within the scope of the 2319 operating MANET network regardless of the method used for 2320 selecting it. 2322 o 'smfConfiguredOpMode' - this writable configuration objects define 2323 the operational mode of the SMF process. The operational mode 2324 defines how the SMF process develops its local estimate of the 2325 CDS. 2327 o 'smfConfiguredRssa' - this writable configuration object sets the 2328 specific Reduced Set Selection Algorithm (RSSA) for the SMF 2329 process. If this object is set inconsistently across the MANET 2330 domain, multicast delivery of data will fail. 2332 o 'smfRssaMember' - this writable configuration object sets the 2333 'interest' of the local SMF node in participating in the CDS. 2334 Setting this object to 'never(3)' on a highly highly connected 2335 device could lead to frequent island formation. Setting this 2336 object to 'always(2)' could support data ex-filtration from the 2337 MANET domain. 2339 o 'smfIpv4Dpd' - this writable configuration object sets the 2340 duplicate packet detection method for forwarding of IPv4 multicast 2341 packets. 2343 o 'smfIpv6Dpd' - this writable configuration object sets the 2344 duplicate packet detection method for forwarding of IPv6 multicast 2345 packets. 2347 o 'smfMaxPktLifetime' - this writable configuration object sets the 2348 estimate of the network packet traversal time. If set too small, 2349 this could lead to poor multicast data delivery ratios throughout 2350 the MANET domain. 2352 o 'smfDpdMaxMemorySize' - this writable configuration object sets 2353 the memory storage size (in Kilo-Bytes) for the cached DPD records 2354 for the combined IPv4 and IPv6 methods. If set too small this 2355 could lead to poor performance of the duplicate packet protection 2356 algorithms and lead to inefficient resource, e.g., link, 2357 utilization within the MANET domain. The local SMF device should 2358 protect itself against memory overruns in the event that too large 2359 a setting is requested. 2361 o 'smfDpdEntryMaxLifetime' - this writable configuration object sets 2362 the maximum lifetime (in seconds) for the cached DPD records for 2363 the combined IPv4 and IPv6 methods. If the memory is running low 2364 prior to the MaxLifetimes being exceeded, the local SMF devices 2365 should purge the oldest records first. 2367 o 'smfNhdpRssaMesgTLVIncluded' - this writable configuration object 2368 indicates whether the associated NHDP messages include the the 2369 RSSA Message TLV, or not. It is highly RECOMMENDED that this 2370 object be set to 'true(1)'. 2372 o 'smfNhdpRssaAddrBlockTLVIncluded' - this writable configuration 2373 object indicates whether the associated NHDP messages include the 2374 the RSSA Address Block TLV, or not. The 2375 smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it 2376 depends on the existence of an address block which may not be 2377 present. If this SMF device is configured with NHDP, then this 2378 object should be set to 'true(1)'. 2380 o 'smfConfiguredAddrForwardingTable' - the writable configuration 2381 objects in this table indicate which multicast IP address are to 2382 be forwarded by this SMF node. Misconfiguration of rows within 2383 this table can limit the ability of this SMF device to forward 2384 multicast data. 2386 o 'smfInterfaceTable' - the writable configuration objects in this 2387 table indicate which SMF node interfaces are participating in the 2388 SMF packet forwarding process. Misconfiguration of rows within 2389 this table can limit the ability of this SMF device to forward 2390 multicast data. 2392 Some of the readable objects in this MIB module (i.e., objects with a 2393 MAX-ACCESS other than not-accessible) may be considered sensitive or 2394 vulnerable in some network environments. It is thus important to 2395 control even GET and/or NOTIFY access to these objects and possibly 2396 to even encrypt the values of these objects when sending them over 2397 the network via SNMP. These are the tables and objects and their 2398 sensitivity/vulnerability: 2400 o 'smfNodeRsStatusIncluded' - this readable state object indicates 2401 that this SMF node is part of the CDS, or not. Being part of the 2402 CDS makes this node a distinguished device. It could be exploited 2403 for data ex-filtration, or denial of service attacks. 2405 o 'smfDiscoveredAddrForwardingTable' - the readable state objects in 2406 this table indicate which, dynamically discovered, multicast IP 2407 address are to be forwarded by this SMF node. 2409 o 'smfNeighborTable' - the readable state objects in this table 2410 indicate current neighbor nodes to this SMF node. Exposing this 2411 information to an attacker could allow the attacker easier access 2412 to the larger MANET domain. 2414 The remainder of the objects in the SMF-MIB are performance counter 2415 objects. While these give an indication of the activity of the SMF 2416 process on this node, it is not expected that exposing these values 2417 pose a security risk to the MANET network. 2419 SNMP versions prior to SNMPv3 did not include adequate security. 2420 Even if the network itself is secure (for example by using IPSec), 2421 even then, there is no control as to who on the secure network is 2422 allowed to access and GET/SET (read/change/create/delete) the objects 2423 in this MIB module. 2425 Implementations MUST provide the security features described by the 2426 SNMPv3 framework (see [RFC3410] ), including full support for 2427 authentication and privacy via the User-based Security Model (USM) 2428 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2429 MAY also provide support for the Transport Security Model (TSM) 2430 [RFC5591] in combination with a secure transport such as SSH 2431 [RFC5592] or TLS/DTLS [RFC6353]. 2433 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2434 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2435 enable cryptographic security. It is then a customer/operator 2436 responsibility to ensure that the SNMP entity giving access to an 2437 instance of this MIB module is properly configured to give access to 2438 the objects only to those principals (users) that have legitimate 2439 rights to indeed GET or SET (change/create/delete) them. 2441 9. Applicability Statement 2443 This document describes objects for configuring parameters of the 2444 Simplified Multicast Forwarding [RFC6621] process on a router. This 2445 MIB module, denoted SMF-MIB, also reports state, performance 2446 information and notifications. This sections provides some examples 2447 of how this MIB module can be used in MANET network deployments. A 2448 fuller discussion of MANET network management use cases and 2449 challenges will be provided elsewhere. 2451 SMF is designed to allow routers to forward IPv4 and IPv6 packets 2452 over the MANET and cover the MANET nodes through the automatic 2453 discovery of efficient estimates of the Minimum Connected Dominating 2454 Set (MCDS) of nodes within the MANET. The MCDS are estimated using 2455 the RSSAs discussed within this document. In the following, three 2456 scenarios are listed where this MIB module is useful, i.e., 2458 o For a Parking Lot Initial Configuration Situation - it is common 2459 for the vehicles comprising the MANET being forward deployed at a 2460 remote location, e.g., the site of a natural disaster, to be off- 2461 loaded in a parking lot where an initial configuration of the 2462 networking devices is performed. The configuration is loaded into 2463 the devices from a fixed location Network Operation Center (NOC) 2464 at the parking lot and the vehicles are stationary at the parking 2465 lot while the configuration changes are made. Standards-based 2466 methods for configuration management from the co-located NOC are 2467 necessary for this deployment option. 2469 o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed 2470 NOC - Here the vehicles carrying the MANET routers carry multiple 2471 wireless interfaces, one of which is a relatively low-bandwidth 2472 on-the-move satellite connection which interconnects a fix NOC to 2473 the nodes of the MANET. Standards-based methods for monitoring 2474 and fault management from the fixed NOC are necessary for this 2475 deployment option. 2477 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 2478 larger vehicles, a hierarchical network management arrangement is 2479 useful. Centralized network management is performed from a fixed 2480 NOC while local management is performed locally from within the 2481 vehicles. Standards-based methods for configuration, monitoring 2482 and fault management are necessary for this deployment option. 2484 10. IANA Considerations 2486 The MIB module in this document uses the following IANA-assigned 2487 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 2489 Descriptor OBJECT IDENTIFIER value 2490 ---------- ----------------------- 2491 SMF-MIB { experimental XXXX } 2492 IANA EDITOR NOTE: please assign XXXX, and remove this note. 2494 11. Contributors 2496 This MIB document uses the template authored by D. Harrington which 2497 is based on contributions from the MIB Doctors, especially Juergen 2498 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2500 12. Acknowledgements 2502 The authors would like to acknowledge the valuable comments from Sean 2503 Harnedy in the early phases of the development of this MIB-module. 2504 The authors would like to thank James Nguyen for his careful review 2505 and comments on this MIB-module and his work on the definitions of 2506 the follow on MIB-modules to configure specific RSSA algorithms 2507 related to SMF. Further, the authors would like to acknowledge to 2508 work of James Nguyen, Brian Little, Ryan Morgan and Justin Dean on 2509 their software development of the SMF-MIB. 2511 13. References 2513 13.1. Normative References 2515 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2516 MIB", RFC 2863, June 2000. 2518 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2519 Architecture for Describing Simple Network Management 2520 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2521 December 2002. 2523 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 2524 Simple Network Management Protocol (SNMP)", STD 62, 2525 RFC 3418, December 2002. 2527 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2528 Schoenwaelder, "Textual Conventions for Internet Network 2529 Addresses", RFC 4001, February 2005. 2531 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2532 Requirement Levels", BCP 14, RFC 2119, March 1997. 2534 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2535 Schoenwaelder, Ed., "Structure of Management Information 2536 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2538 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2539 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2540 STD 58, RFC 2579, April 1999. 2542 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2543 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2544 April 1999. 2546 [RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621, 2547 May 2012. 2549 13.2. Informative References 2551 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2552 "Introduction and Applicability Statements for Internet- 2553 Standard Management Framework", RFC 3410, December 2002. 2555 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2556 (USM) for version 3 of the Simple Network Management 2557 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 2559 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 2560 Advanced Encryption Standard (AES) Cipher Algorithm in the 2561 SNMP User-based Security Model", RFC 3826, June 2004. 2563 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2564 for the Simple Network Management Protocol (SNMP)", 2565 RFC 5591, June 2009. 2567 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 2568 Shell Transport Model for the Simple Network Management 2569 Protocol (SNMP)", RFC 5592, June 2009. 2571 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 2572 Model for the Simple Network Management Protocol (SNMP)", 2573 RFC 6353, July 2011. 2575 Appendix A. 2577 *************************************************************** 2578 * Note to the RFC Editor (to be removed prior to publication) * 2579 * * 2580 * The reference to RFC xxxx within the DESCRIPTION clauses * 2581 * of the MIB module point to this draft and are to be * 2582 * assigned by the RFC Editor. * 2583 * * 2584 *************************************************************** 2586 Authors' Addresses 2588 Robert G. Cole 2589 US Army CERDEC 2590 6010 Frankford Road 2591 Aberdeen Proving Ground, Maryland 21005 2592 USA 2594 Phone: +1 443 395 8744 2595 EMail: robert.g.cole@us.army.mil 2597 Joseph Macker 2598 Naval Research Laboratory 2599 Washington, D.C. 20375 2600 USA 2602 EMail: macker@itd.nrl.navy.mil 2604 Brian Adamson 2605 Naval Research Laboratory 2606 Washington, D.C. 20375 2607 USA 2609 EMail: adamson@itd.nrl.navy.mil