idnits 2.17.1 draft-cole-manet-smf-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 20. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1780. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1791. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1798. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1804. 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 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 (November 3, 2008) is 5652 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 1590, but not defined == Missing Reference: 'RFC4001' is mentioned on line 354, but not defined == Missing Reference: 'RFC 4001' is mentioned on line 710, but not defined == Missing Reference: 'TODOs' is mentioned on line 1713, but not defined == Outdated reference: A later version (-14) exists of draft-ietf-manet-smf-07 ** Downref: Normative reference to an Experimental draft: draft-ietf-manet-smf (ref. 'I-D.ietf-manet-smf') Summary: 2 errors (**), 0 flaws (~~), 7 warnings (==), 7 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: May 7, 2009 B. Adamson 6 Navy Research Laboratory 7 S. Harnedy 8 Booz Allen Hamilton 9 November 3, 2008 11 Definition of Managed Objects for the Manet Simplified Multicast 12 Framework Relay Set Process 13 draft-cole-manet-smf-mib-01 15 Status of This Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on May 7, 2009. 40 Copyright Notice 42 Copyright (C) The IETF Trust (2008). 44 Abstract 46 This memo defines a portion of the Management Information Base (MIB) 47 for use with network management protocols in the Internet community. 48 In particular, it describes objects for configuring aspects of the 49 Simplified Multicast Forwarding (SMF) process. The SMF MIB also 50 reports state information, performance metrics, and notifications. 51 In addition to configuration, this additional state and performance 52 information is useful to management stations troubleshooting 53 multicast forwarding problems. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. The Internet-Standard Management Framework . . . . . . . . . . 3 59 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 62 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 64 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 65 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 6 66 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7 67 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 7 68 5.5. The Notifications Group . . . . . . . . . . . . . . . . . 7 69 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 70 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 71 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 8 72 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 73 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 74 8. Security Considerations . . . . . . . . . . . . . . . . . . . 33 75 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35 76 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 35 77 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 36 78 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 36 79 12.1. Normative References . . . . . . . . . . . . . . . . . . . 36 80 12.2. Informative References . . . . . . . . . . . . . . . . . . 36 81 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 36 82 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 37 84 1. Introduction 86 This memo defines a portion of the Management Information Base (MIB) 87 for use with network management protocols in the Internet community. 88 In particular, it describes objects for configuring aspects of a 89 process implementing Simplified Multicast Forwarding (SMF) 90 [I-D.ietf-manet-smf]. SMF provides multicast duplicate packet 91 detection (DPD) and supports algorithms for constructing an estimate 92 of a mobile ad hoc network (MANET) Minimum Connected Dominating Set 93 (MCDS) for efficient multicast forwarding. The SMF MIB also reports 94 state information, performance metrics, and notifications. In 95 addition to configuration, this additional state and performance 96 information is useful to management stations troubleshooting 97 multicast forwarding problems. 99 2. The Internet-Standard Management Framework 101 For a detailed overview of the documents that describe the current 102 Internet-Standard Management Framework, please refer to section 7 of 103 RFC 3410 [RFC3410]. 105 Managed objects are accessed via a virtual information store, termed 106 the Management Information Base or MIB. MIB objects are generally 107 accessed through the Simple Network Management Protocol (SNMP). 108 Objects in the MIB are defined using the mechanisms defined in the 109 Structure of Management Information (SMI). This memo specifies a MIB 110 module that is compliant to the SMIv2, which is described in STD 58, 111 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 112 [RFC2580]. 114 3. Conventions 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted as described in RFC 2119 [RFC2119]. 120 4. Overview 122 SMF provides methods for implementing DPD-based multicast forwarding 123 with the optional use of CDS-based relay sets. The MCDS is the 124 smallest set of MANET nodes (comprising a connected cluster) which 125 cover all the nodes in the cluster with their transmissions. As the 126 density of the MANET nodes increase, the fraction of nodes required 127 in an MCDS decreases. Using the MCDS as a multicast forwarding set 128 then becomes an efficient multicast mechanism for MANETs. 130 Various algorithms for the construction of estimates of the MCDS 131 exist. The Simplified Multicast Framework [I-D.ietf-manet-smf] 132 describes some of these. It further defines various operational 133 modes for a node which is participating in the collective creation of 134 the MCDS estimates. These modes depend upon the set of related MANET 135 routing and discovery protocols and mechanisms in operation in the 136 specific MANET node. 138 A SMF routers' MIB contains SMF process configuration parameters 139 (e.g. specific CDS algorithm), state information (e.g., current 140 membership in the CDS), performance counters (e.g., packet counters), 141 and notifications. 143 4.1. SMF Management Model 145 This section describes the management model for the SMF node process. 147 Figure 1 (reproduced from Figure 4 of [I-D.ietf-manet-smf]) shows the 148 relationship between the SMF Relay Set selection algorithm and the 149 related algorithms, processes and protocols running in the MANET 150 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 151 topology information gotten from the MANET Neighborhood Discovery 152 Protocol (NHDP), from the specific MANET routing protocol running on 153 the node, or from Layer 2 information passed up to the higher layer 154 protocol processes. 156 Possible L2 Trigger/Information 157 | 158 | 159 ______________ ______|_____ __________________ 160 | MANET | | | | | 161 | Neighborhood | | Relay Set | | Other Heuristics | 162 | Discovery |------------| Selection |-------| (Preference,etc) | 163 | Protocol | neighbor | Algorithm | | | 164 |______________| info |____________| |__________________| 165 \ / 166 \ / 167 neighbor\ / Dynamic Relay 168 info* \ ____________ / Set Status 169 \ | SMF | / (State, {neighbor info}) 170 `---| Relay Set |---' 171 | State | 172 ---|____________| 173 / 174 / 175 ______________ 176 | Coexistent | 177 | MANET | 178 | Unicast | 179 | Process | 180 |______________| 182 Figure 1: SMF Relay Set Control Options 184 4.2. Terms 186 The following definitions apply throughout this document: 188 o Configuration Objects - switches, tables, objects which are 189 initialized to default settings or set through the management 190 interface defined by this MIB. 192 o Tunable Configuration Objects - objects whose values affect timing 193 or attempt bounds on the SMF RS process. 195 o State Objects - automatically generated values which define the 196 current operating state of the SMF RS process in the router. 198 o Performance Objects - automatically generated values which help an 199 administrator or automated tool to assess the performance of the 200 CDS multicast process on the router and the overall multicasting 201 performance within the MANET routing domain. 203 5. Structure of the MIB Module 205 This section presents the structure of the SMF MIB module. The 206 objects are arranged into the following groups: 208 o smfMIBNotifications - defines the notifications associated with 209 the SMF MIB. 211 o smfMIBObjects - defines the objects forming the basis for the SMF 212 MIB. These objects are divided up by function into the following 213 groups: 215 * Configuration Group - This group contains the SMF objects that 216 configure specific options that determine the overall operation 217 of the SMF RSSA and the resulting multicast performance. 219 * State Group - Contains information describing the current state 220 of the SMF RSSA process such as the Neighbor Table. 222 * Performance Group - Contains objects which help to characterize 223 the performance of the SMF RSSA process, typically statistics 224 counters. 226 o smfMIBConformance - defines minimal and full conformance of 227 implementations to this SMF MIB. 229 5.1. Textual Conventions 231 The textual conventions used in the SMF MIB are as follows. The 232 RowStatus textual convention is imported from RFC 2579 [RFC2579]. 234 5.2. The Configuration Group 236 The SMF device is configured with a set of controls. The list of 237 configuration controls for the SMF device follow. 239 o Operational Mode - topology information from NHDP, CDS-aware 240 unicast routing or Cross-layer from Layer 2 242 o SMF RSSA - the specific RSSA operational on the device 244 o Duplicate Packet detection for IPv4 - Identification-based or 245 Hash-based DPD 247 o Duplicate Packet detection for IPv6 - Identification-based or 248 Hash-based DPD 250 o NHDP RSSA Message TLV - if NHDP mode is selected, then is the RSSA 251 Message TLV included in the NHDP exchanges. (Question: Is this 252 and the following two TLVs optional and are they included as a 253 group or independently of one another?) 255 o NHDP RSSA Address Block TLV - if NHDP mode is selected, then is 256 the RSSA Address Block TLV included in the NHDP exchanges. 258 o Router Priority TLV - if NHDP mode is selected, then is the Router 259 Priority TLV included in the NHDP exchanges. 261 5.3. The State Group 263 The State Subtree reports current state information. 265 o Node RSS State - is the node currently in or out of the Relay Set. 267 o Neighbors Table - a table containing current neighbors and their 268 operational RSSA. 270 5.4. The Performance Group 272 The Performance subtree reports primarily counters that relate to SMF 273 RSSA performance. The SMF performance counters consists of per node 274 and per interface objects: (Note: Need to have a discussion of the 275 important and measurable events related to SMF RSSA multicast 276 performance.) (Note: Do we need to break these out by type, i.e., v4 277 versus v6?) 279 o Total multicast packets received - 281 o Total multicast packets forwarded - 283 o Total duplicate multicast packets detected - 285 o Per interface statistics table with the following entries: 287 * Multicast packets received 289 * Multicast packets forwarded 291 * Duplicate multicast packets detected 293 5.5. The Notifications Group 295 The Notifications Subtree contains the list of notifications 296 supported within the SMF-MIB and their intended purpose or utility. 297 This group is currently empty. 299 6. Relationship to Other MIB Modules 301 [TODO]: The text of this section specifies the relationship of the 302 MIB modules contained in this document to other standards, 303 particularly to standards containing other MIB modules. Definitions 304 imported from other MIB modules and other MIB modules that SHOULD be 305 implemented in conjunction with the MIB module contained within this 306 document are identified in this section. 308 6.1. Relationship to the SNMPv2-MIB 310 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 311 mandatory for all systems, and the objects apply to the entity as a 312 whole. The 'system' group provides identification of the management 313 entity and certain other system-wide data. The SMF-MIB does not 314 duplicate those objects. 316 6.2. Relationship to the IF-MIB 318 [TODO] This section is included as an example; If the MIB module is 319 not an adjunct of the Interface MIB, then this section should be 320 removed. 322 6.3. MIB modules required for IMPORTS 324 [TODO]: Citations are not permitted within a MIB module, but any 325 module mentioned in an IMPORTS clause or document mentioned in a 326 REFERENCE clause is a Normative reference, and must be cited 327 someplace within the narrative sections. If there are imported items 328 in the MIB module, such as Textual Conventions, that are not already 329 cited, they can be cited in text here. Since relationships to other 330 MIB modules should be described in the narrative text, this section 331 is typically used to cite modules from which Textual Conventions are 332 imported. 334 The following SMF-MIB module IMPORTS objects from SNMPv2-SMI 335 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB 336 [RFC2863] 338 7. Definitions 340 MANET-SMF-MIB DEFINITIONS ::= BEGIN 342 IMPORTS 343 MODULE-IDENTITY, OBJECT-TYPE, 344 Counter32, mib-2 345 FROM SNMPv2-SMI -- [RFC2578] 346 TruthValue 347 FROM SNMPv2-TC -- [RFC2579] 348 MODULE-COMPLIANCE, OBJECT-GROUP 349 FROM SNMPv2-CONF -- [RFC2580] 350 InterfaceIndex 351 FROM IF-MIB -- [RFC2863] 352 InetAddress, InetAddressType, 353 InetAddressPrefixLength 354 FROM INET-ADDRESS-MIB -- [RFC4001] 355 ; 357 manetSmfMIB MODULE-IDENTITY 358 LAST-UPDATED "200811031300Z" -- November 03, 2008 359 ORGANIZATION "IETF MANET Working Group" 360 CONTACT-INFO 361 "WG E-Mail: manet@ietf.org 363 WG Chairs: ian.chakeres@gmail.com 364 jmacker@nrl.navy.mil 366 Editors: Robert G. Cole 367 Johns Hopkins University 368 Applied Physics Lab and 369 Department of Computer Science 370 11000 Johns Hopkins Road 371 Room 02-257 372 Laurel, MD 22014 373 USA 374 +1 443 778-6951 375 robert.cole@jhuapl.edu 377 Joseph Macker 378 Naval Research Laboratory 379 Washington, D.C. 20375 380 USA 381 macker@itd.nrl.navy.mil 383 Brian Adamson 384 Naval Research Laboratory 385 Washington, D.C. 20375 386 USA 387 adamson@itd.nrl.navy.mil 389 Sean Harnedy 390 Booz Allen Hamilton 391 333 City Boulevard West 392 Orange, CA 92868 393 USA 394 +1 714 938-3898 395 harnedy_sean@bah.com" 397 DESCRIPTION 398 "This MIB module contains managed object definitions for 399 the Manet SMF RSSA process defined in: Macker, J.(ed.), 400 Simplified Multicast Forwarding draft-ietf-manet-smf-07, 401 February 25, 2008. 403 Copyright (C) The IETF Trust (2008). This version 404 of this MIB module is part of RFC xxxx; see the RFC 405 itself for full legal notices." 407 -- Revision History 408 REVISION "200811031300Z" -- November 03, 2008 409 DESCRIPTION 410 "Updated draft of this MIB module published as 411 draft-cole-manet-smf-mib-01.txt. Added gateway filter 412 table and reports capabilities following rmon." 413 REVISION "200807071200Z" -- July 07, 2008 414 DESCRIPTION 415 "Initial draft of this MIB module published as 416 draft-cole-manet-smf-mib-00.txt." 417 -- RFC-Editor assigns XXXX 418 ::= { mib-2 998 } -- to be assigned by IANA 420 -- 421 -- Top-Level Object Identifier Assignments 422 -- 424 smfMIBNotifications OBJECT IDENTIFIER ::= { manetSmfMIB 0 } 425 smfMIBObjects OBJECT IDENTIFIER ::= { manetSmfMIB 1 } 426 smfMIBConformance OBJECT IDENTIFIER ::= { manetSmfMIB 2 } 428 -- 429 -- smfConfigurationGroup 430 -- 431 -- This group contains the SMF objects that configure specific 432 -- options that determine the overall performance and operation 433 -- of the multicast forwarding process for the router device 434 -- and its interfaces. 435 -- 437 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 439 smfOperationalMode OBJECT-TYPE 440 SYNTAX INTEGER { 441 withNHDP(1), 442 cdsAwareRouting(2), 443 crossLayer(3) 444 } 445 MAX-ACCESS read-write 446 STATUS current 447 DESCRIPTION 448 "The SMF RSS node operational mode. 450 The value withNHDP(1) indicates ... 451 The value cdsAwareRouting(2) indicates ... 452 The value crossLayer(3) indicates... ." 453 ::= { smfConfigurationGroup 1 } 455 -- 456 -- Note: Would like to develop a capabilities Table listing 457 -- the supported RSSA's. Need to figure out a good way to 458 -- assciate specific RSSA algorithm configuration settings 459 -- with the different RSSA's supported. This would replace 460 -- the following smfRSSA, smfIpv4Dpd and smfIpv6Dpd objects. 461 -- 463 smfRssa OBJECT-TYPE 464 SYNTAX INTEGER { 465 cF(1), 466 sMPR(2), 467 eCDS(3), 468 mprCDS(4) 469 -- future(5-127) 470 -- noStdAction(128-239) 471 -- experimental(240-255) 472 } 473 MAX-ACCESS read-write 474 STATUS current 475 DESCRIPTION 476 "The SMF RSS operational algorithm. 478 The value cf(1) indicates ... 480 The value experimental(240-255) indicates... ." 481 ::= { smfConfigurationGroup 2 } 483 smfRssMember OBJECT-TYPE 484 SYNTAX INTEGER { 485 potential(1), 486 always(2), 487 never(3) 488 } 489 MAX-ACCESS read-write 490 STATUS current 491 DESCRIPTION 492 "The RSSA downselects a set of forwarders for 493 multicast forwarding. Sometimes it is useful 494 to force an agent to be included or excluded 495 from the resulting RSS. This object is a 496 switch to allow for this behavior. 498 The value potential(1) allows the selected 499 RSSA to determine if this agent is included 500 or excluded from the RSS. 502 The value always(1) forces the selected 503 RSSA include this agent in the RSS. 505 The value never(3) forces the selected 506 RSSA to exclude this agent from the RSS." 507 ::= { smfConfigurationGroup 3 } 509 smfIpv4Dpd OBJECT-TYPE 510 SYNTAX INTEGER { 511 identificationBased(1), 512 hashBased(2) 513 } 514 MAX-ACCESS read-write 515 STATUS current 516 DESCRIPTION 517 "The current method for IPv4 duplicate packet 518 detection. 519 The value identificationBased(1) 520 indicates... 522 The value 'hashBased(2) indicates... ." 523 ::= { smfConfigurationGroup 4 } 525 smfIpv6Dpd OBJECT-TYPE 526 SYNTAX INTEGER { 527 identificationBased(1), 528 hashBased(2) 529 } 530 MAX-ACCESS read-write 531 STATUS current 532 DESCRIPTION 533 "The current method for IPv6 duplicate packet 534 detection. 535 The value identificationBased(1) 536 indicates... 538 The value 'hashBased(2) indicates... ." 539 ::= { smfConfigurationGroup 5 } 541 smfNhdpRssaMesgTLVIncluded OBJECT-TYPE 542 SYNTAX TruthValue 543 MAX-ACCESS read-write 544 STATUS current 545 DESCRIPTION 546 "Indicates whether the associated NHDP messages 547 include the RSSA Message TLV, or not. This 548 is an optional SMF operational setting. 549 The value true(1) indicates that this TLV is 550 included; the value false(2) indicates that it 551 is not included." 552 ::= { smfConfigurationGroup 6 } 554 smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 555 SYNTAX TruthValue 556 MAX-ACCESS read-write 557 STATUS current 558 DESCRIPTION 559 "Indicates whether the associated NHDP messages 560 include the RSSA Address Block TLV, or not. 561 This is an optional SMF operational setting. 562 The value true(1) indicates that this TLV is 563 included; the value false(2) indicates that it 564 is not included." 565 ::= { smfConfigurationGroup 7 } 567 smfNhdpRouterPriorityTLVIncluded OBJECT-TYPE 568 SYNTAX TruthValue 569 MAX-ACCESS read-write 570 STATUS current 571 DESCRIPTION 572 "Indicates whether the associated NHDP messages 573 include the RSSA Router Priority TLV, or not. 574 This is an optional SMF operational setting. 575 The value true(1) indicates that this TLV is 576 included; the value false(2) indicates that it 577 is not included." 578 ::= { smfConfigurationGroup 8 } 580 -- 581 -- SMF Gateway Filter Table 582 -- 583 smfGatewayFilterTable OBJECT-TYPE 584 SYNTAX SEQUENCE OF SmfGatewayFilterEntry 585 MAX-ACCESS not-accessible 586 STATUS obsolete 587 DESCRIPTION 588 "The SMF Gateway can be configured to filter 589 multicast packets into and outof the SMF 590 MANET domain. This table defines the filter 591 rules which define packet matching and 592 related actions. The rules are in order ..." 593 REFERENCE 594 "The SMF draft." 595 ::= { smfConfigurationGroup 9 } 597 smfGatewayFilterEntry OBJECT-TYPE 598 SYNTAX SmfGatewayFilterEntry 599 MAX-ACCESS not-accessible 600 STATUS current 601 DESCRIPTION 602 "A single entry in the smfGatewayFilterTable." 603 REFERENCE 604 "The SMF draft." 605 INDEX { smfGatewayFilterIf, 606 smfGatewayFilterIfDirection } 607 ::= { smfResponsibleAddrTable 1 } 609 SmfResponsibleAddrEntry ::= 610 SEQUENCE { 611 smfGatewayFilterIf 612 InterfaceIndex, 613 smfGatewayFilterIfDirection 614 INTEGER, 615 smfGatewayFilterRuleRank 616 INTEGER, 617 smfGatewayFilterDestAddrType 618 InetAddressType, 619 smfGatewayFilterDestAddr 620 InetAddress, 621 smfGatewayFilterDestAddrPrefixLen 622 InetAddressPrefixLength, 623 smfGatewayFilterSrcAddrType 624 InetAddressType, 625 smfGatewayFilterSrcAddr 626 InetAddress, 627 smfGatewayFilterSrcAddrPrefixLen 628 InetAddressPrefixLength, 629 smfGatewayFilterProtocolNumber 630 INTEGER, 632 smfGatewayFilterDestPortNumber 633 INTEGER, 634 smfGatewayFilterAction 635 INTEGER, 636 smfGatewayFilterRowStatus 637 RowStatus 638 } 640 smfGatewayFilterIfIndex OBJECT-TYPE 641 SYNTAX InterfaceIndex 642 MAX-ACCESS not-accessible 643 STATUS current 644 DESCRIPTION 645 "The ifIndex for this node interface 646 that is filtering this rule." 647 ::= { smfGatewayFilterEntry 1 } 649 smfGatewayFilterIfDirection OBJECT-TYPE 650 SYNTAX INTEGER 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "The ifIndex direction for this interface 655 filtering rule." 656 ::= { smfGatewayFilterEntry 2 } 658 smfGatewayFilterRuleRank OBJECT-TYPE 659 SYNTAX INTEGER 660 MAX-ACCESS not-accessible 661 STATUS current 662 DESCRIPTION 663 "The rank of the rule specified in 664 this entry." 665 REFERENCE 666 "The SMF draft." 667 ::= { smfGatewayFilterEntry 3 } 669 smfGatewayFilterDestAddrType OBJECT-TYPE 670 SYNTAX InetAddressType 671 MAX-ACCESS not-accessible 672 STATUS current 673 DESCRIPTION 674 "The type of the DestAddr, as defined 675 in the InetAddress MIB [RFC 4001]." 676 REFERENCE 677 "The SMF draft." 678 ::= { smfGatewayFilterEntry 4 } 679 smfGatewayFilterDestAddr OBJECT-TYPE 680 SYNTAX InetAddress 681 MAX-ACCESS not-accessible 682 STATUS current 683 DESCRIPTION 684 "The destination IP address of this rule. The type 685 of this address is determined by the value of the 686 smfGatewayFilterDestAddrType object." 687 REFERENCE 688 "The SMF draft." 689 ::= { smfGatewayFilterEntry 5 } 691 smfGatewayFilterDestAddrPrefixLen OBJECT-TYPE 692 SYNTAX InetAddressPrefixLength 693 MAX-ACCESS not-accessible 694 STATUS current 695 DESCRIPTION 696 "Indicates the number of leading one bits that form the 697 mask to be logical-ANDed with the destination address 698 before being compared to the value in the 699 smfGatewayFilterDestAddr field." 700 REFERENCE 701 "The SMF draft." 702 ::= { smfGatewayFilterEntry 6 } 704 smfGatewayFilterSrcAddrType OBJECT-TYPE 705 SYNTAX InetAddressType 706 MAX-ACCESS not-accessible 707 STATUS current 708 DESCRIPTION 709 "The type of the SrcAddr, as defined 710 in the InetAddress MIB [RFC 4001]." 711 REFERENCE 712 "The SMF draft." 713 ::= { smfGatewayFilterEntry 7 } 715 smfGatewayFilterSrcAddr OBJECT-TYPE 716 SYNTAX InetAddress 717 MAX-ACCESS not-accessible 718 STATUS current 719 DESCRIPTION 720 "The source IP address of this rule. The type 721 of this address is determined by the value of the 722 smfGatewayFilterSrcAddrType object." 723 REFERENCE 724 "The SMF draft." 725 ::= { smfGatewayFilterEntry 8 } 726 smfGatewayFilterSrcAddrPrefixLen OBJECT-TYPE 727 SYNTAX InetAddressPrefixLength 728 MAX-ACCESS not-accessible 729 STATUS current 730 DESCRIPTION 731 "Indicates the number of leading one bits that form the 732 mask to be logical-ANDed with the destination address 733 before being compared to the value in the 734 smfGatewayFilterSrcAddr field." 735 REFERENCE 736 "The SMF draft." 737 ::= { smfGatewayFilterEntry 9 } 739 smfGatewayFilterSrcAddr OBJECT-TYPE 740 SYNTAX InetAddress 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "The source IP address of this rule. The type 745 of this address is determined by the value of the 746 smfGatewayFilterSrcAddrType object." 747 REFERENCE 748 "The SMF draft." 749 ::= { smfGatewayFilterEntry 10 } 751 smfGatewayFilterProtocolNumber OBJECT-TYPE 752 SYNTAX INTEGER 753 MAX-ACCESS read-write 754 STATUS current 755 DESCRIPTION 756 "The Protocol Number defined in RFC 5237." 757 ::= { smfGatewayFilterEntry 11 } 759 smfGatewayFilterDestPortNumber OBJECT-TYPE 760 SYNTAX INTEGER 761 MAX-ACCESS read-write 762 STATUS current 763 DESCRIPTION 764 "The destination Port Number defined in 765 RFC XXXX." 766 ::= { smfGatewayFilterEntry 12 } 768 smfGatewayFilterAction OBJECT-TYPE 769 SYNTAX INTEGER 770 MAX-ACCESS read-write 771 STATUS current 772 DESCRIPTION 773 "The action to be taken if the rule is 774 matched." 775 RFC XXXX." 776 ::= { smfGatewayFilterEntry 13 } 778 smfGatewayFilterRowStatus OBJECT-TYPE 779 SYNTAX RowStatus 780 MAX-ACCESS read-create 781 STATUS current 782 DESCRIPTION 783 "This object permits management of the table 784 by facilitating actions such as row creation, 785 construction, and destruction. The value of 786 this object has no effect on whether other 787 objects in this conceptual row can be 788 modified." 789 ::= { smfGatewayFilterEntry 14 } 791 -- 792 -- smfStateGroup 793 -- 794 -- Contains information describing the current state of the SMF 795 -- process such as the current inclusion in the RS or not. 796 -- 798 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 800 smfNodeRsStatusIncluded OBJECT-TYPE 801 SYNTAX TruthValue 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "The current status of the SMF node in the context of 806 the MANETs relay set. A value of true(1) indicates 807 that the node is currently part of the MANET Relay 808 Set. A value of false(2) indicates that the node 809 is currently not part of the MANET Relay Set." 810 ::= { smfStateGroup 1 } 812 -- 813 -- SMF Neighbor Table 814 -- 816 smfNeighborTable OBJECT-TYPE 817 SYNTAX SEQUENCE OF SmfNeighborEntry 818 MAX-ACCESS not-accessible 819 STATUS current 820 DESCRIPTION 821 "The SMF NeighborTable describes the 822 current neighbor nodes, their address 823 and SMF RSSA and the interface on which 824 they can be reached." 825 REFERENCE 826 "Simplified Multicast Forwarding for MANET 827 (SMF), Macker, J., February 2008. 828 Section 7: SMF Neighborhood Discovery 829 Requirements." 830 ::= { smfStateGroup 2 } 832 smfNeighborEntry OBJECT-TYPE 833 SYNTAX SmfNeighborEntry 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "The SMF Neighbor Table contains the 838 set of one-hop neighbors, the interface 839 they are reachable on and the SMF RSSA 840 they are currently running." 841 INDEX { smfNeighborIpAddrType, 842 smfNeighborIpAddr, 843 smfNeighborPrefixLen } 844 ::= { smfNeighborTable 1 } 846 SmfNeighborEntry ::= 847 SEQUENCE { 848 smfNeighborIpAddrType 849 InetAddressType, 850 smfNeighborIpAddr 851 InetAddress, 852 smfNeighborPrefixLen 853 InetAddressPrefixLength, 854 smfNeighborRSSA 855 INTEGER, 856 smfNeighborNextHopInterface 857 InterfaceIndex 858 } 860 smfNeighborIpAddrType OBJECT-TYPE 861 SYNTAX InetAddressType 862 MAX-ACCESS not-accessible 863 STATUS current 864 DESCRIPTION 865 "The neighbor IP address type." 867 ::= { smfNeighborEntry 1 } 869 smfNeighborIpAddr OBJECT-TYPE 870 SYNTAX InetAddress 871 MAX-ACCESS not-accessible 872 STATUS current 873 DESCRIPTION 874 "The neighbor Inet IPv4 or IPv6 address." 875 ::= { smfNeighborEntry 2 } 877 smfNeighborPrefixLen OBJECT-TYPE 878 SYNTAX InetAddressPrefixLength 879 MAX-ACCESS not-accessible 880 STATUS current 881 DESCRIPTION 882 "The prefix length. This is a decimal value that 883 indicates the number of contiguous, higher-order 884 bits of the address that make up the network 885 portion of the address." 886 ::= { smfNeighborEntry 3 } 888 smfNeighborRSSA OBJECT-TYPE 889 SYNTAX INTEGER { 890 cF(1), 891 sMPR(2), 892 eCDS(3), 893 mprCDS(4) 894 -- future(5-127) 895 -- noStdAction(128-239) 896 -- experimental(240-255) 897 } 898 MAX-ACCESS read-only 899 STATUS current 900 DESCRIPTION 901 "The current RSSA running on the neighbor. 902 The list is identical to that described 903 above for the smfRssa object." 904 ::= { smfNeighborEntry 4 } 906 smfNeighborNextHopInterface OBJECT-TYPE 907 SYNTAX InterfaceIndex 908 MAX-ACCESS read-only 909 STATUS current 910 DESCRIPTION 911 "The interface ifIndex over which the 912 neighbor is reachable in one-hop." 913 ::= { smfNeighborEntry 5 } 914 -- 915 -- SMF Performance Group 916 -- 917 -- Contains objects which help to characterize the 918 -- performance of the SMF RSSA process, such as statistics 919 -- counters. There are two types of SMF RSSA statistics: 920 -- global counters and per interface counters. 921 -- 923 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 925 smfGlobalPerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 927 -- 928 -- Note: There may be other objects we wish to track. These may 929 -- include counters of HASH collisions, metrics related 930 -- to average, min or max number of neighbors, and other 931 -- objects. These are TBD. 932 -- 934 smfMultiPktsRecvTotal OBJECT-TYPE 935 SYNTAX Counter32 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "A counter of the total number of 940 multicast IP packets received by the 941 device." 942 ::= { smfGlobalPerfGroup 1 } 944 smfMultiPktsForwardedTotal OBJECT-TYPE 945 SYNTAX Counter32 946 MAX-ACCESS read-only 947 STATUS current 948 DESCRIPTION 949 "A counter of the total number of 950 multicast IP packets forwarded by the 951 device." 952 ::= { smfGlobalPerfGroup 2 } 954 smfDuplMultiPktsDetectedTotal OBJECT-TYPE 955 SYNTAX Counter32 956 MAX-ACCESS read-only 957 STATUS current 958 DESCRIPTION 959 "A counter of the total number of duplicate 960 multicast IP packets detected by the 961 device." 963 ::= { smfGlobalPerfGroup 3 } 965 smfDroppedMultiPktsTTLExceededTotal OBJECT-TYPE 966 SYNTAX Counter32 967 MAX-ACCESS read-only 968 STATUS current 969 DESCRIPTION 970 "A counter of the total number of dropped 971 multicast IP packets by the 972 device due to TTL exceeded." 973 ::= { smfGlobalPerfGroup 4 } 975 -- 976 -- Per SMF Interface Performance Table 977 -- 979 smfInterfacePerfGroup OBJECT IDENTIFIER ::= {smfPerformanceGroup 2} 981 smfInterfacePerfTable OBJECT-TYPE 982 SYNTAX SEQUENCE OF SmfInterfacePerfEntry 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "The SMF Interface Performance Table 987 describes the SMF statistics per 988 interface." 989 ::= { smfInterfacePerfGroup 1 } 991 smfInterfacePerfEntry OBJECT-TYPE 992 SYNTAX SmfInterfacePerfEntry 993 MAX-ACCESS not-accessible 994 STATUS current 995 DESCRIPTION 996 "The SMF Interface Performance entry 997 describes the statistics for a particular 998 node interface." 999 INDEX { smfIfPerfIfIndex } 1000 ::= { smfInterfacePerfTable 1 } 1002 SmfInterfacePerfEntry ::= 1003 SEQUENCE { 1004 smfIfPerfIfIndex 1005 InterfaceIndex, 1006 smfMultiPktsRecvPerIf 1007 Counter32, 1008 smfMultiPktsForwardedPerIf 1009 Counter32, 1011 smfDuplMultiPktsDetectedPerIf 1012 Counter32 1013 } 1015 smfIfPerfIfIndex OBJECT-TYPE 1016 SYNTAX InterfaceIndex 1017 MAX-ACCESS not-accessible 1018 STATUS current 1019 DESCRIPTION 1020 "The ifIndex for this node interface 1021 that is collecting this set of 1022 performance management statistics." 1023 ::= { smfInterfacePerfEntry 1 } 1025 smfMultiPktsRecvPerIf OBJECT-TYPE 1026 SYNTAX Counter32 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "A counter of the number of 1031 multicast IP packets received by the 1032 device on this interface." 1033 ::= { smfInterfacePerfEntry 2 } 1035 smfMultiPktsForwardedPerIf OBJECT-TYPE 1036 SYNTAX Counter32 1037 MAX-ACCESS read-only 1038 STATUS current 1039 DESCRIPTION 1040 "A counter of the number of 1041 multicast IP packets forwarded by the 1042 device on this interface." 1043 ::= { smfInterfacePerfEntry 3 } 1045 smfDuplMultiPktsDetectedPerIf OBJECT-TYPE 1046 SYNTAX Counter32 1047 MAX-ACCESS read-only 1048 STATUS current 1049 DESCRIPTION 1050 "A counter of the number of duplicate 1051 multicast IP packets detected by the 1052 device on this interface." 1053 ::= { smfInterfacePerfEntry 4 } 1055 smfDroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1056 SYNTAX Counter32 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "A counter of the number of dropped 1061 multicast IP packets by the 1062 device on this interface due to TTL 1063 exceeded." 1064 ::= { smfInterfacePerfEntry 5 } 1066 -- 1067 -- Reports Control 1068 -- This and the following tables are modeled 1069 -- after the report control and collection 1070 -- capabilities found in RMON II, RFC XXXX 1072 -- 1073 -- Note: Starting down this road only for general performance 1074 -- measures first. If desireable, then will add reports for 1075 -- IF specific measurements. 1076 -- 1078 smfReportsGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1080 smfGenReportCntrlTable OBJECT-TYPE 1081 SYNTAX SEQUENCE OF SmfGenReportCntrlEntry 1082 MAX-ACCESS not-accessible 1083 STATUS current 1084 DESCRIPTION 1085 "The smfGenReportCntrlTable is the controlling entry 1086 that manages the population of studies in the 1087 Report for selected time intervals. 1089 Note that this is not like the typical RMON 1090 controlTable and dataTable in which each entry creates 1091 its own data table. Each entry in this table enables the 1092 creation of multiple data tables on a study basis. For each 1093 interval, the study is updated in place, and the current 1094 data content of the table becomes invalid. 1096 The control table entries are persistent across 1097 system reboots." 1098 ::= { smfReportsGroup 1 } 1100 smfGenReportCntrlEntry OBJECT-TYPE 1101 SYNTAX SmfGenReportCntrlEntry 1102 MAX-ACCESS not-accessible 1103 STATUS current 1104 DESCRIPTION 1105 "A conceptual row in the smfGenReportCntrlTable. 1107 An example of the indexing of this entry is 1108 smfGenReportCntrInterval.1" 1109 INDEX { smfGenReportCntrlIndex } 1110 ::= { smfGenReportCntrlTable 1 } 1112 SmfGenReportCntrlEntry ::= SEQUENCE { 1113 smfGenReportCntrlIndex Unsigned32, 1114 smfGenReportCntrlInterval Unsigned32, 1115 smfGenReportCntrlReqSize Unsigned32, 1116 smfGenReportCntrlGrantedSize Unsigned32, 1117 smfGenReportCntrlReqReports Unsigned32, 1118 smfGenReportCntrlGrantedReports Unsigned32, 1119 smfGenReportCntrlStartTime TimeStamp, 1120 smfGenReportCntrlReportNumber Unsigned32, 1121 smfGenReportCntrlInsertsDenied Counter32, 1122 smfGenReportCntrlOwner OwnerString, 1123 smfGenReportCntrlStorageType StorageType, 1124 smfGenReportCntrlStatus RowStatus 1125 } 1127 smfGenReportCntrlIndex OBJECT-TYPE 1128 SYNTAX Unsigned32 (1..65535) 1129 MAX-ACCESS not-accessible 1130 STATUS current 1131 DESCRIPTION 1132 "An index that uniquely identifies an entry in the 1133 smfGenReportCntrlTable. Each such entry defines a unique 1134 report whose results are placed in the smfGenReportTable on 1135 behalf of this smfGenReportCntrlEntry." 1136 ::= { smfGenReportCntrlEntry 1 } 1138 smfGenReportCntrlInterval OBJECT-TYPE 1139 SYNTAX Unsigned32 1140 UNITS "Seconds" 1141 MAX-ACCESS read-create 1142 STATUS current 1143 DESCRIPTION 1144 "The interval in seconds over which data is accumulated before 1145 being aggregated into a report in the smfGenReportTable. 1146 All reports with the same smfGenReportCntrlIndex will be 1147 based on the same interval. 1149 This object may not be modified if the associated 1150 smfGenReportCntrlStatus object is equal to active(1)." 1151 DEFVAL { 3600 } 1152 ::= { smfGenReportCntrlEntry 2 } 1154 smfGenReportCntrlReqSize OBJECT-TYPE 1155 SYNTAX Unsigned32 1156 MAX-ACCESS read-create 1157 STATUS current 1158 DESCRIPTION 1159 "The maximum number of Client and Server combination 1160 entries requested for this report. 1162 When this object is created or modified, the probe 1163 should set smfGenReportCntrlGrantedSize as closely to this 1164 object as is possible for the particular probe 1165 implementation and available resources. 1167 It is important to note that this value is the number of 1168 requested entries in the smfGenReportTable only. 1170 This object may not be modified if the associated 1171 smfGenReportCntrlStatus object is equal to active(1)." 1172 ::= { smfGenReportCntrlEntry 3 } 1174 smfGenReportCntrlGrantedSize OBJECT-TYPE 1175 SYNTAX Unsigned32 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "The maximum number of performance entries in this report. 1181 When the associated smfGenReportCntrlReqSize object is 1182 created or modified, the probe should set this 1183 object as closely to the requested value as is 1184 possible for the particular implementation and 1185 available resources. The probe must not lower this 1186 value except as a result of a set to the associated 1187 smfGenReportCntrlReqSize object. 1189 It is an implementation-specific matter as to whether 1190 zero-valued entries are available." 1191 ::= { smfGenReportCntrlEntry 4 } 1193 smfGenReportCntrlReqReports OBJECT-TYPE 1194 SYNTAX Unsigned32 (1..65535) 1195 MAX-ACCESS read-create 1196 STATUS current 1197 DESCRIPTION 1198 "The number of saved reports requested to be allocated on 1199 behalf of this entry. 1201 This object may not be modified if the associated 1202 smfGenReportCntrlStatus object is equal to active(1)." 1203 ::= { smfGenReportCntrlEntry 5 } 1205 smfGenReportCntrlGrantedReports OBJECT-TYPE 1206 SYNTAX Unsigned32 (0..65535) 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION 1210 "The number of saved reports the agent has allocated based 1211 on the requested amount in smfGenReportCntrlReqReports. 1212 Because each report can have many entries, the total number 1213 of entries allocated will be this number multiplied by the 1214 value of smfGenReportCntrlGrantedSize, or by 1 if that 1215 object doesn't exist. 1217 When the associated smfGenReportCntrlReqReports object is 1218 created or modified, the agent should set this object as 1219 closely to the requested value as is possible for the 1220 particular implementation and available resources. When 1221 considering available resources, the agent must consider its 1222 ability to allocate this many reports, each with the number 1223 of entries represented by smfGenReportCntrlGrantedSize, or 1224 by 1 if that object doesn't exist. 1226 Note that although the storage required for each report may 1227 fluctuate due to changing conditions, the agent must continue 1228 to have storage available to satisfy the full report size for 1229 all reports, when necessary. Further, the agent must not 1230 lower this value except as a result of a set to the 1231 associated smfGenReportCntrlReqSize object." 1232 ::= { smfGenReportCntrlEntry 6 } 1234 smfGenReportCntrlStartTime OBJECT-TYPE 1235 SYNTAX TimeStamp 1236 MAX-ACCESS read-only 1237 STATUS current 1238 DESCRIPTION 1239 "The value of sysUpTime when the system began processing the 1240 report in progress. Note that the report in progress is not 1241 available. 1243 This object may be used by the management station to figure 1244 out the start time for all previous reports saved for this 1245 smfGenReportCntrlEntry, as reports are started at fixed 1246 intervals." 1247 ::= { smfGenReportCntrlEntry 7 } 1249 smfGenReportCntrlReportNumber OBJECT-TYPE 1250 SYNTAX Unsigned32 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "The number of the report in progress. When an 1255 smfGenReportCntrlEntry is activated, the first report will 1256 be numbered zero." 1257 ::= { smfGenReportCntrlEntry 8 } 1259 smfGenReportCntrlInsertsDenied OBJECT-TYPE 1260 SYNTAX Counter32 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "The number of attempts to add an entry to reports for 1265 this SmfGenReportCntrlEntry that failed because the number 1266 of entries would have exceeded smfGenReportCntrlGrantedSize. 1268 This number is valuable in determining if enough entries have 1269 been allocated for reports in light of fluctuating network 1270 usage. Note that an entry that is denied will often be 1271 attempted again, so this number will not predict the exact 1272 number of additional entries needed, but it can be used to 1273 understand the relative magnitude of the problem. 1275 Also note that there is no ordering specified for the entries 1276 in the report; thus, there are no rules for which entries 1277 will be omitted when not enough entries are available. As a 1278 consequence, the agent is not required to delete 'least 1279 valuable' entries first." 1280 ::= { smfGenReportCntrlEntry 9 } 1282 smfGenReportCntrlOwner OBJECT-TYPE 1283 SYNTAX OwnerString 1284 MAX-ACCESS read-create 1285 STATUS current 1286 DESCRIPTION 1287 "The entity that configured this entry and is 1288 therefore using the resources assigned to it. 1290 This object may not be modified if the associated 1291 smfGenReportCntrlStatus object is equal to active(1)." 1292 ::= { smfGenReportCntrlEntry 10 } 1294 smfGenReportCntrlStorageType OBJECT-TYPE 1295 SYNTAX StorageType 1296 MAX-ACCESS read-create 1297 STATUS current 1298 DESCRIPTION 1299 "The storage type of this smfGenReportCntrlEntry. If the 1300 value of this object is 'permanent', no objects in this row 1301 need to be writable." 1302 ::= { smfGenReportCntrlEntry 11 } 1304 smfGenReportCntrlStatus OBJECT-TYPE 1305 SYNTAX RowStatus 1306 MAX-ACCESS read-create 1307 STATUS current 1308 DESCRIPTION 1309 "The status of this performance control entry. 1311 An entry may not exist in the active state unless each 1312 object in the entry has an appropriate value. 1314 Once this object is set to active(1), no objects in the 1315 smfGenReportCntrlTable can be changed. 1317 If this object is not equal to active(1), all associated 1318 entries in the smfGenReportTable shall be deleted." 1319 ::= { smfGenReportCntrlEntry 12 } 1321 -- 1322 -- Reports 1323 -- 1325 smfGenReportTable OBJECT-TYPE 1326 SYNTAX SEQUENCE OF SmfGenReportEntry 1327 MAX-ACCESS not-accessible 1328 STATUS current 1329 DESCRIPTION 1330 "This table contains 1331 studies for each of the control table entries in 1332 smfGenReportCntrlTable. These studies are 1333 provided based on the selections and parameters 1334 found for the entry in the 1335 smfGenReportCntrlTable. 1337 The performance counter are the same as those 1338 specified in the smfPerformanceGroup." 1339 ::= { smfReportsGroup 2 } 1341 smfGenReportEntry OBJECT-TYPE 1342 SYNTAX SmfGenReportEntry 1343 MAX-ACCESS not-accessible 1344 STATUS current 1345 DESCRIPTION 1346 "A conceptual row in the smfGenReportTable. 1348 The smfGenReportCntrlIndex value in the index identifies the 1349 smfGenReportCntrlEntry on whose behalf this entry was 1350 created. 1352 The smfGenReportIndex value in the index identifies which 1353 report (in the series of reports) this entry is a part of. 1355 An example of the indexing of this entry is 1356 smfGenReportMultiPktsForwarded.3.15" 1357 INDEX { smfGenReportCntrlIndex, 1358 smfGenReportIndex 1359 } 1360 ::= { smfGenReportTable 1 } 1362 SmfGenReportEntry ::= SEQUENCE { 1363 smfGenReportIndex Unsigned32, 1364 smfGenReportMultiPktsRecvTot ZeroBasedCounter32, 1365 smfGenReportMultiPktsForwardedTot ZeroBasedCounter32, 1366 smfGenReportDuplMultiPktsDetected ZeroBasedCounter32, 1367 } 1369 smfGenReportIndex OBJECT-TYPE 1370 SYNTAX Unsigned32 (1..2147483647) 1371 MAX-ACCESS not-accessible 1372 STATUS current 1373 DESCRIPTION 1374 "The value of smfGenReportCntrlNumber for the report to 1375 which this entry belongs." 1376 ::= { smfGenReportEntry 1 } 1378 smfGenReportMultiPktsRecvTot OBJECT-TYPE 1379 SYNTAX ZeroBasedCounter32 1380 MAX-ACCESS read-only 1381 STATUS current 1382 DESCRIPTION 1383 "The count of the total number of ...." 1384 ::= { smfGenReportEntry 2 } 1386 smfGenReportMultiPktsForwardedTot OBJECT-TYPE 1387 SYNTAX ZeroBasedCounter32 1388 MAX-ACCESS read-only 1389 STATUS current 1390 DESCRIPTION 1391 "The count of the total number of ...." 1392 ::= { smfGenReportEntry 3 } 1394 smfGenReportDuplMultiPktsDetectedTot OBJECT-TYPE 1395 SYNTAX ZeroBasedCounter32 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "The count of the total number of ...." 1400 ::= { smfGenReportEntry 4 } 1402 smfGenReportDroppedMultiPktsTTLExceededTot OBJECT-TYPE 1403 SYNTAX ZeroBasedCounter32 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "The count of the total number of ...." 1408 ::= { smfGenReportEntry 5 } 1410 -- 1411 -- Notifications 1412 -- 1414 -- Note: What notifications do we want for this MIB? 1416 -- 1417 -- Compliance Statements 1418 -- 1420 -- Note: need to update the Compliance section once the mib 1421 -- objects stablize. 1423 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 1424 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 1426 smfBasicCompliance MODULE-COMPLIANCE 1427 STATUS current 1428 DESCRIPTION "The basic implementation requirements for 1429 managed network entities that implement 1430 the SMF RSSA process." 1431 MODULE -- this module 1432 MANDATORY-GROUPS { smfConfigObjectsGroup } 1433 ::= { smfCompliances 1 } 1435 smfFullCompliance MODULE-COMPLIANCE 1436 STATUS current 1437 DESCRIPTION "The full implementation requirements for 1438 managed network entities that implement 1439 the SMF RSSA process." 1440 MODULE -- this module 1441 MANDATORY-GROUPS { smfConfigObjectsGroup, 1442 smfStateObjectsGroup, 1443 smfPerfObjectsGroup } 1444 ::= { smfCompliances 2 } 1446 -- 1447 -- Units of Conformance 1448 -- 1450 smfConfigObjectsGroup OBJECT-GROUP 1451 OBJECTS { 1452 smfOperationalMode, 1453 smfRssa, 1454 smfIpv4Dpd, 1455 smfIpv6Dpd, 1456 smfNhdpRssaMesgTLVIncluded, 1457 smfNhdpRssaAddrBlockTLVIncluded, 1458 smfNhdpRouterPriorityTLVIncluded 1459 } 1460 STATUS current 1461 DESCRIPTION 1462 "Set of SMF configuration objects implemented 1463 in this module." 1464 ::= { smfMIBGroups 1 } 1466 smfStateObjectsGroup OBJECT-GROUP 1467 OBJECTS { 1468 smfNodeRsStatusIncluded, 1469 smfNeighborRSSA, 1470 smfNeighborNextHopInterface 1471 } 1472 STATUS current 1473 DESCRIPTION 1474 "Set of SMF state objects implemented 1475 in this module." 1476 ::= { smfMIBGroups 2 } 1478 smfPerfObjectsGroup OBJECT-GROUP 1479 OBJECTS { 1480 smfMultiPktsRecvTotal, 1481 smfMultiPktsForwardedTotal, 1482 smfDuplMultiPktsDetectedTotal, 1483 smfDroppedMultiPktsTTLExceededTotal, 1484 smfMultiPktsRecvPerIf, 1485 smfMultiPktsForwardedPerIf, 1486 smfDuplMultiPktsDetectedPerIf, 1487 smfDroppedMultiPktsTTLExceededPerIf 1488 } 1489 STATUS current 1490 DESCRIPTION 1491 "Set of SMF performance objects implemented 1492 in this module by total and per interface." 1493 ::= { smfMIBGroups 3 } 1495 END 1497 8. Security Considerations 1499 [TODO] Each specification that defines one or more MIB modules MUST 1500 contain a section that discusses security considerations relevant to 1501 those modules. This section MUST be patterned after the latest 1502 approved template (available at 1503 http://www.ops.ietf.org/mib-security.html). Remember that the 1504 objective is not to blindly copy text from the template, but rather 1505 to think and evaluate the risks/vulnerabilities and then state/ 1506 document the result of this evaluation. 1508 [TODO] if you have any read-write and/or read-create objects, please 1509 include the following boilerplate paragraph. 1511 There are a number of management objects defined in this MIB module 1512 with a MAX-ACCESS clause of read-write and/or read-create. Such 1513 objects may be considered sensitive or vulnerable in some network 1514 environments. The support for SET operations in a non-secure 1515 environment without proper protection can have a negative effect on 1516 network operations. These are the tables and objects and their 1517 sensitivity/vulnerability: 1519 o [TODO] writeable MIB objects that could be especially disruptive 1520 if abused MUST be explicitly listed by name and the associated 1521 security risks MUST be spelled out; RFC 2669 has a very good 1522 example. 1524 o [TODO] list the writable tables and objects and state why they are 1525 sensitive. 1527 [TODO] else if there are no read-write objects in your MIB module, 1528 use the following boilerplate paragraph. 1530 There are no management objects defined in this MIB module that have 1531 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1532 MIB module is implemented correctly, then there is no risk that an 1533 intruder can alter or create any management objects of this MIB 1534 module via direct SNMP SET operations. 1536 [TODO] if you have any sensitive readable objects, please include the 1537 following boilerplate paragraph. 1539 Some of the readable objects in this MIB module (i.e., objects with a 1540 MAX-ACCESS other than not-accessible) may be considered sensitive or 1541 vulnerable in some network environments. It is thus important to 1542 control even GET and/or NOTIFY access to these objects and possibly 1543 to even encrypt the values of these objects when sending them over 1544 the network via SNMP. These are the tables and objects and their 1545 sensitivity/vulnerability: 1547 o [TODO] you must explicitly list by name any readable objects that 1548 are sensitive or vulnerable and the associated security risks MUST 1549 be spelled out (for instance, if they might reveal customer 1550 information or violate personal privacy laws such as those of the 1551 European Union if exposed to unauthorized parties) 1553 o [TODO] list the tables and objects and state why they are 1554 sensitive. 1556 [TODO] discuss what security the protocol used to carry the 1557 information should have. The following three boilerplate paragraphs 1558 should not be changed without very good reason. Changes will almost 1559 certainly require justification during IESG review. 1561 SNMP versions prior to SNMPv3 did not include adequate security. 1562 Even if the network itself is secure (for example by using IPSec), 1563 even then, there is no control as to who on the secure network is 1564 allowed to access and GET/SET (read/change/create/delete) the objects 1565 in this MIB module. 1567 It is RECOMMENDED that implementers consider the security features as 1568 provided by the SNMPv3 framework (see [RFC3410], section 8), 1569 including full support for the SNMPv3 cryptographic mechanisms (for 1570 authentication and privacy). 1572 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1573 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1574 enable cryptographic security. It is then a customer/operator 1575 responsibility to ensure that the SNMP entity giving access to an 1576 instance of this MIB module is properly configured to give access to 1577 the objects only to those principals (users) that have legitimate 1578 rights to indeed GET or SET (change/create/delete) them. 1580 9. IANA Considerations 1582 [TODO] In order to comply with IESG policy as set forth in 1583 http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is 1584 submitted to the IESG for publication MUST contain an IANA 1585 Considerations section. The requirements for this section vary 1586 depending what actions are required of the IANA. see RFC4181 section 1587 3.5 for more information on writing an IANA clause for a MIB module 1588 document. 1590 [TODO] select an option and provide the necessary details. 1592 Option #1: 1594 The MIB module in this document uses the following IANA-assigned 1595 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1597 Descriptor OBJECT IDENTIFIER value 1598 ---------- ----------------------- 1600 sampleMIB { mib-2 XXX } 1602 Option #2: 1604 Editor's Note (to be removed prior to publication): the IANA is 1605 requested to assign a value for "XXX" under the 'mib-2' subtree and 1606 to record the assignment in the SMI Numbers registry. When the 1607 assignment has been made, the RFC Editor is asked to replace "XXX" 1608 (here and in the MIB module) with the assigned value and to remove 1609 this note. 1611 Note well: prior to official assignment by the IANA, a draft document 1612 MUST use placeholders (such as "XXX" above) rather than actual 1613 numbers. See RFC4181 Section 4.5 for an example of how this is done 1614 in a draft MIB module. 1616 Option #3: 1618 This memo includes no request to IANA. 1620 10. Contributors 1622 This MIB document uses the template authored by D. Harrington which 1623 is based on contributions from the MIb Doctors, especially Juergen 1624 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 1626 11. Acknowledgements 1628 12. References 1630 12.1. Normative References 1632 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1633 Interfaces Group MIB", RFC 2863, June 2000. 1635 [RFC3418] Presuhn, R., "Management Information Base (MIB) 1636 for the Simple Network Management Protocol 1637 (SNMP)", STD 62, RFC 3418, December 2002. 1639 [RFC2119] Bradner, S., "Key words for use in RFCs to 1640 Indicate Requirement Levels", BCP 14, RFC 2119, 1641 March 1997. 1643 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1644 Schoenwaelder, Ed., "Structure of Management 1645 Information Version 2 (SMIv2)", STD 58, 1646 RFC 2578, April 1999. 1648 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1649 Schoenwaelder, Ed., "Textual Conventions for 1650 SMIv2", STD 58, RFC 2579, April 1999. 1652 [RFC2580] McCloghrie, K., Perkins, D., and J. 1653 Schoenwaelder, "Conformance Statements for 1654 SMIv2", STD 58, RFC 2580, April 1999. 1656 [I-D.ietf-manet-smf] Macker, J. and S. Team, "Simplified Multicast 1657 Forwarding for MANET", draft-ietf-manet-smf-07 1658 (work in progress), February 2008. 1660 12.2. Informative References 1662 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 1663 Stewart, "Introduction and Applicability 1664 Statements for Internet-Standard Management 1665 Framework", RFC 3410, December 2002. 1667 Appendix A. Change Log 1669 Not applicable to draft 00 1671 1. 1673 Appendix B. Open Issues 1675 This section contains the set of open issues related to the 1676 development and design of the SMF-MIB. This section will not be 1677 present in the final version of the MIB and will be removed once all 1678 the open issues have been resolved. 1680 1. Clarify handling of the NHDP TLV message inclusions? 1682 2. Can we develop a capabilities table for the supported RSSA 1683 algorithms? And, if so, can each supportted RSSA have a 1684 different set of configuration parameters? 1686 3. Is the Gateway Filter table appropriate for this MIB or should 1687 it be handled in a seperate MIB worked elsewhere? How should 1688 this table be indexed and how should it represent the ordering 1689 of the rules (or chains)? Should this be greatly simplified? 1690 How do we handle null values in the rules? 1692 4. What are the additional performance objects to be included, 1693 e.g., Hash collisions, max, min and average neighbor set? How 1694 would average be determined? 1696 5. Is it useful to track the effectiveness of the coverage of the 1697 current RSSA? Is it possible to track this? 1699 6. Complete notification group. 1701 7. Complete conformance group. 1703 8. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 1705 9. Identify all objects requiring non-volatile storage in their 1706 DESCRIPTION clauses. 1708 10. Incorporate parameter relationship conditions into their 1709 DESCRIPTION clauses. 1711 11. Complete the security analysis and section. 1713 12. Cleanup all the [TODOs] from the MIB template. 1715 *************************************************************** 1716 * Note to the RFC Editor (to be removed prior to publication) * 1717 * * 1718 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 1719 * of the MIB module point to this draft and are to be * 1720 * assigned by the RFC Editor. * 1721 * * 1722 * 2) The reference to RFCXXX2 throughout this document point * 1723 * to the current draft-ietf-manet-smf-xx.txt. This * 1724 * need to be replaced with the XXX RFC number. * 1725 * * 1726 *************************************************************** 1728 Authors' Addresses 1730 Robert G. Cole 1731 Johns Hopkins University 1732 11100 Johns Hopkins Road, Room 257 1733 Laurel, Maryland 21073 1734 USA 1736 Phone: +1 443 778 6951 1737 EMail: robert.cole@jhuapl.edu 1738 URI: http://www.cs.jhu.edu/~rgcole/ 1740 Joseph Macker 1741 Navy Research Laboratory 1742 XXX Street 1743 Washington, D.C. 20375 1744 USA 1746 Phone: +1 xxx xxx-xxxx 1747 EMail: macker@itd.nrl.navy.mil 1749 Brian Adamson 1750 Navy Research Laboratory 1751 XXX Street 1752 Washington, D.C. 20375 1753 USA 1755 Phone: +1 xxx xxx-xxxx 1756 EMail: adamson@itd.nrl.navy.mil 1757 Sean Harnedy 1758 Booz Allen Hamilton 1759 333 City Boulevard West 1760 Orange, CA 92868 1761 USA 1763 Phone: +1 xxx xxx-xxxx 1764 EMail: harnedy_sean@bah.com 1766 Full Copyright Statement 1768 Copyright (C) The IETF Trust (2008). 1770 This document is subject to the rights, licenses and restrictions 1771 contained in BCP 78, and except as set forth therein, the authors 1772 retain all their rights. 1774 This document and the information contained herein are provided on an 1775 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1776 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1777 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1778 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1779 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1780 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1782 Intellectual Property 1784 The IETF takes no position regarding the validity or scope of any 1785 Intellectual Property Rights or other rights that might be claimed to 1786 pertain to the implementation or use of the technology described in 1787 this document or the extent to which any license under such rights 1788 might or might not be available; nor does it represent that it has 1789 made any independent effort to identify any such rights. Information 1790 on the procedures with respect to rights in RFC documents can be 1791 found in BCP 78 and BCP 79. 1793 Copies of IPR disclosures made to the IETF Secretariat and any 1794 assurances of licenses to be made available, or the result of an 1795 attempt made to obtain a general license or permission for the use of 1796 such proprietary rights by implementers or users of this 1797 specification can be obtained from the IETF on-line IPR repository at 1798 http://www.ietf.org/ipr. 1800 The IETF invites any interested party to bring to its attention any 1801 copyrights, patents or patent applications, or other proprietary 1802 rights that may cover technology that may be required to implement 1803 this standard. Please address the information to the IETF at 1804 ietf-ipr@ietf.org. 1806 Acknowledgement 1808 Funding for the RFC Editor function is provided by the IETF 1809 Administrative Support Activity (IASA).