idnits 2.17.1 draft-ietf-manet-smf-mib-08.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 == 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 (September 2, 2013) is 3888 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'SMF' is mentioned on line 655, but not defined Summary: 0 errors (**), 0 flaws (~~), 3 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: March 6, 2014 B. Adamson 6 Naval Research Laboratory 7 September 2, 2013 9 Definition of Managed Objects for the Manet Simplified Multicast 10 Framework Relay Set Process 11 draft-ietf-manet-smf-mib-08 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 March 6, 2014. 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 information, 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 Duplicate Packet Detection 126 (DPD)-based multicast forwarding with the optional use of Connected 127 Dominating Set (CDS)-based relay sets. The CDS provides a complete 128 connected coverage of the nodes comprising the MANET. The Minimum 129 CDS (MCDS) is the smallest set of MANET nodes (comprising a connected 130 cluster) which cover all the nodes in the cluster with their 131 transmissions. As the density of the MANET nodes increase, the 132 fraction of nodes required in an MCDS decreases. Using the MCDS as a 133 multicast forwarding set then becomes an efficient multicast 134 mechanism for MANETs. 136 Various algorithms for the construction of estimates of the MCDS 137 exist. The Simplified Multicast Framework [RFC6621] describes some 138 of these. It further defines various operational modes for a node 139 which is participating in the collective creation of the MCDS 140 estimates. These modes depend upon the set of related MANET routing 141 and discovery protocols and mechanisms in operation in the specific 142 MANET node. 144 A SMF router's MIB contains SMF process configuration parameters 145 (e.g. specific CDS algorithm), state information (e.g., current 146 membership in the CDS), performance counters (e.g., packet counters), 147 and notifications. 149 4.1. SMF Management Model 151 This section describes the management model for the SMF node process. 153 Figure 1 (reproduced from Figure 4 of [RFC6621]) shows the 154 relationship between the SMF Relay Set selection algorithm and the 155 related algorithms, processes and protocols running in the MANET 156 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 157 topology information gotten from the MANET Neighborhood Discovery 158 Protocol (NHDP), from the specific MANET routing protocol running on 159 the node, or from Layer 2 information passed up to the higher layer 160 protocol processes. 162 ______________ ____________ 163 | | | | 164 | Neighborhood | | Relay Set | 165 | Discovery |------------->| Selection | 166 | | neighbor | | 167 |______________| info |____________| 168 \ / 169 \ / 170 neighbor\ / forwarding 171 info* \ _____________ / status 172 \ | | / 173 `-->| Forwarding |<--' 174 | Process | 175 ----------------->|_____________|-----------------> 176 incoming packet, forwarded packets 177 interface id*, and 178 previous hop* 180 Figure 1: SMF Router Architecture 182 4.2. Terms 184 The following definitions apply throughout this document: 186 o Configuration Objects - switches, tables, objects which are 187 initialized to default settings or set through the management 188 interfaces such as defined by this MIB. 190 o Tunable Configuration Objects - objects whose values affect timing 191 or attempt bounds on the SMF Relay Set (RS) process. 193 o State Objects - automatically generated values which define the 194 current operating state of the SMF RS process in the router. 196 o Performance Objects - automatically generated values which help an 197 administrator or automated tool to assess the performance of the 198 CDS multicast process on the router and the overall multicast 199 performance within the MANET routing domain. 201 5. Structure of the MIB Module 203 This section presents the structure of the SMF-MIB module. The 204 objects are arranged into the following groups: 206 o smfMIBNotifications - defines the notifications associated with 207 the SMF process. 209 o smfMIBObjects - defines the objects forming the basis for the SMF- 210 MIB. These objects are divided up by function into the following 211 groups: 213 * Capabilities Group - This group contains the SMF objects that 214 the device uses to advertise its local capabilities with 215 respect to, e.g., the supported RSSAs. 217 * Configuration Group - This group contains the SMF objects that 218 configure specific options that determine the overall operation 219 of the SMF process and the resulting multicast performance. 221 * State Group - Contains information describing the current state 222 of the SMF process such as the Neighbor Table. 224 * Performance Group - Contains objects which help to characterize 225 the performance of the SMF process, typically counters for 226 statistical computations. 228 o smfMIBConformance - defines two, i.e., minimal and full, 229 conformance implementations for the SMF-MIB. 231 5.1. Textual Conventions 233 The textual conventions defined within the SMF-MIB are: 235 o The SmfStatus is defined within the SMF-MIB. This contains the 236 current operational status of the SMF process on an interface. 238 o The SmfOpModeID represents an index that identifies a specific SMF 239 operational mode. 241 o The SmfRssaID represents an index that identifies, through 242 reference, a specific RSSA available for operation on the device. 244 5.2. The Capabilities Group 246 The SMF device supports a set of capabilities. The list of 247 capabilities which the device can advertise are: 249 o Operational Mode - topology information from NHDP, CDS-aware 250 unicast routing or Cross-layer from Layer 2. 252 o SMF RSSA - the specific RSSA operational on the device. Note that 253 configuration, state and performance objects related to a specific 254 RSSA must be defined within a separate MIB. 256 5.3. The Configuration Group 258 The SMF device is configured with a set of controls. Some of the 259 prominent configuration controls for the SMF device are: 261 o Operational Mode - determines where topology information is 262 derived from, e.g., NHDP, CDS-aware unicast routing or Cross-layer 263 from Layer 2. 265 o SMF RSSA - the specific RSSA operational on the device. 267 o Duplicate Packet detection for IPv4 - Identification-based or 268 Hash-based DPD. 270 o Duplicate Packet detection for IPv6 - Identification-based or 271 Hash-based DPD. 273 o SMF Type Message TLV - if NHDP mode is selected, then the SMF Type 274 Message TLV MAY be included in the NHDP exchanges. 276 o SMF Address Block TLV - if NHDP mode is selected, then the SMF 277 Address Block TLV SHOULD be included in the NHDP exchanges. 279 5.4. The State Group 281 The State sub-tree reports current state information, e.g., 283 o Node RSSA State - identifies whether the node is currently in or 284 out of the Relay Set. 286 o Neighbors Table - a table containing current one-hop neighbors and 287 their operational RSSA. 289 5.5. The Performance Group 291 The Performance sub-tree reports primarily counters that relate to 292 SMF RSSA performance. The SMF performance counters consists of per 293 node and per interface objects: 295 o Total multicast packets received. 297 o Total multicast packets forwarded. 299 o Total duplicate multicast packets detected. 301 o Per interface statistics table with the following entries: 303 * Multicast packets received. 305 * Multicast packets forwarded. 307 * Duplicate multicast packets detected. 309 5.6. The Notifications Group 311 The Notifications Sub-tree contains the list of notifications 312 supported within the SMF-MIB and their intended purpose and utility. 314 5.7. Tables and Indexing 316 The SMF-MIB module contains a number of tables which record data 317 related to: 319 o configuration and operation of packet forwarding on the local 320 router, 322 o configuration and operation of local MANET interfaces on the 323 router, and 325 o configuration and operation of various RSSA algorithms for packet 326 forwarding. 328 The SMF-MIB module's tables are indexed via the following constructs: 330 o smfOpModeCapabilitiesID - the index identifying the SMF modes. 332 o smfRssaCapabilitiesID - the index identifying the RSSAs supported 333 by this specific device. 335 o smfConfiguredAddrForwardingAddrType and 336 smfConfiguredAddrForwardingFirstAddr - indexes to configured 337 multicast addresses which are forwarded by the SMF process. 339 o smfIfIndex - the IfIndex of the interface on the local router on 340 which SMF is configured. 342 o smfDiscoveredAddrForwardingAddrType and 343 smfDiscoveredAddrForwardingFirstAddr - indexes to discovered 344 multicast addresses which are forwarded by the SMF process. 346 o smfNeighborIpAddrType, smfNeighborIpAddr, and smfNeighborPrefixLen 347 - the interface index set of specific one-hop neighbor nodes to 348 this local router. 350 These tables and their associated indexing are: 352 o smfOpModeCapabilitiesTable - identifies the resident set of SMF 353 Operational Modes on this router. This table has 'INDEX { 354 smfOpModeCapabilitiesID }. 356 o smfRssaCapabilitiesTable - contains reference to the specific set 357 of RSSAs currently supported on this device. This table has 358 'INDEX { smfRssaCapabilitiesID }'. 360 o smfConfiguredAddrForwardingTable - contains information on 361 multicast addresses which are to be forwarded by the SMF process 362 on this device. This table has 'INDEX { 363 smfConfiguredAddrForwardingAddrType, 364 smfConfiguredAddrForwardingFirstAddr, 365 smfConfiguredAddrForwardingLastAddr }'. 367 o smfInterfaceTable - describes the SMF interfaces on this device 368 that are participating in the SMF packet forwarding process. This 369 table has 'INDEX { smfIfIndex }'. 371 o smfDiscoveredAddrForwardingTable - contains discovered address for 372 SMF packet forwarding. This table has 'INDEX { 373 smfDiscoveredAddrForwardingAddrType, 374 smfDiscoveredAddrForwardingFirstAddr }'. 376 o smfNeighborTable - describes the current neighbor nodes, their 377 addresses and the SMF RSSA and the interface on which they can be 378 reached. This table has 'INDEX { smfNeighborIpAddrType, 379 smfNeighborIpAddr, smfNeighborPrefixLen }'. 381 o smfIpv4InterfaceTable - contains the IPv4 related SMF statistics 382 per each SMF interface on this device. This table has 'INDEX { 383 smfIfIndex }'. 385 o smfIpv6InterfaceTable - contains the IPv6 related SMF statistics 386 per each SMF interface on this device. This table has 'INDEX { 387 smfIfIndex }'. 389 6. Relationship to Other MIB Modules 391 6.1. Relationship to the SNMPv2-MIB 393 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 394 mandatory for all systems, and the objects apply to the entity as a 395 whole. The 'system' group provides identification of the management 396 entity and certain other system-wide data. The SMF-MIB does not 397 duplicate those objects. 399 6.2. MIB modules required for IMPORTS 401 The textual conventions imported for use in the SMF-MIB are as 402 follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 403 Counter32, Unsigned32, Integer32 and mib-2 textual conventions are 404 imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 405 and TruthValue textual conventions are imported from RFC 2579 406 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- 407 GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 408 InterfaceIndexOrZero textual convention is imported from RFC 2863 409 [RFC2863]. The SnmpAdminString textual convention is imported from 410 RFC 3411 [RFC3411]. The InetAddress, InetAddressType and 411 InetAddressPrefixLength textual conventions are imported from RFC 412 4001 [RFC4001]. 414 6.3. Relationship to the Future RSSA-MIBs 416 In a sense, the SMF-MIB is a general front-end to a set of, yet to be 417 developed, RSSA-specific MIBs. These RSSA-specific MIBs will define 418 the objects for the configuration, state, performance and 419 notification required for the operation of these specific RSSAs. The 420 SMF-MIB Capabilities Group allows the remote management station the 421 ability to query the router to discover the set of supported RSSAs. 423 7. Definitions 425 SMF-MIB DEFINITIONS ::= BEGIN 427 IMPORTS 429 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 430 Counter32, Integer32, TimeTicks, experimental 431 FROM SNMPv2-SMI -- [RFC2578] 433 TEXTUAL-CONVENTION, RowStatus, TruthValue, 434 DisplayString 435 FROM SNMPv2-TC -- [RFC2579] 437 MODULE-COMPLIANCE, OBJECT-GROUP, 438 NOTIFICATION-GROUP 439 FROM SNMPv2-CONF -- [RFC2580] 441 InterfaceIndexOrZero 442 FROM IF-MIB -- [RFC2863] 444 SnmpAdminString 445 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 447 InetAddress, InetAddressType, 448 InetAddressPrefixLength 449 FROM INET-ADDRESS-MIB -- [RFC4001] 450 ; 452 smfMIB MODULE-IDENTITY 453 LAST-UPDATED "201309011300Z" -- September 01, 2013 454 ORGANIZATION "IETF MANET Working Group" 455 CONTACT-INFO 456 "WG E-Mail: manet@ietf.org 458 WG Chairs: sratliff@cisco.com 459 jmacker@nrl.navy.mil 461 Editors: Robert G. Cole 462 US Army CERDEC 463 Space and Terrestrial Communications 464 6010 Frankford Road 465 Aberdeen Proving Ground, MD 21005 466 USA 467 +1 443 395-8744 468 robert.g.cole@us.army.mil 470 Joseph Macker 471 Naval Research Laboratory 472 Washington, D.C. 20375 473 USA 474 macker@itd.nrl.navy.mil 476 Brian Adamson 477 Naval Research Laboratory 478 Washington, D.C. 20375 479 USA 480 adamson@itd.nrl.navy.mil" 482 DESCRIPTION 483 "This MIB module contains managed object definitions for 484 the Manet SMF RSSA process defined in: 486 [SMF] Macker, J.(ed.), 487 Simplified Multicast Forwarding, RFC 6621, 488 May 2012. 490 Copyright (C) The IETF Trust (2012). This version 491 of this MIB module is part of RFC xxxx; see the RFC 492 itself for full legal notices." 494 -- Revision History 495 REVISION "201309011300Z" -- September 01, 2013 496 DESCRIPTION 497 "The first version of this MIB module, 498 published as RFC xxxx. 499 " 500 -- RFC-Editor assigns xxxx 501 ::= { experimental xxxx } -- to be assigned by IANA 503 -- 504 -- TEXTUAL CONVENTIONs 505 -- 507 SmfStatus ::= TEXTUAL-CONVENTION 508 STATUS current 509 DESCRIPTION 510 "An indication of the operability of a SMF 511 function or feature. For example, the status 512 of an interface: 'enabled' indicates that 513 this interface is performing SMF functions, 514 and 'disabled' indicates that it is not. 515 Similarly for the status of the device: 516 'enabled' indicates that the device has 517 enabled the SMF functions on the device and 518 'disabled' means that the device and all interfaces 519 have disabled all SMF functions." 520 SYNTAX INTEGER { 521 enabled (1), 522 disabled (2) 523 } 525 SmfOpModeID ::= TEXTUAL-CONVENTION 526 STATUS current 527 DESCRIPTION 528 "An index that identifies through reference to a specific 529 SMF operations mode. There are basically three styles 530 of SMF operation with reduced relay sets: 532 Independent operation 'independent(1)' - 533 SMF performs its own relay 534 set selection using information from an associated 535 MANET NHDP process. 537 CDS-aware unicast routing operation 'routing(2)'- 538 a coexistent unicast routing 539 protocol provides dynamic relay 540 set state based upon its own control plane 541 CDS or neighborhood discovery information. 543 Cross-layer operation 'crossLayer(3)' - 544 SMF operates using neighborhood 545 status and triggers from a 546 cross-layer information base for dynamic relay 547 set selection and maintenance." 548 REFERENCE 549 "RFC 6621 - Simplified Multicast Forwarding 550 (SMF), Macker, J., May 2012." 551 SYNTAX INTEGER { 552 independent (1), 553 routing (2), 554 crossLayer (3) 555 -- future (4-255) 556 } 558 SmfRssaID ::= TEXTUAL-CONVENTION 559 STATUS current 560 DESCRIPTION 561 "An index that identifies through reference to a specific 562 RSSA algorithms. Several are currently defined 563 in the appendix of RFC 6621." 564 REFERENCE 565 "RFC 6621 - Simplified Multicast Forwarding 566 (SMF), Macker, J., May 2012." 567 SYNTAX INTEGER { 568 cF(1), 569 sMPR(2), 570 eCDS(3), 571 mprCDS(4) 572 -- future(5-127) 573 -- noStdAction(128-239) 574 -- experimental(240-255) 575 } 577 -- 578 -- Top-Level Object Identifier Assignments 579 -- 581 smfMIBNotifications OBJECT IDENTIFIER ::= { smfMIB 0 } 582 smfMIBObjects OBJECT IDENTIFIER ::= { smfMIB 1 } 583 smfMIBConformance OBJECT IDENTIFIER ::= { smfMIB 2 } 584 -- 585 -- smfMIBObjects Assignments: 586 -- smfCapabilitiesGroup - 1 587 -- smfConfigurationGroup - 2 588 -- smfStateGroup - 3 589 -- smfPerformanceGroup - 4 590 -- 592 -- 593 -- smfCapabilitiesGroup 594 -- 595 -- This group contains the SMF objects that identify specific 596 -- capabilities within this device related to SMF functions. 597 -- 599 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 601 -- 602 -- SMF Operational Mode Capabilities Table 603 -- 605 smfOpModeCapabilitiesTable OBJECT-TYPE 606 SYNTAX SEQUENCE OF SmfOpModeCapabilitiesEntry 607 MAX-ACCESS not-accessible 608 STATUS current 609 DESCRIPTION 610 "The smfOpModeCapabilitiesTable identifies the 611 resident set of SMF Operational Modes on this 612 router." 613 REFERENCE 614 "RFC 6621 - Simplified Multicast Forwarding 615 (SMF), Macker, J., May 2012." 616 ::= { smfCapabilitiesGroup 1 } 618 smfOpModeCapabilitiesEntry OBJECT-TYPE 619 SYNTAX SmfOpModeCapabilitiesEntry 620 MAX-ACCESS not-accessible 621 STATUS current 622 DESCRIPTION 623 "Information about a particular operational 624 mode. 625 " 626 INDEX { smfOpModeCapabilitiesID } 627 ::= { smfOpModeCapabilitiesTable 1 } 629 SmfOpModeCapabilitiesEntry ::= SEQUENCE { 630 smfOpModeCapabilitiesID SmfOpModeID, 631 smfOpModeCapabilitiesName SnmpAdminString, 632 smfOpModeCapabilitiesReference SnmpAdminString 633 } 635 smfOpModeCapabilitiesID OBJECT-TYPE 636 SYNTAX SmfOpModeID 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "The index for this entry. This object identifies 641 the particular operational mode for this device." 642 ::= { smfOpModeCapabilitiesEntry 1 } 644 smfOpModeCapabilitiesName OBJECT-TYPE 645 SYNTAX SnmpAdminString 646 MAX-ACCESS read-only 647 STATUS current 648 DESCRIPTION 649 "The textual name of this operational 650 mode. Current operational modes include: 651 'independent', 652 'routing', and 653 'crossLayer' Mode. 654 Others may be defined 655 in future revisions of [SMF]." 656 ::= { smfOpModeCapabilitiesEntry 2 } 658 smfOpModeCapabilitiesReference OBJECT-TYPE 659 SYNTAX SnmpAdminString 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 663 "This object contains a reference to the document 664 that defines this operational mode." 665 ::= { smfOpModeCapabilitiesEntry 3 } 667 -- 668 -- SMF RSSA Capabilities Table 669 -- 671 smfRssaCapabilitiesTable OBJECT-TYPE 672 SYNTAX SEQUENCE OF SmfRssaCapabilitiesEntry 673 MAX-ACCESS not-accessible 674 STATUS current 675 DESCRIPTION 676 "The smfRssaCapabilitiesTable contains 677 reference to the specific set of RSSAs 678 currently supported on this device. 680 " 681 REFERENCE 682 "RFC 6621 - Simplified Multicast Forwarding 683 (SMF), Macker, J., May 2012." 684 ::= { smfCapabilitiesGroup 2 } 686 smfRssaCapabilitiesEntry OBJECT-TYPE 687 SYNTAX SmfRssaCapabilitiesEntry 688 MAX-ACCESS not-accessible 689 STATUS current 690 DESCRIPTION 691 "Information about a particular RSSA 692 algorithm. 694 By default, the agent should support at least the 695 Classical Flooding 'cF' algorithm. All compliant 696 SMF forwarders must support Classical Flooding. 697 Hence, at least one entry in this table must 698 exist with the smfRssaCapabilitiesID indicating 699 'cF'." 700 INDEX { smfRssaCapabilitiesID } 701 ::= { smfRssaCapabilitiesTable 1 } 703 SmfRssaCapabilitiesEntry ::= SEQUENCE { 704 smfRssaCapabilitiesID SmfRssaID, 705 smfRssaCapabilitiesName SnmpAdminString, 706 smfRssaCapabilitiesReference SnmpAdminString 707 } 709 smfRssaCapabilitiesID OBJECT-TYPE 710 SYNTAX SmfRssaID 711 MAX-ACCESS not-accessible 712 STATUS current 713 DESCRIPTION 714 "The index for this entry. This object identifies 715 the particular RSSA algorithm in this MIB 716 module. Example RSSAs are found in the 717 appendix of RFC 6621." 718 REFERENCE 719 "RFC 6621 - Simplified Multicast Forwarding 720 (SMF), Macker, J., May 2012." 721 ::= { smfRssaCapabilitiesEntry 1 } 723 smfRssaCapabilitiesName OBJECT-TYPE 724 SYNTAX SnmpAdminString 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "The textual name of this RSSA algorithm. 729 Currently defined names are: 730 'cF', 731 'sMPR', 732 'eCDS', 733 'mprCDS'. 734 " 735 ::= { smfRssaCapabilitiesEntry 2 } 737 smfRssaCapabilitiesReference OBJECT-TYPE 738 SYNTAX SnmpAdminString 739 MAX-ACCESS read-only 740 STATUS current 741 DESCRIPTION 742 "This object contains a published reference 743 to the document that defines this algorithm. 744 " 745 ::= { smfRssaCapabilitiesEntry 3 } 747 -- 748 -- smfConfigurationGroup 749 -- 750 -- This group contains the SMF objects that configure specific 751 -- options that determine the overall performance and operation 752 -- of the multicast forwarding process for the router device 753 -- and its interfaces. 754 -- 756 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 758 smfAdminStatus OBJECT-TYPE 759 SYNTAX SmfStatus 760 MAX-ACCESS read-write 761 STATUS current 762 DESCRIPTION 763 "The configured status of the SMF process 764 on this device. 'enabled(1)' means that 765 SMF is configured to run on this device. 766 'disabled(2)' mean that the SMF process 767 is configured off. 769 Prior to SNM functions being performed over 770 specific interfaces, this object must first 771 be 'enabled'. If this object is 'disabled', 772 then no SMF functions SHOULD be performed on 773 the device and all smfIfAdminStatus objects 774 SHOULD also be set to 'disabled'. When 775 this object is changed from 'enabled' to 776 'disabled', then all smfIfAdminStatus objects 777 SHOULD also be set to 'disabled'. 779 The default value for this object SHOULD be 780 'enabled'. 782 This object is persistent and when written 783 the entity SHOULD save the change to 784 non-volatile storage." 785 DEFVAL { enabled } 786 ::= { smfConfigurationGroup 1 } 788 smfRouterIDAddrType OBJECT-TYPE 789 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 790 MAX-ACCESS read-write 791 STATUS current 792 DESCRIPTION 793 "The address type of the address used for 794 SMF ID of this router as specified 795 in the 'smfRouterID' next. 797 Only the values ipv4(1) and ipv6(2) 798 are supported. 800 This can be set by the management station, 801 the smfRouterID must be a routable address 802 assigned to this router. If the management 803 station does not assign this value, then the 804 router should choose the highest routable 805 IP address assigned to this router. 807 This object is persistent and when written 808 the entity SHOULD save the change to 809 non-volatile storage." 810 DEFVAL { ipv4 } 811 ::= { smfConfigurationGroup 2 } 813 smfRouterID OBJECT-TYPE 814 SYNTAX InetAddress (SIZE(4|16)) 815 MAX-ACCESS read-write 816 STATUS current 817 DESCRIPTION 818 "The IP address used as the SMF router ID. 819 This can be set by the management station. 820 If not explicitly set, then the device 821 should select a routable IP address 822 assigned to this router for use as 823 the 'smfRouterID'. 825 The smfRouterID is a logical identification 826 that MUST be consistent across interoperable 827 SMF neighborhoods and it is RECOMMENDED to be 828 chosen as the numerically largest address 829 contained in a node's 'Neighbor Address List' 830 as defined in NHDP. A smfRouterID MUST be 831 unique within the scope of the operating 832 MANET network regardless of the method used 833 for selecting it. 835 This object is persistent and when written 836 the entity SHOULD save the change to 837 non-volatile storage." 838 REFERENCE 839 "RFC 6621 - Simplified Multicast Forwarding 840 (SMF), Macker, J., May 2012." 841 ::= { smfConfigurationGroup 3 } 843 smfConfiguredOpMode OBJECT-TYPE 844 SYNTAX SmfOpModeID 845 MAX-ACCESS read-write 846 STATUS current 847 DESCRIPTION 848 "The SMF RSS node operational mode as defined 849 in the TEXTUAL CONVENTION for `SmfOpModeID' 850 and in this MIB module. 852 The default value for this object is 853 'independent(1)'. 855 This object is persistent and when written 856 the entity SHOULD save the change to 857 non-volatile storage." 858 REFERENCE 859 "RFC 6621 - Simplified Multicast Forwarding 860 (SMF), Macker, J., May 2012." 861 DEFVAL { independent } 862 ::= { smfConfigurationGroup 4 } 864 smfConfiguredRssa OBJECT-TYPE 865 SYNTAX SmfRssaID 866 MAX-ACCESS read-write 867 STATUS current 868 DESCRIPTION 869 "The SMF RSS currently operational algorithm 870 as defined in the TEXTUAL CONVENTION for 871 `SmfRssaID' and in RFC 6621. 873 The deflaut value for this object is 874 'cF(1)', i.e., Classical Flooding. 876 This object is persistent and when written 877 the entity SHOULD save the change to 878 non-volatile storage." 879 REFERENCE 880 "RFC 6621 - Simplified Multicast Forwarding 881 (SMF), Macker, J., May 2012." 882 DEFVAL { cF } 883 ::= { smfConfigurationGroup 5 } 885 smfRssaMember OBJECT-TYPE 886 SYNTAX INTEGER { 887 potential(1), 888 always(2), 889 never(3) 890 } 891 MAX-ACCESS read-write 892 STATUS current 893 DESCRIPTION 894 "The RSSA downselects a set of forwarders for 895 multicast forwarding. Sometimes it is useful 896 to force an agent to be included or excluded 897 from the resulting RSS. This object is a 898 switch to allow for this behavior. 900 The value 'potential(1)' allows the selected 901 RSSA to determine if this agent is included 902 or excluded from the RSS. 904 The value 'always(1)' forces the selected 905 RSSA include this agent in the RSS. 907 The value 'never(3)' forces the selected 908 RSSA to exclude this agent from the RSS. 910 The default setting for this object is 911 'potential(1)'. Other settings could pose 912 operational risks under certain conditions. 914 This object is persistent and when written 915 the entity SHOULD save the change to 916 non-volatile storage." 917 REFERENCE 918 "RFC 6621 - Simplified Multicast Forwarding 919 (SMF), Macker, J., May 2012." 920 DEFVAL { potential } 921 ::= { smfConfigurationGroup 6 } 923 smfIpv4Dpd OBJECT-TYPE 924 SYNTAX INTEGER { 925 hashBased(1), 926 identificationBased(2) 927 } 928 MAX-ACCESS read-write 929 STATUS current 930 DESCRIPTION 931 "The current method for IPv4 duplicate packet 932 detection. 934 The value 'hashBased(1)' indicates that the 935 routers duplicate packet detection is based 936 upon comparing a hash over the packet fields. 937 This is the default setting for this object. 939 The value 'identificationBased(2)' 940 indicates that the duplicate packet 941 detection relies upon header information 942 in the multicast packets to identify 943 previously received packets. 945 This object is persistent and when written 946 the entity SHOULD save the change to 947 non-volatile storage." 948 REFERENCE 949 "RFC 6621 - Simplified Multicast Forwarding 950 (SMF), Macker, J., May 2012." 951 DEFVAL { hashBased } 952 ::= { smfConfigurationGroup 7 } 954 smfIpv6Dpd OBJECT-TYPE 955 SYNTAX INTEGER { 956 hashBased(1), 957 identificationBased(2) 958 } 959 MAX-ACCESS read-write 960 STATUS current 961 DESCRIPTION 962 "The current method for IPv6 duplicate packet 963 detection. 965 The values indicate the type of method used 966 for duplicate packet detection as described 967 the previous description for the object 968 `smfIpv4Dpd'. 970 The default value for this object is 971 'hashBased(1)'. 973 This object is persistent and when written 974 the entity SHOULD save the change to 975 non-volatile storage." 976 REFERENCE 977 "RFC 6621 - Simplified Multicast Forwarding 978 (SMF), Macker, J., May 2012." 979 DEFVAL { hashBased } 980 ::= { smfConfigurationGroup 8 } 982 smfMaxPktLifetime OBJECT-TYPE 983 SYNTAX Integer32 (0..65535) 984 UNITS "Seconds" 985 MAX-ACCESS read-write 986 STATUS current 987 DESCRIPTION 988 "The estimate of the network packet 989 traversal time. 991 This object is persistent and when written 992 the entity SHOULD save the change to 993 non-volatile storage." 994 REFERENCE 995 "RFC 6621 - Simplified Multicast Forwarding 996 (SMF), Macker, J., May 2012." 997 DEFVAL { 60 } 998 ::= { smfConfigurationGroup 9 } 1000 smfDpdMaxMemorySize OBJECT-TYPE 1001 SYNTAX Integer32 (0..65535) 1002 UNITS "Kilo-Bytes" 1003 MAX-ACCESS read-write 1004 STATUS current 1005 DESCRIPTION 1006 "The locally reserved memory for storage 1007 of cached DPD records for both IPv4 and 1008 IPv6 methods. 1010 The local SMF device should protect itself 1011 against the SNMP manager from requesting 1012 too large a memory value. If this is the case, 1013 an error indication should be returned in response 1014 to the SNMP SET request. 1016 This object is persistent and when written 1017 the entity SHOULD save the change to 1018 non-volatile storage." 1019 REFERENCE 1020 "RFC 6621 - Simplified Multicast Forwarding 1021 (SMF), Macker, J., May 2012." 1022 DEFVAL { 1024 } 1023 ::= { smfConfigurationGroup 10 } 1025 smfDpdEntryMaxLifetime OBJECT-TYPE 1026 SYNTAX Integer32 (0..65525) 1027 UNITS "Seconds" 1028 MAX-ACCESS read-write 1029 STATUS current 1030 DESCRIPTION 1031 "The maximum lifetime of a cached DPD 1032 record in the local device storage. 1034 If the memory is running low prior to the 1035 MaxLifetimes being exceeded, the local SMF 1036 devices should purge the oldest records first. 1038 This object is persistent and when written 1039 the entity SHOULD save the change to 1040 non-volatile storage." 1041 REFERENCE 1042 "RFC 6621 - Simplified Multicast Forwarding 1043 (SMF), Macker, J., May 2012." 1044 DEFVAL { 600 } 1045 ::= { smfConfigurationGroup 11 } 1047 -- 1048 -- Configuration of messages to be included in 1049 -- NHDP message exchanges in support of SMF 1050 -- operations. 1051 -- 1053 smfNhdpRssaMesgTLVIncluded OBJECT-TYPE 1054 SYNTAX TruthValue 1055 MAX-ACCESS read-write 1056 STATUS current 1057 DESCRIPTION 1058 "Indicates whether the associated NHDP messages 1059 include the RSSA Message TLV, or not. This 1060 is an optional SMF operational setting. 1061 The value 'true(1)' indicates that this TLV is 1062 included; the value 'false(2)' indicates that it 1063 is not included. 1065 It is RECOMMENDED that the RSSA Message TLV 1066 be included in the NHDP messages. 1068 This object is persistent and when written 1069 the entity SHOULD save the change to 1070 non-volatile storage." 1071 REFERENCE 1072 "RFC 6621 - Simplified Multicast Forwarding 1073 (SMF), Macker, J., May 2012." 1074 DEFVAL { true } 1075 ::= { smfConfigurationGroup 12 } 1077 smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 1078 SYNTAX TruthValue 1079 MAX-ACCESS read-write 1080 STATUS current 1081 DESCRIPTION 1082 "Indicates whether the associated NHDP messages 1083 include the RSSA Address Block TLV, or not. 1084 This is an optional SMF operational setting. 1085 The value 'true(1)' indicates that this TLV is 1086 included; the value 'false(2)' indicates that it 1087 is not included. 1089 The smfNhdpRssaAddrBlockTLVIncluded is optional 1090 in all cases as it depends on the existence of 1091 an address block which may not be present. 1092 If this SMF device is configured with NHDP, 1093 then this object SHOULD be set to 'true(1)'. 1095 This object is persistent and when written 1096 the entity SHOULD save the change to 1097 non-volatile storage." 1098 REFERENCE 1099 "RFC 6621 - Simplified Multicast Forwarding 1100 (SMF), Macker, J., May 2012." 1101 DEFVAL { true } 1102 ::= { smfConfigurationGroup 13 } 1104 -- 1105 -- Table identifying configured multicast addresses to be forwarded. 1107 -- 1109 smfConfiguredAddrForwardingTable OBJECT-TYPE 1110 SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry 1111 MAX-ACCESS not-accessible 1112 STATUS current 1113 DESCRIPTION 1114 "The (conceptual) table containing information on multicast 1115 addresses which are to be forwarded by the SMF process. 1117 Entries in this table are configured. As well, addresses 1118 to be forwarded by the SMF device can be dynamically 1119 discovered by other means. The corresponding state 1120 table, smfDiscoveredAddrForwardingTable, contains 1121 these additional, dynamically discovered address for 1122 forwarding. 1124 Each row is associated with a range of multicast 1125 addresses, and ranges for different rows must be disjoint. 1127 The objects in this table are persistent and when written 1128 the entity SHOULD save the change to 1129 non-volatile storage." 1130 REFERENCE 1131 "RFC 6621 - Simplified Multicast Forwarding 1132 (SMF), Macker, J., May 2012." 1133 ::= { smfConfigurationGroup 15 } 1135 smfConfiguredAddrForwardingEntry OBJECT-TYPE 1136 SYNTAX SmfConfiguredAddrForwardingEntry 1137 MAX-ACCESS not-accessible 1138 STATUS current 1139 DESCRIPTION 1140 "An entry (conceptual row) containing the information on a 1141 particular multicast scope." 1142 INDEX { smfConfiguredAddrForwardingAddrType, 1143 smfConfiguredAddrForwardingFirstAddr, 1144 smfConfiguredAddrForwardingLastAddr } 1145 ::= { smfConfiguredAddrForwardingTable 1 } 1147 SmfConfiguredAddrForwardingEntry ::= SEQUENCE { 1148 smfConfiguredAddrForwardingAddrType InetAddressType, 1149 smfConfiguredAddrForwardingFirstAddr InetAddress, 1150 smfConfiguredAddrForwardingLastAddr InetAddress, 1151 smfConfiguredAddrForwardingStatus RowStatus 1152 } 1154 smfConfiguredAddrForwardingAddrType OBJECT-TYPE 1155 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1156 MAX-ACCESS not-accessible 1157 STATUS current 1158 DESCRIPTION 1159 "The type of the addresses in the multicast forwarding 1160 range. Legal values correspond to the subset of 1161 address families for which multicast address allocation 1162 is supported. 1164 Only the values ipv4(1) and 1165 ipv6(2) are supported. 1167 This object is persistent and when written 1168 the entity SHOULD save the change to 1169 non-volatile storage." 1170 ::= { smfConfiguredAddrForwardingEntry 1 } 1172 smfConfiguredAddrForwardingFirstAddr OBJECT-TYPE 1173 SYNTAX InetAddress (SIZE(4|16)) 1174 MAX-ACCESS not-accessible 1175 STATUS current 1176 DESCRIPTION 1177 "The first address in the multicast scope range. The type 1178 of this address is determined by the value of the 1179 smfConfiguredAddrForwardingAddrType object. 1181 The value for this object must be less than or equal 1182 to the value entered for the 1183 smfConfiguredAddrForwardingLastAddr. 1185 This object is persistent and when written 1186 the entity SHOULD save the change to 1187 non-volatile storage." 1188 ::= { smfConfiguredAddrForwardingEntry 2 } 1190 smfConfiguredAddrForwardingLastAddr OBJECT-TYPE 1191 SYNTAX InetAddress (SIZE(4|16)) 1192 MAX-ACCESS not-accessible 1193 STATUS current 1194 DESCRIPTION 1195 "The last address in the multicast scope range. 1196 The type of this address is determined by the 1197 value of the smfConfiguredAddrForwardingAddrType 1198 object. 1200 The value for this object must be greater than or 1201 equal to the value entered for the 1202 smfConfiguredAddrForwardingFirstAddr. 1204 This object is persistent and when written 1205 the entity SHOULD save the change to 1206 non-volatile storage." 1207 ::= { smfConfiguredAddrForwardingEntry 3 } 1209 smfConfiguredAddrForwardingStatus OBJECT-TYPE 1210 SYNTAX RowStatus 1211 MAX-ACCESS read-create 1212 STATUS current 1213 DESCRIPTION 1214 "The status of this row, by which new entries may be 1215 created, or old entries deleted from this table." 1216 ::= { smfConfiguredAddrForwardingEntry 4 } 1218 -- 1219 -- SMF Interfaces Configuration Table 1220 -- 1222 smfInterfaceTable OBJECT-TYPE 1223 SYNTAX SEQUENCE OF SmfInterfaceEntry 1224 MAX-ACCESS not-accessible 1225 STATUS current 1226 DESCRIPTION 1227 "The SMF Interface Table describes the SMF 1228 interfaces that are participating in the 1229 SMF packet forwarding process. The ifIndex is 1230 from the interfaces group defined in the 1231 Interfaces Group MIB (RFC 2863). As such, 1232 this table 'sparse augments' the ifTable 1233 specifically when SMF is to be configured to 1234 operate over this interface. 1236 A conceptual row in this table exists if and only 1237 if either a manager has explicitly created the row 1238 or there is an interface on the managed device 1239 that supports and runs SMF. 1241 The manager can create a row by setting 1242 rowStatus to 'createAndGo' or 'createAndWait'. 1243 Row objects having associated DEFVAL clauses are 1244 automatically defined by the agent with these 1245 values during row creation, unless the manager 1246 explicitly defines these object values during the 1247 row creation. 1249 If the corresponding entry with ifIndex value 1250 is deleted from the Interface Table, then the entry 1251 in this table is automatically deleted and 1252 SMF is disabled on this interface, 1253 and all configuration and state information 1254 related to this interface is to be removed 1255 from memory. 1257 If the value of the smfAdminStatus object is changed 1258 from 'enabled' to 'disabled', then all rows in this 1259 table are to be deleted and all 1260 configuration and state information 1261 related to this interface is to be removed 1262 from memory." 1263 REFERENCE 1264 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1265 K., and F. Kastenholtz, June 2000." 1266 ::= { smfConfigurationGroup 16 } 1268 smfInterfaceEntry OBJECT-TYPE 1269 SYNTAX SmfInterfaceEntry 1270 MAX-ACCESS not-accessible 1271 STATUS current 1272 DESCRIPTION 1273 "The SMF interface entry describes one SMF 1274 interface as indexed by its ifIndex. 1276 The objects in this table are persistent and when 1277 written the device SHOULD save the change to 1278 non-volatile storage. For further information 1279 on the storage behavior for these objects, refer 1280 to the description for the smfIfRowStatus 1281 object." 1282 INDEX { smfIfIndex } 1283 ::= { smfInterfaceTable 1 } 1285 SmfInterfaceEntry ::= 1286 SEQUENCE { 1287 smfIfIndex InterfaceIndexOrZero, 1288 smfIfName DisplayString, 1289 smfIfAdminStatus SmfStatus, 1290 smfIfRowStatus RowStatus 1291 } 1293 smfIfIndex OBJECT-TYPE 1294 SYNTAX InterfaceIndexOrZero 1295 MAX-ACCESS not-accessible 1296 STATUS current 1297 DESCRIPTION 1298 "The ifIndex for this SMF interface. This value 1299 MUST correspond to an ifIndex referring 1300 to a valid entry in The Interfaces Table." 1301 REFERENCE 1302 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1303 K., and F. Kastenholtz, June 2000." 1304 ::= { smfInterfaceEntry 1 } 1306 smfIfName OBJECT-TYPE 1307 SYNTAX DisplayString 1308 MAX-ACCESS read-only 1309 STATUS current 1310 DESCRIPTION 1311 "The textual name of the interface. The value of this 1312 object should be the name of the interface as assigned by 1313 the local device and should be suitable for use in commands 1314 entered at the device's `console'. This might be a text 1315 name, such as `le0' or a simple port number, such as `1', 1316 depending on the interface naming syntax of the device. 1318 If there is no local name, or this object is otherwise 1319 not applicable, then this object contains 1320 a zero-length string." 1321 ::= { smfInterfaceEntry 2 } 1323 smfIfAdminStatus OBJECT-TYPE 1324 SYNTAX SmfStatus 1325 MAX-ACCESS read-create 1326 STATUS current 1327 DESCRIPTION 1328 "The SMF interface's administrative status. 1329 The value 'enabled' denotes that the interface 1330 is running the SMF forwarding process. 1331 The value 'disabled' denotes that the interface is 1332 currently external to the SMF forwarding process. 1334 The default value for this object is 'enabled(1)'. 1336 This object SHOULD be persistent and when 1337 written the device SHOULD save the change to 1338 non-volatile storage." 1339 DEFVAL { enabled } 1340 ::= { smfInterfaceEntry 3 } 1342 smfIfRowStatus OBJECT-TYPE 1343 SYNTAX RowStatus 1344 MAX-ACCESS read-create 1345 STATUS current 1346 DESCRIPTION 1347 "This object permits management of the table 1348 by facilitating actions such as row creation, 1349 construction, and destruction. The value of 1350 this object has no effect on whether other 1351 objects in this conceptual row can be 1352 modified. 1354 An entry may not exist in the active(1) state unless all 1355 objects in the entry have a defined appropriate value. For 1356 objects with DEFVAL clauses, the management station 1357 does not need to specify the value of this object in order 1358 for the row to transit to the active(1) state; the default 1359 value for this object is used. For objects that do not 1360 have DEFVAL clauses, then the network manager MUST 1361 specify the value of this object prior to this row 1362 transitioning to the active(1) state. 1364 When this object transitions to active(1), all objects 1365 in this row SHOULD be written to non-volatile (stable) 1366 storage. Read-create objects in this row MAY be modified. 1367 When an object in a row with smfIfRowStatus of active(1) 1368 is changed, then the updated value MUST be reflected in SMF 1369 and this new object value MUST be written to non-volatile 1370 storage. 1372 If this object is not equal to active(1), all associated 1373 entries in the smfIpv4InterfaceperfTable and the 1374 smfIpv6InterfacePerfTable MUST be deleted." 1375 ::= { smfInterfaceEntry 4 } 1377 -- 1378 -- smfStateGroup 1379 -- 1380 -- Contains information describing the current state of the SMF 1381 -- process such as the current inclusion in the RS or not. 1382 -- 1384 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1386 smfNodeRsStatusIncluded OBJECT-TYPE 1387 SYNTAX TruthValue 1388 MAX-ACCESS read-only 1389 STATUS current 1390 DESCRIPTION 1391 "The current status of the SMF node in the context of 1392 the MANETs relay set. A value of 'true(1)' indicates 1393 that the node is currently part of the MANET Relay 1394 Set. A value of 'false(2)' indicates that the node 1395 is currently not part of the MANET Relay Set." 1396 REFERENCE 1397 "RFC 6621 - Simplified Multicast Forwarding 1398 (SMF), Macker, J., May 2012." 1399 ::= { smfStateGroup 1 } 1401 smfDpdMemoryOverflow OBJECT-TYPE 1402 SYNTAX Counter32 1403 UNITS "Overruns" 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "The number of times that the memory for caching 1408 records for DPD overran and records had to be flushed. 1409 The number of records to be flushed upon a buffer 1410 overflow is an implementation specific decision." 1411 REFERENCE 1412 "RFC 6621 - Simplified Multicast Forwarding 1413 (SMF), Macker, J., May 2012." 1414 ::= { smfStateGroup 2 } 1416 -- 1417 -- Dynamically Discovered Multicast Addr Table 1418 -- 1420 smfDiscoveredAddrForwardingTable OBJECT-TYPE 1421 SYNTAX SEQUENCE OF SmfDiscoveredAddrForwardingEntry 1422 MAX-ACCESS not-accessible 1423 STATUS current 1424 DESCRIPTION 1425 "This state table, smfDiscoveredAddrForwardingTable, 1426 contains additional, dynamically discovered addresses 1427 for forwarding. 1429 Each row is associated with a range of 1430 multicast addresses, and ranges for different rows 1431 must be disjoint." 1432 REFERENCE 1433 "RFC 6621 - Simplified Multicast Forwarding 1434 (SMF), Macker, J., May 2012." 1435 ::= { smfStateGroup 3 } 1437 smfDiscoveredAddrForwardingEntry OBJECT-TYPE 1438 SYNTAX SmfDiscoveredAddrForwardingEntry 1439 MAX-ACCESS not-accessible 1440 STATUS current 1441 DESCRIPTION 1442 "An entry (conceptual row) containing the information on a 1443 particular multicast scope." 1444 INDEX { smfDiscoveredAddrForwardingAddrType, 1445 smfDiscoveredAddrForwardingFirstAddr, 1446 smfDiscoveredAddrForwardingLastAddr } 1447 ::= { smfDiscoveredAddrForwardingTable 1 } 1449 SmfDiscoveredAddrForwardingEntry ::= SEQUENCE { 1450 smfDiscoveredAddrForwardingAddrType InetAddressType, 1451 smfDiscoveredAddrForwardingFirstAddr InetAddress, 1452 smfDiscoveredAddrForwardingLastAddr InetAddress, 1453 smfDiscoveredAddrForwardingSource SnmpAdminString 1454 } 1456 smfDiscoveredAddrForwardingAddrType OBJECT-TYPE 1457 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1458 MAX-ACCESS not-accessible 1459 STATUS current 1460 DESCRIPTION 1461 "The type of the addresses in the multicast forwarding 1462 range. Legal values correspond to the subset of 1463 address families for which multicast address allocation 1464 is supported. 1466 Only the values ipv4(1) and 1467 ipv6(2) are supported." 1468 ::= { smfDiscoveredAddrForwardingEntry 1 } 1470 smfDiscoveredAddrForwardingFirstAddr OBJECT-TYPE 1471 SYNTAX InetAddress (SIZE(4|16)) 1472 MAX-ACCESS not-accessible 1473 STATUS current 1474 DESCRIPTION 1475 "The first address in the multicast scope range. The type 1476 of this address is determined by the value of the 1477 smfConfiguredAddrForwardingAddrType object. 1479 The value for this object must be less than or 1480 equal to the value entered for the 1481 smfDiscoveredAddrForwardingLastAddr." 1482 ::= { smfDiscoveredAddrForwardingEntry 2 } 1484 smfDiscoveredAddrForwardingLastAddr OBJECT-TYPE 1485 SYNTAX InetAddress (SIZE(4|16)) 1486 MAX-ACCESS not-accessible 1487 STATUS current 1488 DESCRIPTION 1489 "The last address in the multicast scope range. 1490 The type of this address is determined by the 1491 value of the smfConfiguredAddrForwardingAddrType 1492 object. 1494 The value for this object must be greater than or 1495 equal to the value entered for the 1496 smfDiscoveredAddrForwardingFirstAddr." 1497 ::= { smfDiscoveredAddrForwardingEntry 3 } 1499 smfDiscoveredAddrForwardingSource OBJECT-TYPE 1500 SYNTAX SnmpAdminString 1501 MAX-ACCESS read-only 1502 STATUS current 1503 DESCRIPTION 1504 "The textual description of the method by which 1505 this multicast address range was discovered." 1506 ::= { smfDiscoveredAddrForwardingEntry 4 } 1508 -- 1509 -- SMF Neighbor Table 1510 -- 1512 smfNeighborTable OBJECT-TYPE 1513 SYNTAX SEQUENCE OF SmfNeighborEntry 1514 MAX-ACCESS not-accessible 1515 STATUS current 1516 DESCRIPTION 1517 "The SMF NeighborTable describes the 1518 current one-hop neighbor nodes, their address 1519 and SMF RSSA and the interface on which 1520 they can be reached." 1521 REFERENCE 1522 "RFC 6621 - Simplified Multicast Forwarding 1523 (SMF), Macker, J., May 2012. 1524 Section 7: SMF Neighborhood Discovery 1525 Requirements." 1526 ::= { smfStateGroup 4 } 1528 smfNeighborEntry OBJECT-TYPE 1529 SYNTAX SmfNeighborEntry 1530 MAX-ACCESS not-accessible 1531 STATUS current 1532 DESCRIPTION 1533 "The SMF Neighbor Table contains the 1534 set of one-hop neighbors, the interface 1535 they are reachable on and the SMF RSSA 1536 they are currently running." 1537 INDEX { smfNeighborIpAddrType, 1538 smfNeighborIpAddr, 1539 smfNeighborPrefixLen } 1540 ::= { smfNeighborTable 1 } 1542 SmfNeighborEntry ::= 1543 SEQUENCE { 1544 smfNeighborIpAddrType InetAddressType, 1545 smfNeighborIpAddr InetAddress, 1546 smfNeighborPrefixLen InetAddressPrefixLength, 1547 smfNeighborRSSA SmfRssaID, 1548 smfNeighborNextHopInterface InterfaceIndexOrZero 1549 } 1551 smfNeighborIpAddrType OBJECT-TYPE 1552 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1553 MAX-ACCESS not-accessible 1554 STATUS current 1555 DESCRIPTION 1556 "The one-hop neighbor IP address type. 1558 Only the values 'ipv4(1)' and 1559 'ipv6(2)' are supported." 1560 ::= { smfNeighborEntry 1 } 1562 smfNeighborIpAddr OBJECT-TYPE 1563 SYNTAX InetAddress (SIZE(4|16)) 1564 MAX-ACCESS not-accessible 1565 STATUS current 1566 DESCRIPTION 1567 "The one-hop neighbor Inet IPv4 or IPv6 1568 address. 1570 Only IPv4 and IPv6 addresses 1571 are supported." 1572 ::= { smfNeighborEntry 2 } 1574 smfNeighborPrefixLen OBJECT-TYPE 1575 SYNTAX InetAddressPrefixLength 1576 UNITS "bits" 1577 MAX-ACCESS not-accessible 1578 STATUS current 1579 DESCRIPTION 1580 "The prefix length. This is a decimal value that 1581 indicates the number of contiguous, higher-order 1582 bits of the address that make up the network 1583 portion of the address." 1584 ::= { smfNeighborEntry 3 } 1586 smfNeighborRSSA OBJECT-TYPE 1587 SYNTAX SmfRssaID 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "The current RSSA running on the neighbor. 1592 The list is identical to that described 1593 above for the smfRssa object." 1594 ::= { smfNeighborEntry 4 } 1596 smfNeighborNextHopInterface OBJECT-TYPE 1597 SYNTAX InterfaceIndexOrZero 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "The interface ifIndex over which the 1602 neighbor is reachable in one-hop." 1603 ::= { smfNeighborEntry 5 } 1605 -- 1606 -- SMF Performance Group 1607 -- 1608 -- Contains objects which help to characterize the 1609 -- performance of the SMF RSSA process, such as statistics 1610 -- counters. There are two types of SMF RSSA statistics: 1611 -- global counters and per interface counters. 1612 -- 1614 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1616 smfGlobalPerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1618 -- 1619 -- IPv4 packet counters 1620 -- 1622 smfIpv4MultiPktsRecvTotal OBJECT-TYPE 1623 SYNTAX Counter32 1624 UNITS "Packets" 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "A counter of the total number of 1629 multicast IPv4 packets received by the 1630 device and delivered to the SMF process." 1631 REFERENCE 1632 "RFC 6621 - Simplified Multicast Forwarding 1633 (SMF), Macker, J., May 2012." 1634 ::= { smfGlobalPerfGroup 1 } 1636 smfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1637 SYNTAX Counter32 1638 UNITS "Packets" 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "A counter of the total number of 1643 multicast IPv4 packets forwarded by the 1644 device." 1645 REFERENCE 1646 "RFC 6621 - Simplified Multicast Forwarding 1647 (SMF), Macker, J., May 2012." 1648 ::= { smfGlobalPerfGroup 2 } 1650 smfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1651 SYNTAX Counter32 1652 UNITS "Packets" 1653 MAX-ACCESS read-only 1654 STATUS current 1655 DESCRIPTION 1656 "A counter of the total number of duplicate 1657 multicast IPv4 packets detected by the 1658 device." 1659 REFERENCE 1660 "RFC 6621 - Simplified Multicast Forwarding 1661 (SMF), Macker, J., May 2012." 1662 ::= { smfGlobalPerfGroup 3 } 1664 smfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1665 SYNTAX Counter32 1666 UNITS "Packets" 1667 MAX-ACCESS read-only 1668 STATUS current 1669 DESCRIPTION 1670 "A counter of the total number of dropped 1671 multicast IPv4 packets by the 1672 device due to TTL exceeded." 1673 REFERENCE 1674 "RFC 6621 - Simplified Multicast Forwarding 1675 (SMF), Macker, J., May 2012." 1676 ::= { smfGlobalPerfGroup 4 } 1678 smfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1679 SYNTAX Counter32 1680 UNITS "Packets" 1681 MAX-ACCESS read-only 1682 STATUS current 1683 DESCRIPTION 1684 "A counter of the total number of IPv4 packets 1685 recieved which have a TTL larger than that 1686 of a previously received identical packet." 1687 REFERENCE 1688 "RFC 6621 - Simplified Multicast Forwarding 1689 (SMF), Macker, J., May 2012." 1690 ::= { smfGlobalPerfGroup 5 } 1692 -- 1693 -- IPv6 packet counters 1694 -- 1696 smfIpv6MultiPktsRecvTotal OBJECT-TYPE 1697 SYNTAX Counter32 1698 UNITS "Packets" 1699 MAX-ACCESS read-only 1700 STATUS current 1701 DESCRIPTION 1702 "A counter of the total number of 1703 multicast IPv6 packets received by the 1704 device and delivered to the SMF process." 1705 REFERENCE 1706 "RFC 6621 - Simplified Multicast Forwarding 1707 (SMF), Macker, J., May 2012." 1708 ::= { smfGlobalPerfGroup 6 } 1710 smfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1711 SYNTAX Counter32 1712 UNITS "Packets" 1713 MAX-ACCESS read-only 1714 STATUS current 1715 DESCRIPTION 1716 "A counter of the total number of 1717 multicast IPv6 packets forwarded by the 1718 device." 1719 REFERENCE 1720 "RFC 6621 - Simplified Multicast Forwarding 1721 (SMF), Macker, J., May 2012." 1723 ::= { smfGlobalPerfGroup 7 } 1725 smfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1726 SYNTAX Counter32 1727 UNITS "Packets" 1728 MAX-ACCESS read-only 1729 STATUS current 1730 DESCRIPTION 1731 "A counter of the total number of duplicate 1732 multicast IPv6 packets detected by the 1733 device." 1734 REFERENCE 1735 "RFC 6621 - Simplified Multicast Forwarding 1736 (SMF), Macker, J., May 2012." 1737 ::= { smfGlobalPerfGroup 8 } 1739 smfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1740 SYNTAX Counter32 1741 UNITS "Packets" 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "A counter of the total number of dropped 1746 multicast IPv6 packets by the 1747 device due to TTL exceeded." 1748 REFERENCE 1749 "RFC 6621 - Simplified Multicast Forwarding 1750 (SMF), Macker, J., May 2012." 1751 ::= { smfGlobalPerfGroup 9 } 1753 smfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1754 SYNTAX Counter32 1755 UNITS "Packets" 1756 MAX-ACCESS read-only 1757 STATUS current 1758 DESCRIPTION 1759 "A counter of the total number of IPv6 packets 1760 recieved which have a TTL larger than that 1761 of a previously recived identical packet." 1762 REFERENCE 1763 "RFC 6621 - Simplified Multicast Forwarding 1764 (SMF), Macker, J., May 2012." 1765 ::= { smfGlobalPerfGroup 10 } 1767 smfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1768 SYNTAX Counter32 1769 UNITS "Packets" 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "A counter of the total number of IPv6 packets 1774 received which required the HAV assist for DPD." 1775 REFERENCE 1776 "RFC 6621 - Simplified Multicast Forwarding 1777 (SMF), Macker, J., May 2012." 1778 ::= { smfGlobalPerfGroup 11 } 1780 smfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1781 SYNTAX Counter32 1782 UNITS "Packets" 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "A counter of the total number of IPv6 packets 1787 recieved which the device inserted the 1788 DPD header option." 1789 REFERENCE 1790 "RFC 6621 - Simplified Multicast Forwarding 1791 (SMF), Macker, J., May 2012." 1792 ::= { smfGlobalPerfGroup 12 } 1794 -- 1795 -- Per SMF Interface Performance Table 1796 -- 1798 smfInterfacePerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1800 smfIpv4InterfacePerfTable OBJECT-TYPE 1801 SYNTAX SEQUENCE OF SmfIpv4InterfacePerfEntry 1802 MAX-ACCESS not-accessible 1803 STATUS current 1804 DESCRIPTION 1805 "The SMF Interface Performance Table 1806 describes the SMF counters per 1807 interface." 1808 REFERENCE 1809 "RFC 6621 - Simplified Multicast Forwarding 1810 (SMF), Macker, J., May 2012." 1811 ::= { smfInterfacePerfGroup 1 } 1813 smfIpv4InterfacePerfEntry OBJECT-TYPE 1814 SYNTAX SmfIpv4InterfacePerfEntry 1815 MAX-ACCESS not-accessible 1816 STATUS current 1817 DESCRIPTION 1818 "The SMF Interface Performance entry 1819 describes the statistics for a particular 1820 node interface." 1821 INDEX { smfIfIndex } 1822 ::= { smfIpv4InterfacePerfTable 1 } 1824 SmfIpv4InterfacePerfEntry ::= 1825 SEQUENCE { 1826 smfIpv4MultiPktsRecvPerIf Counter32, 1827 smfIpv4MultiPktsForwardedPerIf Counter32, 1828 smfIpv4DuplMultiPktsDetectedPerIf Counter32, 1829 smfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1830 smfIpv4TTLLargerThanPreviousPerIf Counter32 1831 } 1833 smfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1834 SYNTAX Counter32 1835 UNITS "Packets" 1836 MAX-ACCESS read-only 1837 STATUS current 1838 DESCRIPTION 1839 "A counter of the number of 1840 multicast IP packets received by the 1841 SMF process on this device on 1842 this interface." 1843 ::= { smfIpv4InterfacePerfEntry 1 } 1845 smfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1846 SYNTAX Counter32 1847 UNITS "Packets" 1848 MAX-ACCESS read-only 1849 STATUS current 1850 DESCRIPTION 1851 "A counter of the number of 1852 multicast IP packets forwarded by the 1853 SMF process on this device 1854 on this interface." 1855 ::= { smfIpv4InterfacePerfEntry 2 } 1857 smfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1858 SYNTAX Counter32 1859 UNITS "Packets" 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 SMF process on this device 1866 on this interface." 1867 ::= { smfIpv4InterfacePerfEntry 3 } 1869 smfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1870 SYNTAX Counter32 1871 UNITS "Packets" 1872 MAX-ACCESS read-only 1873 STATUS current 1874 DESCRIPTION 1875 "A counter of the total number of dropped 1876 multicast IPv4 packets by the SMF process 1877 on this device on this interface 1878 due to TTL exceeded." 1879 ::= { smfIpv4InterfacePerfEntry 4 } 1881 smfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1882 SYNTAX Counter32 1883 UNITS "Packets" 1884 MAX-ACCESS read-only 1885 STATUS current 1886 DESCRIPTION 1887 "A counter of the total number of IPv4 packets 1888 received by the SMF process on this device 1889 on this interface which have a TTL larger than 1890 that of a previously recived identical packet." 1891 ::= { smfIpv4InterfacePerfEntry 5 } 1893 smfIpv6InterfacePerfTable OBJECT-TYPE 1894 SYNTAX SEQUENCE OF SmfIpv6InterfacePerfEntry 1895 MAX-ACCESS not-accessible 1896 STATUS current 1897 DESCRIPTION 1898 "The SMF Interface Performance Table 1899 describes the SMF counters per 1900 interface." 1901 REFERENCE 1902 "RFC 6621 - Simplified Multicast Forwarding 1903 (SMF), Macker, J., May 2012." 1904 ::= { smfInterfacePerfGroup 2 } 1906 smfIpv6InterfacePerfEntry OBJECT-TYPE 1907 SYNTAX SmfIpv6InterfacePerfEntry 1908 MAX-ACCESS not-accessible 1909 STATUS current 1910 DESCRIPTION 1911 "The SMF Interface Performance entry 1912 describes the counters for a particular 1913 node interface." 1914 INDEX { smfIfIndex } 1915 ::= { smfIpv6InterfacePerfTable 1 } 1917 SmfIpv6InterfacePerfEntry ::= 1918 SEQUENCE { 1919 smfIpv6MultiPktsRecvPerIf Counter32, 1920 smfIpv6MultiPktsForwardedPerIf Counter32, 1921 smfIpv6DuplMultiPktsDetectedPerIf Counter32, 1922 smfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1923 smfIpv6TTLLargerThanPreviousPerIf Counter32, 1924 smfIpv6HAVAssistsReqdPerIf Counter32, 1925 smfIpv6DpdHeaderInsertionsPerIf Counter32 1926 } 1928 smfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1929 SYNTAX Counter32 1930 UNITS "Packets" 1931 MAX-ACCESS read-only 1932 STATUS current 1933 DESCRIPTION 1934 "A counter of the number of 1935 multicast IP packets received by the 1936 SMF process on this device 1937 on this interface." 1938 ::= { smfIpv6InterfacePerfEntry 1 } 1940 smfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 1941 SYNTAX Counter32 1942 UNITS "Packets" 1943 MAX-ACCESS read-only 1944 STATUS current 1945 DESCRIPTION 1946 "A counter of the number of 1947 multicast IP packets forwarded by the 1948 SMF process on this device 1949 on this interface." 1950 ::= { smfIpv6InterfacePerfEntry 2 } 1952 smfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 1953 SYNTAX Counter32 1954 UNITS "Packets" 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "A counter of the number of duplicate 1959 multicast IP packets detected by the 1960 SMF process on this device 1961 on this interface." 1962 ::= { smfIpv6InterfacePerfEntry 3 } 1964 smfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1965 SYNTAX Counter32 1966 UNITS "Packets" 1967 MAX-ACCESS read-only 1968 STATUS current 1969 DESCRIPTION 1970 "A counter of the number of dropped 1971 multicast IP packets by the 1972 SMF process on this device 1973 on this interface due to TTL 1974 exceeded." 1975 ::= { smfIpv6InterfacePerfEntry 4 } 1977 smfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 1978 SYNTAX Counter32 1979 UNITS "Packets" 1980 MAX-ACCESS read-only 1981 STATUS current 1982 DESCRIPTION 1983 "A counter of the total number of IPv6 packets 1984 received which have a TTL larger than that 1985 of a previously received identical packet 1986 by the SMF process on this device on this 1987 interface." 1988 ::= { smfIpv6InterfacePerfEntry 5 } 1990 smfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 1991 SYNTAX Counter32 1992 UNITS "Packets" 1993 MAX-ACCESS read-only 1994 STATUS current 1995 DESCRIPTION 1996 "A counter of the total number of IPv6 packets 1997 received by the SMF process on this device 1998 on this interface which required the 1999 HAV assist for DPD." 2000 ::= { smfIpv6InterfacePerfEntry 6 } 2002 smfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 2003 SYNTAX Counter32 2004 UNITS "Packets" 2005 MAX-ACCESS read-only 2006 STATUS current 2007 DESCRIPTION 2008 "A counter of the total number of IPv6 packets 2009 received by the SMF process on this device 2010 on this interface which the device inserted the 2011 DPD header option." 2012 ::= { smfIpv6InterfacePerfEntry 7 } 2014 -- 2015 -- Notifications 2016 -- 2018 smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 0 } 2019 smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 } 2021 -- smfMIBNotifObjects 2023 smfAdminStatusChange NOTIFICATION-TYPE 2024 OBJECTS { smfRouterIDAddrType, -- The originator of 2025 -- the notification. 2026 smfRouterID, -- The originator of 2027 -- the notification. 2028 smfAdminStatus -- The new status of the 2029 -- SMF process. 2030 } 2031 STATUS current 2032 DESCRIPTION 2033 "smfAdminStatusChange is a notification sent when a 2034 the 'smfAdminStatus' object changes." 2035 ::= { smfMIBNotifObjects 1 } 2037 smfConfiguredOpModeChange NOTIFICATION-TYPE 2038 OBJECTS { smfRouterIDAddrType, -- The originator of 2039 -- the notification. 2040 smfRouterID, -- The originator of 2041 -- the notification. 2042 smfConfiguredOpMode -- The new Operations 2043 -- Mode of the SMF 2044 -- process. 2045 } 2046 STATUS current 2047 DESCRIPTION 2048 "smfConfiguredOpModeChange is a notification 2049 sent when a the 'smfConfiguredOpMode' object 2050 changes." 2051 ::= { smfMIBNotifObjects 2 } 2053 smfConfiguredRssaChange NOTIFICATION-TYPE 2054 OBJECTS { smfRouterIDAddrType, -- The originator of 2055 -- the notification. 2056 smfRouterID, -- The originator of 2057 -- the notification. 2058 smfConfiguredRssa -- The new RSSA for 2059 -- the SMF process. 2060 } 2061 STATUS current 2062 DESCRIPTION 2063 "smfAdminStatusChange is a notification sent when a 2064 the 'smfConfiguredRssa' object changes." 2065 ::= { smfMIBNotifObjects 3 } 2067 smfIfAdminStatusChange NOTIFICATION-TYPE 2068 OBJECTS { smfRouterIDAddrType, -- The originator of 2069 -- the notification. 2070 smfRouterID, -- The originator of 2071 -- the notification. 2072 smfIfName, -- The interface whose 2073 -- status has changed. 2074 smfIfAdminStatus -- The new status of the 2075 -- SMF interface. 2076 } 2077 STATUS current 2078 DESCRIPTION 2079 "smfIfAdminStatusChange is a notification sent when a 2080 the 'smfIfAdminStatus' object changes." 2081 ::= { smfMIBNotifObjects 4 } 2083 smfDpdMemoryOverflowEvent NOTIFICATION-TYPE 2084 OBJECTS { smfRouterIDAddrType, -- The originator of 2085 -- the notification. 2086 smfRouterID, -- The originator of 2087 -- the notification. 2088 smfDpdMemoryOverflow -- The counter of 2089 -- the overflows. 2090 } 2091 STATUS current 2092 DESCRIPTION 2093 "smfDpdMemoryOverflowEvents is sent when the 2094 number of memory overflow events exceeds the 2095 the 'smfDpdMemoryOverflowThreshold' within the 2096 previous number of seconds defined by the 2097 'smfDpdMemoryOverflowWindow'." 2098 ::= { smfMIBNotifObjects 5 } 2100 -- smfMIBNotifControl 2101 smfDpdMemoryOverflowThreshold OBJECT-TYPE 2102 SYNTAX Integer32 (0..255) 2103 UNITS "Events" 2104 MAX-ACCESS read-write 2105 STATUS current 2106 DESCRIPTION 2107 "A threshold value for the 2108 `smfDpdmemoryOverflowEvents' object. 2109 If the number of occurences exceeds 2110 this threshold within the previous 2111 number of seconds 2112 'smfDpdMemoryOverflowWindow', 2113 then the `smfDpdMemoryOverflowEvent' 2114 notification is sent. 2116 The default value for this object is 2117 '1'." 2118 DEFVAL { 1 } 2119 ::= { smfMIBNotifControl 1 } 2121 smfDpdMemoryOverflowWindow OBJECT-TYPE 2122 SYNTAX TimeTicks 2123 MAX-ACCESS read-write 2124 STATUS current 2125 DESCRIPTION 2126 "A time window value for the 2127 `smfDpdmemoryOverflowEvents' object. 2128 If the number of occurences exceeds 2129 the `smfDpdMemoryOverflowThreshold' 2130 within the previous number of seconds 2131 'smfDpdMemoryOverflowWindow', 2132 then the `smfDpdMemoryOverflowEvent' 2133 notification is sent. 2135 The default value for this object is 2136 '1'." 2137 DEFVAL { 1 } 2138 ::= { smfMIBNotifControl 2 } 2140 -- 2141 -- Compliance Statements 2142 -- 2144 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2145 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2146 smfBasicCompliance MODULE-COMPLIANCE 2147 STATUS current 2148 DESCRIPTION "The basic 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 ::= { smfCompliances 1 } 2156 smfFullCompliance MODULE-COMPLIANCE 2157 STATUS current 2158 DESCRIPTION "The full implementation requirements for 2159 managed network entities that implement 2160 the SMF RSSA process." 2161 MODULE -- this module 2162 MANDATORY-GROUPS { smfCapabObjectsGroup, 2163 smfConfigObjectsGroup, 2164 smfStateObjectsGroup, 2165 smfPerfObjectsGroup, 2166 smfNotifObjectsGroup, 2167 smfNotificationsGroup 2168 } 2169 ::= { smfCompliances 2 } 2171 -- 2172 -- Units of Conformance 2173 -- 2175 smfCapabObjectsGroup OBJECT-GROUP 2176 OBJECTS { 2177 smfOpModeCapabilitiesName, 2178 smfOpModeCapabilitiesReference, 2180 smfRssaCapabilitiesName, 2181 smfRssaCapabilitiesReference 2182 } 2183 STATUS current 2184 DESCRIPTION 2185 "Set of SMF configuration objects implemented 2186 in this module." 2187 ::= { smfMIBGroups 1 } 2189 smfConfigObjectsGroup OBJECT-GROUP 2190 OBJECTS { 2191 smfAdminStatus, 2192 smfRouterIDAddrType, 2193 smfRouterID, 2194 smfIfName, 2195 smfConfiguredOpMode, 2196 smfConfiguredRssa, 2197 smfRssaMember, 2198 smfIpv4Dpd, 2199 smfIpv6Dpd, 2200 smfMaxPktLifetime, 2201 smfDpdMaxMemorySize, 2202 smfDpdEntryMaxLifetime, 2203 smfNhdpRssaMesgTLVIncluded, 2204 smfNhdpRssaAddrBlockTLVIncluded, 2206 smfConfiguredAddrForwardingStatus, 2208 smfIfAdminStatus, 2209 smfIfRowStatus 2210 } 2211 STATUS current 2212 DESCRIPTION 2213 "Set of SMF configuration objects implemented 2214 in this module." 2215 ::= { smfMIBGroups 2 } 2217 smfStateObjectsGroup OBJECT-GROUP 2218 OBJECTS { 2219 smfNodeRsStatusIncluded, 2220 smfDpdMemoryOverflow, 2222 smfDiscoveredAddrForwardingSource, 2224 smfNeighborRSSA, 2225 smfNeighborNextHopInterface 2226 } 2227 STATUS current 2228 DESCRIPTION 2229 "Set of SMF state objects implemented 2230 in this module." 2231 ::= { smfMIBGroups 3 } 2233 smfPerfObjectsGroup OBJECT-GROUP 2234 OBJECTS { 2235 smfIpv4MultiPktsRecvTotal, 2236 smfIpv4MultiPktsForwardedTotal, 2237 smfIpv4DuplMultiPktsDetectedTotal, 2238 smfIpv4DroppedMultiPktsTTLExceededTotal, 2239 smfIpv4TTLLargerThanPreviousTotal, 2241 smfIpv6MultiPktsRecvTotal, 2242 smfIpv6MultiPktsForwardedTotal, 2243 smfIpv6DuplMultiPktsDetectedTotal, 2244 smfIpv6DroppedMultiPktsTTLExceededTotal, 2245 smfIpv6TTLLargerThanPreviousTotal, 2246 smfIpv6HAVAssistsReqdTotal, 2247 smfIpv6DpdHeaderInsertionsTotal, 2249 smfIpv4MultiPktsRecvPerIf, 2250 smfIpv4MultiPktsForwardedPerIf, 2251 smfIpv4DuplMultiPktsDetectedPerIf, 2252 smfIpv4DroppedMultiPktsTTLExceededPerIf, 2253 smfIpv4TTLLargerThanPreviousPerIf, 2255 smfIpv6MultiPktsRecvPerIf, 2256 smfIpv6MultiPktsForwardedPerIf, 2257 smfIpv6DuplMultiPktsDetectedPerIf, 2258 smfIpv6DroppedMultiPktsTTLExceededPerIf, 2259 smfIpv6TTLLargerThanPreviousPerIf, 2260 smfIpv6HAVAssistsReqdPerIf, 2261 smfIpv6DpdHeaderInsertionsPerIf 2262 } 2263 STATUS current 2264 DESCRIPTION 2265 "Set of SMF performance objects implemented 2266 in this module by total and per interface." 2267 ::= { smfMIBGroups 4 } 2269 smfNotifObjectsGroup OBJECT-GROUP 2270 OBJECTS { 2271 smfDpdMemoryOverflowThreshold, 2272 smfDpdMemoryOverflowWindow 2273 } 2274 STATUS current 2275 DESCRIPTION 2276 "Set of SMF notification control 2277 objects implemented in this module." 2278 ::= { smfMIBGroups 5 } 2280 smfNotificationsGroup NOTIFICATION-GROUP 2281 NOTIFICATIONS { 2282 smfAdminStatusChange, 2283 smfConfiguredOpModeChange, 2284 smfConfiguredRssaChange, 2285 smfIfAdminStatusChange, 2286 smfDpdMemoryOverflowEvent 2287 } 2288 STATUS current 2289 DESCRIPTION 2290 "Set of SMF notifications implemented 2291 in this module." 2292 ::= { smfMIBGroups 6 } 2294 END 2296 8. Security Considerations 2298 This section discusses security implications of the choices made in 2299 this SMF-MIB module. 2301 There are a number of management objects defined in this MIB module 2302 with a MAX-ACCESS clause of read-write and/or read-create. Such 2303 objects may be considered sensitive or vulnerable in some network 2304 environments. The support for SET operations in a non-secure 2305 environment without proper protection can have a negative effect on 2306 network operations. These are the tables and objects and their 2307 sensitivity/vulnerability: 2309 o 'smfAdminStatus' - this writable configuration object controls the 2310 operational status of the SMF process. If this setting is 2311 configured inconsistently across the MANET multicast domain, then 2312 delivery of multicast data may be inconsistent across the domain; 2313 some nodes may not receive multicast data intended for them. 2315 o 'smfRouterIDAddrType' and 'smfRouterID' - these writable 2316 configuration objects define the ID of the SMF process. These 2317 objects should be configured with a routable address defined on 2318 the local SMF device. The smfRouterID is a logical identification 2319 that MUST be configured as unique across inter-operating SMF 2320 neighborhoods and it is RECOMMENDED to be chosen as the 2321 numerically largest address contained in a node's 'Neighbor 2322 Address List' as defined in NHDP. A smfRouterID MUST be unique 2323 within the scope of the operating MANET network regardless of the 2324 method used for selecting it. 2326 o 'smfConfiguredOpMode' - this writable configuration objects define 2327 the operational mode of the SMF process. The operational mode 2328 defines how the SMF process develops its local estimate of the 2329 CDS. 2331 o 'smfConfiguredRssa' - this writable configuration object sets the 2332 specific Reduced Set Selection Algorithm (RSSA) for the SMF 2333 process. If this object is set inconsistently across the MANET 2334 domain, multicast delivery of data will fail. 2336 o 'smfRssaMember' - this writable configuration object sets the 2337 'interest' of the local SMF node in participating in the CDS. 2338 Setting this object to 'never(3)' on a highly highly connected 2339 device could lead to frequent island formation. Setting this 2340 object to 'always(2)' could support data ex-filtration from the 2341 MANET domain. 2343 o 'smfIpv4Dpd' - this writable configuration object sets the 2344 duplicate packet detection method for forwarding of IPv4 multicast 2345 packets. 2347 o 'smfIpv6Dpd' - this writable configuration object sets the 2348 duplicate packet detection method for forwarding of IPv6 multicast 2349 packets. 2351 o 'smfMaxPktLifetime' - this writable configuration object sets the 2352 estimate of the network packet traversal time. If set too small, 2353 this could lead to poor multicast data delivery ratios throughout 2354 the MANET domain. 2356 o 'smfDpdMaxMemorySize' - this writable configuration object sets 2357 the memory storage size (in Kilo-Bytes) for the cached DPD records 2358 for the combined IPv4 and IPv6 methods. If set too small this 2359 could lead to poor performance of the duplicate packet protection 2360 algorithms and lead to inefficient resource, e.g., link, 2361 utilization within the MANET domain. The local SMF device should 2362 protect itself against memory overruns in the event that too large 2363 a setting is requested. 2365 o 'smfDpdEntryMaxLifetime' - this writable configuration object sets 2366 the maximum lifetime (in seconds) for the cached DPD records for 2367 the combined IPv4 and IPv6 methods. If the memory is running low 2368 prior to the MaxLifetimes being exceeded, the local SMF devices 2369 should purge the oldest records first. 2371 o 'smfNhdpRssaMesgTLVIncluded' - this writable configuration object 2372 indicates whether the associated NHDP messages include the the 2373 RSSA Message TLV, or not. It is highly RECOMMENDED that this 2374 object be set to 'true(1)'. 2376 o 'smfNhdpRssaAddrBlockTLVIncluded' - this writable configuration 2377 object indicates whether the associated NHDP messages include the 2378 the RSSA Address Block TLV, or not. The 2379 smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it 2380 depends on the existence of an address block which may not be 2381 present. If this SMF device is configured with NHDP, then this 2382 object should be set to 'true(1)'. 2384 o 'smfConfiguredAddrForwardingTable' - the writable configuration 2385 objects in this table indicate which multicast IP address are to 2386 be forwarded by this SMF node. Misconfiguration of rows within 2387 this table can limit the ability of this SMF device to forward 2388 multicast data. 2390 o 'smfInterfaceTable' - the writable configuration objects in this 2391 table indicate which SMF node interfaces are participating in the 2392 SMF packet forwarding process. Misconfiguration of rows within 2393 this table can limit the ability of this SMF device to forward 2394 multicast data. 2396 Some of the readable objects in this MIB module (i.e., objects with a 2397 MAX-ACCESS other than not-accessible) may be considered sensitive or 2398 vulnerable in some network environments. It is thus important to 2399 control even GET and/or NOTIFY access to these objects and possibly 2400 to even encrypt the values of these objects when sending them over 2401 the network via SNMP. These are the tables and objects and their 2402 sensitivity/vulnerability: 2404 o 'smfNodeRsStatusIncluded' - this readable state object indicates 2405 that this SMF node is part of the CDS, or not. Being part of the 2406 CDS makes this node a distinguished device. It could be exploited 2407 for data ex-filtration, or denial of service attacks. 2409 o 'smfDiscoveredAddrForwardingTable' - the readable state objects in 2410 this table indicate which, dynamically discovered, multicast IP 2411 address are to be forwarded by this SMF node. 2413 o 'smfNeighborTable' - the readable state objects in this table 2414 indicate current neighbor nodes to this SMF node. Exposing this 2415 information to an attacker could allow the attacker easier access 2416 to the larger MANET domain. 2418 The remainder of the objects in the SMF-MIB are performance counter 2419 objects. While these give an indication of the activity of the SMF 2420 process on this node, it is not expected that exposing these values 2421 pose a security risk to the MANET network. 2423 SNMP versions prior to SNMPv3 did not include adequate security. 2424 Even if the network itself is secure (for example by using IPSec), 2425 even then, there is no control as to who on the secure network is 2426 allowed to access and GET/SET (read/change/create/delete) the objects 2427 in this MIB module. 2429 Implementations MUST provide the security features described by the 2430 SNMPv3 framework (see [RFC3410] ), including full support for 2431 authentication and privacy via the User-based Security Model (USM) 2433 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2434 MAY also provide support for the Transport Security Model (TSM) 2435 [RFC5591] in combination with a secure transport such as SSH 2436 [RFC5592] or TLS/DTLS [RFC6353]. 2438 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2439 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2440 enable cryptographic security. It is then a customer/operator 2441 responsibility to ensure that the SNMP entity giving access to an 2442 instance of this MIB module is properly configured to give access to 2443 the objects only to those principals (users) that have legitimate 2444 rights to indeed GET or SET (change/create/delete) them. 2446 9. Applicability Statement 2448 This document describes objects for configuring parameters of the 2449 Simplified Multicast Forwarding [RFC6621] process on a Mobile Ad-Hoc 2450 Network (MANET) router. This MIB module, denoted SMF-MIB, also 2451 reports state and performance information and notifications. This 2452 section provides some examples of how this MIB module can be used in 2453 MANET network deployments. A fuller discussion of MANET network 2454 management use cases and challenges will be provided elsewhere. 2456 SMF is designed to allow MANET routers to forward IPv4 and IPv6 2457 packets over the MANET and cover the MANET nodes through the 2458 automatic discovery of efficient estimates of the Minimum Connected 2459 Dominating Set (MCDS) of nodes within the MANET. The MCDS are 2460 estimated using the Relay Set Selection Algorithms (RSSAs) discussed 2461 within this document. In the following, three scenarios are listed 2462 where this MIB module is useful, i.e., 2464 o For a Parking Lot Initial Configuration Situation - it is common 2465 for the vehicles comprising the MANET being forward deployed at a 2466 remote location, e.g., the site of a natural disaster, to be off- 2467 loaded in a parking lot where an initial configuration of the 2468 networking devices is performed. The configuration is loaded into 2469 the devices from a fixed location Network Operation Center (NOC) 2470 at the parking lot and the vehicles are stationary at the parking 2471 lot while the configuration changes are made. Standards-based 2472 methods for configuration management from the co-located NOC are 2473 necessary for this deployment option. The set of interesting 2474 configuration objects for the SMF process are listed within this 2475 MIB module. 2477 o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed 2478 NOC - Here the vehicles carrying the MANET routers carry multiple 2479 wireless interfaces, one of which is a relatively low-bandwidth 2480 on-the-move satellite connection which interconnects a fix NOC to 2481 the nodes of the MANET. Standards-based methods for monitoring 2482 and fault management from the fixed NOC are necessary for this 2483 deployment option. 2485 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 2486 larger vehicles, a hierarchical network management arrangement is 2487 useful. Centralized network management is performed from a fixed 2488 NOC while local management is performed locally from within the 2489 vehicles. Standards-based methods for configuration, monitoring 2490 and fault management are necessary for this deployment option. 2492 10. IANA Considerations 2494 The MIB module in this document uses the following IANA-assigned 2495 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 2497 Descriptor OBJECT IDENTIFIER value 2498 ---------- ----------------------- 2499 SMF-MIB { experimental XXXX } 2500 IANA EDITOR NOTE: please assign XXXX, and remove this note. 2502 11. Contributors 2504 This MIB document uses the template authored by D. Harrington which 2505 is based on contributions from the MIB Doctors, especially Juergen 2506 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2508 12. Acknowledgements 2510 The authors would like to acknowledge the valuable comments from Sean 2511 Harnedy in the early phases of the development of this MIB-module. 2512 The authors would like to thank James Nguyen for his careful review 2513 and comments on this MIB-module and his work on the definitions of 2514 the follow on MIB-modules to configure specific RSSA algorithms 2515 related to SMF. Further, the authors would like to acknowledge to 2516 work of James Nguyen, Brian Little, Ryan Morgan and Justin Dean on 2517 their software development of the SMF-MIB. 2519 13. References 2521 13.1. Normative References 2523 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2524 MIB", RFC 2863, June 2000. 2526 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2527 Architecture for Describing Simple Network Management 2528 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2529 December 2002. 2531 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 2532 Simple Network Management Protocol (SNMP)", STD 62, 2533 RFC 3418, December 2002. 2535 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2536 Schoenwaelder, "Textual Conventions for Internet Network 2537 Addresses", RFC 4001, February 2005. 2539 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2540 Requirement Levels", BCP 14, RFC 2119, March 1997. 2542 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2543 Schoenwaelder, Ed., "Structure of Management Information 2544 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2546 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2547 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2548 STD 58, RFC 2579, April 1999. 2550 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2551 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2552 April 1999. 2554 [RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621, 2555 May 2012. 2557 13.2. Informative References 2559 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2560 "Introduction and Applicability Statements for Internet- 2561 Standard Management Framework", RFC 3410, December 2002. 2563 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2564 (USM) for version 3 of the Simple Network Management 2565 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 2567 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 2568 Advanced Encryption Standard (AES) Cipher Algorithm in the 2569 SNMP User-based Security Model", RFC 3826, June 2004. 2571 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2572 for the Simple Network Management Protocol (SNMP)", 2573 RFC 5591, June 2009. 2575 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 2576 Shell Transport Model for the Simple Network Management 2577 Protocol (SNMP)", RFC 5592, June 2009. 2579 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 2580 Model for the Simple Network Management Protocol (SNMP)", 2581 RFC 6353, July 2011. 2583 Appendix A. 2585 *************************************************************** 2586 * Note to the RFC Editor (to be removed prior to publication) * 2587 * * 2588 * The reference to RFC xxxx within the DESCRIPTION clauses * 2589 * of the MIB module point to this draft and are to be * 2590 * assigned by the RFC Editor. * 2591 * * 2592 *************************************************************** 2594 Authors' Addresses 2596 Robert G. Cole 2597 US Army CERDEC 2598 6010 Frankford Road 2599 Aberdeen Proving Ground, Maryland 21005 2600 USA 2602 Phone: +1 443 395 8744 2603 EMail: robert.g.cole@us.army.mil 2605 Joseph Macker 2606 Naval Research Laboratory 2607 Washington, D.C. 20375 2608 USA 2610 EMail: macker@itd.nrl.navy.mil 2612 Brian Adamson 2613 Naval Research Laboratory 2614 Washington, D.C. 20375 2615 USA 2617 EMail: adamson@itd.nrl.navy.mil