draft-ietf-manet-smf-mib-00.txt   draft-ietf-manet-smf-mib-01.txt 
Internet Engineering Task Force R. Cole Internet Engineering Task Force R. Cole
Internet-Draft Johns Hopkins University Internet-Draft Johns Hopkins University
Intended status: Standards Track J. Macker Intended status: Standards Track J. Macker
Expires: October 26, 2009 B. Adamson Expires: April 29, 2010 B. Adamson
Naval Research Laboratory Naval Research Laboratory
S. Harnedy S. Harnedy
Booz Allen Hamilton Booz Allen Hamilton
April 24, 2009 October 26, 2009
Definition of Managed Objects for the Manet Simplified Multicast Definition of Managed Objects for the Manet Simplified Multicast
Framework Relay Set Process Framework Relay Set Process
draft-ietf-manet-smf-mib-00 draft-ietf-manet-smf-mib-01
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 26, 2009. This Internet-Draft will expire on April 29, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the In particular, it describes objects for configuring aspects of the
Simplified Multicast Forwarding (SMF) process. The SMF MIB also Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc
reports state information, performance metrics, and notifications. Networks (MANETs). The SMF-MIB also reports state information,
In addition to configuration, this additional state and performance performance metrics, and notifications. In addition to
information is useful to management stations troubleshooting configuration, this additional state and performance information is
multicast forwarding problems. useful to operators troubleshooting multicast forwarding problems.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4
4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6
5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6 5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6
5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7
5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7
5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7
5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8
6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 8 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 8
6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 6.3. Relationship to the Future RSSA-MIBs . . . . . . . . . . . 9
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Security Considerations . . . . . . . . . . . . . . . . . . . 38 8. Security Considerations . . . . . . . . . . . . . . . . . . . 40
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 41 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 42
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 41 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 43
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43
12.1. Normative References . . . . . . . . . . . . . . . . . . . 41 12.1. Normative References . . . . . . . . . . . . . . . . . . . 43
12.2. Informative References . . . . . . . . . . . . . . . . . . 41 12.2. Informative References . . . . . . . . . . . . . . . . . . 43
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 42 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 44
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 42 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 44
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 45
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of a In particular, it describes objects for configuring aspects of a
process implementing Simplified Multicast Forwarding (SMF) process implementing Simplified Multicast Forwarding (SMF)
[I-D.ietf-manet-smf]. SMF provides multicast duplicate packet [I-D.ietf-manet-smf] for Mobile Ad-Hoc Networks (MANETs). SMF
detection (DPD) and supports algorithms for constructing an estimate provides multicast Duplicate Packet Detection (DPD) and supports
of a mobile ad hoc network (MANET) Minimum Connected Dominating Set algorithms for constructing an estimate of a MANET Minimum Connected
(MCDS) for efficient multicast forwarding. The SMF MIB also reports Dominating Set (MCDS) for efficient multicast forwarding. The SMF-
state information, performance metrics, and notifications. In MIB also reports state information, performance metrics, and
addition to configuration, this additional state and performance notifications. In addition to configuration, this additional state
information is useful to management stations troubleshooting and performance information is useful to operators troubleshooting
multicast forwarding problems. multicast forwarding problems.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
skipping to change at page 3, line 44 skipping to change at page 3, line 44
3. Conventions 3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
4. Overview 4. Overview
SMF provides methods for implementing DPD-based multicast forwarding SMF provides methods for implementing DPD-based multicast forwarding
with the optional use of CDS-based relay sets. The MCDS is the with the optional use of Connected Dominating Set (CDS)-based relay
smallest set of MANET nodes (comprising a connected cluster) which sets. The CDS provides a complete connected coverage of the nodes
cover all the nodes in the cluster with their transmissions. As the comprising the MANET. The MCDS is the smallest set of MANET nodes
density of the MANET nodes increase, the fraction of nodes required (comprising a connected cluster) which cover all the nodes in the
in an MCDS decreases. Using the MCDS as a multicast forwarding set cluster with their transmissions. As the density of the MANET nodes
then becomes an efficient multicast mechanism for MANETs. 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 Various algorithms for the construction of estimates of the MCDS
exist. The Simplified Multicast Framework [I-D.ietf-manet-smf] exist. The Simplified Multicast Framework [I-D.ietf-manet-smf]
describes some of these. It further defines various operational describes some of these. It further defines various operational
modes for a node which is participating in the collective creation of modes for a node which is participating in the collective creation of
the MCDS estimates. These modes depend upon the set of related MANET the MCDS estimates. These modes depend upon the set of related MANET
routing and discovery protocols and mechanisms in operation in the routing and discovery protocols and mechanisms in operation in the
specific MANET node. specific MANET node.
A SMF routers' MIB contains SMF process configuration parameters A SMF routers' MIB contains SMF process configuration parameters
skipping to change at page 6, line 7 skipping to change at page 6, line 7
o State Objects - automatically generated values which define the o State Objects - automatically generated values which define the
current operating state of the SMF RS process in the router. current operating state of the SMF RS process in the router.
o Performance Objects - automatically generated values which help an o Performance Objects - automatically generated values which help an
administrator or automated tool to assess the performance of the administrator or automated tool to assess the performance of the
CDS multicast process on the router and the overall multicasting CDS multicast process on the router and the overall multicasting
performance within the MANET routing domain. performance within the MANET routing domain.
5. Structure of the MIB Module 5. Structure of the MIB Module
This section presents the structure of the SMF MIB module. The This section presents the structure of the SMF-MIB module. The
objects are arranged into the following groups: objects are arranged into the following groups:
o smfMIBNotifications - defines the notifications associated with o smfMIBNotifications - defines the notifications associated with
the SMF MIB. the SMF-MIB.
o smfMIBObjects - defines the objects forming the basis for the SMF o smfMIBObjects - defines the objects forming the basis for the SMF-
MIB. These objects are divided up by function into the following MIB. These objects are divided up by function into the following
groups: groups:
o o
* Capabilities Group - This group contains the SMF objects that * Capabilities Group - This group contains the SMF objects that
the device uses to advertise its local capabilities with the device uses to advertise its local capabilities with
respect to, e.g., the supported RSSAs. respect to, e.g., the supported RSSAs.
* Configuration Group - This group contains the SMF objects that * Configuration Group - This group contains the SMF objects that
skipping to change at page 6, line 35 skipping to change at page 6, line 35
of the SMF RSSA and the resulting multicast performance. of the SMF RSSA and the resulting multicast performance.
* State Group - Contains information describing the current state * State Group - Contains information describing the current state
of the SMF RSSA process such as the Neighbor Table. of the SMF RSSA process such as the Neighbor Table.
* Performance Group - Contains objects which help to characterize * Performance Group - Contains objects which help to characterize
the performance of the SMF RSSA process, typically statistics the performance of the SMF RSSA process, typically statistics
counters. counters.
o smfMIBConformance - defines minimal and full conformance of o smfMIBConformance - defines minimal and full conformance of
implementations to this SMF MIB. implementations to this SMF-MIB.
5.1. Textual Conventions 5.1. Textual Conventions
The textual conventions used in the SMF MIB are as follows. The The textual conventions defined within the SMF-MIB are as follows.
RowStatus textual convention is imported from RFC 2579 [RFC2579]. The SmfStatus is defined within the SMF-MIB. This contains the
current operational status of the SMF process on the interface. The
SmfOpModeID represents an index that identifies a specific SMF
operational mode. The SmfRssaID represents an index that identifies
through reference a specific RSSA avaliable for operation on the
device.
5.2. The Capabilities Group 5.2. The Capabilities Group
The SMF device supports a set of capabilities. The list of The SMF device supports a set of capabilities. The list of
capabilities which the device can advertise are: capabilities which the device can advertise are:
o Operational Mode - topology information from NHDP, CDS-aware o Operational Mode - topology information from NHDP, CDS-aware
unicast routing or Cross-layer from Layer 2 unicast routing or Cross-layer from Layer 2.
o SMF RSSA - the specific RSSA operational on the device o SMF RSSA - the specific RSSA operational on the device. Note that
configuration, state and performance objects related to aspecific
RSSA must be defined within another speperate MIB.
5.3. The Configuration Group 5.3. The Configuration Group
The SMF device is configured with a set of controls. The list of The SMF device is configured with a set of controls. The list of
configuration controls for the SMF device follow. configuration controls for the SMF device follow.
o Operational Mode - topology information from NHDP, CDS-aware o Operational Mode - topology information from NHDP, CDS-aware
unicast routing or Cross-layer from Layer 2 unicast routing or Cross-layer from Layer 2.
o SMF RSSA - the specific RSSA operational on the device o SMF RSSA - the specific RSSA operational on the device.
o Duplicate Packet detection for IPv4 - Identification-based or o Duplicate Packet detection for IPv4 - Identification-based or
Hash-based DPD Hash-based DPD.
o Duplicate Packet detection for IPv6 - Identification-based or o Duplicate Packet detection for IPv6 - Identification-based or
Hash-based DPD Hash-based DPD.
o NHDP RSSA Message TLV - if NHDP mode is selected, then is the RSSA o NHDP RSSA Message TLV - if NHDP mode is selected, then is the RSSA
Message TLV included in the NHDP exchanges. (Question: Is this Message TLV included in the NHDP exchanges. [Note: Is this and
and the following two TLVs optional and are they included as a the following two TLVs optional and are they included as a group
group or independently of one another?) or independently of one another?].
o NHDP RSSA Address Block TLV - if NHDP mode is selected, then is o NHDP RSSA Address Block TLV - if NHDP mode is selected, then is
the RSSA Address Block TLV included in the NHDP exchanges. the RSSA Address Block TLV included in the NHDP exchanges.
o Router Priority TLV - if NHDP mode is selected, then is the Router o Router Priority TLV - if NHDP mode is selected, then is the Router
Priority TLV included in the NHDP exchanges. Priority TLV included in the NHDP exchanges.
5.4. The State Group 5.4. The State Group
The State Subtree reports current state information. The State Subtree reports current state information.
o Node RSS State - is the node currently in or out of the Relay Set. 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 o Neighbors Table - a table containing current neighbors and their
operational RSSA. operational RSSA.
5.5. The Performance Group 5.5. The Performance Group
The Performance subtree reports primarily counters that relate to SMF The Performance subtree reports primarily counters that relate to SMF
RSSA performance. The SMF performance counters consists of per node RSSA performance. The SMF performance counters consists of per node
and per interface objects: (Note: Need to have a discussion of the and per interface objects:
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 received.
o Total multicast packets forwarded -
o Total duplicate multicast packets detected - o Total multicast packets forwarded.
o Total duplicate multicast packets detected.
o Per interface statistics table with the following entries: o Per interface statistics table with the following entries:
o o
* Multicast packets received * Multicast packets received.
* Multicast packets forwarded * Multicast packets forwarded.
* Duplicate multicast packets detected * Duplicate multicast packets detected.
5.6. The Notifications Group 5.6. The Notifications Group
The Notifications Subtree contains the list of notifications The Notifications Subtree contains the list of notifications
supported within the SMF-MIB and their intended purpose or utility. supported within the SMF-MIB and their intended purpose or utility.
This group is currently empty. [Note: This group is currently empty.]
6. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
[TODO]: The text of this section specifies the relationship of the [TODO]: The text of this section specifies the relationship of the
MIB modules contained in this document to other standards, MIB modules contained in this document to other standards,
particularly to standards containing other MIB modules. Definitions particularly to standards containing other MIB modules. Definitions
imported from other MIB modules and other MIB modules that SHOULD be imported from other MIB modules and other MIB modules that SHOULD be
implemented in conjunction with the MIB module contained within this implemented in conjunction with the MIB module contained within this
document are identified in this section. document are identified in this section.
6.1. Relationship to the SNMPv2-MIB 6.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 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 mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The SMF-MIB does not entity and certain other system-wide data. The SMF-MIB does not
duplicate those objects. duplicate those objects.
6.2. Relationship to the IF-MIB 6.2. MIB modules required for IMPORTS
[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 The textual conventions imported for use in the SMF-MIB are as
follows. The MOUDULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, Integer32 and mib-2 textual conventions are
imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus
and TruthValue textual conventions are imported from RFC 2579
[RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION-
GROUP textual conventions are imported from RFC 2580 [RFC2580]. The
InterfaceIndexOrZero textual convention is imported from RFC 2863
[RFC2863]. The SnmpAdminString textual convention is imported from
RFC 3411 [RFC3411]. The InetAddress, InetAddressType and
InetAddressPrefixLength textual conventions are imported from RFC
4001 [RFC4001].
[TODO]: Citations are not permitted within a MIB module, but any 6.3. Relationship to the Future RSSA-MIBs
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 In a sense, the SMF-MIB is a general front-end to a set of, yet to be
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB developed, RSSA-specific MIBs. These RSSA-specific MIBs will define
[RFC2863] the objects for the configuration, state, performance and
notification objects required for the operation of these specific
RSSAs.
7. Definitions 7. Definitions
MANET-SMF-MIB DEFINITIONS ::= BEGIN MANET-SMF-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, Integer32, mib-2 Counter32, Unsigned32, Integer32, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
skipping to change at page 9, line 44 skipping to change at page 9, line 47
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411] FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
InetAddress, InetAddressType, InetAddress, InetAddressType,
InetAddressPrefixLength InetAddressPrefixLength
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- [RFC4001]
; ;
manetSmfMIB MODULE-IDENTITY manetSmfMIB MODULE-IDENTITY
LAST-UPDATED "200904211300Z" -- April 21, 2009 LAST-UPDATED "200910261300Z" -- October 26, 2009
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG Chairs: ian.chakeres@gmail.com WG Chairs: ian.chakeres@gmail.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Robert G. Cole Editors: Robert G. Cole
Johns Hopkins University Johns Hopkins University
Applied Physics Lab and Applied Physics Lab and
skipping to change at page 10, line 40 skipping to change at page 10, line 43
Booz Allen Hamilton Booz Allen Hamilton
333 City Boulevard West 333 City Boulevard West
Orange, CA 92868 Orange, CA 92868
USA USA
+1 714 938-3898 +1 714 938-3898
harnedy_sean@bah.com" harnedy_sean@bah.com"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions for "This MIB module contains managed object definitions for
the Manet SMF RSSA process defined in: Macker, J.(ed.), the Manet SMF RSSA process defined in: Macker, J.(ed.),
Simplified Multicast Forwarding draft-ietf-manet-smf-08, Simplified Multicast Forwarding draft-ietf-manet-smf-09,
November 03, 2008. July 13, 2009.
Copyright (C) The IETF Trust (2008). This version Copyright (C) The IETF Trust (2008). This version
of this MIB module is part of RFC xxxx; see the RFC of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices." itself for full legal notices."
-- Revision History -- Revision History
REVISION "200910261300Z" -- October 26, 2009
DESCRIPTION
"Updated draft of this MIB module published as
draft-ietf-manet-smf-mib-01.txt. A few changes
were made in the development of this draft.
Specifically, the following changes were made:
- Updated the textual material, included
section on IMPORTS, relationship to other
MIBs, etc.
"
REVISION "200904211300Z" -- April 21, 2009 REVISION "200904211300Z" -- April 21, 2009
DESCRIPTION DESCRIPTION
"Updated draft of this MIB module published as "Updated draft of this MIB module published as
draft-ietf-manet-smf-mib-00.txt. A few changes draft-ietf-manet-smf-mib-00.txt. A few changes
were made in the development of this draft. were made in the development of this draft.
Specifically, the following changes were made: Specifically, the following changes were made:
- Removed the smfGatewayFilterTable from this - Removed the smfGatewayFilterTable from this
draft. It is a useful construct, e.g., draft. It is a useful construct, e.g.,
an IPTABLES-MIB, but might best be handled an IPTABLES-MIB, but might best be handled
as a seperate MIB and worked within a as a seperate MIB and worked within a
skipping to change at page 12, line 10 skipping to change at page 12, line 24
DESCRIPTION DESCRIPTION
"Initial draft of this MIB module published as "Initial draft of this MIB module published as
draft-cole-manet-smf-mib-00.txt." draft-cole-manet-smf-mib-00.txt."
-- RFC-Editor assigns XXXX -- RFC-Editor assigns XXXX
::= { mib-2 998 } -- to be assigned by IANA ::= { mib-2 998 } -- to be assigned by IANA
-- --
-- TEXTUAL CONVENTIONs -- TEXTUAL CONVENTIONs
-- --
Status ::= TEXTUAL-CONVENTION SmfStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the operability of a DYMO "An indication of the operability of a SMF
function or feature. For example, the status function or feature. For example, the status
of an interface: 'enabled' indicates that of an interface: 'enabled' indicates that
it is willing to communicate with other DYMO routers, it is performing SMF functions,
and 'disabled' indicates that it is not." and 'disabled' indicates that it is not."
SYNTAX INTEGER { SYNTAX INTEGER {
enabled (1), enabled (1),
disabled (2) disabled (2)
} }
SmfOpModeID ::= TEXTUAL-CONVENTION SmfOpModeID ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 15, line 5 skipping to change at page 15, line 17
-- --
-- SMF RSSA Capabilities Table -- SMF RSSA Capabilities Table
-- --
smfRssaCapabilitiesTable OBJECT-TYPE smfRssaCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfRssaCapabilitiesEntry SYNTAX SEQUENCE OF SmfRssaCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smfRssaCapabilitiesTable contains ... "The smfRssaCapabilitiesTable contains
reference to the specific set of RSSAs
currently supported on this device.
" "
::= { smfCapabilitiesGroup 2 } ::= { smfCapabilitiesGroup 2 }
smfRssaCapabilitiesEntry OBJECT-TYPE smfRssaCapabilitiesEntry OBJECT-TYPE
SYNTAX SmfRssaCapabilitiesEntry SYNTAX SmfRssaCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular algorithm." "Information about a particular RSSA
algorithm."
INDEX { smfRssaCapabilitiesID } INDEX { smfRssaCapabilitiesID }
::= { smfRssaCapabilitiesTable 1 } ::= { smfRssaCapabilitiesTable 1 }
SmfRssaCapabilitiesEntry ::= SEQUENCE { SmfRssaCapabilitiesEntry ::= SEQUENCE {
smfRssaCapabilitiesID SmfRssaID, smfRssaCapabilitiesID SmfRssaID,
smfRssaCapabilitiesName SnmpAdminString, smfRssaCapabilitiesName SnmpAdminString,
smfRssaCapabilitiesReference SnmpAdminString smfRssaCapabilitiesReference SnmpAdminString
} }
smfRssaCapabilitiesID OBJECT-TYPE smfRssaCapabilitiesID OBJECT-TYPE
SYNTAX SmfRssaID SYNTAX SmfRssaID
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this entry. This object identifies "The index for this entry. This object identifies
the particular algorithm in this MIB module." the particular RSSA algorithm in this MIB
module."
::= { smfRssaCapabilitiesEntry 1 } ::= { smfRssaCapabilitiesEntry 1 }
smfRssaCapabilitiesName OBJECT-TYPE smfRssaCapabilitiesName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual name of this algorithm. "The textual name of this RSSA algorithm.
" "
::= { smfRssaCapabilitiesEntry 2 } ::= { smfRssaCapabilitiesEntry 2 }
smfRssaCapabilitiesReference OBJECT-TYPE smfRssaCapabilitiesReference OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a reference to the document that "This object contains a published reference
defines this algorithm. to the document that defines this algorithm.
" "
::= { smfRssaCapabilitiesEntry 3 } ::= { smfRssaCapabilitiesEntry 3 }
-- --
-- smfConfigurationGroup -- smfConfigurationGroup
-- --
-- This group contains the SMF objects that configure specific -- This group contains the SMF objects that configure specific
-- options that determine the overall performance and operation -- options that determine the overall performance and operation
-- of the multicast forwarding process for the router device -- of the multicast forwarding process for the router device
-- and its interfaces. -- and its interfaces.
-- --
smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 }
smfAdminStatus OBJECT-TYPE smfAdminStatus OBJECT-TYPE
SYNTAX Status SYNTAX SmfStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configured status of the SMF process "The configured status of the SMF process
on this device. Enabled(1) means that on this device. Enabled(1) means that
SMF is configured to run on this device. SMF is configured to run on this device.
Disabled(2) mean that the SMF process Disabled(2) mean that the SMF process
is configured off." is configured off.
::= { smfConfigurationGroup 1 }
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 1 }
smfConfiguredOpMode OBJECT-TYPE smfConfiguredOpMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
withNHDP(1), withNHDP(1),
cdsAwareRouting(2), cdsAwareRouting(2),
crossLayer(3), crossLayer(3),
other(4) other(4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF RSS node operational mode. "The SMF RSS node operational mode.
The value withNHDP(1) indicates ... The value withNHDP(1) indicates ...
The value cdsAwareRouting(2) indicates ... The value cdsAwareRouting(2) indicates ...
The value crossLayer(3) indicates... ." The value crossLayer(3) indicates... .
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 2 } ::= { smfConfigurationGroup 2 }
smfConfiguredRssa OBJECT-TYPE smfConfiguredRssa OBJECT-TYPE
SYNTAX SmfRssaID SYNTAX SmfRssaID
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF RSS currently operational algorithm. "The SMF RSS currently operational algorithm.
The value cf(1) indicates ... The value cf(1) indicates ...
The value experimental(240-255) indicates... ." The value experimental(240-255) indicates... .
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 3 } ::= { smfConfigurationGroup 3 }
smfRssaMember OBJECT-TYPE smfRssaMember OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
potential(1), potential(1),
always(2), always(2),
never(3) never(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 17, line 33 skipping to change at page 18, line 19
switch to allow for this behavior. switch to allow for this behavior.
The value potential(1) allows the selected The value potential(1) allows the selected
RSSA to determine if this agent is included RSSA to determine if this agent is included
or excluded from the RSS. or excluded from the RSS.
The value always(1) forces the selected The value always(1) forces the selected
RSSA include this agent in the RSS. RSSA include this agent in the RSS.
The value never(3) forces the selected The value never(3) forces the selected
RSSA to exclude this agent from the RSS." RSSA to exclude this agent from the RSS.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 4 } ::= { smfConfigurationGroup 4 }
smfIpv4Dpd OBJECT-TYPE smfIpv4Dpd OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
identificationBased(1), identificationBased(1),
hashBased(2) hashBased(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current method for IPv4 duplicate packet "The current method for IPv4 duplicate packet
detection. detection.
The value identificationBased(1) The value identificationBased(1)
indicates... indicates...
The value 'hashBased(2) indicates... ." The value 'hashBased(2) indicates... .
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 5 } ::= { smfConfigurationGroup 5 }
smfIpv6Dpd OBJECT-TYPE smfIpv6Dpd OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
identificationBased(1), identificationBased(1),
hashBased(2) hashBased(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current method for IPv6 duplicate packet "The current method for IPv6 duplicate packet
detection. detection.
The value identificationBased(1) The value identificationBased(1)
indicates... indicates...
The value 'hashBased(2) indicates... ." The value 'hashBased(2) indicates... .
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 6 } ::= { smfConfigurationGroup 6 }
smfMaxPktLifetime OBJECT-TYPE smfMaxPktLifetime OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The estimate of the network packet "The estimate of the network packet
traversal time. traversal time.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
" "
DEFVAL { 60 } DEFVAL { 60 }
::= { smfConfigurationGroup 7 } ::= { smfConfigurationGroup 7 }
smfDpdMaxMemorySize OBJECT-TYPE smfDpdMaxMemorySize OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
UNITS "Kilo-Bytes" UNITS "Kilo-Bytes"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The locally reserved memory for storage "The locally reserved memory for storage
of cached DPD records for both IPv4 and of cached DPD records for both IPv4 and
IPv6 methods. IPv6 methods.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
" "
DEFVAL { 1024 } DEFVAL { 1024 }
::= { smfConfigurationGroup 8 } ::= { smfConfigurationGroup 8 }
smfDpdEntryMaxLifetime OBJECT-TYPE smfDpdEntryMaxLifetime OBJECT-TYPE
SYNTAX Integer32 (0..65525) SYNTAX Integer32 (0..65525)
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum lifetime of a cached DPD "The maximum lifetime of a cached DPD
record in the local device storage. record in the local device storage.
skipping to change at page 19, line 5 skipping to change at page 20, line 16
smfDpdEntryMaxLifetime OBJECT-TYPE smfDpdEntryMaxLifetime OBJECT-TYPE
SYNTAX Integer32 (0..65525) SYNTAX Integer32 (0..65525)
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum lifetime of a cached DPD "The maximum lifetime of a cached DPD
record in the local device storage. record in the local device storage.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
" "
DEFVAL { 600 } DEFVAL { 600 }
::= { smfConfigurationGroup 9 } ::= { smfConfigurationGroup 9 }
-- --
-- Configuration of messages to be included in -- Configuration of messages to be included in
-- NHDP message exchanges in support of SMF -- NHDP message exchanges in support of SMF
-- operations. -- operations.
-- --
smfNhdpRssaMesgTLVIncluded OBJECT-TYPE smfNhdpRssaMesgTLVIncluded OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the associated NHDP messages "Indicates whether the associated NHDP messages
include the RSSA Message TLV, or not. This include the RSSA Message TLV, or not. This
is an optional SMF operational setting. is an optional SMF operational setting.
The value true(1) indicates that this TLV is The value true(1) indicates that this TLV is
included; the value false(2) indicates that it included; the value false(2) indicates that it
is not included." is not included.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 10 } ::= { smfConfigurationGroup 10 }
smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the associated NHDP messages "Indicates whether the associated NHDP messages
include the RSSA Address Block TLV, or not. include the RSSA Address Block TLV, or not.
This is an optional SMF operational setting. This is an optional SMF operational setting.
The value true(1) indicates that this TLV is The value true(1) indicates that this TLV is
included; the value false(2) indicates that it included; the value false(2) indicates that it
is not included." is not included.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 11 } ::= { smfConfigurationGroup 11 }
smfNhdpRouterPriorityTLVIncluded OBJECT-TYPE smfNhdpRouterPriorityTLVIncluded OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the associated NHDP messages "Indicates whether the associated NHDP messages
include the RSSA Router Priority TLV, or not. include the RSSA Router Priority TLV, or not.
This is an optional SMF operational setting. This is an optional SMF operational setting.
The value true(1) indicates that this TLV is The value true(1) indicates that this TLV is
included; the value false(2) indicates that it included; the value false(2) indicates that it
is not included." is not included.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 12 } ::= { smfConfigurationGroup 12 }
-- --
-- Table identifying configured multicast addresses to be forwarded. -- Table identifying configured multicast addresses to be forwarded.
-- --
smfConfiguredAddrForwardingTable OBJECT-TYPE smfConfiguredAddrForwardingTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table containing information on multicast "The (conceptual) table containing information on multicast
addresses which are to be forwarded by the SMF process. addresses which are to be forwarded by the SMF process.
Entries in this table are configured. As well, addresses Entries in this table are configured. As well, addresses
to be forwarded by the SMF device can be dynamically to be forwarded by the SMF device can be dynamically
discovered by other means. The corresponding state discovered by other means. The corresponding state
table, table, smfDiscoveredAddrForwardingTable, contains
smfDiscoveredAddrForwardingTable contains
these additional, dynamically discovered address for these additional, dynamically discovered address for
forwarding. forwarding.
Each row is associated with a range of multicast Each row is associated with a range of multicast
addresses, and ranges for different rows must be disjoint. addresses, and ranges for different rows must be disjoint.
The objects in this table are persistent and when written
the entity SHOULD save the change to
non-volatile storage.
" "
::= { smfConfigurationGroup 13 } ::= { smfConfigurationGroup 13 }
smfConfiguredAddrForwardingEntry OBJECT-TYPE smfConfiguredAddrForwardingEntry OBJECT-TYPE
SYNTAX SmfConfiguredAddrForwardingEntry SYNTAX SmfConfiguredAddrForwardingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) containing the information on a "An entry (conceptual row) containing the information on a
particular multicast scope." particular multicast scope."
skipping to change at page 22, line 13 skipping to change at page 23, line 43
smfInterfaceTable OBJECT-TYPE smfInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfInterfaceEntry SYNTAX SEQUENCE OF SmfInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF Interface Table describes the SMF "The SMF Interface Table describes the SMF
interfaces that are participating in the interfaces that are participating in the
SMF packet forwarding process. The ifIndex is SMF packet forwarding process. The ifIndex is
from the interfaces group defined in the from the interfaces group defined in the
Interfaces Group MIB. Interfaces Group MIB.
The objects in this table are persistent
and when written the entity SHOULD save
the change to non-volatile storage.
" "
REFERENCE REFERENCE
"RFC 2863 - The Interfaces Group MIB, McCloghrie, "RFC 2863 - The Interfaces Group MIB, McCloghrie,
K., and F. Kastenholtz, June 2000." K., and F. Kastenholtz, June 2000."
::= { smfConfigurationGroup 14 } ::= { smfConfigurationGroup 14 }
smfInterfaceEntry OBJECT-TYPE smfInterfaceEntry OBJECT-TYPE
SYNTAX SmfInterfaceEntry SYNTAX SmfInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF interface entry describes one SMF "The SMF interface entry describes one SMF
interface as indexed by its ifIndex." interface as indexed by its ifIndex."
INDEX { smfIfIndex } INDEX { smfIfIndex }
::= { smfInterfaceTable 1 } ::= { smfInterfaceTable 1 }
SmfInterfaceEntry ::= SmfInterfaceEntry ::=
SEQUENCE { SEQUENCE {
smfIfIndex InterfaceIndexOrZero, smfIfIndex InterfaceIndexOrZero,
smfIfAdminStatus Status, smfIfAdminStatus SmfStatus,
smfIfRowStatus RowStatus smfIfRowStatus RowStatus
} }
smfIfIndex OBJECT-TYPE smfIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex for this SMF interface." "The ifIndex for this SMF interface."
::= { smfInterfaceEntry 1 } ::= { smfInterfaceEntry 1 }
smfIfAdminStatus OBJECT-TYPE smfIfAdminStatus OBJECT-TYPE
SYNTAX Status SYNTAX SmfStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF interface's administrative status. "The SMF interface's administrative status.
The value 'enabled' denotes that the interface The value 'enabled' denotes that the interface
is running the SMF forwarding process. is running the SMF forwarding process.
The value 'disabled' denotes that the interface is The value 'disabled' denotes that the interface is
external to the SMF forwarding process. external to the SMF forwarding process.
" "
::= { smfInterfaceEntry 2 } ::= { smfInterfaceEntry 2 }
smfIfRowStatus OBJECT-TYPE smfIfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 26, line 18 skipping to change at page 28, line 5
SYNTAX SEQUENCE OF SmfNeighborEntry SYNTAX SEQUENCE OF SmfNeighborEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF NeighborTable describes the "The SMF NeighborTable describes the
current neighbor nodes, their address current neighbor nodes, their address
and SMF RSSA and the interface on which and SMF RSSA and the interface on which
they can be reached." they can be reached."
REFERENCE REFERENCE
"Simplified Multicast Forwarding for MANET "Simplified Multicast Forwarding for MANET
(SMF), Macker, J., February 2008. (SMF), Macker, J., July 2009.
Section 7: SMF Neighborhood Discovery Section 7: SMF Neighborhood Discovery
Requirements." Requirements."
::= { smfStateGroup 4 } ::= { smfStateGroup 4 }
smfNeighborEntry OBJECT-TYPE smfNeighborEntry OBJECT-TYPE
SYNTAX SmfNeighborEntry SYNTAX SmfNeighborEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF Neighbor Table contains the "The SMF Neighbor Table contains the
skipping to change at page 33, line 24 skipping to change at page 35, line 13
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF Interface Performance entry "The SMF Interface Performance entry
describes the statistics for a particular describes the statistics for a particular
node interface." node interface."
INDEX { smfIpv6IfPerfIfIndex } INDEX { smfIpv6IfPerfIfIndex }
::= { smfIpv6InterfacePerfTable 1 } ::= { smfIpv6InterfacePerfTable 1 }
SmfIpv6InterfacePerfEntry ::= SmfIpv6InterfacePerfEntry ::=
SEQUENCE { SEQUENCE {
smfIpv6IfPerfIfIndex InterfaceIndexOrZero, smfIpv6IfPerfIfIndex InterfaceIndexOrZero,
smfIpv6MultiPktsRecvPerIf Counter32, smfIpv6MultiPktsRecvPerIf Counter32,
smfIpv6MultiPktsForwardedPerIf Counter32, smfIpv6MultiPktsForwardedPerIf Counter32,
smfIpv6DuplMultiPktsDetectedPerIf Counter32, smfIpv6DuplMultiPktsDetectedPerIf Counter32,
smfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, smfIpv6DroppedMultiPktsTTLExceededPerIf Counter32,
smfIpv6TTLLargerThanPreviousPerIf Counter32, smfIpv6TTLLargerThanPreviousPerIf Counter32,
smfIpv6HAVAssistsReqdPerIf Counter32, smfIpv6HAVAssistsReqdPerIf Counter32,
smfIpv6DpdHeaderInsertionsPerIf Counter32 smfIpv6DpdHeaderInsertionsPerIf Counter32
} }
smfIpv6IfPerfIfIndex OBJECT-TYPE smfIpv6IfPerfIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex for this node interface "The ifIndex for this node interface
that is collecting this set of that is collecting this set of
performance management statistics. performance management statistics.
skipping to change at page 41, line 22 skipping to change at page 43, line 14
11. Acknowledgements 11. Acknowledgements
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The [RFC2863] McCloghrie, K. and F. Kastenholz, "The
Interfaces Group MIB", RFC 2863, June 2000. Interfaces Group MIB", RFC 2863, June 2000.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network
Management Protocol (SNMP) Management
Frameworks", STD 62, RFC 3411, December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) [RFC3418] Presuhn, R., "Management Information Base (MIB)
for the Simple Network Management Protocol for the Simple Network Management Protocol
(SNMP)", STD 62, RFC 3418, December 2002. (SNMP)", STD 62, RFC 3418, December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for
Internet Network Addresses", RFC 4001,
February 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to [RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14, RFC 2119, Indicate Requirement Levels", BCP 14, RFC 2119,
March 1997. March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Schoenwaelder, Ed., "Structure of Management
Information Version 2 (SMIv2)", STD 58, Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999. RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for Schoenwaelder, Ed., "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2580] McCloghrie, K., Perkins, D., and J.
Schoenwaelder, "Conformance Statements for Schoenwaelder, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[I-D.ietf-manet-smf] Macker, J. and S. Team, "Simplified Multicast [I-D.ietf-manet-smf] Macker, J. and S. Team, "Simplified Multicast
Forwarding for MANET", draft-ietf-manet-smf-08 Forwarding", draft-ietf-manet-smf-09 (work in
(work in progress), November 2008. progress), July 2009.
12.2. Informative References 12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. [RFC3410] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction and Applicability Stewart, "Introduction and Applicability
Statements for Internet-Standard Management Statements for Internet-Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
Appendix A. Change Log Appendix A. Change Log
Not applicable to draft 00 This section tracks the revision history in the development of this
SMF-MIB. It will be removed from the final version of this document.
1. These changes were made from draft-ietf-manet-dymo-mib-00 to
draft-ietf-manet-dymo-mib-01.
1. Editorial changes to the textual material. These included the
addition of the paragraphs on TEXTUAL-CONVENTIONS defined and
imported into this MIB and relationships to other MIBs.
2. Identified those objects in the SMF-MIB requiring non-volatile
storage.
3. Changed the name of the TEXTUAL-CONVENTION 'Status', defined
within this MIB to 'SmfStatus'.
Appendix B. Open Issues Appendix B. Open Issues
This section contains the set of open issues related to the This section contains the set of open issues related to the
development and design of the SMF-MIB. This section will not be 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 present in the final version of the MIB and will be removed once all
the open issues have been resolved. the open issues have been resolved.
1. Clarify handling of the NHDP TLV message inclusions? 1. The text states 'NHDP RSSA Message TLV - if NHDP mode is
selected, then is the RSSA Message TLV included in the NHDP
2. Can we develop a capabilities table for the supported RSSA exchanges.' Is this and the following two TLVs optional and are
algorithms? And, if so, can each supported RSSA have a they included as a group or independently of one another?].
different set of configuration parameters?
3. Is the Gateway Filter table appropriate for this MIB or should
it be handled in a separate MIB worked elsewhere? How should
this table be indexed and how should it represent the ordering
of the rules (or chains)? Should this be greatly simplified?
How do we handle null values in the rules? --- This has been
removed from the draft-ietf-smf-mib-00 version of the MIB. It
is probably more appropriate for a seperate MIB worked within a
security focused working group. It is a good construct however,
e.g., defining an IPTABLES-MIB.
4. Is it useful to track the effectiveness of the coverage of the
current RSSA? Is it possible to track this?
5. Complete notification group.
6. Complete conformance group. 2. Is it useful to track the effectiveness of the coverage of the
current RSSA? Is it possible to track this?
7. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 3. Complete notification group.
8. Update the text of the document to reflect the final state of 4. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB.
the MIB.
9. Identify all objects requiring non-volatile storage in their 5. Update the text of the document to reflect the final state of the
DESCRIPTION clauses. MIB.
10. Incorporate parameter relationship conditions into their 6. Incorporate parameter relationship conditions into their
DESCRIPTION clauses. DESCRIPTION clauses.
11. Complete the security analysis and section. 7. Complete the security analysis and section.
12. Cleanup all the [TODOs] from the MIB template. 8. Cleanup all the [TODOs] from the MIB template.
Appendix C. Appendix C.
*************************************************************** ***************************************************************
* Note to the RFC Editor (to be removed prior to publication) * * Note to the RFC Editor (to be removed prior to publication) *
* * * *
* 1) The reference to RFCXXXX within the DESCRIPTION clauses * * 1) The reference to RFCXXXX within the DESCRIPTION clauses *
* of the MIB module point to this draft and are to be * * of the MIB module point to this draft and are to be *
* assigned by the RFC Editor. * * assigned by the RFC Editor. *
* * * *
 End of changes. 80 change blocks. 
149 lines changed or deleted 238 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/