idnits 2.17.1 draft-cole-manet-smf-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 5 instances of too long lines in the document, the longest one being 1 character in excess of 72. 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 seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 28, 2009) is 5507 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'TODO' is mentioned on line 2448, but not defined == Missing Reference: 'RFC2021' is mentioned on line 393, but not defined ** Obsolete undefined reference: RFC 2021 (Obsoleted by RFC 4502) == Missing Reference: 'RFC2819' is mentioned on line 408, but not defined == Missing Reference: 'RFC3411' is mentioned on line 414, but not defined == Missing Reference: 'RFC4001' is mentioned on line 418, but not defined == Missing Reference: 'RFC 4001' is mentioned on line 1183, but not defined == Missing Reference: 'TODOs' is mentioned on line 2570, but not defined == Outdated reference: A later version (-14) exists of draft-ietf-manet-smf-08 ** Downref: Normative reference to an Experimental draft: draft-ietf-manet-smf (ref. 'I-D.ietf-manet-smf') Summary: 3 errors (**), 0 flaws (~~), 10 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force R. Cole 3 Internet-Draft Johns Hopkins University 4 Intended status: Standards Track J. Macker 5 Expires: September 1, 2009 B. Adamson 6 Naval Research Laboratory 7 S. Harnedy 8 Booz Allen Hamilton 9 February 28, 2009 11 Definition of Managed Objects for the Manet Simplified Multicast 12 Framework Relay Set Process 13 draft-cole-manet-smf-mib-02 15 Status of This Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on September 1, 2009. 38 Copyright Notice 40 Copyright (c) 2009 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. 50 Abstract 52 This memo defines a portion of the Management Information Base (MIB) 53 for use with network management protocols in the Internet community. 54 In particular, it describes objects for configuring aspects of the 55 Simplified Multicast Forwarding (SMF) process. The SMF MIB also 56 reports state information, performance metrics, and notifications. 57 In addition to configuration, this additional state and performance 58 information is useful to management stations troubleshooting 59 multicast forwarding problems. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. The Internet-Standard Management Framework . . . . . . . . . . 3 65 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 68 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 70 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 71 5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6 72 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7 73 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7 74 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7 75 5.6. The Reports Group . . . . . . . . . . . . . . . . . . . . 8 76 5.7. The Notifications Group . . . . . . . . . . . . . . . . . 8 77 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 78 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 79 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 9 80 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 81 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 82 8. Security Considerations . . . . . . . . . . . . . . . . . . . 51 83 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53 84 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 54 85 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 54 86 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54 87 12.1. Normative References . . . . . . . . . . . . . . . . . . . 54 88 12.2. Informative References . . . . . . . . . . . . . . . . . . 55 89 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 55 90 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 55 91 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 56 93 1. Introduction 95 This memo defines a portion of the Management Information Base (MIB) 96 for use with network management protocols in the Internet community. 97 In particular, it describes objects for configuring aspects of a 98 process implementing Simplified Multicast Forwarding (SMF) 99 [I-D.ietf-manet-smf]. SMF provides multicast duplicate packet 100 detection (DPD) and supports algorithms for constructing an estimate 101 of a mobile ad hoc network (MANET) Minimum Connected Dominating Set 102 (MCDS) for efficient multicast forwarding. The SMF MIB also reports 103 state information, performance metrics, and notifications. In 104 addition to configuration, this additional state and performance 105 information is useful to management stations troubleshooting 106 multicast forwarding problems. 108 2. The Internet-Standard Management Framework 110 For a detailed overview of the documents that describe the current 111 Internet-Standard Management Framework, please refer to section 7 of 112 RFC 3410 [RFC3410]. 114 Managed objects are accessed via a virtual information store, termed 115 the Management Information Base or MIB. MIB objects are generally 116 accessed through the Simple Network Management Protocol (SNMP). 117 Objects in the MIB are defined using the mechanisms defined in the 118 Structure of Management Information (SMI). This memo specifies a MIB 119 module that is compliant to the SMIv2, which is described in STD 58, 120 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 121 [RFC2580]. 123 3. Conventions 125 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 126 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 127 document are to be interpreted as described in RFC 2119 [RFC2119]. 129 4. Overview 131 SMF provides methods for implementing DPD-based multicast forwarding 132 with the optional use of CDS-based relay sets. The MCDS is the 133 smallest set of MANET nodes (comprising a connected cluster) which 134 cover all the nodes in the cluster with their transmissions. As the 135 density of the MANET nodes increase, the fraction of nodes required 136 in an MCDS decreases. Using the MCDS as a multicast forwarding set 137 then becomes an efficient multicast mechanism for MANETs. 139 Various algorithms for the construction of estimates of the MCDS 140 exist. The Simplified Multicast Framework [I-D.ietf-manet-smf] 141 describes some of these. It further defines various operational 142 modes for a node which is participating in the collective creation of 143 the MCDS estimates. These modes depend upon the set of related MANET 144 routing and discovery protocols and mechanisms in operation in the 145 specific MANET node. 147 A SMF routers' MIB contains SMF process configuration parameters 148 (e.g. specific CDS algorithm), state information (e.g., current 149 membership in the CDS), performance counters (e.g., packet counters), 150 and notifications. 152 4.1. SMF Management Model 154 This section describes the management model for the SMF node process. 156 Figure 1 (reproduced from Figure 4 of [I-D.ietf-manet-smf]) shows the 157 relationship between the SMF Relay Set selection algorithm and the 158 related algorithms, processes and protocols running in the MANET 159 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 160 topology information gotten from the MANET Neighborhood Discovery 161 Protocol (NHDP), from the specific MANET routing protocol running on 162 the node, or from Layer 2 information passed up to the higher layer 163 protocol processes. 165 Possible L2 Trigger/Information 166 | 167 | 168 ______________ ______|_____ __________________ 169 | MANET | | | | | 170 | Neighborhood | | Relay Set | | Other Heuristics | 171 | Discovery |------------| Selection |-------| (Preference,etc) | 172 | Protocol | neighbor | Algorithm | | | 173 |______________| info |____________| |__________________| 174 \ / 175 \ / 176 neighbor\ / Dynamic Relay 177 info* \ ____________ / Set Status 178 \ | SMF | / (State, {neighbor info}) 179 `---| Relay Set |---' 180 | State | 181 ---|____________| 182 / 183 / 184 ______________ 185 | Coexistent | 186 | MANET | 187 | Unicast | 188 | Process | 189 |______________| 191 Figure 1: SMF Relay Set Control Options 193 4.2. Terms 195 The following definitions apply throughout this document: 197 o Configuration Objects - switches, tables, objects which are 198 initialized to default settings or set through the management 199 interface defined by this MIB. 201 o Tunable Configuration Objects - objects whose values affect timing 202 or attempt bounds on the SMF RS process. 204 o State Objects - automatically generated values which define the 205 current operating state of the SMF RS process in the router. 207 o Performance Objects - automatically generated values which help an 208 administrator or automated tool to assess the performance of the 209 CDS multicast process on the router and the overall multicasting 210 performance within the MANET routing domain. 212 5. Structure of the MIB Module 214 This section presents the structure of the SMF MIB module. The 215 objects are arranged into the following groups: 217 o smfMIBNotifications - defines the notifications associated with 218 the SMF MIB. 220 o smfMIBObjects - defines the objects forming the basis for the SMF 221 MIB. These objects are divided up by function into the following 222 groups: 224 o 226 * Capabilities Group - This group contains the SMF objects that 227 the device uses to advertise its local capabilities with 228 respect to, e.g., the supported RSSAs. 230 * Configuration Group - This group contains the SMF objects that 231 configure specific options that determine the overall operation 232 of the SMF RSSA and the resulting multicast performance. 234 * State Group - Contains information describing the current state 235 of the SMF RSSA process such as the Neighbor Table. 237 * Performance Group - Contains objects which help to characterize 238 the performance of the SMF RSSA process, typically statistics 239 counters. 241 * Reports Group - Contains objects which allow the device to 242 develop and locally store performance related reports. The 243 management application can then pull these locally stored 244 reports when it wishes. 246 o smfMIBConformance - defines minimal and full conformance of 247 implementations to this SMF MIB. 249 5.1. Textual Conventions 251 The textual conventions used in the SMF MIB are as follows. The 252 RowStatus textual convention is imported from RFC 2579 [RFC2579]. 254 5.2. The Capabilities Group 256 The SMF device supports a set of capabilities. The list of 257 capabilities which the device can advertise are: 259 o Operational Mode - topology information from NHDP, CDS-aware 260 unicast routing or Cross-layer from Layer 2 262 o SMF RSSA - the specific RSSA operational on the device 264 5.3. The Configuration Group 266 The SMF device is configured with a set of controls. The list of 267 configuration controls for the SMF device follow. 269 o Operational Mode - topology information from NHDP, CDS-aware 270 unicast routing or Cross-layer from Layer 2 272 o SMF RSSA - the specific RSSA operational on the device 274 o Duplicate Packet detection for IPv4 - Identification-based or 275 Hash-based DPD 277 o Duplicate Packet detection for IPv6 - Identification-based or 278 Hash-based DPD 280 o NHDP RSSA Message TLV - if NHDP mode is selected, then is the RSSA 281 Message TLV included in the NHDP exchanges. (Question: Is this 282 and the following two TLVs optional and are they included as a 283 group or independently of one another?) 285 o NHDP RSSA Address Block TLV - if NHDP mode is selected, then is 286 the RSSA Address Block TLV included in the NHDP exchanges. 288 o Router Priority TLV - if NHDP mode is selected, then is the Router 289 Priority TLV included in the NHDP exchanges. 291 5.4. The State Group 293 The State Subtree reports current state information. 295 o Node RSS State - is the node currently in or out of the Relay Set. 297 o Neighbors Table - a table containing current neighbors and their 298 operational RSSA. 300 5.5. The Performance Group 302 The Performance subtree reports primarily counters that relate to SMF 303 RSSA performance. The SMF performance counters consists of per node 304 and per interface objects: (Note: Need to have a discussion of the 305 important and measurable events related to SMF RSSA multicast 306 performance.) (Note: Do we need to break these out by type, i.e., v4 307 versus v6?) 309 o Total multicast packets received - 311 o Total multicast packets forwarded - 313 o Total duplicate multicast packets detected - 315 o Per interface statistics table with the following entries: 317 o 319 * Multicast packets received 321 * Multicast packets forwarded 323 * Duplicate multicast packets detected 325 5.6. The Reports Group 327 The SMF device supports a a capability to generate and store locally 328 a set of performance reports. The objects to control the generation 329 of these reports and to identify the information contained within 330 these reports are contained within this group. These objects 331 include: 333 o Report Control Objects - which specify the storage requirements, 334 the time and duration and the authorship of the reports. 336 o Report Objects - which identify the information, i.e., metrics, 337 contained within these reports. Currently, these objects 338 represent a sub-set of the objects found within the Performance 339 Group discussed above. 341 5.7. The Notifications Group 343 The Notifications Subtree contains the list of notifications 344 supported within the SMF-MIB and their intended purpose or utility. 345 This group is currently empty. 347 6. Relationship to Other MIB Modules 349 [TODO]: The text of this section specifies the relationship of the 350 MIB modules contained in this document to other standards, 351 particularly to standards containing other MIB modules. Definitions 352 imported from other MIB modules and other MIB modules that SHOULD be 353 implemented in conjunction with the MIB module contained within this 354 document are identified in this section. 356 6.1. Relationship to the SNMPv2-MIB 358 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 359 mandatory for all systems, and the objects apply to the entity as a 360 whole. The 'system' group provides identification of the management 361 entity and certain other system-wide data. The SMF-MIB does not 362 duplicate those objects. 364 6.2. Relationship to the IF-MIB 366 [TODO] This section is included as an example; If the MIB module is 367 not an adjunct of the Interface MIB, then this section should be 368 removed. 370 6.3. MIB modules required for IMPORTS 372 [TODO]: Citations are not permitted within a MIB module, but any 373 module mentioned in an IMPORTS clause or document mentioned in a 374 REFERENCE clause is a Normative reference, and must be cited 375 someplace within the narrative sections. If there are imported items 376 in the MIB module, such as Textual Conventions, that are not already 377 cited, they can be cited in text here. Since relationships to other 378 MIB modules should be described in the narrative text, this section 379 is typically used to cite modules from which Textual Conventions are 380 imported. 382 The following SMF-MIB module IMPORTS objects from SNMPv2-SMI 383 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB 384 [RFC2863] 386 7. Definitions 388 MANET-SMF-MIB DEFINITIONS ::= BEGIN 390 IMPORTS 392 ZeroBasedCounter32 393 FROM RMON2-MIB -- [RFC2021] 395 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 396 Counter32, Unsigned32, Integer32, mib-2 397 FROM SNMPv2-SMI -- [RFC2578] 399 TEXTUAL-CONVENTION, RowStatus, TruthValue, 400 TimeStamp, StorageType 401 FROM SNMPv2-TC -- [RFC2579] 403 MODULE-COMPLIANCE, OBJECT-GROUP, 404 NOTIFICATION-GROUP 405 FROM SNMPv2-CONF -- [RFC2580] 407 OwnerString 408 FROM RMON-MIB -- [RFC2819] 410 InterfaceIndexOrZero 411 FROM IF-MIB -- [RFC2863] 413 SnmpAdminString 414 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 416 InetAddress, InetAddressType, 417 InetAddressPrefixLength 418 FROM INET-ADDRESS-MIB -- [RFC4001] 419 ; 421 manetSmfMIB MODULE-IDENTITY 422 LAST-UPDATED "200902271300Z" -- February 27, 2009 423 ORGANIZATION "IETF MANET Working Group" 424 CONTACT-INFO 425 "WG E-Mail: manet@ietf.org 427 WG Chairs: ian.chakeres@gmail.com 428 jmacker@nrl.navy.mil 430 Editors: Robert G. Cole 431 Johns Hopkins University 432 Applied Physics Lab and 433 Department of Computer Science 434 11000 Johns Hopkins Road 435 Room 02-257 436 Laurel, MD 22014 437 USA 438 +1 443 778-6951 439 robert.cole@jhuapl.edu 441 Joseph Macker 442 Naval Research Laboratory 443 Washington, D.C. 20375 444 USA 445 macker@itd.nrl.navy.mil 447 Brian Adamson 448 Naval Research Laboratory 449 Washington, D.C. 20375 450 USA 451 adamson@itd.nrl.navy.mil 453 Sean Harnedy 454 Booz Allen Hamilton 455 333 City Boulevard West 456 Orange, CA 92868 457 USA 458 +1 714 938-3898 459 harnedy_sean@bah.com" 461 DESCRIPTION 462 "This MIB module contains managed object definitions for 463 the Manet SMF RSSA process defined in: Macker, J.(ed.), 464 Simplified Multicast Forwarding draft-ietf-manet-smf-08, 465 November 03, 2008. 467 Copyright (C) The IETF Trust (2008). This version 468 of this MIB module is part of RFC xxxx; see the RFC 469 itself for full legal notices." 471 -- Revision History 472 REVISION "200902271300Z" -- February 27, 2009 473 DESCRIPTION 474 "Updated draft of this MIB module published as 475 draft-cole-manet-smf-mib-02.txt. Fairly extensive 476 revisions and additions to this MIB were made 477 in this version. Specifically, the following 478 changes were made in development of this version: 479 - added a Capabilities Group within the Objects 480 Group to allow the device to report supported 481 capabilities, e.g., RSSAs supported. 482 - added administrative status objects for device 483 and interfaces 484 - added multicast address forwarding tables, both 485 for configured (within Configuration Group) and 486 discovered (within the State Group). 487 - added additional Performance counters related 488 to DPD functions. 489 - Split up the performance counters into IPv4 490 and IPv6, for both global and per interface 491 statistics. 492 - Split out the reports capability into a seperate 493 Reports Group under the Objects Group. 494 " 495 REVISION "200811031300Z" -- November 03, 2008 496 DESCRIPTION 497 "Updated draft of this MIB module published as 498 draft-cole-manet-smf-mib-01.txt. Added gateway filter 499 table and reports capabilities following rmon." 500 REVISION "200807071200Z" -- July 07, 2008 501 DESCRIPTION 502 "Initial draft of this MIB module published as 503 draft-cole-manet-smf-mib-00.txt." 504 -- RFC-Editor assigns XXXX 505 ::= { mib-2 998 } -- to be assigned by IANA 507 -- 508 -- TEXTUAL CONVENTIONs 509 -- 511 Status ::= TEXTUAL-CONVENTION 512 STATUS current 513 DESCRIPTION 514 "An indication of the operability of a DYMO 515 function or feature. For example, the status 516 of an interface: 'enabled' indicates that 517 it is willing to communicate with other DYMO routers, 518 and 'disabled' indicates that it is not." 519 SYNTAX INTEGER { 520 enabled (1), 521 disabled (2) 522 } 524 SmfOpModeID ::= TEXTUAL-CONVENTION 525 DISPLAY-HINT "d" 526 STATUS current 527 DESCRIPTION 528 "An index that identifies through reference to a specific 529 SMF operations mode ... 530 " 531 SYNTAX Unsigned32 (1..2147483647) 533 SmfRssaID ::= TEXTUAL-CONVENTION 534 STATUS current 535 DESCRIPTION 536 "An index that identifies through reference to a specific 537 RSSA algorithms ... 538 " 539 SYNTAX INTEGER { 540 cF(1), 541 sMPR(2), 542 eCDS(3), 543 mprCDS(4) 544 -- future(5-127) 545 -- noStdAction(128-239) 546 -- experimental(240-255) 547 } 549 -- 550 -- Top-Level Object Identifier Assignments 551 -- 553 smfMIBNotifications OBJECT IDENTIFIER ::= { manetSmfMIB 0 } 554 smfMIBObjects OBJECT IDENTIFIER ::= { manetSmfMIB 1 } 555 smfMIBConformance OBJECT IDENTIFIER ::= { manetSmfMIB 2 } 557 -- 558 -- smfMIBObjects Assignments: 559 -- smfCapabilitiesGroup - 1 560 -- smfConfigurationGroup - 2 561 -- smfStateGroup - 3 562 -- smfPerformanceGroup - 4 563 -- smfReportsGroup - 5 564 -- 566 -- 567 -- smfCapabilitiesGroup 568 -- 569 -- This group contains the SMF objects that identify specific 570 -- capabilities within this device related to SMF functions. 571 -- 573 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 575 -- 576 -- SMF Operational Mode Capabilities Table 577 -- 579 smfOpModeCapabilitiesTable OBJECT-TYPE 580 SYNTAX SEQUENCE OF SmfOpModeCapabilitiesEntry 581 MAX-ACCESS not-accessible 582 STATUS current 583 DESCRIPTION 584 "The smfOpModeCapabilitiesTable contains ... 585 " 586 ::= { smfCapabilitiesGroup 1 } 588 smfOpModeCapabilitiesEntry OBJECT-TYPE 589 SYNTAX SmfOpModeCapabilitiesEntry 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "Information about a particular operational 594 mode. 595 " 596 INDEX { smfOpModeCapabilitiesID } 597 ::= { smfOpModeCapabilitiesTable 1 } 599 SmfOpModeCapabilitiesEntry ::= SEQUENCE { 600 smfOpModeCapabilitiesID SmfOpModeID, 601 smfOpModeCapabilitiesName SnmpAdminString, 602 smfOpModeCapabilitiesReference SnmpAdminString 603 } 605 smfOpModeCapabilitiesID OBJECT-TYPE 606 SYNTAX SmfOpModeID 607 MAX-ACCESS not-accessible 608 STATUS current 609 DESCRIPTION 610 "The index for this entry. This object identifies 611 the particular operational mode for this device. 612 " 613 ::= { smfOpModeCapabilitiesEntry 1 } 615 smfOpModeCapabilitiesName OBJECT-TYPE 616 SYNTAX SnmpAdminString 617 MAX-ACCESS read-only 618 STATUS current 619 DESCRIPTION 620 "The textual name of this operational 621 mode. 622 " 623 ::= { smfOpModeCapabilitiesEntry 2 } 625 smfOpModeCapabilitiesReference OBJECT-TYPE 626 SYNTAX SnmpAdminString 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "This object contains a reference to the document that 631 defines this operational mode. 632 " 633 ::= { smfOpModeCapabilitiesEntry 3 } 635 -- 636 -- SMF RSSA Capabilities Table 637 -- 639 smfRssaCapabilitiesTable OBJECT-TYPE 640 SYNTAX SEQUENCE OF SmfRssaCapabilitiesEntry 641 MAX-ACCESS not-accessible 642 STATUS current 643 DESCRIPTION 644 "The smfRssaCapabilitiesTable contains ... 645 " 646 ::= { smfCapabilitiesGroup 2 } 648 smfRssaCapabilitiesEntry OBJECT-TYPE 649 SYNTAX SmfRssaCapabilitiesEntry 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "Information about a particular algorithm." 654 INDEX { smfRssaCapabilitiesID } 655 ::= { smfRssaCapabilitiesTable 1 } 657 SmfRssaCapabilitiesEntry ::= SEQUENCE { 658 smfRssaCapabilitiesID SmfRssaID, 659 smfRssaCapabilitiesName SnmpAdminString, 660 smfRssaCapabilitiesReference SnmpAdminString 661 } 663 smfRssaCapabilitiesID OBJECT-TYPE 664 SYNTAX SmfRssaID 665 MAX-ACCESS not-accessible 666 STATUS current 667 DESCRIPTION 668 "The index for this entry. This object identifies 669 the particular algorithm in this MIB module." 670 ::= { smfRssaCapabilitiesEntry 1 } 672 smfRssaCapabilitiesName OBJECT-TYPE 673 SYNTAX SnmpAdminString 674 MAX-ACCESS read-only 675 STATUS current 676 DESCRIPTION 677 "The textual name of this algorithm. 678 " 679 ::= { smfRssaCapabilitiesEntry 2 } 681 smfRssaCapabilitiesReference OBJECT-TYPE 682 SYNTAX SnmpAdminString 683 MAX-ACCESS read-only 684 STATUS current 685 DESCRIPTION 686 "This object contains a reference to the document that 687 defines this algorithm. 688 " 689 ::= { smfRssaCapabilitiesEntry 3 } 691 -- 692 -- smfConfigurationGroup 693 -- 694 -- This group contains the SMF objects that configure specific 695 -- options that determine the overall performance and operation 696 -- of the multicast forwarding process for the router device 697 -- and its interfaces. 698 -- 700 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 702 smfAdminStatus OBJECT-TYPE 703 SYNTAX Status 704 MAX-ACCESS read-write 705 STATUS current 706 DESCRIPTION 707 "The configured status of the SMF process 708 on this device. Enabled(1) means that 709 SMF is configured to run on this device. 710 Disabled(2) mean that the SMF process 711 is configured off." 712 ::= { smfConfigurationGroup 1 } 714 smfConfiguredOpMode OBJECT-TYPE 715 SYNTAX INTEGER { 716 withNHDP(1), 717 cdsAwareRouting(2), 718 crossLayer(3), 719 other(4) 720 } 721 MAX-ACCESS read-write 722 STATUS current 723 DESCRIPTION 724 "The SMF RSS node operational mode. 726 The value withNHDP(1) indicates ... 727 The value cdsAwareRouting(2) indicates ... 728 The value crossLayer(3) indicates... ." 729 ::= { smfConfigurationGroup 2 } 731 smfConfiguredRssa OBJECT-TYPE 732 SYNTAX SmfRssaID 733 MAX-ACCESS read-write 734 STATUS current 735 DESCRIPTION 736 "The SMF RSS currently operational algorithm. 738 The value cf(1) indicates ... 740 The value experimental(240-255) indicates... ." 741 ::= { smfConfigurationGroup 3 } 743 smfRssaMember OBJECT-TYPE 744 SYNTAX INTEGER { 745 potential(1), 746 always(2), 747 never(3) 748 } 749 MAX-ACCESS read-write 750 STATUS current 751 DESCRIPTION 752 "The RSSA downselects a set of forwarders for 753 multicast forwarding. Sometimes it is useful 754 to force an agent to be included or excluded 755 from the resulting RSS. This object is a 756 switch to allow for this behavior. 758 The value potential(1) allows the selected 759 RSSA to determine if this agent is included 760 or excluded from the RSS. 762 The value always(1) forces the selected 763 RSSA include this agent in the RSS. 765 The value never(3) forces the selected 766 RSSA to exclude this agent from the RSS." 767 ::= { smfConfigurationGroup 4 } 769 smfIpv4Dpd OBJECT-TYPE 770 SYNTAX INTEGER { 771 identificationBased(1), 772 hashBased(2) 773 } 774 MAX-ACCESS read-write 775 STATUS current 776 DESCRIPTION 777 "The current method for IPv4 duplicate packet 778 detection. 779 The value identificationBased(1) 780 indicates... 782 The value 'hashBased(2) indicates... ." 783 ::= { smfConfigurationGroup 5 } 785 smfIpv6Dpd OBJECT-TYPE 786 SYNTAX INTEGER { 787 identificationBased(1), 788 hashBased(2) 789 } 790 MAX-ACCESS read-write 791 STATUS current 792 DESCRIPTION 793 "The current method for IPv6 duplicate packet 794 detection. 795 The value identificationBased(1) 796 indicates... 798 The value 'hashBased(2) indicates... ." 799 ::= { smfConfigurationGroup 6 } 801 smfMaxPktLifetime OBJECT-TYPE 802 SYNTAX Integer32 (0..65535) 803 UNITS "Seconds" 804 MAX-ACCESS read-write 805 STATUS current 806 DESCRIPTION 807 "The estimate of the network packet 808 traversal time. 809 " 810 DEFVAL { 60 } 811 ::= { smfConfigurationGroup 7 } 813 smfDpdMaxMemorySize OBJECT-TYPE 814 SYNTAX Integer32 (0..65535) 815 UNITS "Kilo-Bytes" 816 MAX-ACCESS read-write 817 STATUS current 818 DESCRIPTION 819 "The locally reserved memory for storage 820 of cached DPD records for both IPv4 and 821 IPv6 methods. 822 " 823 DEFVAL { 1024 } 824 ::= { smfConfigurationGroup 8 } 826 smfDpdEntryMaxLifetime OBJECT-TYPE 827 SYNTAX Integer32 (0..65525) 828 UNITS "Seconds" 829 MAX-ACCESS read-write 830 STATUS current 831 DESCRIPTION 832 "The maximum lifetime of a cached DPD 833 record in the local device storage. 834 " 835 DEFVAL { 600 } 836 ::= { smfConfigurationGroup 9 } 838 -- 839 -- Configuration of messages to be included in 840 -- NHDP message exchanges in support of SMF 841 -- operations. 842 -- 844 smfNhdpRssaMesgTLVIncluded OBJECT-TYPE 845 SYNTAX TruthValue 846 MAX-ACCESS read-write 847 STATUS current 848 DESCRIPTION 849 "Indicates whether the associated NHDP messages 850 include the RSSA Message TLV, or not. This 851 is an optional SMF operational setting. 852 The value true(1) indicates that this TLV is 853 included; the value false(2) indicates that it 854 is not included." 855 ::= { smfConfigurationGroup 10 } 857 smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 858 SYNTAX TruthValue 859 MAX-ACCESS read-write 860 STATUS current 861 DESCRIPTION 862 "Indicates whether the associated NHDP messages 863 include the RSSA Address Block TLV, or not. 864 This is an optional SMF operational setting. 865 The value true(1) indicates that this TLV is 866 included; the value false(2) indicates that it 867 is not included." 869 ::= { smfConfigurationGroup 11 } 871 smfNhdpRouterPriorityTLVIncluded OBJECT-TYPE 872 SYNTAX TruthValue 873 MAX-ACCESS read-write 874 STATUS current 875 DESCRIPTION 876 "Indicates whether the associated NHDP messages 877 include the RSSA Router Priority TLV, or not. 878 This is an optional SMF operational setting. 879 The value true(1) indicates that this TLV is 880 included; the value false(2) indicates that it 881 is not included." 882 ::= { smfConfigurationGroup 12 } 884 -- 885 -- Table identifying configured multicast addresses to be forwarded. 886 -- 888 smfConfiguredAddrForwardingTable OBJECT-TYPE 889 SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry 890 MAX-ACCESS not-accessible 891 STATUS current 892 DESCRIPTION 893 "The (conceptual) table containing information on multicast 894 addresses which are to be forwarded by the SMF process. 896 Entries in this table are configured. As well, addresses 897 to be forwarded by the SMF device can be dynamically discovered 898 by other means. The corresponding state table, 899 smfDiscoveredAddrForwardingTable contains 900 these additional, dynamically discovered address for 901 forwarding. 903 Each row is associated with a range of multicast addresses, 904 and ranges for different rows must be disjoint. 905 " 906 ::= { smfConfigurationGroup 13 } 908 smfConfiguredAddrForwardingEntry OBJECT-TYPE 909 SYNTAX SmfConfiguredAddrForwardingEntry 910 MAX-ACCESS not-accessible 911 STATUS current 912 DESCRIPTION 913 "An entry (conceptual row) containing the information on a 914 particular multicast scope." 915 INDEX { smfConfiguredAddrForwardingAddrType, 916 smfConfiguredAddrForwardingFirstAddr } 917 ::= { smfConfiguredAddrForwardingTable 1 } 919 SmfConfiguredAddrForwardingEntry ::= SEQUENCE { 920 smfConfiguredAddrForwardingAddrType InetAddressType, 921 smfConfiguredAddrForwardingFirstAddr InetAddress, 922 smfConfiguredAddrForwardingLastAddr InetAddress, 923 smfConfiguredAddrForwardingStatus RowStatus 924 } 926 smfConfiguredAddrForwardingAddrType OBJECT-TYPE 927 SYNTAX InetAddressType 928 MAX-ACCESS not-accessible 929 STATUS current 930 DESCRIPTION 931 "The type of the addresses in the multicast forwarding 932 range. Legal values correspond to the subset of 933 address families for which multicast address allocation 934 is supported." 935 ::= { smfConfiguredAddrForwardingEntry 1 } 937 smfConfiguredAddrForwardingFirstAddr OBJECT-TYPE 938 SYNTAX InetAddress (SIZE(0..20)) 939 MAX-ACCESS not-accessible 940 STATUS current 941 DESCRIPTION 942 "The first address in the multicast scope range. The type 943 of this address is determined by the value of the 944 smfConfiguredAddrForwardingAddrType object." 945 ::= { smfConfiguredAddrForwardingEntry 2 } 947 smfConfiguredAddrForwardingLastAddr OBJECT-TYPE 948 SYNTAX InetAddress (SIZE(0..20)) 949 MAX-ACCESS read-create 950 STATUS current 951 DESCRIPTION 952 "The last address in the multicast scope range. 953 The type of this address is determined by the 954 value of the smfConfiguredAddrForwardingAddrType 955 object." 956 ::= { smfConfiguredAddrForwardingEntry 3 } 958 smfConfiguredAddrForwardingStatus OBJECT-TYPE 959 SYNTAX RowStatus 960 MAX-ACCESS read-create 961 STATUS current 962 DESCRIPTION 963 "The status of this row, by which new entries may be 964 created, or old entries deleted from this table. If write 965 access is supported, the other writable objects in this 966 table may be modified even while the status is `active'." 967 ::= { smfConfiguredAddrForwardingEntry 4 } 969 -- 970 -- SMF Interfaces Configuration Table 971 -- 973 smfInterfaceTable OBJECT-TYPE 974 SYNTAX SEQUENCE OF SmfInterfaceEntry 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "The SMF Interface Table describes the SMF 979 interfaces that are participating in the 980 SMF packet forwarding process. The ifIndex is 981 from the interfaces group defined in the 982 Interfaces Group MIB. 983 " 984 REFERENCE 985 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 986 K., and F. Kastenholtz, June 2000." 987 ::= { smfConfigurationGroup 14 } 989 smfInterfaceEntry OBJECT-TYPE 990 SYNTAX SmfInterfaceEntry 991 MAX-ACCESS not-accessible 992 STATUS current 993 DESCRIPTION 994 "The SMF interface entry describes one SMF 995 interface as indexed by its ifIndex." 996 INDEX { smfIfIndex } 997 ::= { smfInterfaceTable 1 } 999 SmfInterfaceEntry ::= 1000 SEQUENCE { 1001 smfIfIndex InterfaceIndexOrZero, 1002 smfIfAdminStatus Status, 1003 smfIfRowStatus RowStatus 1004 } 1006 smfIfIndex OBJECT-TYPE 1007 SYNTAX InterfaceIndexOrZero 1008 MAX-ACCESS not-accessible 1009 STATUS current 1010 DESCRIPTION 1011 "The ifIndex for this SMF interface." 1012 ::= { smfInterfaceEntry 1 } 1014 smfIfAdminStatus OBJECT-TYPE 1015 SYNTAX Status 1016 MAX-ACCESS read-create 1017 STATUS current 1018 DESCRIPTION 1019 "The SMF interface's administrative status. 1020 The value 'enabled' denotes that the interface 1021 is running the SMF forwarding process. 1022 The value 'disabled' denotes that the interface is 1023 external to the SMF forwarding process. 1024 " 1025 ::= { smfInterfaceEntry 2 } 1027 smfIfRowStatus OBJECT-TYPE 1028 SYNTAX RowStatus 1029 MAX-ACCESS read-create 1030 STATUS current 1031 DESCRIPTION 1032 "This object permits management of the table 1033 by facilitating actions such as row creation, 1034 construction, and destruction. The value of 1035 this object has no effect on whether other 1036 objects in this conceptual row can be 1037 modified." 1038 ::= { smfInterfaceEntry 3 } 1040 -- 1041 -- SMF Gateway Filter Table 1042 -- (Note: Not sure at this point what to do with this 1043 -- table. Most likely want to move to a seperate MIB.) 1044 -- 1046 smfGatewayFilterTable OBJECT-TYPE 1047 SYNTAX SEQUENCE OF SmfGatewayFilterEntry 1048 MAX-ACCESS not-accessible 1049 STATUS obsolete 1050 DESCRIPTION 1051 "The SMF Gateway can be configured to filter 1052 multicast packets into and outof the SMF 1053 MANET domain. This table defines the filter 1054 rules which define packet matching and 1055 related actions. The rules are in order ..." 1057 REFERENCE 1058 "The SMF draft." 1059 ::= { smfConfigurationGroup 15 } 1061 smfGatewayFilterEntry OBJECT-TYPE 1062 SYNTAX SmfGatewayFilterEntry 1063 MAX-ACCESS not-accessible 1064 STATUS current 1065 DESCRIPTION 1066 "A single entry in the smfGatewayFilterTable." 1067 REFERENCE 1068 "The SMF draft." 1069 INDEX { smfGatewayFilterIndex } 1070 ::= { smfGatewayFilterTable 1 } 1072 SmfGatewayFilterEntry ::= 1073 SEQUENCE { 1074 smfGatewayFilterIndex InterfaceIndexOrZero, 1075 smfGatewayFilterIf InterfaceIndexOrZero, 1076 smfGatewayFilterIfDirection INTEGER, 1077 smfGatewayFilterRuleRank Integer32, 1078 smfGatewayFilterDestAddrType InetAddressType, 1079 smfGatewayFilterDestAddr InetAddress, 1080 smfGatewayFilterDestAddrPrefixLen InetAddressPrefixLength, 1081 smfGatewayFilterSrcAddrType InetAddressType, 1082 smfGatewayFilterSrcAddr InetAddress, 1083 smfGatewayFilterSrcAddrPrefixLen InetAddressPrefixLength, 1084 smfGatewayFilterProtocolNumber Integer32, 1085 smfGatewayFilterDestPortNumber Integer32, 1086 smfGatewayFilterAction INTEGER, 1087 smfGatewayFilterRowStatus RowStatus 1088 } 1090 smfGatewayFilterIndex OBJECT-TYPE 1091 SYNTAX InterfaceIndexOrZero 1092 MAX-ACCESS not-accessible 1093 STATUS current 1094 DESCRIPTION 1095 "The Index for this filter rule. 1096 " 1097 ::= { smfGatewayFilterEntry 1 } 1099 smfGatewayFilterIf OBJECT-TYPE 1100 SYNTAX InterfaceIndexOrZero 1101 MAX-ACCESS read-create 1102 STATUS current 1103 DESCRIPTION 1104 "The ifIndex for this node interface 1105 that is filtering this rule." 1106 ::= { smfGatewayFilterEntry 2 } 1108 smfGatewayFilterIfDirection OBJECT-TYPE 1109 SYNTAX INTEGER { 1110 in(1), 1111 out(2) 1112 } 1113 MAX-ACCESS read-create 1114 STATUS current 1115 DESCRIPTION 1116 "The ifIndex direction for this interface 1117 filtering rule." 1118 ::= { smfGatewayFilterEntry 3 } 1120 smfGatewayFilterRuleRank OBJECT-TYPE 1121 SYNTAX Integer32 (1..65535) 1122 MAX-ACCESS read-create 1123 STATUS current 1124 DESCRIPTION 1125 "The rank of the rule specified in 1126 this entry. This rank is specified by 1127 the management application. The rules applied 1128 on this device are rank ordered by this 1129 rank, from smallest (applied first) to 1130 largest (applied last). The rule ranks do not 1131 have to be contiguous, but they must be unique. 1132 When a management application changes this rank 1133 and the new rank is identical to the rank of another 1134 entry, then that entry's rank and all other entries 1135 with a rank greater than this rank must be incremented 1136 by one. 1137 " 1138 REFERENCE 1139 "The SMF draft." 1140 ::= { smfGatewayFilterEntry 4 } 1142 smfGatewayFilterDestAddrType OBJECT-TYPE 1143 SYNTAX InetAddressType 1144 MAX-ACCESS read-create 1145 STATUS current 1146 DESCRIPTION 1147 "The type of the DestAddr, as defined 1148 in the InetAddress MIB [RFC 4001]." 1149 REFERENCE 1150 "The SMF draft." 1151 ::= { smfGatewayFilterEntry 5 } 1152 smfGatewayFilterDestAddr OBJECT-TYPE 1153 SYNTAX InetAddress 1154 MAX-ACCESS read-create 1155 STATUS current 1156 DESCRIPTION 1157 "The destination IP address of this rule. The type 1158 of this address is determined by the value of the 1159 smfGatewayFilterDestAddrType object." 1160 REFERENCE 1161 "The SMF draft." 1162 ::= { smfGatewayFilterEntry 6 } 1164 smfGatewayFilterDestAddrPrefixLen OBJECT-TYPE 1165 SYNTAX InetAddressPrefixLength 1166 MAX-ACCESS read-create 1167 STATUS current 1168 DESCRIPTION 1169 "Indicates the number of leading one bits that form the 1170 mask to be logical-ANDed with the destination address 1171 before being compared to the value in the 1172 smfGatewayFilterDestAddr field." 1173 REFERENCE 1174 "The SMF draft." 1175 ::= { smfGatewayFilterEntry 7 } 1177 smfGatewayFilterSrcAddrType OBJECT-TYPE 1178 SYNTAX InetAddressType 1179 MAX-ACCESS read-create 1180 STATUS current 1181 DESCRIPTION 1182 "The type of the SrcAddr, as defined 1183 in the InetAddress MIB [RFC 4001]." 1184 REFERENCE 1185 "The SMF draft." 1186 ::= { smfGatewayFilterEntry 8 } 1188 smfGatewayFilterSrcAddr OBJECT-TYPE 1189 SYNTAX InetAddress 1190 MAX-ACCESS read-create 1191 STATUS current 1192 DESCRIPTION 1193 "The source IP address of this rule. The type 1194 of this address is determined by the value of the 1195 smfGatewayFilterSrcAddrType object." 1196 REFERENCE 1197 "The SMF draft." 1198 ::= { smfGatewayFilterEntry 9 } 1199 smfGatewayFilterSrcAddrPrefixLen OBJECT-TYPE 1200 SYNTAX InetAddressPrefixLength 1201 MAX-ACCESS read-create 1202 STATUS current 1203 DESCRIPTION 1204 "Indicates the number of leading one bits that form the 1205 mask to be logical-ANDed with the destination address 1206 before being compared to the value in the 1207 smfGatewayFilterSrcAddr field." 1208 REFERENCE 1209 "The SMF draft." 1210 ::= { smfGatewayFilterEntry 10 } 1212 -- Note: check out the necessary range for protocol 1213 -- and port numbers. 1214 smfGatewayFilterProtocolNumber OBJECT-TYPE 1215 SYNTAX Integer32(0..65535) 1216 MAX-ACCESS read-create 1217 STATUS current 1218 DESCRIPTION 1219 "The Protocol Number defined in RFC 5237." 1220 ::= { smfGatewayFilterEntry 11 } 1222 smfGatewayFilterDestPortNumber OBJECT-TYPE 1223 SYNTAX Integer32(0..65535) 1224 MAX-ACCESS read-create 1225 STATUS current 1226 DESCRIPTION 1227 "The destination Port Number defined in 1228 RFC XXXX." 1229 ::= { smfGatewayFilterEntry 12 } 1231 smfGatewayFilterAction OBJECT-TYPE 1232 SYNTAX INTEGER { 1233 drop(1), 1234 pass(2), 1235 other(3) 1236 } 1237 MAX-ACCESS read-create 1238 STATUS current 1239 DESCRIPTION 1240 "The action to be taken if the rule is 1241 matched." 1242 ::= { smfGatewayFilterEntry 13 } 1244 smfGatewayFilterRowStatus OBJECT-TYPE 1245 SYNTAX RowStatus 1246 MAX-ACCESS read-create 1247 STATUS current 1248 DESCRIPTION 1249 "This object permits management of the table 1250 by facilitating actions such as row creation, 1251 construction, and destruction. The value of 1252 this object has no effect on whether other 1253 objects in this conceptual row can be 1254 modified." 1255 ::= { smfGatewayFilterEntry 14 } 1257 -- 1258 -- smfStateGroup 1259 -- 1260 -- Contains information describing the current state of the SMF 1261 -- process such as the current inclusion in the RS or not. 1262 -- 1264 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1266 smfNodeRsStatusIncluded OBJECT-TYPE 1267 SYNTAX TruthValue 1268 MAX-ACCESS read-only 1269 STATUS current 1270 DESCRIPTION 1271 "The current status of the SMF node in the context of 1272 the MANETs relay set. A value of true(1) indicates 1273 that the node is currently part of the MANET Relay 1274 Set. A value of false(2) indicates that the node 1275 is currently not part of the MANET Relay Set." 1276 ::= { smfStateGroup 1 } 1278 smfDpdMemoryOverflow OBJECT-TYPE 1279 SYNTAX Counter32 1280 MAX-ACCESS read-only 1281 STATUS current 1282 DESCRIPTION 1283 "The number of times that the memory for caching 1284 records for DPD overran and records had to be flushed. 1285 The number of records to be flushed upon a buffer 1286 overflow is an implementation specific decision. 1287 " 1288 ::= { smfStateGroup 2 } 1289 -- 1290 -- Dynamically Discovered Multicast Addr Table 1291 -- 1293 smfDiscoveredAddrForwardingTable OBJECT-TYPE 1294 SYNTAX SEQUENCE OF SmfDiscoveredAddrForwardingEntry 1295 MAX-ACCESS not-accessible 1296 STATUS current 1297 DESCRIPTION 1298 "The (conceptual) table containing information on multicast 1299 addresses which are to be forwarded by the SMF process. 1301 Entries in this table are configured. As well, addresses 1302 to be forwarded by the SMF device can be dynamically discovered 1303 by other means. The corresponding state table, 1304 smfDiscoveredAddrForwardingTable contains 1305 these additional, dynamically discovered address for 1306 forwarding. 1308 Each row is associated with a range of multicast addresses, 1309 and ranges for different rows must be disjoint. 1310 " 1311 ::= { smfStateGroup 3 } 1313 smfDiscoveredAddrForwardingEntry OBJECT-TYPE 1314 SYNTAX SmfDiscoveredAddrForwardingEntry 1315 MAX-ACCESS not-accessible 1316 STATUS current 1317 DESCRIPTION 1318 "An entry (conceptual row) containing the information on a 1319 particular multicast scope." 1320 INDEX { smfDiscoveredAddrForwardingAddrType, 1321 smfDiscoveredAddrForwardingFirstAddr } 1322 ::= { smfDiscoveredAddrForwardingTable 1 } 1324 SmfDiscoveredAddrForwardingEntry ::= SEQUENCE { 1325 smfDiscoveredAddrForwardingAddrType InetAddressType, 1326 smfDiscoveredAddrForwardingFirstAddr InetAddress, 1327 smfDiscoveredAddrForwardingLastAddr InetAddress, 1328 smfDiscoveredAddrForwardingStatus RowStatus 1329 } 1331 smfDiscoveredAddrForwardingAddrType OBJECT-TYPE 1332 SYNTAX InetAddressType 1333 MAX-ACCESS not-accessible 1334 STATUS current 1335 DESCRIPTION 1336 "The type of the addresses in the multicast forwarding 1337 range. Legal values correspond to the subset of 1338 address families for which multicast address allocation 1339 is supported." 1340 ::= { smfDiscoveredAddrForwardingEntry 1 } 1342 smfDiscoveredAddrForwardingFirstAddr OBJECT-TYPE 1343 SYNTAX InetAddress (SIZE(0..20)) 1344 MAX-ACCESS not-accessible 1345 STATUS current 1346 DESCRIPTION 1347 "The first address in the multicast scope range. The type 1348 of this address is determined by the value of the 1349 smfConfiguredAddrForwardingAddrType object." 1350 ::= { smfDiscoveredAddrForwardingEntry 2 } 1352 smfDiscoveredAddrForwardingLastAddr OBJECT-TYPE 1353 SYNTAX InetAddress (SIZE(0..20)) 1354 MAX-ACCESS read-create 1355 STATUS current 1356 DESCRIPTION 1357 "The last address in the multicast scope range. 1358 The type of this address is determined by the 1359 value of the smfConfiguredAddrForwardingAddrType 1360 object." 1361 ::= { smfDiscoveredAddrForwardingEntry 3 } 1363 smfDiscoveredAddrForwardingStatus OBJECT-TYPE 1364 SYNTAX RowStatus 1365 MAX-ACCESS read-create 1366 STATUS current 1367 DESCRIPTION 1368 "The status of this row, by which new entries may be 1369 created, or old entries deleted from this table. If write 1370 access is supported, the other writable objects in this 1371 table may be modified even while the status is `active'." 1372 ::= { smfDiscoveredAddrForwardingEntry 4 } 1374 -- 1375 -- SMF Neighbor Table 1376 -- 1378 smfNeighborTable OBJECT-TYPE 1379 SYNTAX SEQUENCE OF SmfNeighborEntry 1380 MAX-ACCESS not-accessible 1381 STATUS current 1382 DESCRIPTION 1383 "The SMF NeighborTable describes the 1384 current neighbor nodes, their address 1385 and SMF RSSA and the interface on which 1386 they can be reached." 1387 REFERENCE 1388 "Simplified Multicast Forwarding for MANET 1389 (SMF), Macker, J., February 2008. 1390 Section 7: SMF Neighborhood Discovery 1391 Requirements." 1392 ::= { smfStateGroup 4 } 1394 smfNeighborEntry OBJECT-TYPE 1395 SYNTAX SmfNeighborEntry 1396 MAX-ACCESS not-accessible 1397 STATUS current 1398 DESCRIPTION 1399 "The SMF Neighbor Table contains the 1400 set of one-hop neighbors, the interface 1401 they are reachable on and the SMF RSSA 1402 they are currently running." 1403 INDEX { smfNeighborIpAddrType, 1404 smfNeighborIpAddr, 1405 smfNeighborPrefixLen } 1406 ::= { smfNeighborTable 1 } 1408 SmfNeighborEntry ::= 1409 SEQUENCE { 1410 smfNeighborIpAddrType InetAddressType, 1411 smfNeighborIpAddr InetAddress, 1412 smfNeighborPrefixLen InetAddressPrefixLength, 1413 smfNeighborRSSA SmfRssaID, 1414 smfNeighborNextHopInterface InterfaceIndexOrZero 1415 } 1417 smfNeighborIpAddrType OBJECT-TYPE 1418 SYNTAX InetAddressType 1419 MAX-ACCESS not-accessible 1420 STATUS current 1421 DESCRIPTION 1422 "The neighbor IP address type." 1423 ::= { smfNeighborEntry 1 } 1425 smfNeighborIpAddr OBJECT-TYPE 1426 SYNTAX InetAddress 1427 MAX-ACCESS not-accessible 1428 STATUS current 1429 DESCRIPTION 1430 "The neighbor Inet IPv4 or IPv6 address." 1432 ::= { smfNeighborEntry 2 } 1434 smfNeighborPrefixLen OBJECT-TYPE 1435 SYNTAX InetAddressPrefixLength 1436 MAX-ACCESS not-accessible 1437 STATUS current 1438 DESCRIPTION 1439 "The prefix length. This is a decimal value that 1440 indicates the number of contiguous, higher-order 1441 bits of the address that make up the network 1442 portion of the address." 1443 ::= { smfNeighborEntry 3 } 1445 smfNeighborRSSA OBJECT-TYPE 1446 SYNTAX SmfRssaID 1447 MAX-ACCESS read-only 1448 STATUS current 1449 DESCRIPTION 1450 "The current RSSA running on the neighbor. 1451 The list is identical to that described 1452 above for the smfRssa object." 1453 ::= { smfNeighborEntry 4 } 1455 smfNeighborNextHopInterface OBJECT-TYPE 1456 SYNTAX InterfaceIndexOrZero 1457 MAX-ACCESS read-only 1458 STATUS current 1459 DESCRIPTION 1460 "The interface ifIndex over which the 1461 neighbor is reachable in one-hop." 1462 ::= { smfNeighborEntry 5 } 1464 -- 1465 -- SMF Performance Group 1466 -- 1467 -- Contains objects which help to characterize the 1468 -- performance of the SMF RSSA process, such as statistics 1469 -- counters. There are two types of SMF RSSA statistics: 1470 -- global counters and per interface counters. 1471 -- 1473 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1475 smfGlobalPerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1476 -- 1477 -- IPv4 packet counters 1478 -- 1480 smfIpv4MultiPktsRecvTotal OBJECT-TYPE 1481 SYNTAX Counter32 1482 MAX-ACCESS read-only 1483 STATUS current 1484 DESCRIPTION 1485 "A counter of the total number of 1486 multicast IPv4 packets received by the 1487 device." 1488 ::= { smfGlobalPerfGroup 1 } 1490 smfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1491 SYNTAX Counter32 1492 MAX-ACCESS read-only 1493 STATUS current 1494 DESCRIPTION 1495 "A counter of the total number of 1496 multicast IPv4 packets forwarded by the 1497 device." 1498 ::= { smfGlobalPerfGroup 2 } 1500 smfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1501 SYNTAX Counter32 1502 MAX-ACCESS read-only 1503 STATUS current 1504 DESCRIPTION 1505 "A counter of the total number of duplicate 1506 multicast IPv4 packets detected by the 1507 device." 1508 ::= { smfGlobalPerfGroup 3 } 1510 smfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1511 SYNTAX Counter32 1512 MAX-ACCESS read-only 1513 STATUS current 1514 DESCRIPTION 1515 "A counter of the total number of dropped 1516 multicast IPv4 packets by the 1517 device due to TTL exceeded." 1518 ::= { smfGlobalPerfGroup 4 } 1520 smfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1521 SYNTAX Counter32 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "A counter of the total number of IPv4 packets 1526 recieved which have a TTL larger than that 1527 of a previously recived identical packet. 1528 " 1529 ::= { smfGlobalPerfGroup 5 } 1531 -- 1532 -- IPv6 packet counters 1533 -- 1535 smfIpv6MultiPktsRecvTotal OBJECT-TYPE 1536 SYNTAX Counter32 1537 MAX-ACCESS read-only 1538 STATUS current 1539 DESCRIPTION 1540 "A counter of the total number of 1541 multicast IPv6 packets received by the 1542 device." 1543 ::= { smfGlobalPerfGroup 6 } 1545 smfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1546 SYNTAX Counter32 1547 MAX-ACCESS read-only 1548 STATUS current 1549 DESCRIPTION 1550 "A counter of the total number of 1551 multicast IPv6 packets forwarded by the 1552 device." 1553 ::= { smfGlobalPerfGroup 7 } 1555 smfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1556 SYNTAX Counter32 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "A counter of the total number of duplicate 1561 multicast IPv6 packets detected by the 1562 device." 1563 ::= { smfGlobalPerfGroup 8 } 1565 smfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1566 SYNTAX Counter32 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "A counter of the total number of dropped 1571 multicast IPv6 packets by the 1572 device due to TTL exceeded." 1573 ::= { smfGlobalPerfGroup 9 } 1575 smfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1576 SYNTAX Counter32 1577 MAX-ACCESS read-only 1578 STATUS current 1579 DESCRIPTION 1580 "A counter of the total number of IPv6 packets 1581 recieved which have a TTL larger than that 1582 of a previously recived identical packet. 1583 " 1584 ::= { smfGlobalPerfGroup 10 } 1586 smfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1587 SYNTAX Counter32 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "A counter of the total number of IPv6 packets 1592 recieved which required the HAV assist for DPD. 1593 " 1594 ::= { smfGlobalPerfGroup 11 } 1596 smfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1597 SYNTAX Counter32 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "A counter of the total number of IPv6 packets 1602 recieved which the device inserted the 1603 DPD header option. 1604 " 1605 ::= { smfGlobalPerfGroup 12 } 1607 -- 1608 -- Per SMF Interface Performance Table 1609 -- 1611 smfInterfacePerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1613 smfIpv4InterfacePerfTable OBJECT-TYPE 1614 SYNTAX SEQUENCE OF SmfIpv4InterfacePerfEntry 1615 MAX-ACCESS not-accessible 1616 STATUS current 1617 DESCRIPTION 1618 "The SMF Interface Performance Table 1619 describes the SMF statistics per 1620 interface." 1621 ::= { smfInterfacePerfGroup 1 } 1623 smfIpv4InterfacePerfEntry OBJECT-TYPE 1624 SYNTAX SmfIpv4InterfacePerfEntry 1625 MAX-ACCESS not-accessible 1626 STATUS current 1627 DESCRIPTION 1628 "The SMF Interface Performance entry 1629 describes the statistics for a particular 1630 node interface." 1631 INDEX { smfIpv4IfPerfIfIndex } 1632 ::= { smfIpv4InterfacePerfTable 1 } 1634 SmfIpv4InterfacePerfEntry ::= 1635 SEQUENCE { 1636 smfIpv4IfPerfIfIndex InterfaceIndexOrZero, 1637 smfIpv4MultiPktsRecvPerIf Counter32, 1638 smfIpv4MultiPktsForwardedPerIf Counter32, 1639 smfIpv4DuplMultiPktsDetectedPerIf Counter32, 1640 smfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1641 smfIpv4TTLLargerThanPreviousPerIf Counter32 1642 } 1644 smfIpv4IfPerfIfIndex OBJECT-TYPE 1645 SYNTAX InterfaceIndexOrZero 1646 MAX-ACCESS not-accessible 1647 STATUS current 1648 DESCRIPTION 1649 "The ifIndex for this node interface 1650 that is collecting this set of 1651 performance management statistics." 1652 ::= { smfIpv4InterfacePerfEntry 1 } 1654 smfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1655 SYNTAX Counter32 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "A counter of the number of 1660 multicast IP packets received by the 1661 device on this interface." 1662 ::= { smfIpv4InterfacePerfEntry 2 } 1664 smfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1665 SYNTAX Counter32 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "A counter of the number of 1670 multicast IP packets forwarded by the 1671 device on this interface." 1672 ::= { smfIpv4InterfacePerfEntry 3 } 1674 smfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1675 SYNTAX Counter32 1676 MAX-ACCESS read-only 1677 STATUS current 1678 DESCRIPTION 1679 "A counter of the number of duplicate 1680 multicast IP packets detected by the 1681 device on this interface." 1682 ::= { smfIpv4InterfacePerfEntry 4 } 1684 smfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1685 SYNTAX Counter32 1686 MAX-ACCESS read-only 1687 STATUS current 1688 DESCRIPTION 1689 "A counter of the total number of dropped 1690 multicast IPv4 packets by the 1691 device due to TTL exceeded." 1692 ::= { smfIpv4InterfacePerfEntry 5 } 1694 smfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1695 SYNTAX Counter32 1696 MAX-ACCESS read-only 1697 STATUS current 1698 DESCRIPTION 1699 "A counter of the total number of IPv4 packets 1700 recieved which have a TTL larger than that 1701 of a previously recived identical packet. 1702 " 1703 ::= { smfIpv4InterfacePerfEntry 6 } 1705 smfIpv6InterfacePerfTable OBJECT-TYPE 1706 SYNTAX SEQUENCE OF SmfIpv6InterfacePerfEntry 1707 MAX-ACCESS not-accessible 1708 STATUS current 1709 DESCRIPTION 1710 "The SMF Interface Performance Table 1711 describes the SMF statistics per 1712 interface." 1713 ::= { smfInterfacePerfGroup 2 } 1714 smfIpv6InterfacePerfEntry OBJECT-TYPE 1715 SYNTAX SmfIpv6InterfacePerfEntry 1716 MAX-ACCESS not-accessible 1717 STATUS current 1718 DESCRIPTION 1719 "The SMF Interface Performance entry 1720 describes the statistics for a particular 1721 node interface." 1722 INDEX { smfIpv6IfPerfIfIndex } 1723 ::= { smfIpv6InterfacePerfTable 1 } 1725 SmfIpv6InterfacePerfEntry ::= 1726 SEQUENCE { 1727 smfIpv6IfPerfIfIndex InterfaceIndexOrZero, 1728 smfIpv6MultiPktsRecvPerIf Counter32, 1729 smfIpv6MultiPktsForwardedPerIf Counter32, 1730 smfIpv6DuplMultiPktsDetectedPerIf Counter32, 1731 smfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1732 smfIpv6TTLLargerThanPreviousPerIf Counter32, 1733 smfIpv6HAVAssistsReqdPerIf Counter32, 1734 smfIpv6DpdHeaderInsertionsPerIf Counter32 1735 } 1737 smfIpv6IfPerfIfIndex OBJECT-TYPE 1738 SYNTAX InterfaceIndexOrZero 1739 MAX-ACCESS not-accessible 1740 STATUS current 1741 DESCRIPTION 1742 "The ifIndex for this node interface 1743 that is collecting this set of 1744 performance management statistics. 1746 For packets generated locally at 1747 this node, performance counters 1748 are assigned to the loopback 1749 interface. 1750 " 1751 ::= { smfIpv6InterfacePerfEntry 1 } 1753 smfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1754 SYNTAX Counter32 1755 MAX-ACCESS read-only 1756 STATUS current 1757 DESCRIPTION 1758 "A counter of the number of 1759 multicast IP packets received by the 1760 device on this interface." 1761 ::= { smfIpv6InterfacePerfEntry 2 } 1762 smfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 1763 SYNTAX Counter32 1764 MAX-ACCESS read-only 1765 STATUS current 1766 DESCRIPTION 1767 "A counter of the number of 1768 multicast IP packets forwarded by the 1769 device on this interface." 1770 ::= { smfIpv6InterfacePerfEntry 3 } 1772 smfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 1773 SYNTAX Counter32 1774 MAX-ACCESS read-only 1775 STATUS current 1776 DESCRIPTION 1777 "A counter of the number of duplicate 1778 multicast IP packets detected by the 1779 device on this interface." 1780 ::= { smfIpv6InterfacePerfEntry 4 } 1782 smfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1783 SYNTAX Counter32 1784 MAX-ACCESS read-only 1785 STATUS current 1786 DESCRIPTION 1787 "A counter of the number of dropped 1788 multicast IP packets by the 1789 device on this interface due to TTL 1790 exceeded." 1791 ::= { smfIpv6InterfacePerfEntry 5 } 1793 smfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 1794 SYNTAX Counter32 1795 MAX-ACCESS read-only 1796 STATUS current 1797 DESCRIPTION 1798 "A counter of the total number of IPv6 packets 1799 recieved which have a TTL larger than that 1800 of a previously recived identical packet. 1801 " 1802 ::= { smfIpv6InterfacePerfEntry 6 } 1804 smfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 1805 SYNTAX Counter32 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION 1809 "A counter of the total number of IPv6 packets 1810 recieved which required the HAV assist for DPD. 1811 " 1812 ::= { smfIpv6InterfacePerfEntry 7 } 1814 smfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 1815 SYNTAX Counter32 1816 MAX-ACCESS read-only 1817 STATUS current 1818 DESCRIPTION 1819 "A counter of the total number of IPv6 packets 1820 recieved which the device inserted the 1821 DPD header option. 1822 " 1823 ::= { smfIpv6InterfacePerfEntry 8 } 1825 -- 1826 -- Reports Control 1827 -- This and the following tables are modeled 1828 -- after the report control and collection 1829 -- capabilities found in RMON II, RFC XXXX 1831 -- 1832 -- Note: Starting down this road only for general performance 1833 -- measures first. If desireable, then will add reports for 1834 -- IF specific measurements. 1835 -- 1837 smfReportsGroup OBJECT IDENTIFIER ::= { smfMIBObjects 5 } 1839 smfGenReportCntrlTable OBJECT-TYPE 1840 SYNTAX SEQUENCE OF SmfGenReportCntrlEntry 1841 MAX-ACCESS not-accessible 1842 STATUS current 1843 DESCRIPTION 1844 "The smfGenReportCntrlTable is the controlling entry 1845 that manages the population of studies in the 1846 Report for selected time intervals. 1848 Note that this is not like the typical RMON 1849 controlTable and dataTable in which each entry creates 1850 its own data table. Each entry in this table enables the 1851 creation of multiple data tables on a study basis. For each 1852 interval, the study is updated in place, and the current 1853 data content of the table becomes invalid. 1855 The control table entries are persistent across 1856 system reboots." 1857 ::= { smfReportsGroup 1 } 1859 smfGenReportCntrlEntry OBJECT-TYPE 1860 SYNTAX SmfGenReportCntrlEntry 1861 MAX-ACCESS not-accessible 1862 STATUS current 1863 DESCRIPTION 1864 "A conceptual row in the smfGenReportCntrlTable. 1866 An example of the indexing of this entry is 1867 smfGenReportCntrInterval.1" 1868 INDEX { smfGenReportCntrlIndex } 1869 ::= { smfGenReportCntrlTable 1 } 1871 SmfGenReportCntrlEntry ::= SEQUENCE { 1872 smfGenReportCntrlIndex Unsigned32, 1873 smfGenReportCntrlInterval Unsigned32, 1874 smfGenReportCntrlReqSize Unsigned32, 1875 smfGenReportCntrlGrantedSize Unsigned32, 1876 smfGenReportCntrlReqReports Unsigned32, 1877 smfGenReportCntrlGrantedReports Unsigned32, 1878 smfGenReportCntrlStartTime TimeStamp, 1879 smfGenReportCntrlReportNumber Unsigned32, 1880 smfGenReportCntrlInsertsDenied Counter32, 1881 smfGenReportCntrlOwner OwnerString, 1882 smfGenReportCntrlStorageType StorageType, 1883 smfGenReportCntrlStatus RowStatus 1884 } 1886 smfGenReportCntrlIndex OBJECT-TYPE 1887 SYNTAX Unsigned32 (1..65535) 1888 MAX-ACCESS not-accessible 1889 STATUS current 1890 DESCRIPTION 1891 "An index that uniquely identifies an entry in the 1892 smfGenReportCntrlTable. Each such entry defines a unique 1893 report whose results are placed in the smfGenReportTable on 1894 behalf of this smfGenReportCntrlEntry." 1895 ::= { smfGenReportCntrlEntry 1 } 1897 smfGenReportCntrlInterval OBJECT-TYPE 1898 SYNTAX Unsigned32 1899 UNITS "Seconds" 1900 MAX-ACCESS read-create 1901 STATUS current 1902 DESCRIPTION 1903 "The interval in seconds over which data is accumulated before 1904 being aggregated into a report in the smfGenReportTable. 1905 All reports with the same smfGenReportCntrlIndex will be 1906 based on the same interval. 1908 This object may not be modified if the associated 1909 smfGenReportCntrlStatus object is equal to active(1)." 1910 DEFVAL { 3600 } 1911 ::= { smfGenReportCntrlEntry 2 } 1913 smfGenReportCntrlReqSize OBJECT-TYPE 1914 SYNTAX Unsigned32 1915 MAX-ACCESS read-create 1916 STATUS current 1917 DESCRIPTION 1918 "The maximum number of Client and Server combination 1919 entries requested for this report. 1921 When this object is created or modified, the probe 1922 should set smfGenReportCntrlGrantedSize as closely to this 1923 object as is possible for the particular probe 1924 implementation and available resources. 1926 It is important to note that this value is the number of 1927 requested entries in the smfGenReportTable only. 1929 This object may not be modified if the associated 1930 smfGenReportCntrlStatus object is equal to active(1)." 1931 ::= { smfGenReportCntrlEntry 3 } 1933 smfGenReportCntrlGrantedSize OBJECT-TYPE 1934 SYNTAX Unsigned32 1935 MAX-ACCESS read-only 1936 STATUS current 1937 DESCRIPTION 1938 "The maximum number of performance entries in this report. 1940 When the associated smfGenReportCntrlReqSize object is 1941 created or modified, the probe should set this 1942 object as closely to the requested value as is 1943 possible for the particular implementation and 1944 available resources. The probe must not lower this 1945 value except as a result of a set to the associated 1946 smfGenReportCntrlReqSize object. 1948 It is an implementation-specific matter as to whether 1949 zero-valued entries are available." 1950 ::= { smfGenReportCntrlEntry 4 } 1952 smfGenReportCntrlReqReports OBJECT-TYPE 1953 SYNTAX Unsigned32 (1..65535) 1954 MAX-ACCESS read-create 1955 STATUS current 1956 DESCRIPTION 1957 "The number of saved reports requested to be allocated on 1958 behalf of this entry. 1960 This object may not be modified if the associated 1961 smfGenReportCntrlStatus object is equal to active(1)." 1962 ::= { smfGenReportCntrlEntry 5 } 1964 smfGenReportCntrlGrantedReports OBJECT-TYPE 1965 SYNTAX Unsigned32 (0..65535) 1966 MAX-ACCESS read-only 1967 STATUS current 1968 DESCRIPTION 1969 "The number of saved reports the agent has allocated based 1970 on the requested amount in smfGenReportCntrlReqReports. 1971 Because each report can have many entries, the total number 1972 of entries allocated will be this number multiplied by the 1973 value of smfGenReportCntrlGrantedSize, or by 1 if that 1974 object doesn't exist. 1976 When the associated smfGenReportCntrlReqReports object is 1977 created or modified, the agent should set this object as 1978 closely to the requested value as is possible for the 1979 particular implementation and available resources. When 1980 considering available resources, the agent must consider its 1981 ability to allocate this many reports, each with the number 1982 of entries represented by smfGenReportCntrlGrantedSize, or 1983 by 1 if that object doesn't exist. 1985 Note that although the storage required for each report may 1986 fluctuate due to changing conditions, the agent must continue 1987 to have storage available to satisfy the full report size for 1988 all reports, when necessary. Further, the agent must not 1989 lower this value except as a result of a set to the 1990 associated smfGenReportCntrlReqSize object." 1991 ::= { smfGenReportCntrlEntry 6 } 1993 smfGenReportCntrlStartTime OBJECT-TYPE 1994 SYNTAX TimeStamp 1995 MAX-ACCESS read-only 1996 STATUS current 1997 DESCRIPTION 1998 "The value of sysUpTime when the system began processing the 1999 report in progress. Note that the report in progress is not 2000 available. 2002 This object may be used by the management station to figure 2003 out the start time for all previous reports saved for this 2004 smfGenReportCntrlEntry, as reports are started at fixed 2005 intervals." 2006 ::= { smfGenReportCntrlEntry 7 } 2008 smfGenReportCntrlReportNumber OBJECT-TYPE 2009 SYNTAX Unsigned32 2010 MAX-ACCESS read-only 2011 STATUS current 2012 DESCRIPTION 2013 "The number of the report in progress. When an 2014 smfGenReportCntrlEntry is activated, the first report will 2015 be numbered zero." 2016 ::= { smfGenReportCntrlEntry 8 } 2018 smfGenReportCntrlInsertsDenied OBJECT-TYPE 2019 SYNTAX Counter32 2020 MAX-ACCESS read-only 2021 STATUS current 2022 DESCRIPTION 2023 "The number of attempts to add an entry to reports for 2024 this SmfGenReportCntrlEntry that failed because the number 2025 of entries would have exceeded smfGenReportCntrlGrantedSize. 2027 This number is valuable in determining if enough entries have 2028 been allocated for reports in light of fluctuating network 2029 usage. Note that an entry that is denied will often be 2030 attempted again, so this number will not predict the exact 2031 number of additional entries needed, but it can be used to 2032 understand the relative magnitude of the problem. 2034 Also note that there is no ordering specified for the entries 2035 in the report; thus, there are no rules for which entries 2036 will be omitted when not enough entries are available. As a 2037 consequence, the agent is not required to delete 'least 2038 valuable' entries first." 2039 ::= { smfGenReportCntrlEntry 9 } 2041 smfGenReportCntrlOwner OBJECT-TYPE 2042 SYNTAX OwnerString 2043 MAX-ACCESS read-create 2044 STATUS current 2045 DESCRIPTION 2046 "The entity that configured this entry and is 2047 therefore using the resources assigned to it. 2049 This object may not be modified if the associated 2050 smfGenReportCntrlStatus object is equal to active(1)." 2051 ::= { smfGenReportCntrlEntry 10 } 2053 smfGenReportCntrlStorageType OBJECT-TYPE 2054 SYNTAX StorageType 2055 MAX-ACCESS read-create 2056 STATUS current 2057 DESCRIPTION 2058 "The storage type of this smfGenReportCntrlEntry. If the 2059 value of this object is 'permanent', no objects in this row 2060 need to be writable." 2061 ::= { smfGenReportCntrlEntry 11 } 2063 smfGenReportCntrlStatus OBJECT-TYPE 2064 SYNTAX RowStatus 2065 MAX-ACCESS read-create 2066 STATUS current 2067 DESCRIPTION 2068 "The status of this performance control entry. 2070 An entry may not exist in the active state unless each 2071 object in the entry has an appropriate value. 2073 Once this object is set to active(1), no objects in the 2074 smfGenReportCntrlTable can be changed. 2076 If this object is not equal to active(1), all associated 2077 entries in the smfGenReportTable shall be deleted." 2078 ::= { smfGenReportCntrlEntry 12 } 2080 -- 2081 -- Reports 2082 -- (Note: This represents a rather conservative list 2083 -- of objects for inclusion within offline report 2084 -- generation. As discussions evolve, more objects 2085 -- may be added to the below set. 2086 -- 2087 -- Also, it is typical to use this construct to define 2088 -- objects representing statistical information and not 2089 -- counter associated information. We need to define a set 2090 -- of statistical objects for these remote reports and 2091 -- replace this place-holder set prior to finalizing this MIB.) 2092 -- 2094 smfGenReportTable OBJECT-TYPE 2095 SYNTAX SEQUENCE OF SmfGenReportEntry 2096 MAX-ACCESS not-accessible 2097 STATUS current 2098 DESCRIPTION 2099 "This table contains 2100 studies for each of the control table entries in 2101 smfGenReportCntrlTable. These studies are 2102 provided based on the selections and parameters 2103 found for the entry in the 2104 smfGenReportCntrlTable. 2106 The performance counter are the same as those 2107 specified in the smfPerformanceGroup." 2108 ::= { smfReportsGroup 2 } 2110 smfGenReportEntry OBJECT-TYPE 2111 SYNTAX SmfGenReportEntry 2112 MAX-ACCESS not-accessible 2113 STATUS current 2114 DESCRIPTION 2115 "A conceptual row in the smfGenReportTable. 2117 The smfGenReportCntrlIndex value in the index identifies the 2118 smfGenReportCntrlEntry on whose behalf this entry was 2119 created. 2121 The smfGenReportIndex value in the index identifies which 2122 report (in the series of reports) this entry is a part of. 2124 An example of the indexing of this entry is 2125 smfGenReportMultiPktsForwarded.3.15" 2126 INDEX { smfGenReportCntrlIndex, 2127 smfGenReportIndex 2128 } 2129 ::= { smfGenReportTable 1 } 2131 SmfGenReportEntry ::= SEQUENCE { 2132 smfGenReportIndex Unsigned32, 2133 smfGenReportIpv4MultiPktsRecvTot ZeroBasedCounter32, 2134 smfGenReportIpv4MultiPktsForwardedTot ZeroBasedCounter32, 2135 smfGenReportIpv4DuplMultiPktsDetectedTot ZeroBasedCounter32, 2136 smfGenReportIpv4DroppedMultiPktsTTLExceededTot ZeroBasedCounter32 2137 } 2139 smfGenReportIndex OBJECT-TYPE 2140 SYNTAX Unsigned32 (1..2147483647) 2141 MAX-ACCESS not-accessible 2142 STATUS current 2143 DESCRIPTION 2144 "The value of smfGenReportCntrlNumber for the report to 2145 which this entry belongs." 2146 ::= { smfGenReportEntry 1 } 2148 smfGenReportIpv4MultiPktsRecvTot OBJECT-TYPE 2149 SYNTAX ZeroBasedCounter32 2150 MAX-ACCESS read-only 2151 STATUS current 2152 DESCRIPTION 2153 "The count of the total number of ...." 2154 ::= { smfGenReportEntry 2 } 2156 smfGenReportIpv4MultiPktsForwardedTot OBJECT-TYPE 2157 SYNTAX ZeroBasedCounter32 2158 MAX-ACCESS read-only 2159 STATUS current 2160 DESCRIPTION 2161 "The count of the total number of ...." 2162 ::= { smfGenReportEntry 3 } 2164 smfGenReportIpv4DuplMultiPktsDetectedTot OBJECT-TYPE 2165 SYNTAX ZeroBasedCounter32 2166 MAX-ACCESS read-only 2167 STATUS current 2168 DESCRIPTION 2169 "The count of the total number of ...." 2170 ::= { smfGenReportEntry 4 } 2172 smfGenReportIpv4DroppedMultiPktsTTLExceededTot OBJECT-TYPE 2173 SYNTAX ZeroBasedCounter32 2174 MAX-ACCESS read-only 2175 STATUS current 2176 DESCRIPTION 2177 "The count of the total number of ...." 2178 ::= { smfGenReportEntry 5 } 2180 -- 2181 -- Notifications 2182 -- 2184 -- Note: What notifications do we want for this MIB? 2186 -- 2187 -- Compliance Statements 2188 -- 2189 -- Note: need to update the Compliance section once the mib 2190 -- objects stablize. 2192 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2193 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2195 smfBasicCompliance MODULE-COMPLIANCE 2196 STATUS current 2197 DESCRIPTION "The basic implementation requirements for 2198 managed network entities that implement 2199 the SMF RSSA process." 2200 MODULE -- this module 2201 MANDATORY-GROUPS { smfCapabObjectsGroup, 2202 smfConfigObjectsGroup } 2203 ::= { smfCompliances 1 } 2205 smfFullCompliance MODULE-COMPLIANCE 2206 STATUS current 2207 DESCRIPTION "The full implementation requirements for 2208 managed network entities that implement 2209 the SMF RSSA process." 2210 MODULE -- this module 2211 MANDATORY-GROUPS { smfCapabObjectsGroup, 2212 smfConfigObjectsGroup, 2213 smfStateObjectsGroup, 2214 smfPerfObjectsGroup, 2215 smfRepObjectsGroup } 2216 ::= { smfCompliances 2 } 2218 -- 2219 -- Units of Conformance 2220 -- 2222 smfCapabObjectsGroup OBJECT-GROUP 2223 OBJECTS { 2224 smfOpModeCapabilitiesName, 2225 smfOpModeCapabilitiesReference, 2227 smfRssaCapabilitiesName, 2228 smfRssaCapabilitiesReference 2229 } 2230 STATUS current 2231 DESCRIPTION 2232 "Set of SMF configuration objects implemented 2233 in this module." 2234 ::= { smfMIBGroups 1 } 2235 smfConfigObjectsGroup OBJECT-GROUP 2236 OBJECTS { 2237 smfAdminStatus, 2238 smfConfiguredOpMode, 2239 smfConfiguredRssa, 2240 smfRssaMember, 2241 smfIpv4Dpd, 2242 smfIpv6Dpd, 2243 smfMaxPktLifetime, 2244 smfDpdMaxMemorySize, 2245 smfDpdEntryMaxLifetime, 2246 smfNhdpRssaMesgTLVIncluded, 2247 smfNhdpRssaAddrBlockTLVIncluded, 2248 smfNhdpRouterPriorityTLVIncluded, 2250 smfConfiguredAddrForwardingLastAddr, 2251 smfConfiguredAddrForwardingStatus, 2253 smfIfAdminStatus, 2254 smfIfRowStatus, 2256 smfGatewayFilterIf, 2257 smfGatewayFilterIfDirection, 2258 smfGatewayFilterRuleRank, 2259 smfGatewayFilterDestAddrType, 2260 smfGatewayFilterDestAddr, 2261 smfGatewayFilterDestAddrPrefixLen, 2262 smfGatewayFilterSrcAddrType, 2263 smfGatewayFilterSrcAddr, 2264 smfGatewayFilterSrcAddrPrefixLen, 2265 smfGatewayFilterProtocolNumber, 2266 smfGatewayFilterDestPortNumber, 2267 smfGatewayFilterAction, 2268 smfGatewayFilterRowStatus 2269 } 2270 STATUS current 2271 DESCRIPTION 2272 "Set of SMF configuration objects implemented 2273 in this module." 2274 ::= { smfMIBGroups 2 } 2276 smfStateObjectsGroup OBJECT-GROUP 2277 OBJECTS { 2278 smfNodeRsStatusIncluded, 2279 smfDpdMemoryOverflow, 2281 smfDiscoveredAddrForwardingLastAddr, 2282 smfDiscoveredAddrForwardingStatus, 2283 smfNeighborRSSA, 2284 smfNeighborNextHopInterface 2285 } 2286 STATUS current 2287 DESCRIPTION 2288 "Set of SMF state objects implemented 2289 in this module." 2290 ::= { smfMIBGroups 3 } 2292 smfPerfObjectsGroup OBJECT-GROUP 2293 OBJECTS { 2294 smfIpv4MultiPktsRecvTotal, 2295 smfIpv4MultiPktsForwardedTotal, 2296 smfIpv4DuplMultiPktsDetectedTotal, 2297 smfIpv4DroppedMultiPktsTTLExceededTotal, 2298 smfIpv4TTLLargerThanPreviousTotal, 2300 smfIpv6MultiPktsRecvTotal, 2301 smfIpv6MultiPktsForwardedTotal, 2302 smfIpv6DuplMultiPktsDetectedTotal, 2303 smfIpv6DroppedMultiPktsTTLExceededTotal, 2304 smfIpv6TTLLargerThanPreviousTotal, 2305 smfIpv6HAVAssistsReqdTotal, 2306 smfIpv6DpdHeaderInsertionsTotal, 2308 smfIpv4MultiPktsRecvPerIf, 2309 smfIpv4MultiPktsForwardedPerIf, 2310 smfIpv4DuplMultiPktsDetectedPerIf, 2311 smfIpv4DroppedMultiPktsTTLExceededPerIf, 2312 smfIpv4TTLLargerThanPreviousPerIf, 2314 smfIpv6MultiPktsRecvPerIf, 2315 smfIpv6MultiPktsForwardedPerIf, 2316 smfIpv6DuplMultiPktsDetectedPerIf, 2317 smfIpv6DroppedMultiPktsTTLExceededPerIf, 2318 smfIpv6TTLLargerThanPreviousPerIf, 2319 smfIpv6HAVAssistsReqdPerIf, 2320 smfIpv6DpdHeaderInsertionsPerIf 2321 } 2322 STATUS current 2323 DESCRIPTION 2324 "Set of SMF performance objects implemented 2325 in this module by total and per interface." 2326 ::= { smfMIBGroups 4 } 2328 smfRepObjectsGroup OBJECT-GROUP 2329 OBJECTS { 2330 smfGenReportCntrlInterval, 2331 smfGenReportCntrlReqSize, 2332 smfGenReportCntrlGrantedSize, 2333 smfGenReportCntrlReqReports, 2334 smfGenReportCntrlGrantedReports, 2335 smfGenReportCntrlStartTime, 2336 smfGenReportCntrlReportNumber, 2337 smfGenReportCntrlInsertsDenied, 2338 smfGenReportCntrlOwner, 2339 smfGenReportCntrlStorageType, 2340 smfGenReportCntrlStatus, 2342 smfGenReportIpv4MultiPktsRecvTot, 2343 smfGenReportIpv4MultiPktsForwardedTot, 2344 smfGenReportIpv4DuplMultiPktsDetectedTot, 2345 smfGenReportIpv4DroppedMultiPktsTTLExceededTot 2346 } 2347 STATUS current 2348 DESCRIPTION 2349 "Set of SMF reports objects implemented 2350 in this module." 2351 ::= { smfMIBGroups 5 } 2353 END 2355 8. Security Considerations 2357 [TODO] Each specification that defines one or more MIB modules MUST 2358 contain a section that discusses security considerations relevant to 2359 those modules. This section MUST be patterned after the latest 2360 approved template (available at 2361 http://www.ops.ietf.org/mib-security.html). Remember that the 2362 objective is not to blindly copy text from the template, but rather 2363 to think and evaluate the risks/vulnerabilities and then state/ 2364 document the result of this evaluation. 2366 [TODO] if you have any read-write and/or read-create objects, please 2367 include the following boilerplate paragraph. 2369 There are a number of management objects defined in this MIB module 2370 with a MAX-ACCESS clause of read-write and/or read-create. Such 2371 objects may be considered sensitive or vulnerable in some network 2372 environments. The support for SET operations in a non-secure 2373 environment without proper protection can have a negative effect on 2374 network operations. These are the tables and objects and their 2375 sensitivity/vulnerability: 2377 o [TODO] writable MIB objects that could be especially disruptive if 2378 abused MUST be explicitly listed by name and the associated 2379 security risks MUST be spelled out; RFC 2669 has a very good 2380 example. 2382 o [TODO] list the writable tables and objects and state why they are 2383 sensitive. 2385 [TODO] else if there are no read-write objects in your MIB module, 2386 use the following boilerplate paragraph. 2388 There are no management objects defined in this MIB module that have 2389 a MAX-ACCESS clause of read-write and/or read-create. So, if this 2390 MIB module is implemented correctly, then there is no risk that an 2391 intruder can alter or create any management objects of this MIB 2392 module via direct SNMP SET operations. 2394 [TODO] if you have any sensitive readable objects, please include the 2395 following boilerplate paragraph. 2397 Some of the readable objects in this MIB module (i.e., objects with a 2398 MAX-ACCESS other than not-accessible) may be considered sensitive or 2399 vulnerable in some network environments. It is thus important to 2400 control even GET and/or NOTIFY access to these objects and possibly 2401 to even encrypt the values of these objects when sending them over 2402 the network via SNMP. These are the tables and objects and their 2403 sensitivity/vulnerability: 2405 o [TODO] you must explicitly list by name any readable objects that 2406 are sensitive or vulnerable and the associated security risks MUST 2407 be spelled out (for instance, if they might reveal customer 2408 information or violate personal privacy laws such as those of the 2409 European Union if exposed to unauthorized parties) 2411 o [TODO] list the tables and objects and state why they are 2412 sensitive. 2414 [TODO] discuss what security the protocol used to carry the 2415 information should have. The following three boilerplate paragraphs 2416 should not be changed without very good reason. Changes will almost 2417 certainly require justification during IESG review. 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 It is RECOMMENDED that implementers consider the security features as 2426 provided by the SNMPv3 framework (see [RFC3410], section 8), 2427 including full support for the SNMPv3 cryptographic mechanisms (for 2428 authentication and privacy). 2430 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2431 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2432 enable cryptographic security. It is then a customer/operator 2433 responsibility to ensure that the SNMP entity giving access to an 2434 instance of this MIB module is properly configured to give access to 2435 the objects only to those principals (users) that have legitimate 2436 rights to indeed GET or SET (change/create/delete) them. 2438 9. IANA Considerations 2440 [TODO] In order to comply with IESG policy as set forth in 2441 http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is 2442 submitted to the IESG for publication MUST contain an IANA 2443 Considerations section. The requirements for this section vary 2444 depending what actions are required of the IANA. see RFC4181 section 2445 3.5 for more information on writing an IANA clause for a MIB module 2446 document. 2448 [TODO] select an option and provide the necessary details. 2450 Option #1: 2452 The MIB module in this document uses the following IANA-assigned 2453 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2455 Descriptor OBJECT IDENTIFIER value 2456 ---------- ----------------------- 2458 sampleMIB { mib-2 XXX } 2460 Option #2: 2462 Editor's Note (to be removed prior to publication): the IANA is 2463 requested to assign a value for "XXX" under the 'mib-2' subtree and 2464 to record the assignment in the SMI Numbers registry. When the 2465 assignment has been made, the RFC Editor is asked to replace "XXX" 2466 (here and in the MIB module) with the assigned value and to remove 2467 this note. 2469 Note well: prior to official assignment by the IANA, a draft document 2470 MUST use placeholders (such as "XXX" above) rather than actual 2471 numbers. See RFC4181 Section 4.5 for an example of how this is done 2472 in a draft MIB module. 2474 Option #3: 2476 This memo includes no request to IANA. 2478 10. Contributors 2480 This MIB document uses the template authored by D. Harrington which 2481 is based on contributions from the MIB Doctors, especially Juergen 2482 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2484 11. Acknowledgements 2486 12. References 2488 12.1. Normative References 2490 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 2491 Interfaces Group MIB", RFC 2863, June 2000. 2493 [RFC3418] Presuhn, R., "Management Information Base (MIB) 2494 for the Simple Network Management Protocol 2495 (SNMP)", STD 62, RFC 3418, December 2002. 2497 [RFC2119] Bradner, S., "Key words for use in RFCs to 2498 Indicate Requirement Levels", BCP 14, RFC 2119, 2499 March 1997. 2501 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2502 Schoenwaelder, Ed., "Structure of Management 2503 Information Version 2 (SMIv2)", STD 58, 2504 RFC 2578, April 1999. 2506 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2507 Schoenwaelder, Ed., "Textual Conventions for 2508 SMIv2", STD 58, RFC 2579, April 1999. 2510 [RFC2580] McCloghrie, K., Perkins, D., and J. 2511 Schoenwaelder, "Conformance Statements for 2512 SMIv2", STD 58, RFC 2580, April 1999. 2514 [I-D.ietf-manet-smf] Macker, J. and S. Team, "Simplified Multicast 2515 Forwarding for MANET", draft-ietf-manet-smf-08 2516 (work in progress), November 2008. 2518 12.2. Informative References 2520 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 2521 Stewart, "Introduction and Applicability 2522 Statements for Internet-Standard Management 2523 Framework", RFC 3410, December 2002. 2525 Appendix A. Change Log 2527 Not applicable to draft 00 2529 1. 2531 Appendix B. Open Issues 2533 This section contains the set of open issues related to the 2534 development and design of the SMF-MIB. This section will not be 2535 present in the final version of the MIB and will be removed once all 2536 the open issues have been resolved. 2538 1. Clarify handling of the NHDP TLV message inclusions? 2540 2. Can we develop a capabilities table for the supported RSSA 2541 algorithms? And, if so, can each supported RSSA have a 2542 different set of configuration parameters? 2544 3. Is the Gateway Filter table appropriate for this MIB or should 2545 it be handled in a separate MIB worked elsewhere? How should 2546 this table be indexed and how should it represent the ordering 2547 of the rules (or chains)? Should this be greatly simplified? 2548 How do we handle null values in the rules? 2550 4. Is it useful to track the effectiveness of the coverage of the 2551 current RSSA? Is it possible to track this? 2553 5. Complete notification group. 2555 6. Complete conformance group. 2557 7. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 2559 8. Update the text of the document to reflect the final state of 2560 the MIB. 2562 9. Identify all objects requiring non-volatile storage in their 2563 DESCRIPTION clauses. 2565 10. Incorporate parameter relationship conditions into their 2566 DESCRIPTION clauses. 2568 11. Complete the security analysis and section. 2570 12. Cleanup all the [TODOs] from the MIB template. 2572 Appendix C. 2574 *************************************************************** 2575 * Note to the RFC Editor (to be removed prior to publication) * 2576 * * 2577 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 2578 * of the MIB module point to this draft and are to be * 2579 * assigned by the RFC Editor. * 2580 * * 2581 * 2) The reference to RFCXXX2 throughout this document point * 2582 * to the current draft-ietf-manet-smf-xx.txt. This * 2583 * need to be replaced with the XXX RFC number. * 2584 * * 2585 *************************************************************** 2587 Authors' Addresses 2589 Robert G. Cole 2590 Johns Hopkins University 2591 11100 Johns Hopkins Road, Room 257 2592 Laurel, Maryland 21073 2593 USA 2595 Phone: +1 443 778 6951 2596 EMail: robert.cole@jhuapl.edu 2597 URI: http://www.cs.jhu.edu/~rgcole/ 2599 Joseph Macker 2600 Naval Research Laboratory 2601 Washington, D.C. 20375 2602 USA 2604 EMail: macker@itd.nrl.navy.mil 2605 Brian Adamson 2606 Naval Research Laboratory 2607 Washington, D.C. 20375 2608 USA 2610 EMail: adamson@itd.nrl.navy.mil 2612 Sean Harnedy 2613 Booz Allen Hamilton 2614 333 City Boulevard West 2615 Orange, CA 92868 2616 USA 2618 EMail: harnedy_sean@bah.com