Internet Engineering Task Force R. Cole Internet-Draft Johns Hopkins University Intended status: Standards Track J. Macker Expires: January 8, 2009 B. Adamson Navy Research Laboratory July 7, 2008 Definition of Managed Objects for the Manet Simplified Multicast Framework Relay Set Process draft-cole-manet-smf-mib-00 Status of This Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on January 8, 2009. Copyright Notice Copyright (C) The IETF Trust (2008). Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects for configuring aspects of the Simplified Multicast Forwarding (SMF) process. The SMF MIB also reports state information, performance metrics, and notifications. Cole, et al. Expires January 8, 2009 [Page 1] Internet-Draft The SMF MIB July 2008 In addition to configuration, this additional state and performance information is useful to management stations troubleshooting multicast forwarding problems. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 6 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 7 5.5. The Notifications Group . . . . . . . . . . . . . . . . . 7 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 8 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 12.1. Normative References . . . . . . . . . . . . . . . . . . . 22 12.2. Informative References . . . . . . . . . . . . . . . . . . 22 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 23 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 23 Cole, et al. Expires January 8, 2009 [Page 2] Internet-Draft The SMF MIB July 2008 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects for configuring aspects of a process implementing Simplified Multicast Forwarding (SMF) [I-D.ietf-manet-smf]. SMF provides multicast duplicate packet detection (DPD) and supports algorithms for constructing an estimate of a mobile ad hoc network (MANET) Minimum Connected Dominating Set (MCDS) for efficient multicast forwarding. The SMF MIB also reports state information, performance metrics, and notifications. In addition to configuration, this additional state and performance information is useful to management stations troubleshooting multicast forwarding problems. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 4. Overview SMF provides methods for implementing DPD-based multicast forwarding with the optional use of CDS-based relay sets. The MCDS is the smallest set of MANET nodes (comprising a connected cluster) which cover all the nodes in the cluster with their transmissions. As the density of the MANET nodes increase, the fraction of nodes required in an MCDS decreases. Using the MCDS as a multicast forwarding set then becomes an efficient multicast mechanism for MANETs. Various algorithms for the construction of estimates of the MCDS exist. The Simplified Multicast Framework [I-D.ietf-manet-smf] Cole, et al. Expires January 8, 2009 [Page 3] Internet-Draft The SMF MIB July 2008 describes some of these. It further defines various operational modes for a node which is participating in the collective creation of the MCDS estimates. These modes depend upon the set of related MANET routing and discovery protocols and mechanisms in operation in the specific MANET node. A SMF routers' MIB contains SMF process configuration parameters (e.g. specific CDS algorithm), state information (e.g., current membership in the CDS), performance counters (e.g., packet counters), and notifications. 4.1. SMF Management Model This section describes the management model for the SMF node process. Figure 1 (reproduced from Figure 4 of [I-D.ietf-manet-smf]) shows the relationship between the SMF Relay Set selection algorithm and the related algorithms, processes and protocols running in the MANET nodes. The Relay Set Selection Algorithm (RSSA) can rely upon topology information gotten from the MANET Neighborhood Discovery Protocol (NHDP), from the specific MANET routing protocol running on the node, or from Layer 2 information passed up to the higher layer protocol processes. Cole, et al. Expires January 8, 2009 [Page 4] Internet-Draft The SMF MIB July 2008 Possible L2 Trigger/Information | | ______________ ______|_____ __________________ | MANET | | | | | | Neighborhood | | Relay Set | | Other Heuristics | | Discovery |------------| Selection |-------| (Preference,etc) | | Protocol | neighbor | Algorithm | | | |______________| info |____________| |__________________| \ / \ / neighbor\ / Dynamic Relay info* \ ____________ / Set Status \ | SMF | / (State, {neighbor info}) `---| Relay Set |---' | State | ---|____________| / / ______________ | Coexistent | | MANET | | Unicast | | Process | |______________| Figure 1: SMF Relay Set Control Options 4.2. Terms The following definitions apply throughout this document: o Configuration Objects - switches, tables, objects which are initialized to default settings or set through the management interface defined by this MIB. o Tunable Configuration Objects - objects whose values affect timing or attempt bounds on the SMF RS process. o State Objects - automatically generated values which define the current operating state of the SMF RS process in the router. o Performance Objects - automatically generated values which help an administrator or automated tool to assess the performance of the CDS multicast process on the router and the overall multicasting performance within the MANET routing domain. Cole, et al. Expires January 8, 2009 [Page 5] Internet-Draft The SMF MIB July 2008 5. Structure of the MIB Module This section presents the structure of the SMF MIB module. The objects are arranged into the following groups: o smfMIBNotifications - defines the notifications associated with the SMF MIB. o smfMIBObjects - defines the objects forming the basis for the SMF MIB. These objects are divided up by function into the following groups: * Configuration Group - This group contains the SMF objects that configure specific options that determine the overall operation of the SMF RSSA and the resulting multicast performance. * State Group - Contains information describing the current state of the SMF RSSA process such as the Neighbor Table. * Performance Group - Contains objects which help to characterize the performance of the SMF RSSA process, typically statistics counters. o smfMIBConformance - defines minimal and full conformance of implementations to this SMF MIB. 5.1. Textual Conventions The textual conventions used in the SMF MIB are as follows. The RowStatus textual convention is imported from RFC 2579 [RFC2579]. 5.2. The Configuration Group The SMF device is configured with a set of controls. The list of configuration controls for the SMF device follow. o Operational Mode - topology information from NHDP, CDS-aware unicast routing or Cross-layer from Layer 2 o SMF RSSA - the specific RSSA operational on the device o Duplicate Packet detection for IPv4 - Identification-based or Hash-based DPD o Duplicate Packet detection for IPv6 - Identification-based or Hash-based DPD Cole, et al. Expires January 8, 2009 [Page 6] Internet-Draft The SMF MIB July 2008 o NHDP RSSA Message TLV - if NHDP mode is selected, then is the RSSA Message TLV included in the NHDP exchanges. (Question: Is this and the following two TLVs optional and are they included as a group or independently of one another?) o NHDP RSSA Address Block TLV - if NHDP mode is selected, then is the RSSA Address Block TLV included in the NHDP exchanges. o Router Priority TLV - if NHDP mode is selected, then is the Router Priority TLV included in the NHDP exchanges. 5.3. The State Group The State Subtree reports current state information. o Node RSS State - is the node currently in or out of the Relay Set. o Neighbors Table - a table containing current neighbors and their operational RSSA. 5.4. The Performance Group The Performance subtree reports primarily counters that relate to SMF RSSA performance. The SMF performance counters consists of per node and per interface objects: (Note: Need to have a discussion of the important and measurable events related to SMF RSSA multicast performance.) (Note: Do we need to break these out by type, i.e., v4 versus v6?) o Total multicast packets received - o Total multicast packets forwarded - o Total duplicate multicast packets detected - o Per interface statistics table with the following entries: * Multicast packets received * Multicast packets forwarded * Duplicate multicast packets detected 5.5. The Notifications Group The Notifications Subtree contains the list of notifications supported within the SMF-MIB and their intended purpose or utility. This group is currently empty. Cole, et al. Expires January 8, 2009 [Page 7] Internet-Draft The SMF MIB July 2008 6. Relationship to Other MIB Modules [TODO]: The text of this section specifies the relationship of the MIB modules contained in this document to other standards, particularly to standards containing other MIB modules. Definitions imported from other MIB modules and other MIB modules that SHOULD be implemented in conjunction with the MIB module contained within this document are identified in this section. 6.1. Relationship to the SNMPv2-MIB The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being mandatory for all systems, and the objects apply to the entity as a whole. The 'system' group provides identification of the management entity and certain other system-wide data. The SMF-MIB does not duplicate those objects. 6.2. Relationship to the IF-MIB [TODO] This section is included as an example; If the MIB module is not an adjunct of the Interface MIB, then this section should be removed. 6.3. MIB modules required for IMPORTS [TODO]: Citations are not permitted within a MIB module, but any module mentioned in an IMPORTS clause or document mentioned in a REFERENCE clause is a Normative reference, and must be cited someplace within the narrative sections. If there are imported items in the MIB module, such as Textual Conventions, that are not already cited, they can be cited in text here. Since relationships to other MIB modules should be described in the narrative text, this section is typically used to cite modules from which Textual Conventions are imported. The following SMF-MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863] 7. Definitions MANET-SMF-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Unsigned32, mib-2 FROM SNMPv2-SMI -- [RFC2578] Cole, et al. Expires January 8, 2009 [Page 8] Internet-Draft The SMF MIB July 2008 TEXTUAL-CONVENTION, RowStatus FROM SNMPv2-TC -- [RFC2579] MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] InetAddress, InetAddressType, InetAddressPrefixLength FROM INET-ADDRESS-MIB -- [RFC4001] InterfaceIndex FROM IF-MIB -- [RFC2863] ; manetSmfMIB MODULE-IDENTITY LAST-UPDATED "200807071200Z" -- July 07, 2008 ORGANIZATION "IETF MANET Working Group" CONTACT-INFO "WG E-Mail: manet@ietf.org WG Chairs: ian.chakeres@gmail.com jmacker@nrl.navy.mil Editors: Robert G. Cole Johns Hopkins University Applied Physics Lab and Department of Computer Science 11000 Johns Hopkins Road Room 02-257 Laurel, MD 22014 USA +1 443 778-6951 robert.cole@jhuapl.edu Joseph Macker Naval Research Laboratory Washington, D.C. 20375 USA macker@itd.nrl.navy.mil Brian Adamson Naval Research Laboratory Washington, D.C. 20375 USA adamson@itd.nrl.navy.mil" DESCRIPTION "This MIB module contains managed object definitions for the Manet SMF RSSA process Cole, et al. Expires January 8, 2009 [Page 9] Internet-Draft The SMF MIB July 2008 defined in: Macker, J., Simplified Multicast Framework, draft-ietf-manet-smf-07, April 10, 2008. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC xxxx; see the RFC itself for full legal notices." -- Revision History REVISION "200807071200Z" -- July 07, 2008 DESCRIPTION "Initial draft of this MIB module published as draft-cole-manet-smf-mib-00.txt." -- RFC-Editor assigns XXXX ::= { mib-2 999 } -- to be assigned by IANA -- -- TEXTUAL CONVENTIONs -- SmfInterfaceOperStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The current operational status of the SMF interface." SYNTAX INTEGER { up(1), down(2), waiting(3), loopback(4), unknown(5) } -- -- Top-Level Object Identifier Assignments -- smfMIBNotifications OBJECT IDENTIFIER ::= { manetSmfMIB 0 } smfMIBObjects OBJECT IDENTIFIER ::= { manetSmfMIB 1 } smfMIBConformance OBJECT IDENTIFIER ::= { manetSmfMIB 2 } -- -- smfConfigurationGroup -- -- This group contains the SMF objects that configure specific -- options that determine the overall performance and operation -- of the multicast forwarding process for the router device -- and its interfaces. -- Cole, et al. Expires January 8, 2009 [Page 10] Internet-Draft The SMF MIB July 2008 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } smfOperationalMode OBJECT-TYPE SYNTAX INTEGER { WithNHDP(0), CDS-Aware-Routing(1), CrossLayer(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The SMF RSS node operational mode. The value 'WithNHDP(0)' indicates .... The value 'CrossLayer(2)' indicates.. ." ::= { smfConfigurationGroup 1 } smfRssa OBJECT-TYPE SYNTAX INTEGER { CF(0), S-MPR(1), E-CDS(2), MPR-CDS(3), Future(4-127), NoStdAction(128-239), Experimental(240-255) } MAX-ACCESS read-write STATUS current DESCRIPTION "The SMF RSS operational algorithm. The value 'CF(0)' indicates .... The value 'Experimental(240-255)' indicates.. ." ::= { smfConfigurationGroup 2 } smfIpv4Dpd OBJECT-TYPE SYNTAX INTEGER { Identification-based(0), Hash-based(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "The current method for IPv4 duplicate packet detection. Cole, et al. Expires January 8, 2009 [Page 11] Internet-Draft The SMF MIB July 2008 The value 'Identification-based(0)' indicates .... The value 'Hash-based(1) indicates.. ." ::= { smfConfigurationGroup 3 } smfIpv6Dpd OBJECT-TYPE SYNTAX INTEGER { Identification-based(0), Hash-based(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "The current method for IPv6 duplicate packet detection. The value 'Identification-based(0)' indicates .... The value 'Hash-based(1) indicates.. ." ::= { smfConfigurationGroup 4 } smfNhdpRssaMesgTlv OBJECT-TYPE SYNTAX INTEGER { NotIncluded(0), Included(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether the associated NHDP messages include the RSSA Message TLV, or not. This is an optional SMF operational setting. Note: we need to include a discussion of the issues associated with not including these TLVs. The value 'NotIncluded(0)' indicates .... The value 'Included(1) indicates.. ." ::= { smfConfigurationGroup 5 } smfNhdpRssaAddrBlockTlv OBJECT-TYPE SYNTAX INTEGER { NotIncluded(0), Cole, et al. Expires January 8, 2009 [Page 12] Internet-Draft The SMF MIB July 2008 Included(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether the associated NHDP messages include the RSSA Address Block TLV, or not. This is an optional SMF operational setting. Note: we need to include a discussion of the issues associated with not including these TLVs. The value 'NotIncluded(0)' indicates .... The value 'Included(1) indicates.. ." ::= { smfConfigurationGroup 6 } smfNhdpRouterPriority OBJECT-TYPE SYNTAX INTEGER { NotIncluded(0), Included(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether the associated NHDP messages include the RSSA Router Priority TLV, or not. This is an optional SMF operational setting. Note: we need to include a discussion of the issues associated with not including these TLVs. The value 'NotIncluded(0)' indicates .... The value 'Included(1) indicates.. ." ::= { smfConfigurationGroup 7 } -- -- smfStateGroup -- -- Contains information describing the current state of the SMF -- process such as the current inclusion in the RS or not. -- smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } Cole, et al. Expires January 8, 2009 [Page 13] Internet-Draft The SMF MIB July 2008 smfNodeRsStatus OBJECT-TYPE SYNTAX INTEGER { NotIncluded(0), Included(1) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current status of the SMF node in the context of the MANETs relay set. The value 'NotIncluded(0)' indicates that the node is currently not part of the MANET's Relay Set. The value 'Included(1)' indicates that the node is currently part of the MANET's Relay Set." ::= { smfStateGroup 1 } -- -- SMF Neighbor Table -- smfNeighborTable OBJECT-TYPE SYNTAX SEQUENCE OF SmfNeighborEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The SMF NeighborTable describes the current neighbor nodes, their address and SMF RSSA and the interface on which they can be reached." REFERENCE "Simplified Multicast Forwarding (SMF), Macker, J., April 2008. Section XXX." ::= { smfStateGroup 2 } smfNeighborEntry OBJECT-TYPE SYNTAX SmfNeighborEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The SMF Neighbor Table contains the set of one-hop neighbors, the interface they are reachable on and the SMF RSSA they are currently running." INDEX { smfNeighborIpAddrType, smfNeighborIpAddr, smfNeighborPrefixLen } Cole, et al. Expires January 8, 2009 [Page 14] Internet-Draft The SMF MIB July 2008 ::= { smfNeighborTable 1 } SmfNeighborEntry ::= SEQUENCE { smfNeighborIpAddrType InetAddressType, smfNeighborIpAddr InetAddress, smfNeighborPrefixLen InetAddressPrefixLength, smfNeighborRSSA INTEGER, smfNeighborNextHopInterface InterfaceIndex } smfNeighborIpAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "The neighbor IP address type." ::= { smfNeighborEntry 1 } smfNeighborIpAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The neighbor Inet IPv4 or IPv6 address." ::= { smfNeighborEntry 2 } smfNeighborPrefixLen OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS not-accessible STATUS current DESCRIPTION "The prefix length. This is a decimal value that indicates the number of contiguous, higher-order bits of the address that make up the network portion of the address." ::= { smfNeighborEntry 3 } smfNeighborRSSA OBJECT-TYPE SYNTAX INTEGER { CF(0), S-MPR(1), E-CDS(2), Cole, et al. Expires January 8, 2009 [Page 15] Internet-Draft The SMF MIB July 2008 MPR-CDS(3), Future(4-127), NoStdAction(128-239), Experimental(240-255) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current RSSA running on the neighbor. The list is identical to that described above for the 'smfRssa' object." ::= { smfNeighborEntry 4 } smfNeighborNextHopInterface OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The interface ifIndex over which the neighbor is reachable in one-hop." ::= { smfNeighborEntry 5 } -- -- SMF Performance Group -- -- Contains objects which help to characterize the -- performance of the SMF RSSA process, typically statistics -- counters. There are two types of SMF RSSA statistics: -- global counters and per interface counters. -- smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } smfGlobalPerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } smfTotalMultiPktsRecv OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of the total number of multicast IP packets received by the device." ::= { smfGlobalPerfGroup 1 } Cole, et al. Expires January 8, 2009 [Page 16] Internet-Draft The SMF MIB July 2008 smfTotalMultiPktsForwarded OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of the total number of multicast IP packets forwarded by the device." ::= { smfGlobalPerfGroup 2 } smfTotalDuplMultiPktsDetected OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of the total number of duplicate multicast IP packets detected by the device." ::= { smfGlobalPerfGroup 3 } -- -- Per SMF Interface Performance Table -- smfInterfacePerfGroup OBJECT IDENTIFIER ::= {smfPerformanceGroup 2} smfInterfacePerfTable OBJECT-TYPE SYNTAX SEQUENCE OF SmfInterfacePerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The SMF Interface Performance Table describes the SMF statistics per interface." ::= { smfInterfacePerfGroup 1 } smfInterfacePerfEntry OBJECT-TYPE SYNTAX SmfInterfacePerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The SMF Interface Performance entry describes the statistics for a particular node interface." INDEX { smfIfPerfIfIndex } ::= { smfInterfacePerfTable 1 } SmfInterfacePerfEntry ::= Cole, et al. Expires January 8, 2009 [Page 17] Internet-Draft The SMF MIB July 2008 SEQUENCE { smfIfPerfIfIndex InterfaceIndex, smfIfMultiPktsRecv Counter32, smfIfMultiPktsForwarded Counter32, smfIfDuplMultiPktsDetected Counter32 } smfIfPerfIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The ifIndex for this node interface that is collecting this set of performance management statistics." ::= { smfInterfacePerfEntry 1 } smfIfMultiPktsRecv OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of the number of multicast IP packets received by the device on the interface." ::= { smfInterfacePerfEntry 2 } smfIfMultiPktsForwarded OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of the number of multicast IP packets forwarded by the device on the interface." ::= { smfInterfacePerfEntry 3 } smfIfDuplMultiPktsDetected OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of the number of duplicate multicast IP packets detected by the Cole, et al. Expires January 8, 2009 [Page 18] Internet-Draft The SMF MIB July 2008 device on the interface." ::= { smfInterfacePerfEntry 4 } -- -- Notifications -- -- Not yet defined -- -- Compliance Statements -- -- Not yet defined END 8. Security Considerations [TODO] Each specification that defines one or more MIB modules MUST contain a section that discusses security considerations relevant to those modules. This section MUST be patterned after the latest approved template (available at http://www.ops.ietf.org/mib-security.html). Remember that the objective is not to blindly copy text from the template, but rather to think and evaluate the risks/vulnerabilities and then state/ document the result of this evaluation. [TODO] if you have any read-write and/or read-create objects, please include the following boilerplate paragraph. There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability: o [TODO] writeable MIB objects that could be especially disruptive if abused MUST be explicitly listed by name and the associated security risks MUST be spelled out; RFC 2669 has a very good example. Cole, et al. Expires January 8, 2009 [Page 19] Internet-Draft The SMF MIB July 2008 o [TODO] list the writable tables and objects and state why they are sensitive. [TODO] else if there are no read-write objects in your MIB module, use the following boilerplate paragraph. There are no management objects defined in this MIB module that have a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB module is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB module via direct SNMP SET operations. [TODO] if you have any sensitive readable objects, please include the following boilerplate paragraph. Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: o [TODO] you must explicitly list by name any readable objects that are sensitive or vulnerable and the associated security risks MUST be spelled out (for instance, if they might reveal customer information or violate personal privacy laws such as those of the European Union if exposed to unauthorized parties) o [TODO] list the tables and objects and state why they are sensitive. [TODO] discuss what security the protocol used to carry the information should have. The following three boilerplate paragraphs should not be changed without very good reason. Changes will almost certainly require justification during IESG review. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Cole, et al. Expires January 8, 2009 [Page 20] Internet-Draft The SMF MIB July 2008 Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 9. IANA Considerations [TODO] In order to comply with IESG policy as set forth in http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is submitted to the IESG for publication MUST contain an IANA Considerations section. The requirements for this section vary depending what actions are required of the IANA. see RFC4181 section 3.5 for more information on writing an IANA clause for a MIB module document. [TODO] select an option and provide the necessary details. Option #1: The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry: Descriptor OBJECT IDENTIFIER value ---------- ----------------------- sampleMIB { mib-2 XXX } Option #2: Editor's Note (to be removed prior to publication): the IANA is requested to assign a value for "XXX" under the 'mib-2' subtree and to record the assignment in the SMI Numbers registry. When the assignment has been made, the RFC Editor is asked to replace "XXX" (here and in the MIB module) with the assigned value and to remove this note. Note well: prior to official assignment by the IANA, a draft document MUST use placeholders (such as "XXX" above) rather than actual numbers. See RFC4181 Section 4.5 for an example of how this is done in a draft MIB module. Option #3: This memo includes no request to IANA. Cole, et al. Expires January 8, 2009 [Page 21] Internet-Draft The SMF MIB July 2008 10. Contributors This MIB document uses the template authored by D. Harrington which is based on contributions from the MIb Doctors, especially Juergen Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 11. Acknowledgements 12. References 12.1. Normative References [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [I-D.ietf-manet-smf] Macker, J. and S. Team, "Simplified Multicast Forwarding for MANET", draft-ietf-manet-smf-07 (work in progress), February 2008. 12.2. Informative References [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. Cole, et al. Expires January 8, 2009 [Page 22] Internet-Draft The SMF MIB July 2008 Appendix A. Change Log Not applicable to draft 00 1. Appendix B. Open Issues This section contains the set of open issues related to the development and design of the SMF-MIB. This section will not be present in the final version of the MIB and will be removed once all the open issues have been resolved. 1. Clarify handling of the NHDP TLV message inclusions? 2. Is it useful to track the effectiveness of the coverage of the current RSSA? Is it possible to track this? 3. Complete notification group. 4. Complete conformance group. 5. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 6. Identify all objects requiring non-volatile storage in their DESCRIPTION clauses. 7. Incorporate parameter relationship conditions into their DESCRIPTION clauses. 8. Complete the security analysis and section. 9. Cleanup all the [TODOs] from the MIB template. Cole, et al. Expires January 8, 2009 [Page 23] Internet-Draft The SMF MIB July 2008 *************************************************************** * Note to the RFC Editor (to be removed prior to publication) * * * * 1) The reference to RFCXXXX within the DESCRIPTION clauses * * of the MIB module point to this draft and are to be * * assigned by the RFC Editor. * * * * 2) The reference to RFCXXX2 throughout this document point * * to the current draft-ietf-manet-smf-xx.txt. This * * need to be replaced with the XXX RFC number. * * * *************************************************************** Authors' Addresses Robert G. Cole Johns Hopkins University 11100 Johns Hopkins Road, Room 257 Laurel, Maryland 21073 USA Phone: +1 443 778 6951 EMail: robert.cole@jhuapl.edu URI: http://www.cs.jhu.edu/~rgcole/ Joseph Macker Navy Research Laboratory XXX Street Washington, D.C. 20375 USA Phone: +1 xxx xxx-xxxx EMail: macker@itd.nrl.navy.mil Brian Adamson Navy Research Laboratory XXX Street Washington, D.C. 20375 USA Phone: +1 xxx xxx-xxxx EMail: adamson@itd.nrl.navy.mil Cole, et al. Expires January 8, 2009 [Page 24] Internet-Draft The SMF MIB July 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgement Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Cole, et al. Expires January 8, 2009 [Page 25]