draft-ietf-manet-smf-mib-13.txt   rfc7367.txt 
Internet Engineering Task Force R. Cole Internet Engineering Task Force (IETF) R. Cole
Internet-Draft US Army CERDEC Request for Comments: 7367 US Army CERDEC
Intended status: Experimental J. Macker Category: Experimental J. Macker
Expires: February 13, 2015 B. Adamson ISSN: 2070-1721 B. Adamson
Naval Research Laboratory Naval Research Laboratory
August 12, 2014 October 2014
Definition of Managed Objects for the Manet Simplified Multicast Definition of Managed Objects for the Mobile Ad Hoc Network (MANET)
Framework Relay Set Process Simplified Multicast Framework Relay Set Process
draft-ietf-manet-smf-mib-13
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 for Mobile Ad-Hoc Simplified Multicast Forwarding (SMF) process for Mobile Ad Hoc
Networks (MANETs). The SMF-MIB module also reports state Networks (MANETs). The SMF-MIB module also reports state
information, performance information, and notifications. In addition information, performance information, and notifications. In addition
to configuration, the additional state and performance information is to configuration, the additional state and performance information is
useful to operators troubleshooting multicast forwarding problems. useful to operators troubleshooting multicast forwarding problems.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for examination, experimental implementation, and
evaluation.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document defines an Experimental Protocol for the Internet
and may be updated, replaced, or obsoleted by other documents at any community. This document is a product of the Internet Engineering
time. It is inappropriate to use Internet-Drafts as reference Task Force (IETF). It represents the consensus of the IETF
material or to cite them other than as "work in progress." community. It has received public review and has been approved for
publication by the Internet Engineering Steering Group (IESG). Not
all documents approved by the IESG are a candidate for any level of
Internet Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on February 13, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7367.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
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 . . . . . . . . . . . . . . . . . 5 5. Structure of the MIB Module .....................................5
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 ....................................6
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 ....................................7
5.7. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 5.7. Tables and Indexing ........................................8
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 6. Relationship to Other MIB Modules ...............................9
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 6.1. Relationship to the SNMPv2-MIB .............................9
6.2. Relationship to the IP-MIB . . . . . . . . . . . . . . . . 9 6.2. Relationship to the IP-MIB .................................9
6.3. Relationship to the IPMCAST-MIB . . . . . . . . . . . . . 10 6.3. Relationship to the IPMCAST-MIB ............................9
6.4. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 6.4. MIB Modules Required for IMPORTS ..........................10
6.5. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10 6.5. Relationship to Future RSSA-MIB Modules ...................10
7. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 11 7. SMF-MIB Definitions ............................................10
8. IANA-SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . 52 8. IANA-SMF-MIB Definitions .......................................51
9. Security Considerations . . . . . . . . . . . . . . . . . . . 56 9. Security Considerations ........................................56
10. Applicability Statement . . . . . . . . . . . . . . . . . . . 60 10. Applicability Statement .......................................59
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 11. IANA Considerations ...........................................62
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 63 12. References ....................................................62
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 63 12.1. Normative References .....................................62
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63 12.2. Informative References ...................................64
14.1. Normative References . . . . . . . . . . . . . . . . . . . 63 Acknowledgements ..................................................65
14.2. Informative References . . . . . . . . . . . . . . . . . . 64 Contributors ......................................................65
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Authors' Addresses ................................................65
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) [RFC6621] process implementing Simplified Multicast Forwarding (SMF) [RFC6621]
for Mobile Ad-Hoc Networks (MANETs). SMF provides multicast for Mobile Ad Hoc Networks (MANETs). SMF provides multicast
Duplicate Packet Detection (DPD) and supports algorithms for Duplicate Packet Detection (DPD) and supports algorithms for
constructing an estimate of a MANET Minimum Connected Dominating Set constructing an estimate of a MANET Minimum Connected Dominating Set
(MCDS) for efficient multicast forwarding. The SMF-MIB module also (MCDS) for efficient multicast forwarding. The SMF-MIB module also
reports state information, performance information, and reports state information, performance information, and
notifications. In addition to configuration, this additional state notifications. In addition to configuration, this additional state
and performance information is useful to operators 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
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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC "OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119]. 2119 [RFC2119].
4. Overview 4. Overview
SMF provides methods for implementing Duplicate Packet Detection SMF provides methods for implementing DPD-based multicast forwarding
(DPD)-based multicast forwarding with the optional use of Connected with the optional use of CDS-based relay sets. The CDS provides a
Dominating Set (CDS)-based relay sets. The CDS provides a complete complete connected coverage of the nodes comprising the MANET. The
connected coverage of the nodes comprising the MANET. The Minimum MCDS is the smallest set of MANET nodes (comprising a connected
CDS (MCDS) is the smallest set of MANET nodes (comprising a connected cluster) that cover all the nodes in the cluster with their
cluster) which cover all the nodes in the cluster with their
transmissions. As the density of the MANET nodes increase, the transmissions. As the density of the MANET nodes increase, the
fraction of nodes required in an MCDS decreases. Using the MCDS as a fraction of nodes required in an MCDS decreases. Using the MCDS as a
multicast forwarding set then becomes an efficient multicast multicast forwarding set then becomes an efficient multicast
mechanism for MANETs. 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 [RFC6621] describes some exist. The Simplified Multicast Framework [RFC6621] describes some
of these. It further defines various operational modes for a node of these. It further defines various operational modes for a node
which is participating in the collective creation of the MCDS that is participating in the collective creation of the MCDS
estimates. These modes depend upon the set of related MANET routing estimates. These modes depend upon the set of related MANET routing
and discovery protocols and mechanisms in operation in the specific and discovery protocols and mechanisms in operation in the specific
MANET node. MANET node.
A SMF router's MIB module contains SMF process configuration A SMF router's MIB module contains SMF process configuration
parameters (e.g. specific CDS algorithm), state information (e.g., parameters (e.g., specific CDS algorithm), state information (e.g.,
current membership in the CDS), performance counters (e.g., packet current membership in the CDS), performance counters (e.g., packet
counters), and notifications. counters), and notifications.
4.1. SMF Management Model 4.1. SMF Management Model
This section describes the management model for the SMF node process. This section describes the management model for the SMF node process.
Figure 1 (reproduced from Figure 1 of [RFC6621]) shows the Figure 1 (reproduced from Figure 1 of [RFC6621]) shows the
relationship between the SMF Relay Set selection algorithm and the relationship between the SMF Relay Set Selection Algorithm and the
related algorithms, processes and protocols running in the MANET related algorithms, processes, and protocols running in the MANET
nodes. The Relay Set Selection Algorithm (RSSA) can rely upon nodes. The Relay Set Selection Algorithm (RSSA) can rely upon
topology information gotten from the MANET Neighborhood Discovery topology information acquired from the MANET Neighborhood Discovery
Protocol (NHDP), from the specific MANET routing protocol running on Protocol (NHDP), from the specific MANET routing protocol running on
the node, or from Layer 2 information passed up to the higher layer the node, or from Layer 2 information passed up to the higher layer
protocol processes. protocol processes.
______________ ____________ ______________ ____________
| | | | | | | |
| Neighborhood | | Relay Set | | Neighborhood | | Relay Set |
| Discovery |------------->| Selection | | Discovery |------------->| Selection |
| | neighbor | | | | neighbor | |
|______________| info |____________| |______________| info |____________|
\ /
\ / \ /
neighbor\ / forwarding neighbor\ / forwarding
info \ _____________ / status info* \ _____________ / status
\ | | / \ | | /
`-->| Forwarding |<--' `-->| Forwarding |<--'
| Process | | Process |
----------------->|_____________|-----------------> ----------------->|_____________|----------------->
incoming packet, forwarded packets incoming packet, forwarded packets
interface id , and interface id*, and
previous hop previous hop*
Figure 1: SMF Router Architecture Figure 1: SMF Router Architecture
The asterisks (*) mark the primitives and relationships needed by
relay set algorithms requiring previous-hop packet-forwarding
knowledge.
4.2. Terms 4.2. Terms
The following definitions apply throughout this document: The following definitions apply throughout this document:
o Configuration Objects - switches, tables, objects which are Configuration Objects: switches, tables, and objects that are
initialized to default settings or set through the management initialized to default settings or set through the management
interfaces such as defined by this MIB module. interfaces such as defined by this MIB module.
o Tunable Configuration Objects - objects whose values affect timing Tunable Configuration Objects: objects whose values affect timing or
or attempt bounds on the SMF Relay Set (RS) process. attempt bounds on the SMF Relay Set (RS) process.
o State Objects - automatically generated values which define the State Objects: automatically generated values that 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 Performance Objects: automatically generated values that 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 multicast CDS multicast process on the router and the overall multicast
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
skipping to change at page 6, line 20 skipping to change at page 5, line 47
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
configure specific options that determine the overall operation configure specific options that determine the overall operation
of the SMF process and the resulting multicast performance. of the SMF process and the resulting multicast performance.
* State Group - Contains information describing the current state * State Group - Contains information describing the current state
of the SMF process such as the Neighbor Table. of the SMF process such as the Neighbor Table.
* Performance Group - Contains objects which help to characterize * Performance Group - Contains objects that help to characterize
the performance of the SMF process, typically counters for the performance of the SMF process, typically counters for
statistical computations. statistical computations.
o smfMIBConformance - defines two, i.e., minimal and full, o smfMIBConformance - defines two, i.e., minimal and full,
conformance implementations for the SMF-MIB module. conformance implementations for the SMF-MIB module.
5.1. Textual Conventions 5.1. Textual Conventions
The textual conventions defined within the SMF-MIB module are: The Textual Conventions defined within the SMF-MIB module:
o The SmfStatus is defined within the SMF-MIB module. This contains o The SmfStatus is defined within the SMF-MIB module. This contains
the current operational status of the SMF process on an interface. the current operational status of the SMF process on an interface.
The textual conventions defined for the SMF-MIB module and maintained The Textual Conventions defined for the SMF-MIB module and maintained
by IANA are: by IANA are:
o The IANAsmfOpModeIdTC represents an index that identifies a o The IANAsmfOpModeIdTC represents an index that identifies a
specific SMF operational mode. This textual convention is specific SMF operational mode. This Textual Convention is
maintained by IANA in the IANA-SMF-MIB. maintained by IANA in the IANA-SMF-MIB.
o The IANAsmfRssaIdTC represents an index that identifies, through o The IANAsmfRssaIdTC represents an index that identifies, through
reference, a specific RSSA available for operation on the device. reference, a specific RSSA available for operation on the device.
This textual convention is maintained by IANA also in the IANA- This Textual Convention is maintained by IANA also in the IANA-
SMF-MIB. SMF-MIB.
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 that the device can advertise is as follows:
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. Note that o SMF RSSA - the specific RSSA operational on the device. Note that
configuration, state and performance objects related to a specific configuration, state, and performance objects related to a
RSSA must be defined within a separate MIB module. specific RSSA must be defined within a separate MIB module.
5.3. The Configuration Group 5.3. The Configuration Group
The SMF device is configured with a set of controls. Some of the The SMF device is configured with a set of controls. Some of the
prominent configuration controls for the SMF device are: prominent configuration controls for the SMF device are:
o Operational Mode - determines where topology information is o Operational Mode - determines from where topology information is
derived from, e.g., NHDP, CDS-aware unicast routing or Cross-layer derived, e.g., NHDP, CDS-aware unicast routing, or Cross-layer
from Layer 2. 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 (I-DPD or H-DPD, respectively).
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 SMF Type Message TLV - if NHDP mode is selected, then the SMF Type o SMF Type Message TLV - if NHDP mode is selected, then the SMF Type
Message TLV MAY be included in the NHDP exchanges. Message TLV MAY be included in the NHDP exchanges.
o SMF Address Block TLV - if NHDP mode is selected, then the SMF o SMF Address Block TLV - if NHDP mode is selected, then the SMF
Address Block TLV SHOULD be included in the NHDP exchanges. Address Block TLV SHOULD be included in the NHDP exchanges.
o SMF Address Forwarding Table - a table identifying configured o SMF Address Forwarding Table - a table identifying configured
multicast addresses to be forwarded by the SMF process. multicast addresses to be forwarded by the SMF process.
5.4. The State Group 5.4. The State Group
The State sub-tree reports current state information, e.g., The State sub-tree reports current state information, for example,
o Node RSSA State - identifies whether the node is currently in or o Node RSSA State - identifies whether the node is currently in or
out of the Relay Set. out of the Relay Set.
o Neighbors Table - a table containing current one-hop neighbors and o Neighbors Table - a table containing current one-hop neighbors and
their operational RSSA. their operational RSSA.
5.5. The Performance Group 5.5. The Performance Group
The Performance sub-tree reports primarily counters that relate to The Performance sub-tree primarily reports counters that relate to
SMF RSSA performance. The SMF performance counters consists of per SMF RSSA performance. The SMF performance counters consist of per-
node and per interface objects: node and per-interface objects:
o Total multicast packets received. o Total multicast packets received.
o Total multicast packets forwarded. o Total multicast packets forwarded.
o Total duplicate multicast packets detected. o Total duplicate multicast packets detected.
o Per interface statistics table with the following entries: o Per interface statistics table with the following entries:
* 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 Sub-tree contains the list of notifications The Notifications sub-tree contains the list of notifications
supported within the SMF-MIB module and their intended purpose and supported within the SMF-MIB module and their intended purpose and
utility. utility.
5.7. Tables and Indexing 5.7. Tables and Indexing
The SMF-MIB module contains a number of tables which record data The SMF-MIB module contains a number of tables that record data
related to: related to:
o configuration and operation of packet forwarding on the local o configuration and operation of packet forwarding on the local
router, router,
o configuration and operation of local MANET interfaces on the o configuration and operation of local MANET interfaces on the
router, and router, and
o configuration and operation of various RSSA algorithms for packet o configuration and operation of various RSSAs for packet
forwarding. forwarding.
The SMF-MIB module's tables are indexed via the following constructs: The SMF-MIB module's tables are indexed via the following constructs:
o smfCapabilitiesIndex - the index identifying the combination of o smfCapabilitiesIndex - the index identifying the combination of
SMF mode and SMF RSSA available on this device. SMF mode and SMF RSSA available on this device.
o smfCfgAddrForwardingIndex - the index to configured multicast o smfCfgAddrForwardingIndex - the index to configured multicast
addresses lists which are forwarded by the SMF process. address lists that are forwarded by the SMF process.
o smfCfgIfIndex - the IfIndex of the interface on the local router o smfCfgIfIndex - the IfIndex of the interface on the local router
on which SMF is configured. on which SMF is configured.
o smfStateNeighborIpAddrType, smfStateNeighborIpAddr, and o smfStateNeighborIpAddrType, smfStateNeighborIpAddr, and
smfStateNeighborPrefixLen - the interface index set of specific smfStateNeighborPrefixLen - the interface index set of specific
one-hop neighbor nodes to this local router. one-hop neighbor nodes to this local router.
These tables and their associated indexing are: These tables and their associated indexing are defined in the SMF-MIB
module:
o smfCapabilitiesTable - identifies the resident set of (SMF o smfCapabilitiesTable - identifies the resident set of (SMF
Operational Modes, SMF RSSA algorithms) available on this router. Operational Modes, SMF RSSA algorithms) available on this router.
This table has 'INDEX { smfCapabilitiesIndex }. This table has 'INDEX { smfCapabilitiesIndex }'.
o smfCfgAddrForwardingTable - contains information on multicast o smfCfgAddrForwardingTable - contains information on multicast
addresses which are to be forwarded by the SMF process on this addresses that are to be forwarded by the SMF process on this
device. This table has 'INDEX { smfCfgAddrForwardingIndex }'. device. This table has 'INDEX { smfCfgAddrForwardingIndex }'.
o smfCfgInterfaceTable - describes the SMF interfaces on this device o smfCfgInterfaceTable - describes the SMF interfaces on this device
that are participating in the SMF packet forwarding process. This that are participating in the SMF packet forwarding process. This
table has 'INDEX { smfCfgIfIndex }'. table has 'INDEX { smfCfgIfIndex }'.
o smfStateNeighborTable - describes the current neighbor nodes, o smfStateNeighborTable - describes the current neighbor nodes,
their addresses and the SMF RSSA and the interface on which they their addresses and the SMF RSSA and the interface on which they
can be reached. This table has 'INDEX { can be reached. This table has 'INDEX {
smfStateNeighborIpAddrType, smfStateNeighborIpAddr, smfStateNeighborIpAddrType, smfStateNeighborIpAddr,
smfStateNeighborPrefixLen }'. smfStateNeighborPrefixLen }'.
o smfPerfIpv4InterfacePerfTable - contains the IPv4 related SMF o smfPerfIpv4InterfacePerfTable - contains the IPv4-related SMF
statistics per each SMF interface on this device. This table has statistics per each SMF interface on this device. This table has
'INDEX { smfCfgIfIndex }'. 'INDEX { smfCfgIfIndex }'.
o smfPerfIpv6InterfacePerfTable - contains the IPv6 related SMF o smfPerfIpv6InterfacePerfTable - contains the IPv6-related SMF
statistics per each SMF interface on this device. This table has statistics per each SMF interface on this device. This table has
'INDEX { smfCfgIfIndex }'. 'INDEX { smfCfgIfIndex }'.
6. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
6.1. Relationship to the SNMPv2-MIB 6.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB module [RFC3418] is defined as The 'system' group in the SNMPv2-MIB module [RFC3418] is defined as
being mandatory for all systems, and the objects apply to the entity being mandatory for all systems, and the objects apply to the entity
as a whole. The 'system' group provides identification of the as a whole. The 'system' group provides identification of the
skipping to change at page 10, line 11 skipping to change at page 9, line 46
The SMF-MIB module counters within the smfPerformanceGroup count The SMF-MIB module counters within the smfPerformanceGroup count
packets handled by the system and interface local SMF process (as packets handled by the system and interface local SMF process (as
discussed above). Not all IP (unicast and multicast) packets on a discussed above). Not all IP (unicast and multicast) packets on a
device interface are handled by the SMF process. So the counters are device interface are handled by the SMF process. So the counters are
tracking different packet streams in the IP-MIB and SMF-MIB modules. tracking different packet streams in the IP-MIB and SMF-MIB modules.
6.3. Relationship to the IPMCAST-MIB 6.3. Relationship to the IPMCAST-MIB
The smfCfgAddrForwardingTable is essentially a filter table (if The smfCfgAddrForwardingTable is essentially a filter table (if
populated) that identifies addresses/packets to be forwarded via the populated) that identifies addresses/packets to be forwarded via the
local SMF flooding process. The RFC 5132 IP Multicast MIB module local SMF flooding process. The IP Multicast MIB module in RFC 5132
[RFC5132] manages objects related to standard IP multicast, which [RFC5132] manages objects related to standard IP multicast, which
could be running in parallel to SMF on the device. could be running in parallel to SMF on the device.
RFC 5132 manages traditional IP-based multicast (based upon multicast RFC 5132 manages traditional IP-based multicast (based upon multicast
routing mechanisms). The SMF-MIB module provides management for a routing mechanisms). The SMF-MIB module provides management for a
MANET subnet-based flooding mechanism which, may be used for MANET subnet-based flooding mechanism which, may be used for
multicast transport (through SMF broadcast) depending upon the MANET multicast transport (through SMF broadcast) depending upon the MANET
dynamics and other factors regarding the MANET subnet. Further, they dynamics and other factors regarding the MANET subnet. Further, they
may co-exist in certain MANET deployments using the may coexist in certain MANET deployments using the
smfCfgAddrForwardingTable to hand certain IP multicast addresses to smfCfgAddrForwardingTable to hand certain IP multicast addresses to
the SMF process and other IP multicast packets to be forwarded by the SMF process and other IP multicast packets to be forwarded by
other IP routed-based multicast mechanisms. SMF and the associated other multicast mechanisms that are IP route based. SMF and the
SMF-MIB module are experimental and these are some of the experiments associated SMF-MIB module are experimental and these are some of the
to be had with SMF and the SMF-MIB module. experiments to be had with SMF and the SMF-MIB module.
6.4. MIB modules required for IMPORTS 6.4. MIB Modules Required for IMPORTS
The textual conventions imported for use in the SMF-MIB module are as The objects imported for use in the SMF-MIB module are as follows.
follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32,
Counter32, Unsigned32, Integer32 and mib-2 textual conventions are Integer32, TimeTicks and experimental macros are imported from RFC
imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus, and TruthValue
and TruthValue textual conventions are imported from RFC 2579 macros are imported from RFC 2579 [RFC2579]. The MODULE-COMPLIANCE,
[RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- OBJECT-GROUP, and NOTIFICATION-GROUP macros are imported from RFC
GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 2580 [RFC2580]. The InterfaceIndexOrZero and ifName textual
InterfaceIndexOrZero textual convention is imported from RFC 2863 conventions are imported from RFC 2863 [RFC2863]. The
[RFC2863]. The SnmpAdminString textual convention is imported from SnmpAdminString textual convention is imported from RFC 3411
RFC 3411 [RFC3411]. The InetAddress, InetAddressType and [RFC3411]. The InetAddress, InetAddressType, and
InetAddressPrefixLength textual conventions are imported from RFC InetAddressPrefixLength textual conventions are imported from RFC
4001 [RFC4001]. 4001 [RFC4001].
6.5. Relationship to the Future RSSA-MIB Moduless 6.5. Relationship to Future RSSA-MIB Modules
In a sense, the SMF-MIB module is a general front-end to a set of, In a sense, the SMF-MIB module is a general front-end to a set of
yet to be developed, RSSA-specific MIB modules. These RSSA-specific yet-to-be developed RSSA-specific MIB modules. These RSSA-specific
MIB modules will define the objects for the configuration, state, MIB modules will define the objects for the configuration, state,
performance and notification required for the operation of these performance and notification required for the operation of these
specific RSSAs. The SMF-MIB module Capabilities Group allows the specific RSSAs. The SMF-MIB module Capabilities Group allows the
remote management station the ability to query the router to discover remote management station the ability to query the router to discover
the set of supported RSSAs. the set of supported RSSAs.
7. SMF-MIB Definitions 7. SMF-MIB Definitions
SMF-MIB DEFINITIONS ::= BEGIN SMF-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Integer32, TimeTicks, experimental Counter32, Integer32, TimeTicks, experimental
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, RowStatus, TruthValue TEXTUAL-CONVENTION, RowStatus, TruthValue
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- RFC 2580
InterfaceIndexOrZero, ifName InterfaceIndexOrZero, ifName
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- RFC 2863
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411] FROM SNMP-FRAMEWORK-MIB -- RFC 3411
InetAddress, InetAddressType, InetAddress, InetAddressType,
InetAddressPrefixLength InetAddressPrefixLength
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- RFC 4001
IANAsmfOpModeIdTC
FROM IANA-SMF-MIB
IANAsmfOpModeIdTC,
IANAsmfRssaIdTC IANAsmfRssaIdTC
FROM IANA-SMF-MIB FROM IANA-SMF-MIB
; ;
smfMIB MODULE-IDENTITY smfMIB MODULE-IDENTITY
LAST-UPDATED "201408121300Z" -- August 12, 2014 LAST-UPDATED "201410100000Z" -- October 10, 2014
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG EMail: manet@ietf.org
WG Chairs: sratliff@cisco.com WG Chairs: sratliff@cisco.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Robert G. Cole Editors: Robert G. Cole
US Army CERDEC US Army CERDEC
Space and Terrestrial Communications
6010 Frankford Road 6010 Frankford Road
Aberdeen Proving Ground, MD 21005 Aberdeen Proving Ground, MD 21005
USA USA
+1 443 395-8744 Phone: +1 443 395-8744
robert.g.cole@us.army.mil EMail: robert.g.cole@us.army.mil
Joseph Macker Joseph Macker
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
USA USA
macker@itd.nrl.navy.mil EMail: macker@itd.nrl.navy.mil
Brian Adamson Brian Adamson
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
USA USA
adamson@itd.nrl.navy.mil" EMail: adamson@itd.nrl.navy.mil"
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: the MANET SMF RSSA process defined in:
Macker, J.(ed.), Macker, J., Ed., Simplified Multicast Forwarding, RFC 6621,
Simplified Multicast Forwarding, RFC 6621,
May 2012. May 2012.
Copyright (C) The IETF Trust (2014). This version Copyright (c) 2014 IETF Trust and the persons identified as
of this MIB module is part of RFC xxxx; see the RFC authors of the code. All rights reserved.
itself for full legal notices."
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
-- Revision History -- Revision History
REVISION "201408121300Z" -- August 12, 2014 REVISION "201410100000Z" -- October 10, 2014
DESCRIPTION DESCRIPTION
"The first version of this MIB module, "The first version of this MIB module,
published as RFC xxxx. published as RFC 7367.
" "
-- RFC-Editor assigns xxxx ::= { experimental 126 }
::= { experimental xxxx } -- to be assigned by IANA
-- --
-- TEXTUAL CONVENTIONs -- TEXTUAL CONVENTIONs
-- --
SmfStatus ::= TEXTUAL-CONVENTION SmfStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the operability of a SMF "An indication of the operability of an 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
this interface is performing SMF functions, this interface is performing SMF functions
and 'disabled' indicates that it is not. and 'disabled' indicates that it is not.
Similarly for the status of the device: Similarly, for the status of the device:
'enabled' indicates that the device has 'enabled' indicates that the device has
enabled the SMF functions on the device and enabled the SMF functions on the device and
'disabled' means that the device and all interfaces 'disabled' means that the device and all interfaces
have disabled all SMF functions." have disabled all SMF functions."
SYNTAX INTEGER { SYNTAX INTEGER {
enabled (1), enabled (1),
disabled (2) disabled (2)
} }
-- --
-- Top-Level Object Identifier Assignments -- Top-Level Object Identifier Assignments
-- --
smfMIBNotifications OBJECT IDENTIFIER ::= { smfMIB 0 } smfMIBNotifications OBJECT IDENTIFIER ::= { smfMIB 0 }
smfMIBObjects OBJECT IDENTIFIER ::= { smfMIB 1 } smfMIBObjects OBJECT IDENTIFIER ::= { smfMIB 1 }
smfMIBConformance OBJECT IDENTIFIER ::= { smfMIB 2 } smfMIBConformance OBJECT IDENTIFIER ::= { smfMIB 2 }
-- --
-- smfMIBObjects Assignments: -- smfMIBObjects Assignments:
skipping to change at page 14, line 13 skipping to change at page 13, line 41
smfCapabilitiesTable OBJECT-TYPE smfCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfCapabilitiesEntry SYNTAX SEQUENCE OF SmfCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smfCapabilitiesTable identifies the "The smfCapabilitiesTable identifies the
resident set of SMF Operational Modes and resident set of SMF Operational Modes and
RSSA combinations that can run on this RSSA combinations that can run on this
forwarder." forwarder."
REFERENCE REFERENCE
"See Section 7.2. 'Reduced Relay Set Forwarding', "See Section 7.2 'Reduced Relay Set Forwarding',
Section 8.1.1. 'SMF Message TLV Type', and Section 8.1.1 'SMF Message TLV Type', and
the Appendices A, B and C in the Appendices A, B, and C in
RFC 6621 - Simplified Multicast Forwarding RFC 6621 - 'Simplified Multicast Forwarding',
(SMF), Macker, J., May 2012." Macker, J., May 2012."
::= { smfCapabilitiesGroup 1 } ::= { smfCapabilitiesGroup 1 }
smfCapabilitiesEntry OBJECT-TYPE smfCapabilitiesEntry OBJECT-TYPE
SYNTAX SmfCapabilitiesEntry SYNTAX SmfCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular operational "Information about a particular operational
mode and RSSA combination. mode and RSSA combination.
" "
skipping to change at page 14, line 45 skipping to change at page 14, line 25
} }
smfCapabilitiesIndex OBJECT-TYPE smfCapabilitiesIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this entry; a unique value, "The index for this entry; a unique value,
greater than zero, for each combination of greater than zero, for each combination of
a particular operational mode and RSSA a particular operational mode and RSSA
algorithm available on this device. available on this device.
It is recommended that values are assigned It is recommended that values are assigned
contiguously starting from 1. contiguously starting from 1.
Rows in this table are automatically Rows in this table are automatically
populated by the entity's management system populated by the entity's management system
on initialization. on initialization.
By default, the agent should support at least the By default, the agent should support at least the
Classical Flooding 'cF' algorithm. All compliant Classical Flooding 'cF' algorithm. All compliant
SMF forwarders must support Classical Flooding. SMF forwarders must support Classical Flooding.
skipping to change at page 15, line 40 skipping to change at page 15, line 20
smfCapabilitiesRssaID OBJECT-TYPE smfCapabilitiesRssaID OBJECT-TYPE
SYNTAX IANAsmfRssaIdTC SYNTAX IANAsmfRssaIdTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies "This object identifies
the particular RSSA algorithm in this MIB the particular RSSA algorithm in this MIB
module. Example RSSAs are found in the module. Example RSSAs are found in the
appendix of RFC 6621." appendix of RFC 6621."
REFERENCE REFERENCE
"See, e.g., Section 8.1.1. 'SMF Message TLV Type', "For example, see Section 8.1.1 'SMF Message TLV Type',
and the Appendices A, B and C in and the Appendices A, B, and C in
RFC 6621 - Simplified Multicast Forwarding RFC 6621 - 'Simplified Multicast Forwarding',
(SMF), Macker, J., May 2012." Macker, J., May 2012."
::= { smfCapabilitiesEntry 3 } ::= { smfCapabilitiesEntry 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.
-- --
skipping to change at page 16, line 17 skipping to change at page 15, line 45
smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 }
smfCfgAdminStatus OBJECT-TYPE smfCfgAdminStatus OBJECT-TYPE
SYNTAX SmfStatus 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)' means that the SMF process
is configured off. is configured off.
Prior to SMF functions being performed over Prior to SMF functions being performed over
specific interfaces, this object must first specific interfaces, this object must first
be 'enabled'. If this object is 'disabled', be 'enabled'. If this object is 'disabled',
then no SMF functions are being performed on then no SMF functions are being performed on
the device and all smfCfgIfAdminStatus objects the device and all smfCfgIfAdminStatus objects
MUST also be set to 'disabled'. When this MUST also be set to 'disabled'. When this
object is changed from 'enabled' to 'disabled' object is changed from 'enabled' to 'disabled'
by the manager, then all smfCfgIfAdminStatus by the manager, then all smfCfgIfAdminStatus
objects MUST also be automatically set to objects MUST also be automatically set to
'disabled' by the agent. 'disabled' by the agent.
The default value for this object SHOULD be The default value for this object SHOULD be
'enabled'. 'enabled'.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
DEFVAL { enabled } DEFVAL { enabled }
::= { smfConfigurationGroup 1 } ::= { smfConfigurationGroup 1 }
smfCfgSmfSysUpTime OBJECT-TYPE smfCfgSmfSysUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 17, line 4 skipping to change at page 16, line 32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time (in hundredths of a second) since the "The time (in hundredths of a second) since the
system SMF process was last re-initialized. system SMF process was last re-initialized.
The SMF process is re-initialized when the The SMF process is re-initialized when the
value of the 'smfCfgAdminStatus' object value of the 'smfCfgAdminStatus' object
transitions to 'enabled' from either a prior transitions to 'enabled' from either a prior
value of 'disabled' or upon initialization value of 'disabled' or upon initialization
of this device." of this device."
::= { smfConfigurationGroup 2 } ::= { smfConfigurationGroup 2 }
smfCfgRouterIDAddrType OBJECT-TYPE smfCfgRouterIDAddrType OBJECT-TYPE
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type of the address used for "The address type of the address used for
SMF ID of this router as specified the SMF ID of this router as specified
in the 'smfCfgRouterID' next. in the 'smfCfgRouterID' next.
Only the values ipv4(1) and ipv6(2) Only the values ipv4(1) and ipv6(2)
are supported. are supported.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
DEFVAL { ipv4 } DEFVAL { ipv4 }
::= { smfConfigurationGroup 3 } ::= { smfConfigurationGroup 3 }
smfCfgRouterID OBJECT-TYPE smfCfgRouterID OBJECT-TYPE
SYNTAX InetAddress (SIZE(4|16)) SYNTAX InetAddress (SIZE(4|16))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address used as the SMF router ID. "The IP address used as the SMF router ID.
This can be set by the management station. This can be set by the management station.
If not explicitly set, then the device If not explicitly set, then the device
SHOULD select a routable IP address SHOULD select a routable IP address
assigned to this router for use as assigned to this router for use as
skipping to change at page 17, line 39 skipping to change at page 17, line 18
DESCRIPTION DESCRIPTION
"The IP address used as the SMF router ID. "The IP address used as the SMF router ID.
This can be set by the management station. This can be set by the management station.
If not explicitly set, then the device If not explicitly set, then the device
SHOULD select a routable IP address SHOULD select a routable IP address
assigned to this router for use as assigned to this router for use as
the 'smfCfgRouterID'. the 'smfCfgRouterID'.
The smfCfgRouterID is a logical identification The smfCfgRouterID is a logical identification
that MUST be consistent across interoperable that MUST be consistent across interoperable
SMF neighborhoods and it is RECOMMENDED to be SMF neighborhoods, and it is RECOMMENDED to be
chosen as the numerically largest address chosen as the numerically largest address
contained in a node's 'Neighbor Address List' contained in a node's 'Neighbor Address List'
as defined in NHDP. A smfCfgRouterID MUST be as defined in NHDP. An smfCfgRouterID MUST be
unique within the scope of the operating unique within the scope of the operating
MANET network regardless of the method used MANET network regardless of the method used
for selecting it. for selecting it.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"See, e.g., "For example, see
Appendix Section A.1. 'E-CDS Relay Set
Selection Overview' and
Appendix Secdtion C.1. 'MPR-CDS Relay Appendix A.1 'E-CDS Relay Set Selection Overview'
Set Selection Overview'
in RFC 6621 - Simplified Multicast Forwarding and
(SMF), Macker, J., May 2012."
Appendix C.1 'MPR-CDS Relay Set Selection
Overview' in
RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012."
::= { smfConfigurationGroup 4 } ::= { smfConfigurationGroup 4 }
smfCfgOperationalMode OBJECT-TYPE smfCfgOperationalMode OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF RSS node operational mode and "The SMF RSS node operational mode and
RSSA algorithm combination active on this RSSA combination active on this
local forwarder. This object is defined local forwarder. This object is defined
to be equal to the smfCapabilitiesIndex to be equal to the smfCapabilitiesIndex,
which identifies the specific active which identifies the specific active
operational mode and RSSA. operational mode and RSSA.
The default value for this object is The default value for this object is
'1' which corresponds to: '1', which corresponds to:
smfCapabilitiesOpModeID i 'cfOnly(1)' smfCapabilitiesOpModeID i 'cfOnly(1)'
smfCapabilitiesRssaID i 'cF(1)' smfCapabilitiesRssaID i 'cF(1)'
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"See Section 7.2. 'Reduced Relay Set Forwarding', "See Section 7.2 'Reduced Relay Set Forwarding',
and the Appendices A, B and C in and the Appendices A, B, and C in
RFC 6621 - Simplified Multicast Forwarding RFC 6621 - 'Simplified Multicast Forwarding',
(SMF), Macker, J., May 2012." Macker, J., Ed., May 2012."
DEFVAL { 1 } DEFVAL { 1 }
::= { smfConfigurationGroup 5 } ::= { smfConfigurationGroup 5 }
smfCfgRssaMember OBJECT-TYPE smfCfgRssaMember 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
skipping to change at page 19, line 15 skipping to change at page 18, line 44
multicast forwarding. Sometimes it is useful multicast forwarding. Sometimes it is useful
to force an agent to be included or excluded to force an agent to be included or excluded
from the resulting RSS. This object is a from the resulting RSS. This object is a
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(2)' forces the selected The value 'always(2)' forces the selected
RSSA include this agent in the RSS. RSSA to 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.
The default setting for this object is The default setting for this object is
'potential(1)'. Other settings could pose 'potential(1)'. Other settings could pose
operational risks under certain conditions. operational risks under certain conditions.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"See Section 7. 'Relay Set Selection' in "See Section 7 'Relay Set Selection' in
RFC 6621 - Simplified Multicast Forwarding RFC 6621 - 'Simplified Multicast Forwarding',
(SMF), Macker, J., May 2012." Macker, J., Ed., May 2012."
DEFVAL { potential } DEFVAL { potential }
::= { smfConfigurationGroup 6 } ::= { smfConfigurationGroup 6 }
smfCfgIpv4Dpd OBJECT-TYPE smfCfgIpv4Dpd OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
hashBased(1), hashBased(1),
identificationBased(2) identificationBased(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 'hashBased(1)' indicates that the The value 'hashBased(1)' indicates that the
routers duplicate packet detection is based router's duplicate packet detection is based
upon comparing a hash over the packet fields. upon comparing a hash over the packet fields.
This is the default setting for this object. This is the default setting for this object.
The value 'identificationBased(2)' The value 'identificationBased(2)'
indicates that the duplicate packet indicates that the duplicate packet
detection relies upon header information detection relies upon header information
in the multicast packets to identify in the multicast packets to identify
previously received packets. previously received packets.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"See Section 6.2. 'IPv4 Duplicate Packet "See Section 6.2 'IPv4 Duplicate Packet
Detection' in RFC 6621 - Simplified Detection' in
Multicast Forwarding (SMF), Macker, J., RFC 6621 - 'Simplified Multicast Forwarding',
May 2012." Macker, J., Ed., May 2012."
DEFVAL { hashBased } DEFVAL { hashBased }
::= { smfConfigurationGroup 7 } ::= { smfConfigurationGroup 7 }
smfCfgIpv6Dpd OBJECT-TYPE smfCfgIpv6Dpd OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
hashBased(1), hashBased(1),
identificationBased(2) identificationBased(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 values indicate the type of method used The values indicate the type of method used
for duplicate packet detection as described for duplicate packet detection as described
the previous description for the object the previous description for the object
`smfCfgIpv4Dpd'. 'smfCfgIpv4Dpd'.
The default value for this object is The default value for this object is
'hashBased(1)'. 'hashBased(1)'.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"See Section 6.1. 'IPv6 Duplicate Packet "See Section 6.1 'IPv6 Duplicate Packet
Detection' in RFC 6621 - Simplified Detection' in
Multicast Forwarding (SMF), Macker, J., RFC 6621 - 'Simplified Multicast Forwarding',
May 2012." Macker, J., Ed., May 2012."
DEFVAL { hashBased } DEFVAL { hashBased }
::= { smfConfigurationGroup 8 } ::= { smfConfigurationGroup 8 }
smfCfgMaxPktLifetime OBJECT-TYPE smfCfgMaxPktLifetime 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 This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"See Section 6. 'SMF Duplicate Packet "See Section 6 'SMF Duplicate Packet
Detection' in RFC 6621 - Simplified Detection' in
Multicast Forwarding (SMF), Macker, J., RFC 6621 - 'Simplified Multicast Forwarding',
May 2012." Macker, J., Ed., May 2012."
DEFVAL { 60 } DEFVAL { 60 }
::= { smfConfigurationGroup 9 } ::= { smfConfigurationGroup 9 }
smfCfgDpdEntryMaxLifetime OBJECT-TYPE smfCfgDpdEntryMaxLifetime 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.
If the memory is running low prior to the If the memory is running low prior to the
MaxLifetime being exceeded, the local SMF MaxLifetime being exceeded, the local SMF
devices should purge the oldest records first. devices should purge the oldest records first.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"See Section 6. 'SMF Duplicate Packet "See Section 6 'SMF Duplicate Packet
Detection' in RFC 6621 - Simplified Detection' in
Multicast Forwarding (SMF), Macker, J., RFC 6621 - 'Simplified Multicast Forwarding',
May 2012." Macker, J., Ed., May 2012."
DEFVAL { 600 } DEFVAL { 600 }
::= { smfConfigurationGroup 10 } ::= { smfConfigurationGroup 10 }
-- --
-- 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.
-- --
smfCfgNhdpRssaMesgTLVIncluded OBJECT-TYPE smfCfgNhdpRssaMesgTLVIncluded 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 or not the associated NHDP
include the RSSA Message TLV, or not. This messages include the RSSA Message TLV. 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.
It is RECOMMENDED that the RSSA Message TLV It is RECOMMENDED that the RSSA Message TLV
be included in the NHDP messages. be included in the NHDP messages.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"See Section 8.1.1. 'SMF Message TLV Type' in "See Section 8.1.1 'SMF Message TLV Type' in
RFC 6621 - Simplified Multicast Forwarding RFC 6621 - 'Simplified Multicast Forwarding',
(SMF), Macker, J., May 2012." Macker, J., Ed., May 2012."
DEFVAL { true } DEFVAL { true }
::= { smfConfigurationGroup 11 } ::= { smfConfigurationGroup 11 }
smfCfgNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE smfCfgNhdpRssaAddrBlockTLVIncluded 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 or not the associated NHDP
include the RSSA Address Block TLV, or not. messages include the RSSA Address Block TLV.
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.
The smfCfgNhdpRssaAddrBlockTLVIncluded is optional The smfCfgNhdpRssaAddrBlockTLVIncluded is optional
in all cases as it depends on the existence of in all cases as it depends on the existence of
an address block which may not be present. an address block that may not be present.
If this SMF device is configured with NHDP, If this SMF device is configured with NHDP,
then this object SHOULD be set to 'true(1)'. then this object SHOULD be set to 'true(1)'.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"See Section 8.1.2. 'SMF Address Block TLV "See Section 8.1.2 'SMF Address Block TLV
Type' in RFC 6621 - Simplified Multicast Type' in
Forwarding (SMF), Macker, J., May 2012." RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012."
DEFVAL { true } DEFVAL { true }
::= { smfConfigurationGroup 12 } ::= { smfConfigurationGroup 12 }
-- --
-- Table identifying configured multicast addresses to be forwarded. -- Table identifying configured multicast addresses to be forwarded.
-- --
smfCfgAddrForwardingTable OBJECT-TYPE smfCfgAddrForwardingTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfCfgAddrForwardingEntry SYNTAX SEQUENCE OF SmfCfgAddrForwardingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smfCfgAddrForwardingTable is essentially a filter "The smfCfgAddrForwardingTable is essentially a filter
table (if populated) that identifies addresses/packets table (if populated) that identifies addresses/packets
to be forwarded viaathe local SMF flooding process. to be forwarded via the local SMF flooding process.
The RFC 5132 IP Multicast MIB module manages objects The IP Multicast MIB module in RFC 5132 manages objects
related to standard IP multicast, which could be running related to standard IP multicast, which could be running
in parallel to SMF on the device. in parallel to SMF on the device.
RFC 5132 manages traditional IP-based multicast (based RFC 5132 manages traditional IP-based multicast (based
upon multicast routing mechanisms). The SMF-MIB module upon multicast routing mechanisms). The SMF-MIB module
provides management for a MANET subnet-based flooding provides management for a MANET subnet-based flooding
mechanism which, may be used for multicast transport mechanism that may be used for multicast transport
(through SMF broadcast) depending upon the MANET dynamics (through SMF broadcast) depending upon the MANET dynamics
and other factors regarding the MANET subnet. Further, and other factors regarding the MANET subnet. Further,
they may co-exist in certain MANET deployments they may coexist in certain MANET deployments
using the smfCfgAddrForwardingTable to hand certain IP using the smfCfgAddrForwardingTable to hand certain IP
multicast addresses to the SMF process and other IP multicast addresses to the SMF process and other IP
multicast packets to be forwarded by other IP multicast packets to be forwarded by other
routed-based multicast mechanisms. SMF and the multicast mechanisms that are IP route based. SMF and
associated SMF-MIB module are experimental and these the associated SMF-MIB module are experimental and these
are some of the experiments to be had with SMF and are some of the experiments to be had with SMF and
the SMF-MIB module. the SMF-MIB module.
This is the (conceptual) table containing information on This is the (conceptual) table containing information on
multicast addresses which are to be forwarded by the SMF multicast addresses that are to be forwarded by the SMF
process. This table represents an IP filters table for process. This table represents an IP filters table for
forwarding (or not) packets based upon their IP forwarding (or not) packets based upon their IP
multicast address. multicast address.
The SMF process can be configured to forward only those The SMF process can be configured to forward only those
multicast addresses found within the multicast addresses found within the
smfCfgAddrForwardingTable. As such, addresses which are smfCfgAddrForwardingTable. As such, addresses that are
to be forwarded by the SMF process MUST be found within to be forwarded by the SMF process MUST be found within
the address ranges configured within this table, unless the address ranges configured within this table, unless
this table is empty. this table is empty.
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.
Different rows MAY share a common Different rows MAY share a common
smfCfgAddrForwardingGroupName to administratively smfCfgAddrForwardingGroupName to administratively
associate different rows. associate different rows.
The objects in this table are persistent and when written The objects in this table are persistent and, when written,
the entity SHOULD save the change to non-volatile storage." the entity SHOULD save the change to non-volatile storage."
REFERENCE REFERENCE
"See Section 9.1. 'Forwarded Multicast Groups' in "See Section 9.1 'Forwarded Multicast Groups' in
RFC 6621 - Simplified Multicast Forwarding RFC 6621 - 'Simplified Multicast Forwarding',
(SMF), Macker, J., May 2012." Macker, J., Ed., May 2012."
::= { smfConfigurationGroup 13 } ::= { smfConfigurationGroup 13 }
smfCfgAddrForwardingEntry OBJECT-TYPE smfCfgAddrForwardingEntry OBJECT-TYPE
SYNTAX SmfCfgAddrForwardingEntry SYNTAX SmfCfgAddrForwardingEntry
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."
INDEX { smfCfgAddrForwardingIndex } INDEX { smfCfgAddrForwardingIndex }
skipping to change at page 24, line 46 skipping to change at page 24, line 23
smfCfgAddrForwardingAddrPrefixLength smfCfgAddrForwardingAddrPrefixLength
InetAddressPrefixLength, InetAddressPrefixLength,
smfCfgAddrForwardingStatus RowStatus smfCfgAddrForwardingStatus RowStatus
} }
smfCfgAddrForwardingIndex OBJECT-TYPE smfCfgAddrForwardingIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies an unique entry "This object identifies a unique entry
for a forwarding group. The index for for a forwarding group. The index for
this entry is a unique value, this entry is a unique value,
greater than zero, for each row. greater than zero, for each row.
It is recommended that values are assigned It is recommended that values are assigned
contiguously starting from 1. contiguously starting from 1.
The value for each row index MUST remain The value for each row index MUST remain
constant from one re-initialization constant from one re-initialization
of the entity's management system to the of the entity's management system to the
next re-initialization." next re-initialization."
skipping to change at page 25, line 24 skipping to change at page 24, line 49
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies a group name for a set of "This object identifies a group name for a set of
row entries in order to administratively associate row entries in order to administratively associate
a set of address ranges. a set of address ranges.
If there is no group name or this object is If there is no group name or this object is
otherwise not applicable, then this object contains otherwise not applicable, then this object contains
a zero-length string. a zero-length string.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
::= { smfCfgAddrForwardingEntry 2 } ::= { smfCfgAddrForwardingEntry 2 }
smfCfgAddrForwardingAddrType OBJECT-TYPE smfCfgAddrForwardingAddrType OBJECT-TYPE
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the addresses in the multicast "The type of the addresses in the multicast
forwarding ranges identified by this table. forwarding ranges identified by this table.
skipping to change at page 25, line 40 skipping to change at page 25, line 18
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the addresses in the multicast "The type of the addresses in the multicast
forwarding ranges identified by this table. forwarding ranges identified by this table.
Only the values ipv4(1) and ipv6(2) are Only the values ipv4(1) and ipv6(2) are
supported. supported.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
::= { smfCfgAddrForwardingEntry 3 } ::= { smfCfgAddrForwardingEntry 3 }
smfCfgAddrForwardingAddress OBJECT-TYPE smfCfgAddrForwardingAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE(4|16)) SYNTAX InetAddress (SIZE(4|16))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast group address which, when "The multicast group address that, when
combined with smfCfgAddrForwardingAddrPrefixLength, combined with smfCfgAddrForwardingAddrPrefixLength,
gives the group prefix for this forwarding range. gives the group prefix for this forwarding range.
The InetAddressType is given by The InetAddressType is given by
smfCfgAddrForwardingAddrType. smfCfgAddrForwardingAddrType.
This address object is only significant up to This address object is only significant up to
smfCfgAddrForwardingAddrPrefixLength bits. The smfCfgAddrForwardingAddrPrefixLength bits. The
remaining address bits are set to zero. This is remaining address bits are set to zero. This is
especially important for this index field, especially important for this index field.
Any non-zero bits would signify an entirely Any non-zero bits would signify an entirely
different entry. different entry.
Legal values correspond to the subset of address Legal values correspond to the subset of address
families for which multicast address allocation families for which multicast address allocation
is supported. is supported.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
::= { smfCfgAddrForwardingEntry 4 } ::= { smfCfgAddrForwardingEntry 4 }
smfCfgAddrForwardingAddrPrefixLength OBJECT-TYPE smfCfgAddrForwardingAddrPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, when "The length in bits of the mask that, when
combined with smfCfgAddrForwardingAddress, combined with smfCfgAddrForwardingAddress,
gives the group prefix for this forwarding gives the group prefix for this forwarding
range. range.
This object is persistent and when written This object is persistent and, when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
::= { smfCfgAddrForwardingEntry 5 } ::= { smfCfgAddrForwardingEntry 5 }
smfCfgAddrForwardingStatus OBJECT-TYPE smfCfgAddrForwardingStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which new entries may be "The status of this row, by which new entries may be
skipping to change at page 27, line 4 skipping to change at page 26, line 28
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which new entries may be "The status of this row, by which new entries may be
created, or old entries deleted from this table." created, or old entries deleted from this table."
::= { smfCfgAddrForwardingEntry 6 } ::= { smfCfgAddrForwardingEntry 6 }
-- --
-- SMF Interfaces Configuration Table -- SMF Interfaces Configuration Table
-- --
smfCfgInterfaceTable OBJECT-TYPE smfCfgInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfCfgInterfaceEntry SYNTAX SEQUENCE OF SmfCfgInterfaceEntry
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 module (RFC 2863). As such, Interfaces Group MIB module (RFC 2863). As such,
this table 'sparse augments' the ifTable this table 'sparse augments' the ifTable
specifically when SMF is to be configured to specifically when SMF is to be configured to
operate over this interface. operate over this interface.
A conceptual row in this table exists if and only A conceptual row in this table exists if and only
if either a manager has explicitly created the row if either a manager has explicitly created the row
or there is an interface on the managed device or there is an interface on the managed device
that automatically supports and runs SMF as part that automatically supports and runs SMF as part
of the device's initialization process. of the device's initialization process.
The manager creates a row in this table by setting The manager creates a row in this table by setting
rowStatus to 'createAndGo' or 'createAndWait'. the rowStatus to 'createAndGo' or 'createAndWait'.
Row objects having associated DEFVAL clauses are Row objects having associated DEFVAL clauses are
automatically defined by the agent with these automatically defined by the agent with these
values during row creation, unless the manager values during row creation, unless the manager
explicitly defines these object values during the explicitly defines these object values during the
row creation. row creation.
As the smfCfgInterfaceTable sparsely augments the As the smfCfgInterfaceTable sparsely augments the
IfTable. Hence, IfTable. Hence,
+ an entry cannot exist in smfCfgInterfaceTable + an entry cannot exist in smfCfgInterfaceTable
skipping to change at page 27, line 50 skipping to change at page 27, line 27
smfCfgInterfaceTable MUST be removed. smfCfgInterfaceTable MUST be removed.
+ the smfCfgIfStatus can have a value of + the smfCfgIfStatus can have a value of
'enabled' or 'disabled' independent of the 'enabled' or 'disabled' independent of the
current value of the ifAdminStatus of the current value of the ifAdminStatus of the
corresponding entry in the ifTable. corresponding entry in the ifTable.
The values of the objects smfCfgAdminStatus and The values of the objects smfCfgAdminStatus and
smfCfgIfAdminStatus reflect the up-down status of smfCfgIfAdminStatus reflect the up-down status of
the SMF process running on the device and on the the SMF process running on the device and on the
specific interfaces respectively. Hence, specific interfaces, respectively. Hence,
+ the value of the smfCfgAdminStatus can be + the value of the smfCfgAdminStatus can be
'enabled' or 'disabled' reflecting the current 'enabled' or 'disabled' reflecting the current
running status of the SMF process on the device. running status of the SMF process on the device.
+ the value of the smfCfgIfAdminStatus can be + the value of the smfCfgIfAdminStatus can be
'enabled' or 'disabled' if the value of the 'enabled' or 'disabled' if the value of the
smfCfgAdminStatus is set to 'enabled'. smfCfgAdminStatus is set to 'enabled'.
+ if the value of the smfCfgAdminStatus is + if the value of the smfCfgAdminStatus is
'disabled', then the corresponding 'disabled', then the corresponding
smfCfgIfAdminStatus objects MUST be set smfCfgIfAdminStatus objects MUST be set
to 'disabled' in the smfCfgInterfaceTable. to 'disabled' in the smfCfgInterfaceTable.
+ once the value of the smfCfgAdminStatus changes + once the value of the smfCfgAdminStatus changes
from 'disabled' to 'enabled', it is up to the from 'disabled' to 'enabled', it is up to the
management system to make the corresponding management system to make the corresponding
changes to the smfCfgIfAdminStatus values changes to the smfCfgIfAdminStatus values
back to 'enabled'. back to 'enabled'.
" "
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 }
smfCfgInterfaceEntry OBJECT-TYPE smfCfgInterfaceEntry OBJECT-TYPE
SYNTAX SmfCfgInterfaceEntry SYNTAX SmfCfgInterfaceEntry
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.
The objects in this table are persistent and when The objects in this table are persistent and, when
written the device SHOULD save the change to written, the device SHOULD save the change to
non-volatile storage. For further information non-volatile storage. For further information
on the storage behavior for these objects, refer on the storage behavior for these objects, refer
to the description for the smfCfgIfRowStatus to the description for the smfCfgIfRowStatus
object." object."
INDEX { smfCfgIfIndex } INDEX { smfCfgIfIndex }
::= { smfCfgInterfaceTable 1 } ::= { smfCfgInterfaceTable 1 }
SmfCfgInterfaceEntry ::= SmfCfgInterfaceEntry ::=
SEQUENCE { SEQUENCE {
smfCfgIfIndex InterfaceIndexOrZero, smfCfgIfIndex InterfaceIndexOrZero,
smfCfgIfAdminStatus SmfStatus, smfCfgIfAdminStatus SmfStatus,
smfCfgIfSmfUpTime TimeTicks, smfCfgIfSmfUpTime TimeTicks,
smfCfgIfRowStatus RowStatus smfCfgIfRowStatus RowStatus
} }
smfCfgIfIndex OBJECT-TYPE smfCfgIfIndex 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. This value "The ifIndex for this SMF interface. This value
MUST correspond to an ifIndex referring MUST correspond to an ifIndex referring
to a valid entry in The Interfaces Table. to a valid entry in the Interfaces Table.
If the manager attempts to create a row If the manager attempts to create a row
for which the ifIndex does not exist on the for which the ifIndex does not exist on the
local device, then the agent SHOULD issue local device, then the agent SHOULD issue
a return value of 'inconsistentValue' and a return value of 'inconsistentValue' and
the operation SHOULD fail." the operation SHOULD fail."
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."
::= { smfCfgInterfaceEntry 1 } ::= { smfCfgInterfaceEntry 1 }
smfCfgIfAdminStatus OBJECT-TYPE smfCfgIfAdminStatus OBJECT-TYPE
SYNTAX SmfStatus 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
currently external to the SMF forwarding process. currently external to the SMF forwarding process.
When the value of the smfCfgAdminStatus is When the value of the smfCfgAdminStatus is
'disabled', then the corresponding smfCfgIfAdminStatus 'disabled', then the corresponding smfCfgIfAdminStatus
objects MUST be set to 'disabled' in the objects MUST be set to 'disabled' in the
smfCfgInterfaceTable. smfCfgInterfaceTable.
The default value for this object is 'enabled(1)'. If this object is not equal to 'enabled', all associated
entries in the 'smfPerfIpv4InterfacePerfTable' and the
'smfPerfIpv6InterfacePerfTable' MUST be deleted.
The default value for this object is 'enabled(1)'.
This object SHOULD be persistent and when This object SHOULD be persistent and when
written the device SHOULD save the change to written the device SHOULD save the change to
non-volatile storage." non-volatile storage."
DEFVAL { enabled } DEFVAL { enabled }
::= { smfCfgInterfaceEntry 2 } ::= { smfCfgInterfaceEntry 2 }
smfCfgIfSmfUpTime OBJECT-TYPE smfCfgIfSmfUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time (in hundredths of a second) since "The time (in hundredths of a second) since
this interface SMF process was last this interface SMF process was last
re-initialized. The interface SMF process re-initialized. The interface SMF process is
is re-initialized when the corresponding re-initialized when the value of the
'smfCfgIfRowStatus' object transits to 'smfCfgIfAdminStatus' object transitions to 'enabled'
the 'active' state." from either a prior value of 'disabled' or upon
initialization of this interface or this device."
::= { smfCfgInterfaceEntry 3 } ::= { smfCfgInterfaceEntry 3 }
smfCfgIfRowStatus OBJECT-TYPE smfCfgIfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object permits management of this table "This object permits management of this table
by facilitating actions such as row creation, by facilitating actions such as row creation,
construction, and destruction. The value of construction, and destruction. The value of
this object has no effect on whether other this object has no effect on whether other
objects in this conceptual row can be objects in this conceptual row can be
modified. modified.
An entry may not exist in the 'active' state unless all An entry may not exist in the 'active' state unless all
objects in the entry have a defined appropriate value. For objects in the entry have a defined appropriate value. For
objects with DEFVAL clauses, the management station objects with DEFVAL clauses, the management station
does not need to specify the value of these objects in order does not need to specify the value of these objects in order
for the row to transit to the 'active' state; the default for the row to transit to the 'active' state; the default
value for these objects is used. For objects that do not value for these objects is used. For objects that do not
have DEFVAL clauses, then the network manager MUST have DEFVAL clauses, the network manager MUST
specify the value of these objects prior to this row specify the value of these objects prior to this row
transitioning to the 'active' state. transitioning to the 'active' state.
When this object transitions to 'active', all objects When this object transitions to 'active', all objects
in this row SHOULD be written to non-volatile (stable) in this row SHOULD be written to non-volatile (stable)
storage. Read-create objects in this row MAY be modified. storage. Read-create objects in this row MAY be modified.
When an object in a row with smfCfgIfRowStatus of 'active' When an object in a row with smfCfgIfRowStatus of 'active'
is changed, then the updated value MUST be reflected in SMF is changed, then the updated value MUST be reflected in SMF
and this new object value MUST be written to non-volatile and this new object value MUST be written to non-volatile
storage. storage."
If this object is not equal to 'active', all associated
entries in the smfPerfIpv4InterfacePerfTable and the
smfPerfIpv6InterfacePerfTable MUST be deleted."
::= { smfCfgInterfaceEntry 4 } ::= { smfCfgInterfaceEntry 4 }
-- --
-- smfStateGroup -- smfStateGroup
-- --
-- Contains information describing the current state of the SMF -- Contains information describing the current state of the SMF
-- process such as the current inclusion in the RS or not. -- process such as the current inclusion in the RS or not.
-- --
smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 }
smfStateNodeRsStatusIncluded OBJECT-TYPE smfStateNodeRsStatusIncluded OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current status of the SMF node in the context of "The current status of the SMF node in the context of
skipping to change at page 31, line 15 skipping to change at page 30, line 39
-- --
smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 }
smfStateNodeRsStatusIncluded OBJECT-TYPE smfStateNodeRsStatusIncluded OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current status of the SMF node in the context of "The current status of the SMF node in the context of
the MANETs relay set. A value of 'true(1)' indicates the MANETs relay set. A value of 'true(1)' indicates
that the node is currently part of the MANET Relay that the node is currently part of the MANET Relay
Set. A value of 'false(2)' indicates that the node Set. A value of 'false(2)' indicates that the node
is currently not part of the MANET Relay Set." is currently not part of the MANET Relay Set."
REFERENCE REFERENCE
"See Section 7. 'Relay Set Selection' in "See Section 7 'Relay Set Selection' in
RFC 6621 - Simplified Multicast Forwarding RFC 6621 - 'Simplified Multicast Forwarding',
(SMF), Macker, J., May 2012." Macker, J., Ed., May 2012."
::= { smfStateGroup 1 } ::= { smfStateGroup 1 }
smfStateDpdMemoryOverflow OBJECT-TYPE smfStateDpdMemoryOverflow OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "DPD Records" UNITS "DPD Records"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DPD records that had to be flushed to "The number of DPD records that had to be flushed to
prevent memory overruns for caching of these records. prevent memory overruns for caching of these records.
The number of records to be flushed upon a buffer The number of records to be flushed upon a buffer
overflow is an implementation specific decision. overflow is an implementation specific decision.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
REFERENCE REFERENCE
"See Section 6. 'SMF Duplicate Packet "See Section 6 'SMF Duplicate Packet
Detection' in RFC 6621 - Simplified Detection' in
Multicast Forwarding (SMF), Macker, J., RFC 6621 - 'Simplified Multicast Forwarding',
May 2012." Macker, J., Ed., May 2012."
::= { smfStateGroup 2 } ::= { smfStateGroup 2 }
-- --
-- SMF Neighbor Table -- SMF Neighbor Table
-- --
smfStateNeighborTable OBJECT-TYPE smfStateNeighborTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfStateNeighborEntry SYNTAX SEQUENCE OF SmfStateNeighborEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF StateNeighborTable describes the "The SMF StateNeighborTable describes the
current one-hop neighbor nodes, their address current one-hop 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
"See Section 7. 'SMF Neighborhood Discovery' and "See Section 8 'SMF Neighborhood Discovery' and
Section 8.1. 'SMF Relay Algorithm TLV Section 8.1. 'SMF Relay Algorithm TLV
Types' in RFC 6621 - Simplified Multicast Types' in
Forwarding (SMF), Macker, J., May 2012." RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012."
::= { smfStateGroup 3 } ::= { smfStateGroup 3 }
smfStateNeighborEntry OBJECT-TYPE smfStateNeighborEntry OBJECT-TYPE
SYNTAX SmfStateNeighborEntry SYNTAX SmfStateNeighborEntry
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
set of one-hop neighbors, the interface set of one-hop neighbors, the interface
they are reachable on and the SMF RSSA they are reachable on, and the SMF RSSA
they are currently running." they are currently running."
INDEX { smfStateNeighborIpAddrType, INDEX { smfStateNeighborIpAddrType,
smfStateNeighborIpAddr, smfStateNeighborIpAddr,
smfStateNeighborPrefixLen } smfStateNeighborPrefixLen }
::= { smfStateNeighborTable 1 } ::= { smfStateNeighborTable 1 }
SmfStateNeighborEntry ::= SmfStateNeighborEntry ::=
SEQUENCE { SEQUENCE {
smfStateNeighborIpAddrType InetAddressType, smfStateNeighborIpAddrType InetAddressType,
smfStateNeighborIpAddr InetAddress, smfStateNeighborIpAddr InetAddress,
skipping to change at page 33, line 25 skipping to change at page 32, line 49
Only IPv4 and IPv6 addresses Only IPv4 and IPv6 addresses
are supported." are supported."
::= { smfStateNeighborEntry 2 } ::= { smfStateNeighborEntry 2 }
smfStateNeighborPrefixLen OBJECT-TYPE smfStateNeighborPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
UNITS "bits" UNITS "bits"
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The prefix length. This is a decimal value that "The prefix length. This is a decimal value that
indicates the number of contiguous, higher-order indicates the number of contiguous, higher-order
bits of the address that make up the network bits of the address that make up the network
portion of the address." portion of the address."
::= { smfStateNeighborEntry 3 } ::= { smfStateNeighborEntry 3 }
smfStateNeighborRSSA OBJECT-TYPE smfStateNeighborRSSA OBJECT-TYPE
SYNTAX IANAsmfRssaIdTC SYNTAX IANAsmfRssaIdTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 33, line 51 skipping to change at page 33, line 27
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface ifIndex over which the "The interface ifIndex over which the
neighbor is reachable in one-hop." neighbor is reachable in one-hop."
::= { smfStateNeighborEntry 6 } ::= { smfStateNeighborEntry 6 }
-- --
-- SMF Performance Group -- SMF Performance Group
-- --
-- Contains objects which help to characterize the -- Contains objects that help to characterize the
-- performance of the SMF RSSA process, such as statistics -- performance of the SMF RSSA process, such as statistics
-- counters. There are two types of SMF RSSA statistics: -- counters. There are two types of SMF RSSA statistics:
-- global counters and per interface counters. -- global counters and per-interface counters.
-- --
-- It is an expectation that SMF devices will -- It is an expectation that SMF devices will
-- implement the standard IP-MIB module RFC4293. -- implement the standard IP-MIB module in RFC 4293.
-- Exactly how to integrate SMF packet handling and -- Exactly how to integrate SMF packet handling and
-- management into the standard IP-MIB module management -- management into the standard IP-MIB module management
-- are part of the experiment. -- is part of the experiment.
-- --
-- The SMF-MIB module counters within the -- The SMF-MIB module counters within the
-- smfPerformanceGroup count packets handled by the -- smfPerformanceGroup count packets handled by the
-- system and interface local SMF process (as discussed -- system and interface local SMF process (as discussed
-- above). Not all IP (unicast and multicast) packets -- above). Not all IP (unicast and multicast) packets
-- on a device interface are handled by the SMF process. -- on a device interface are handled by the SMF process.
-- So the counters are tracking different packet streams -- So the counters are tracking different packet streams
-- in the IP-MIB and SMF-MIB modules. -- in the IP-MIB and SMF-MIB modules.
-- --
skipping to change at page 34, line 42 skipping to change at page 34, line 18
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of "A counter of the total number of
multicast IPv4 packets received by the multicast IPv4 packets received by the
device and delivered to the SMF process. device and delivered to the SMF process.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
::= { smfPerfGobalGroup 1 } ::= { smfPerfGobalGroup 1 }
smfPerfIpv4MultiPktsForwardedTotal OBJECT-TYPE smfPerfIpv4MultiPktsForwardedTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of "A counter of the total number of
multicast IPv4 packets forwarded by the multicast IPv4 packets forwarded by the
device. device.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
::= { smfPerfGobalGroup 2 } ::= { smfPerfGobalGroup 2 }
smfPerfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE smfPerfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of duplicate "A counter of the total number of duplicate
multicast IPv4 packets detected by the multicast IPv4 packets detected by the
device. device.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
REFERENCE REFERENCE
"See Section 6.2. 'IPv4 Duplicate Packet "See Section 6.2 'IPv4 Duplicate Packet
Detection' in RFC 6621 - Simplified Multicast Detection' in
Forwarding (SMF), Macker, J., May 2012." RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012."
::= { smfPerfGobalGroup 3 } ::= { smfPerfGobalGroup 3 }
smfPerfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE smfPerfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of dropped "A counter of the total number of dropped
multicast IPv4 packets by the multicast IPv4 packets by the
device due to TTL exceeded. device due to Time to Live (TTL) exceeded.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
REFERENCE REFERENCE
"See Section 5. 'SMF Packet Processing and "See Section 5 'SMF Packet Processing and
Forwarding' in RFC 6621 - Simplified Forwarding' in
Multicast Forwarding (SMF), Macker, J., RFC 6621 - 'Simplified Multicast Forwarding',
May 2012." Macker, J., Ed., May 2012."
::= { smfPerfGobalGroup 4 } ::= { smfPerfGobalGroup 4 }
smfPerfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE smfPerfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv4 packets "A counter of the total number of IPv4 packets
recieved which have a TTL larger than that received that have a TTL larger than that
of a previously received identical packet. of a previously received identical packet.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
REFERENCE REFERENCE
"See Section 5. 'SMF Packet Processing and "See Section 5 'SMF Packet Processing and
Forwarding' in RFC 6621 - Simplified Multicast Forwarding' in
Forwarding (SMF), Macker, J., May 2012." RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012."
::= { smfPerfGobalGroup 5 } ::= { smfPerfGobalGroup 5 }
-- --
-- IPv6 packet counters -- IPv6 packet counters
-- --
smfPerfIpv6MultiPktsRecvTotal OBJECT-TYPE smfPerfIpv6MultiPktsRecvTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of "A counter of the total number of
multicast IPv6 packets received by the multicast IPv6 packets received by the
device and delivered to the SMF process. device and delivered to the SMF process.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
::= { smfPerfGobalGroup 6 } ::= { smfPerfGobalGroup 6 }
smfPerfIpv6MultiPktsForwardedTotal OBJECT-TYPE smfPerfIpv6MultiPktsForwardedTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of "A counter of the total number of
multicast IPv6 packets forwarded by the multicast IPv6 packets forwarded by the
device. device.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
::= { smfPerfGobalGroup 7 } ::= { smfPerfGobalGroup 7 }
smfPerfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE smfPerfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of duplicate "A counter of the total number of duplicate
multicast IPv6 packets detected by the multicast IPv6 packets detected by the
device. device.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
REFERENCE REFERENCE
"See Section 6.1. 'IPv6 Duplicate Packet "See Section 6.1 'IPv6 Duplicate Packet
Detection' in RFC 6621 - Simplified Multicast Detection' in
Forwarding (SMF), Macker, J., May 2012." RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012."
::= { smfPerfGobalGroup 8 } ::= { smfPerfGobalGroup 8 }
smfPerfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE smfPerfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of dropped "A counter of the total number of dropped
multicast IPv6 packets by the multicast IPv6 packets by the
device due to TTL exceeded. device due to TTL exceeded.
skipping to change at page 38, line 15 skipping to change at page 37, line 41
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of dropped "A counter of the total number of dropped
multicast IPv6 packets by the multicast IPv6 packets by the
device due to TTL exceeded. device due to TTL exceeded.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
REFERENCE REFERENCE
"See Section 5. 'SMF Packet Processing and "See Section 5 'SMF Packet Processing and
Forwarding' in RFC 6621 - Simplified Forwarding' in
Multicast Forwarding (SMF), Macker, J., RFC 6621 - 'Simplified Multicast Forwarding',
May 2012." Macker, J., Ed., May 2012."
::= { smfPerfGobalGroup 9 } ::= { smfPerfGobalGroup 9 }
smfPerfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE smfPerfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv6 packets "A counter of the total number of IPv6 packets
recieved which have a TTL larger than that received that have a TTL larger than that
of a previously recived identical packet. of a previously received identical packet.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
REFERENCE REFERENCE
"See Section 5. 'SMF Packet Processing and "See Section 5 'SMF Packet Processing and
Forwarding' in RFC 6621 - Simplified Multicast Forwarding' in
Forwarding (SMF), Macker, J., May 2012." RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012."
::= { smfPerfGobalGroup 10 } ::= { smfPerfGobalGroup 10 }
smfPerfIpv6HAVAssistsReqdTotal OBJECT-TYPE smfPerfIpv6HAVAssistsReqdTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv6 packets "A counter of the total number of IPv6 packets
received which required the HAV assist for DPD. received that required the Hash Assist Value (HAV)
for DPD.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
REFERENCE REFERENCE
"See Section 6.1.1. 'IPv6 SMF_DPD Option Header' "See Section 6.1.1 'IPv6 SMF_DPD Option Header' in
in RFC 6621 - Simplified Multicast Forwarding RFC 6621 - 'Simplified Multicast Forwarding',
(SMF), Macker, J., May 2012." Macker, J., Ed., May 2012."
::= { smfPerfGobalGroup 11 } ::= { smfPerfGobalGroup 11 }
smfPerfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE smfPerfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv6 packets "A counter of the total number of IPv6 packets
recieved which the device inserted the received that the device inserted the
DPD header option. DPD header option.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled. In order to check for disabled and later enabled. In order to check for
the occurrence of such a discontinuity when monitoring the occurrence of such a discontinuity when monitoring
this counter object, it is recommended that the this counter object, it is recommended that the
smfCfgSmfSysUpTime object also be monitored." smfCfgSmfSysUpTime object also be monitored."
REFERENCE REFERENCE
"See Section 6.1.2. 'IPv6 Identification-Based "See Section 6.1.2 'IPv6 Identification-Based
DPD' in RFC 6621 - Simplified Multicast DPD' in
Forwarding (SMF), Macker, J., May 2012." RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012."
::= { smfPerfGobalGroup 12 } ::= { smfPerfGobalGroup 12 }
-- --
-- Per SMF Interface Performance Table -- Per SMF Interface Performance Table
-- --
smfPerfInterfaceGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } smfPerfInterfaceGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 }
smfPerfIpv4InterfacePerfTable OBJECT-TYPE smfPerfIpv4InterfacePerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfPerfIpv4InterfacePerfEntry SYNTAX SEQUENCE OF SmfPerfIpv4InterfacePerfEntry
skipping to change at page 40, line 44 skipping to change at page 40, line 23
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the number of multicast IP "A counter of the number of multicast IP
packets received by the SMF process on packets received by the SMF process on
this device on this interface. this device on this interface.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv4InterfacePerfEntry 1 } ::= { smfPerfIpv4InterfacePerfEntry 1 }
smfPerfIpv4MultiPktsForwardedPerIf OBJECT-TYPE smfPerfIpv4MultiPktsForwardedPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the number of "A counter of the number of
multicast IP packets forwarded by the multicast IP packets forwarded by the
SMF process on this device SMF process on this device
on this interface. on this interface.
skipping to change at page 41, line 16 skipping to change at page 40, line 43
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the number of "A counter of the number of
multicast IP packets forwarded by the multicast IP packets forwarded by the
SMF process on this device SMF process on this device
on this interface. on this interface.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv4InterfacePerfEntry 2 } ::= { smfPerfIpv4InterfacePerfEntry 2 }
smfPerfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE smfPerfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the number of duplicate "A counter of the number of duplicate
multicast IP packets detected by the multicast IP packets detected by the
SMF process on this device SMF process on this device
on this interface. on this interface.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv4InterfacePerfEntry 3 } ::= { smfPerfIpv4InterfacePerfEntry 3 }
smfPerfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE smfPerfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of dropped "A counter of the total number of dropped
multicast IPv4 packets by the SMF process multicast IPv4 packets by the SMF process
on this device on this interface on this device on this interface
due to TTL exceeded. due to TTL exceeded.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv4InterfacePerfEntry 4 } ::= { smfPerfIpv4InterfacePerfEntry 4 }
smfPerfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE smfPerfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv4 packets "A counter of the total number of IPv4 packets
received by the SMF process on this device received by the SMF process on this device
on this interface which have a TTL larger than on this interface that have a TTL larger than
that of a previously received identical packet. that of a previously received identical packet.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv4InterfacePerfEntry 5 } ::= { smfPerfIpv4InterfacePerfEntry 5 }
smfPerfIpv6InterfacePerfTable OBJECT-TYPE smfPerfIpv6InterfacePerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfPerfIpv6InterfacePerfEntry SYNTAX SEQUENCE OF SmfPerfIpv6InterfacePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 43, line 33 skipping to change at page 43, line 11
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the number of "A counter of the number of
multicast IP packets received by the multicast IP packets received by the
SMF process on this device SMF process on this device
on this interface. on this interface.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv6InterfacePerfEntry 1 } ::= { smfPerfIpv6InterfacePerfEntry 1 }
smfPerfIpv6MultiPktsForwardedPerIf OBJECT-TYPE smfPerfIpv6MultiPktsForwardedPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the number of "A counter of the number of
multicast IP packets forwarded by the multicast IP packets forwarded by the
SMF process on this device SMF process on this device
on this interface. on this interface.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv6InterfacePerfEntry 2 } ::= { smfPerfIpv6InterfacePerfEntry 2 }
smfPerfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE smfPerfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the number of duplicate "A counter of the number of duplicate
multicast IP packets detected by the multicast IP packets detected by the
SMF process on this device SMF process on this device
on this interface. on this interface.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv6InterfacePerfEntry 3 } ::= { smfPerfIpv6InterfacePerfEntry 3 }
smfPerfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE smfPerfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the number of dropped "A counter of the number of dropped
multicast IP packets by the multicast IP packets by the
SMF process on this device SMF process on this device
on this interface due to TTL on this interface due to TTL
exceeded. exceeded.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv6InterfacePerfEntry 4 } ::= { smfPerfIpv6InterfacePerfEntry 4 }
smfPerfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE smfPerfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv6 packets "A counter of the total number of IPv6 packets
received which have a TTL larger than that received that have a TTL larger than that
of a previously received identical packet of a previously received identical packet
by the SMF process on this device on this by the SMF process on this device on this
interface. interface.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv6InterfacePerfEntry 5 } ::= { smfPerfIpv6InterfacePerfEntry 5 }
smfPerfIpv6HAVAssistsReqdPerIf OBJECT-TYPE smfPerfIpv6HAVAssistsReqdPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv6 packets "A counter of the total number of IPv6 packets
received by the SMF process on this device received by the SMF process on this device
on this interface which required the on this interface that required the
HAV assist for DPD. HAV assist for DPD.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv6InterfacePerfEntry 6 } ::= { smfPerfIpv6InterfacePerfEntry 6 }
smfPerfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE smfPerfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Packets" UNITS "Packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv6 packets "A counter of the total number of IPv6 packets
received by the SMF process on this device received by the SMF process on this device
on this interface which the device inserted the on this interface that the device inserted the
DPD header option. DPD header option.
There is the potential for a counter discontinuity There is the potential for a counter discontinuity
in this object if the system SMF process had been in this object if the system SMF process has been
disabled and later enabled on this interface. disabled and later enabled on this interface.
In order to check for the occurrence of such a In order to check for the occurrence of such a
discontinuity when monitoring this counter object, discontinuity when monitoring this counter object,
it is recommended that the smfCfgIfSmfUpTime it is recommended that the smfCfgIfSmfUpTime
object also be monitored." object also be monitored."
::= { smfPerfIpv6InterfacePerfEntry 7 } ::= { smfPerfIpv6InterfacePerfEntry 7 }
-- --
-- Notifications -- Notifications
-- --
skipping to change at page 46, line 38 skipping to change at page 46, line 14
smfNotifAdminStatusChange NOTIFICATION-TYPE smfNotifAdminStatusChange NOTIFICATION-TYPE
OBJECTS { smfCfgRouterIDAddrType, -- The originator of OBJECTS { smfCfgRouterIDAddrType, -- The originator of
-- the notification. -- the notification.
smfCfgRouterID, -- The originator of smfCfgRouterID, -- The originator of
-- the notification. -- the notification.
smfCfgAdminStatus -- The new status of the smfCfgAdminStatus -- The new status of the
-- SMF process. -- SMF process.
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"smfCfgAdminStatusChange is a notification sent when a "smfCfgAdminStatusChange is a notification sent when
the 'smfCfgAdminStatus' object changes." the 'smfCfgAdminStatus' object changes."
::= { smfMIBNotifObjects 1 } ::= { smfMIBNotifObjects 1 }
smfNotifConfiguredOpModeChange NOTIFICATION-TYPE smfNotifConfiguredOpModeChange NOTIFICATION-TYPE
OBJECTS { smfCfgRouterIDAddrType, -- The originator of OBJECTS { smfCfgRouterIDAddrType, -- The originator of
-- the notification. -- the notification.
smfCfgRouterID, -- The originator of smfCfgRouterID, -- The originator of
-- the notification. -- the notification.
smfCfgOperationalMode -- The new Operations smfCfgOperationalMode -- The new Operations
-- Mode of the SMF -- Mode of the SMF
skipping to change at page 47, line 25 skipping to change at page 46, line 46
-- the notification. -- the notification.
smfCfgRouterID, -- The originator of smfCfgRouterID, -- The originator of
-- the notification. -- the notification.
ifName, -- The interface whose ifName, -- The interface whose
-- status has changed. -- status has changed.
smfCfgIfAdminStatus -- The new status of the smfCfgIfAdminStatus -- The new status of the
-- SMF interface. -- SMF interface.
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"smfCfgIfAdminStatusChange is a notification sent when a "smfCfgIfAdminStatusChange is a notification sent when
the 'smfCfgIfAdminStatus' object changes." the 'smfCfgIfAdminStatus' object changes."
::= { smfMIBNotifObjects 3 } ::= { smfMIBNotifObjects 3 }
smfNotifDpdMemoryOverflowEvent NOTIFICATION-TYPE smfNotifDpdMemoryOverflowEvent NOTIFICATION-TYPE
OBJECTS { smfCfgRouterIDAddrType, -- The originator of OBJECTS { smfCfgRouterIDAddrType, -- The originator of
-- the notification. -- the notification.
smfCfgRouterID, -- The originator of smfCfgRouterID, -- The originator of
-- the notification. -- the notification.
smfStateDpdMemoryOverflow -- The counter of smfStateDpdMemoryOverflow -- The counter of
-- the overflows. -- the overflows.
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"smfNotifDpdMemoryOverflowEvents is sent when the "smfNotifDpdMemoryOverflowEvents is sent when the
number of memory overflow events exceeds the number of memory overflow events exceeds
the 'smfNotifDpdMemoryOverflowThreshold' within the the 'smfNotifDpdMemoryOverflowThreshold' within the
previous number of seconds defined by the previous number of seconds defined by the
'smfNotifDpdMemoryOverflowWindow'." 'smfNotifDpdMemoryOverflowWindow'."
::= { smfMIBNotifObjects 4 } ::= { smfMIBNotifObjects 4 }
-- smfMIBNotifControl -- smfMIBNotifControl
smfNotifDpdMemoryOverflowThreshold OBJECT-TYPE smfNotifDpdMemoryOverflowThreshold OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
UNITS "Events" UNITS "Events"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A threshold value for the "A threshold value for the
`smfNotifDpdmemoryOverflowEvents' object. 'smfNotifDpdmemoryOverflowEvents' object.
If the number of occurences exceeds If the number of occurrences exceeds
this threshold within the previous this threshold within the previous
number of seconds number of seconds
'smfNotifDpdMemoryOverflowWindow', 'smfNotifDpdMemoryOverflowWindow',
then the `smfNotifDpdMemoryOverflowEvent' then the 'smfNotifDpdMemoryOverflowEvent'
notification is sent. notification is sent.
The default value for this object is The default value for this object is
'1'." '1'."
DEFVAL { 1 } DEFVAL { 1 }
::= { smfMIBNotifControl 1 } ::= { smfMIBNotifControl 1 }
smfNotifDpdMemoryOverflowWindow OBJECT-TYPE smfNotifDpdMemoryOverflowWindow OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A time window value for the "A time window value for the
`smfNotifDpdmemoryOverflowEvents' object. 'smfNotifDpdmemoryOverflowEvents' object.
If the number of occurences exceeds If the number of occurrences exceeds
the `smfNotifDpdMemoryOverflowThreshold' the 'smfNotifDpdMemoryOverflowThreshold'
within the previous number of seconds within the previous number of seconds
'smfNotifDpdMemoryOverflowWindow', 'smfNotifDpdMemoryOverflowWindow',
then the `smfNotifDpdMemoryOverflowEvent' then the 'smfNotifDpdMemoryOverflowEvent'
notification is sent. notification is sent.
The default value for this object is The default value for this object is
'1'." '1'."
DEFVAL { 1 } DEFVAL { 1 }
::= { smfMIBNotifControl 2 } ::= { smfMIBNotifControl 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
skipping to change at page 52, line 8 skipping to change at page 51, line 22
DESCRIPTION DESCRIPTION
"Set of SMF notifications implemented "Set of SMF notifications implemented
in this module." in this module."
::= { smfMIBGroups 6 } ::= { smfMIBGroups 6 }
END END
8. IANA-SMF-MIB Definitions 8. IANA-SMF-MIB Definitions
This section contains the IANA-SMF-MIB module. This MIB module This section contains the IANA-SMF-MIB module. This MIB module
defines two textual conventions for which IANA SHOULD maintain and defines two Textual Conventions for which IANA SHOULD maintain and
keep synchronized with the registry identified below within the keep synchronized with the registry identified below within the
IANAsmfOpModeIdTC and the IANAsmfRssaIdTC TEXTUAL-CONVENTIONs. IANAsmfOpModeIdTC and the IANAsmfRssaIdTC TEXTUAL-CONVENTIONs.
The IANAsmfOpModeIdTC defines an index that identifies through The IANAsmfOpModeIdTC defines an index that identifies through
reference to a specific SMF operations mode. The index is an integer reference to a specific SMF operations mode. The index is an integer
valued named-number enumeration consisting of an integer and label. valued named-number enumeration consisting of an integer and label.
IANA is to create and maintain this textual convention. Future IANA is to create and maintain this Textual Convention. Future
assignments are made to anyone on a first come, first served basis. assignments are made to anyone on a first come, first served basis.
There is no substantive review of the request, other than to ensure There is no substantive review of the request, other than to ensure
that it is well-formed and does not duplicate an existing assignment. that it is well-formed and does not duplicate an existing assignment.
However, requests must include a minimal amount of clerical However, requests must include a minimal amount of clerical
information, such as a point of contact (including an email address) information, such as a point of contact (including an email address)
and a brief description of the method being identified as a new SMF and a brief description of the method being identified as a new SMF
operations mode. operations mode.
The IANAsmfRssaIdTC defines an index that identifies through The IANAsmfRssaIdTC defines an index that identifies through
reference to a specific Reduced Set Selection Algorithm (RSSA). The reference to a specific Reduced Set Selection Algorithm (RSSA). The
index is an integer valued named-number enumeration consisting of an index is an integer valued named-number enumeration consisting of an
integer and label. IANA is to create and maintain this textual integer and label. IANA is to create and maintain this Textual
convention. Convention.
Future assignments to the IANAsmfRssaIdTC for the index range 5-127 Future assignments to the IANAsmfRssaIdTC for the index range 5-127
require an RFC publication (either as an IETF submission or as an RFC require an RFC publication (either as an IETF submission or as an
Editor Independent submission [RFC5742]). The type of RFC MUST be Independent submission [RFC5742]). The category of RFC MUST be
Standards Track. The specific RSSA algorithms MUST be documented in Standards Track. The specific RSSAs MUST be documented in sufficient
sufficient detail so that interoperability between independent detail so that interoperability between independent implementations
implementations is possible. is possible.
Future assignments to the IANAsmfRssaIdTC for the index range 128-239 Future assignments to the IANAsmfRssaIdTC for the index range 128-239
are private or local use only, with the type and purpose defined by are private or local use only, with the type and purpose defined by
the local site. No attempt is made to prevent multiple sites from the local site. No attempt is made to prevent multiple sites from
using the same value in different (and incompatible) ways. There is using the same value in different (and incompatible) ways. There is
no need for IANA to review such assignments (since IANA will not no need for IANA to review such assignments (since IANA will not
record these) and assignments are not generally useful for broad record these), and assignments are not generally useful for broad
interoperability. It is the responsibility of the sites making use interoperability. It is the responsibility of the sites making use
of the Private Use range to ensure that no conflicts occur (within of the Private Use range to ensure that no conflicts occur (within
the intended scope of use). the intended scope of use).
Future assignments to the IANAsmfRssaIdTC for the index range 240-255 Future assignments to the IANAsmfRssaIdTC for the index range 240-255
are to facilitate experimentation. These require an RFC publication are to facilitate experimentation. These require an RFC publication
(either as an IETF submission or as an RFC Editor Independent (either as an IETF submission or as an Independent submission
submission [RFC5742]). The type of RFC MUST be Experimental. The [RFC5742]). The category of RFC MUST be Experimental. The RSSA
RSSA algorithms MUST be documented in sufficient detail so that algorithms MUST be documented in sufficient detail so that
interoperability between independent implementations is possible. interoperability between independent implementations is possible.
IANA-SMF-MIB DEFINITIONS ::= BEGIN This MIB module references [RFC3626], [RFC5614], [RFC6621], and
[RFC7181].
IMPORTS IANA-SMF-MIB DEFINITIONS ::= BEGIN
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
ianaSmfMIB MODULE-IDENTITY IMPORTS
LAST-UPDATED "201408121300Z" -- August 12, 2014 MODULE-IDENTITY, mib-2
ORGANIZATION "IANA" FROM SNMPv2-SMI -- RFC 2578
CONTACT-INFO "Internet Assigned Numbers Authority TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- RFC 2579
Postal: ICANN ianaSmfMIB MODULE-IDENTITY
4676 Admiralty Way, Suite 330 LAST-UPDATED "201410100000Z" -- October 10, 2014
Marina del Rey, CA 90292 ORGANIZATION "IANA"
CONTACT-INFO "Internet Assigned Numbers Authority
Tel: +1 310 823 9358 Postal: ICANN
E-Mail: iana@iana.org" 12025 Waterfront Drive, Suite 300
DESCRIPTION "This MIB module defines the Los Angeles, CA 90094-2536
IANAsmfOpModeIdTC and IANAsmfRssaIdTC United States
Textual Conventions, and thus the
enumerated values of the
smfCapabilitiesOpModeID and
smfCapabilitiesRssaID objects defined
in the SMF-MIB."
REVISION "201408121300Z" -- August 12, 2014
DESCRIPTION "Initial version of this MIB as published in
RFC KKKK."
::= { mib-2 kkkk }
IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION Tel: +1 310 301 5800
STATUS current EMail: iana@iana.org"
DESCRIPTION DESCRIPTION "This MIB module defines the
"An index that identifies through reference to a specific IANAsmfOpModeIdTC and IANAsmfRssaIdTC
SMF operations mode. There are basically three styles Textual Conventions, and thus the
of SMF operation with reduced relay sets currently enumerated values of the
identified: smfCapabilitiesOpModeID and
smfCapabilitiesRssaID objects defined
in the SMF-MIB."
REVISION "201410100000Z" -- October 10, 2014
DESCRIPTION
"Initial version of this MIB as published in RFC 7367.
Independent operation 'independent(1)' - Copyright (c) 2014 IETF Trust and the persons identified as
SMF performs its own relay authors of the code. All rights reserved.
set selection using information from an associated
MANET NHDP process.
CDS-aware unicast routing operation 'routing(2)'- Redistribution and use in source and binary forms, with or
a coexistent unicast routing without modification, is permitted pursuant to, and subject
protocol provides dynamic relay to the license terms contained in, the Simplified BSD License
set state based upon its own control plane set forth in Section 4.c of the IETF Trust's Legal Provisions
CDS or neighborhood discovery information. Relating to IETF Documents
(http://trustee.ietf.org/license-info).
"
::= { mib-2 225 }
Cross-layer operation 'crossLayer(3)' - IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION
SMF operates using neighborhood STATUS current
status and triggers from a DESCRIPTION
cross-layer information base for dynamic relay "An index that identifies through reference to a specific
set selection and maintenance. SMF operations mode. There are basically three styles
of SMF operation with reduced relay sets currently
identified:
Independent operation 'independent(1)' -
SMF performs its own relay
set selection using information from an associated
MANET NHDP process.
IANA MUST update this textual convention accordingly. CDS-aware unicast routing operation 'routing(2)'-
a coexistent unicast routing
protocol provides dynamic relay
set state based upon its own control plane
Connected Dominating Set (CDS) or neighborhood
discovery information.
The definition of this textual convention with the Cross-layer operation 'crossLayer(3)' -
addition of newly assigned values is published SMF operates using neighborhood
periodically by the IANA, in either the Assigned status and triggers from a
Numbers RFC, or some derivative of it specific to cross-layer information base for dynamic relay
Internet Network Management number assignments. (The set selection and maintenance.
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values SHOULD be made to IANA via IANA MUST update this Textual Convention accordingly.
email (iana@iana.org)."
REFERENCE
"See Section 7.2. 'Reduced Relay Set Forwarding',
and the Appendices A, B and C in
RFC 6621 - Simplified Multicast Forwarding
(SMF), Macker, J., May 2012."
SYNTAX INTEGER {
independent (1),
routing (2),
crossLayer (3)
-- future (4-255)
}
IANAsmfRssaIdTC ::= TEXTUAL-CONVENTION The definition of this Textual Convention with the
STATUS current addition of newly assigned values is updated
DESCRIPTION periodically by the IANA, in the
"An index that identifies through reference to a specific IANA-maintained registries. (The
RSSA algorithms. Several are currently defined latest arrangements can be obtained by contacting the
in the Appendix A, B and C of RFC 6621. IANA.)
Requests for new values SHOULD be made to IANA via
email (iana@iana.org)."
REFERENCE
"See Section 7.2 'Reduced Relay Set Forwarding',
and the Appendices A, B, and C in
RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012."
SYNTAX INTEGER {
independent (1),
routing (2),
crossLayer (3)
-- future (4-255)
}
Examples of RSSA algorithms already identified within IANAsmfRssaIdTC ::= TEXTUAL-CONVENTION
this TC are: STATUS current
DESCRIPTION
"An index that identifies through reference to specific
RSSAs. Several are currently defined
in the Appendices A, B, and C of RFC 6621.
Classical Flooding (cF(1)) - is the standard Examples of RSSAs already identified within
flooding algorithm where each node in the next this Textual Convention (TC) are:
retransmits the information on each of its interfaces.
Source-Based Multipint Relay (sMPR(2)) - Classical Flooding (cF(1)) - is the standard
this algorithm is used by Optimized Link State Routing flooding algorithm where each node in the next
(OLSR) and OLSR version 2 (OLSRv2) protocols for the retransmits the information on each of its interfaces.
relay of link state updates and other control
information [RFC3626]. Since each router picks
its neighboring relays independently, sMPR
forwarders depend upon previous hop information
(e.g., source MAC address) to operate correctly.
Extended Connected Dominating Set (eCDS(3)) - Source-Based Multipoint Relay (sMPR(2)) -
defined in [RFC5614] this algorithm forms a single this algorithm is used by Optimized Link State Routing
CDS mesh for the SMF operating region. Its (OLSR) and OLSR version 2 (OLSRv2) protocols for the
packet-forwarding rules are not dependent upon relay of link state updates and other control
previous hop knowledge in contrast to sMPR. information (RFC 3626, RFC 7181). Since each router
picks its neighboring relays independently, sMPR
forwarders depend upon previous hop information
(e.g., source Media Access Control (MAC) address) to
operate correctly.
Multipoint Relay Connected Dominating Set (mprCDS(4)) - Essential Connected Dominating Set (eCDS(3)) -
This algorithm is an extension to the basic sMPR defined in RFC 5614, this algorithm forms a single
election algorithm that results in a shared CDS mesh for the SMF operating region. Its
(non-source-specific) SMF CDS. Thus, its forwarding packet-forwarding rules are not dependent upon
rules are not dependent upon previous hop information, previous hop knowledge in contrast to sMPR.
similar to eCDS.
IANA MUST update this textual convention accordingly. Multipoint Relay Connected Dominating Set (mprCDS(4)) -
This algorithm is an extension to the basic sMPR
election algorithm that results in a shared
(non-source-specific) SMF CDS. Thus, its forwarding
rules are not dependent upon previous hop information,
similar to eCDS.
The definition of this textual convention with the IANA MUST update this Textual Convention accordingly.
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values SHOULD be made to IANA via The definition of this Textual Convention with the
email (iana@iana.org)." addition of newly assigned values is updated
REFERENCE periodically by the IANA, in the
"See, e.g., IANA-maintained registries. (The
latest arrangements can be obtained by contacting the
IANA.)
Section 8.1.1. 'SMF Message TLV Type', Requests for new values SHOULD be made to IANA via
Appendix A. 'Essential Connecting Dominating Set (E-CDS) email (iana@iana.org)."
Algorithm', REFERENCE
Appendix B. 'Source-Based Multipoint Relay (S-MPR) "For example, see:
Algorithm', and
Appendix C. 'Multipoint Relay Connected Dominating Set
(MPR-CDS) Algorithm'
in RFC 6621 - Macker, J., `Simplified Multicast
Forwarding (SMF)', May 2012.
RFC 3626 - Clausen, T., and P. Jacquet, `Optimized Link Section 8.1.1. 'SMF Message TLV Type' and the Appendices
State Routing Protocol (OLSR)', October 2003. A, B, and C in
RFC 6621 - 'Simplified Multicast Forwarding',
Macker, J., Ed., May 2012.
RFC 5614 - Ogier, R. and P. Spagnolo, `Mobile Ad Hoc RFC 3626 - Clausen, T., Ed., and P. Jacquet, Ed., 'Optimized
Network (MANET) Extension of OSPF Using Connected Link State Routing Protocol (OLSR)', October 2003.
Dominating Set (CDS) Flooding', August 2009.
"
SYNTAX INTEGER {
cF(1),
sMPR(2),
eCDS(3),
mprCDS(4)
-- future(5-127)
-- noStdAction(128-239)
-- experimental(240-255)
}
END RFC 5614 - Ogier, R. and P. Spagnolo, 'Mobile Ad Hoc
Network (MANET) Extension of OSPF Using Connected
Dominating Set (CDS) Flooding', August 2009.
RFC 7181 - Clausen, T., Dearlove, C., Jacquet, P., and
U. Herberg, 'The Optimized Link State Routing Protocol
Version 2', April 2014."
SYNTAX INTEGER {
cF(1),
sMPR(2),
eCDS(3),
mprCDS(4)
-- future(5-127)
-- noStdAction(128-239)
-- experimental(240-255)
}
END
9. Security Considerations 9. Security Considerations
This section discusses security implications of the choices made in This section discusses security implications of the choices made in
this SMF-MIB module. this SMF-MIB module.
There are a number of management objects defined in this MIB module 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 with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
skipping to change at page 56, line 45 skipping to change at page 56, line 28
o 'smfCfgAdminStatus' - this writable configuration object controls o 'smfCfgAdminStatus' - this writable configuration object controls
the operational status of the SMF process. If this setting is the operational status of the SMF process. If this setting is
configured inconsistently across the MANET multicast domain, then configured inconsistently across the MANET multicast domain, then
delivery of multicast data may be inconsistent across the domain; delivery of multicast data may be inconsistent across the domain;
some nodes may not receive multicast data intended for them. some nodes may not receive multicast data intended for them.
o 'smfCfgRouterIDAddrType' and 'smfCfgRouterID' - these writable o 'smfCfgRouterIDAddrType' and 'smfCfgRouterID' - these writable
configuration objects define the ID of the SMF process. These configuration objects define the ID of the SMF process. These
objects should be configured with a routable address defined on objects should be configured with a routable address defined on
the local SMF device. The smfCfgRouterID is a logical the local SMF device. The smfCfgRouterID is a logical
identification that MUST be configured as unique across inter- identification that MUST be configured as unique across
operating SMF neighborhoods and it is RECOMMENDED to be chosen as interoperating SMF neighborhoods, and it is RECOMMENDED to be
the numerically largest address contained in a node's 'Neighbor chosen as the numerically largest address contained in a node's
Address List' as defined in NHDP. A smfCfgRouterID MUST be unique
within the scope of the operating MANET network regardless of the 'Neighbor Address List' as defined in NHDP. A smfCfgRouterID MUST
method used for selecting it. If these objects are mis-configured be unique within the scope of the operating MANET network
or configured in-consistently across the MANET, then the ability regardless of the method used for selecting it. If these objects
of various RSSA algorithms, e.g., ECDS, may be compromised. This are misconfigured or configured inconsistently across the MANET,
would potentially result in some routers within the MANET not then the ability of various RSSAs, e.g., eCDS, may be compromised.
This would potentially result in some routers within the MANET not
receiving multicast packets destine to them. Hence, intentionally receiving multicast packets destine to them. Hence, intentionally
mis-configuring these objects could pose a form of Denial-of- misconfiguring these objects could pose a form of Denial-of-
Service (DOS) attack against the MANET. Service (DoS) attack against the MANET.
o 'smfCfgOpMode' - this writable configuration object defines the o 'smfCfgOpMode' - this writable configuration object defines the
operational mode of the SMF process. The operational mode defines operational mode of the SMF process. The operational mode defines
how the SMF process receives its data to form its local estimate how the SMF process receives its data to form its local estimate
of the CDS. It is recommended that the value for this object be of the CDS. It is recommended that the value for this object be
set consistently across the MANET to ensure proper operation of set consistently across the MANET to ensure proper operation of
the multicast packet forwarding. If the value for this object is the multicast packet forwarding. If the value for this object is
set inconsistently across the MANET, the result may be that set inconsistently across the MANET, the result may be that
multicast packet delivery will be compromised within the MANET. multicast packet delivery will be compromised within the MANET.
Hence, intentionally mis-configuring this object could pose a form Hence, intentionally misconfiguring this object could pose a form
DOS attack against the MANET. DoS attack against the MANET.
o 'smfCfgRssa' - this writable configuration object sets the o 'smfCfgRssa' - this writable configuration object sets the
specific Reduced Set Selection Algorithm (RSSA) for the SMF specific RSSA for the SMF process. If this object is set
process. If this object is set inconsistently across the MANET inconsistently across the MANET domain, multicast delivery of data
domain, multicast delivery of data will likely fail. Hence, will likely fail. Hence, intentionally misconfiguring this object
intentionally mis-configuring this object could pose a form DOS could pose a form DoS attack against the MANET.
attack against the MANET.
o 'smfCfgRssaMember' - this writable configuration object sets the o 'smfCfgRssaMember' - this writable configuration object sets the
'interest' of the local SMF node in participating in the CDS. 'interest' of the local SMF node in participating in the CDS.
Setting this object to 'never(3)' on a highly highly connected Setting this object to 'never(3)' on a highly connected device
device could lead to frequent island formation. Setting this could lead to frequent island formation. Setting this object to
object to 'always(2)' could support data ex-filtration from the 'always(2)' could support data ex-filtration from the MANET
MANET domain. domain.
o 'smfCfgIpv4Dpd' - this writable configuration object sets the o 'smfCfgIpv4Dpd' - this writable configuration object sets the
duplicate packet detection method, i.e., H-DPD or I-DPD, for duplicate packet detection method, i.e., H-DPD or I-DPD, for
forwarding of IPv4 multicast packets. Forwarders may operate with forwarding of IPv4 multicast packets. Forwarders may operate with
mixed H-DPD and I-DPD modes as long as they consistently perform mixed H-DPD and I-DPD modes as long as they consistently perform
the appropriate DPD routines outlined [RFC6621]. However, it is the appropriate DPD routines outlined in [RFC6621]. However, it
RECOMMENDED that a deployment be configured with a common mode for is RECOMMENDED that a deployment be configured with a common mode
operational consistency. for operational consistency.
o 'smfCfgIpv6Dpd' - this writable configuration object sets the o 'smfCfgIpv6Dpd' - this writable configuration object sets the
duplicate packet detection method for forwarding of IPv6 multicast duplicate packet detection method for the forwarding of IPv6
packets. Since IPv6 SMF does specifies an option header, the multicast packets. Since IPv6 SMF does specify an option header,
interoperability constraints are not as loose as in the IPv4 the interoperability constraints are not as loose as in the IPv4
version, and forwarders SHOULD NOT operate with mixed H-DPD and version, and forwarders SHOULD NOT operate with mixed H-DPD and
I-DPD modes. Hence the value for this object SHOULD be I-DPD modes. Hence, the value for this object SHOULD be
consistently set within the forwarders comprising the MANET, else consistently set within the forwarders comprising the MANET, else
inconsistent forwarding may result unnecessary multicast packet inconsistent forwarding may result unnecessary multicast packet
dropping. dropping.
o 'smfCfgMaxPktLifetime' - this writable configuration object sets o 'smfCfgMaxPktLifetime' - this writable configuration object sets
the estimate of the network packet traversal time. If set too the estimate of the network packet traversal time. If set too
small, this could lead to poor multicast data delivery ratios small, this could lead to poor multicast data delivery ratios
throughout the MANET domain. This could serve as a form of DOS throughout the MANET domain. This could serve as a form of DoS
attack if this object value is set too small. attack if this object value is set too small.
o 'smfCfgDpdEntryMaxLifetime' - this writable configuration object o 'smfCfgDpdEntryMaxLifetime' - this writable configuration object
sets the maximum lifetime (in seconds) for the cached DPD records sets the maximum lifetime (in seconds) for the cached DPD records
for the combined IPv4 and IPv6 methods. If the memory is running for the combined IPv4 and IPv6 methods. If the memory is running
low prior to the MaxLifetime being exceeded, the local SMF devices low prior to the MaxLifetime being exceeded, the local SMF devices
should purge the oldest records first. If this object value is should purge the oldest records first. If this object value is
set too small, then the effectiveness of the SMF DPD algorithms set too small, then the effectiveness of the SMF DPD algorithms
may become greatly diminished causing a higher than necessary may become greatly diminished causing a higher than necessary
packet load on the MANET. packet load on the MANET.
o 'smfCfgNhdpRssaMesgTLVIncluded' - this writable configuration o 'smfCfgNhdpRssaMesgTLVIncluded' - this writable configuration
object indicates whether the associated NHDP messages include the object indicates whether or not the associated NHDP messages
RSSA Message TLV, or not. It is highly RECOMMENDED that this include the RSSA Message TLV. It is highly RECOMMENDED that this
object be set to 'true(1)' when the SMF operation mode is set to object be set to 'true(1)' when the SMF operation mode is set to
independent as this information will inform the local forwarder of independent as this information will inform the local forwarder of
the RSSA algorithm implemented in neighboring forwarders and is the RSSA implemented in neighboring forwarders and is used to
used to ensure consistent forwarding across the MANET. While it ensure consistent forwarding across the MANET. While it is
is possible that SMF neighbors MAY be configured differently with possible that SMF neighbors MAY be configured differently with
respect to the RSSA algorithm and still operate cooperatively, but respect to the RSSA and still operate cooperatively, but these
these cases will vary dependent upon the algorithm types cases will vary dependent upon the algorithm types designated and
designated and this situation SHOULD be avoided. this situation SHOULD be avoided.
o 'smfCfgNhdpRssaAddrBlockTLVIncluded' - this writable configuration o 'smfCfgNhdpRssaAddrBlockTLVIncluded' - this writable configuration
object indicates whether the associated NHDP messages include the object indicates whether or not the associated NHDP messages
the RSSA Address Block TLV, or not. The include the RSSA Address Block TLV. The
smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it
depends on the existence of an address block which may not be depends on the existence of an address block that may not be
present. If this SMF device is configured with NHDP, then this present. If this SMF device is configured with NHDP, then this
object should be set to 'true(1)' as this TLV enables CDS relay object should be set to 'true(1)' as this TLV enables CDS relay
algorithm operation and configuration to be shared among 2-hop algorithm operation and configuration to be shared among 2-hop
neighborhoods. Some relay algorithms require 2-hop neighbor neighborhoods. Some relay algorithms require 2-hop neighbor
configuration in order to correctly select relay sets. configuration in order to correctly select relay sets.
o 'smfCfgAddrForwardingTable' - the writable configuration objects o 'smfCfgAddrForwardingTable' - the writable configuration objects
in this table indicate which multicast IP addresses are to be in this table indicate which multicast IP addresses are to be
forwarded by this SMF node. Misconfiguration of rows within this forwarded by this SMF node. Misconfiguration of rows within this
table can limit the ability of this SMF device to properly forward table can limit the ability of this SMF device to properly forward
skipping to change at page 59, line 15 skipping to change at page 58, line 49
Some of the readable objects in this MIB module (i.e., objects with a 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 MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o 'smfNodeRsStatusIncluded' - this readable state object indicates o 'smfNodeRsStatusIncluded' - this readable state object indicates
that this SMF node is part of the CDS, or not. Being part of the whether or not this SMF node is part of the CDS. Being part of
CDS makes this node a distinguished device. It could be exploited the CDS makes this node a distinguished device. It could be
for data ex-filtration, or denial of service attacks. exploited for data ex-filtration, or DoS attacks.
o 'smfStateNeighborTable' - the readable state objects in this table o 'smfStateNeighborTable' - the readable state objects in this table
indicate current neighbor nodes to this SMF node. Exposing this indicate current neighbor nodes to this SMF node. Exposing this
information to an attacker could allow the attacker easier access information to an attacker could allow the attacker easier access
to the larger MANET domain. to the larger MANET domain.
The remainder of the objects in the SMF-MIB module are performance The remainder of the objects in the SMF-MIB module are performance
counter objects. While these give an indication of the activity of counter objects. While these give an indication of the activity of
the SMF process on this node, it is not expected that exposing these the SMF process on this node, it is not expected that exposing these
values pose a security risk to the MANET network. values poses a security risk to the MANET network.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), 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 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 allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
Implementations MUST provide the security features described by the Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410] ), including full support for SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM) authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM) MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH [RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353]. [RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
10. Applicability Statement 10. Applicability Statement
This document describes objects for configuring parameters of the This document describes objects for configuring parameters of the
Simplified Multicast Forwarding [RFC6621] process on a Mobile Ad-Hoc Simplified Multicast Forwarding [RFC6621] process on a Mobile Ad Hoc
Network (MANET) router. This MIB module, denoted SMF-MIB, also Network (MANET) router. This MIB module, denoted SMF-MIB, also
reports state and performance information and notifications. This reports state and performance information and notifications. This
section provides some examples of how this MIB module can be used in section provides some examples of how this MIB module can be used in
MANET network deployments. A fuller discussion of MANET network MANET network deployments. A fuller discussion of MANET network
management use cases and challenges will be provided elsewhere. management use cases and challenges is out of scope for this
document.
SMF is designed to allow MANET routers to forward IPv4 and IPv6 SMF is designed to allow MANET routers to forward IPv4 and IPv6
packets over the MANET and cover the MANET nodes through the packets over the MANET and cover the MANET nodes through the
automatic discovery of efficient estimates of the Minimum Connected automatic discovery of efficient estimates of the Minimum Connected
Dominating Set (MCDS) of nodes within the MANET. The MCDS are Dominating Set (MCDS) of nodes within the MANET. The MCDS is
estimated using the Relay Set Selection Algorithms (RSSAs) discussed estimated using the Relay Set Selection Algorithms (RSSAs) discussed
within this document. In the following, three scenarios are listed within this document. In the following, three scenarios are listed
where this MIB module is useful, i.e., where this MIB module is useful:
o For a Parking Lot Initial Configuration Situation - it is common o For a Parking Lot Initial Configuration Situation - it is common
for the vehicles comprising the MANET being forward deployed at a for the vehicles comprising the MANET being forward deployed at a
remote location, e.g., the site of a natural disaster, to be off- remote location, e.g., the site of a natural disaster, to be off-
loaded in a parking lot where an initial configuration of the loaded in a parking lot where an initial configuration of the
networking devices is performed. The configuration is loaded into networking devices is performed. The configuration is loaded into
the devices from a fixed location Network Operation Center (NOC) the devices from a fixed-location Network Operations Center (NOC)
at the parking lot and the vehicles are stationary at the parking at the parking lot, and the vehicles are stationary at the parking
lot while the configuration changes are made. Standards-based lot while the configuration changes are made. Standards-based
methods for configuration management from the co-located NOC are methods for configuration management from the co-located NOC are
necessary for this deployment option. The set of interesting necessary for this deployment option. The set of interesting
configuration objects for the SMF process are listed within this configuration objects for the SMF process are listed within this
MIB module. MIB module.
o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed
NOC - Here the vehicles carrying the MANET routers carry multiple NOC - Here the vehicles carrying the MANET routers carry multiple
wireless interfaces, one of which is a relatively low-bandwidth wireless interfaces, one of which is a relatively low-bandwidth
on-the-move satellite connection which interconnects a fix NOC to on-the-move satellite connection that interconnects a fix NOC to
the nodes of the MANET. Standards-based methods for monitoring the nodes of the MANET. Standards-based methods for monitoring
and fault management from the fixed NOC are necessary for this and fault management from the fixed NOC are necessary for this
deployment option. deployment option.
o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for
larger vehicles, a hierarchical network management arrangement is larger vehicles, a hierarchical network management arrangement is
useful. Centralized network management is performed from a fixed useful. Centralized network management is performed from a fixed
NOC while local management is performed locally from within the NOC while local management is performed locally from within the
vehicles. Standards-based methods for configuration, monitoring vehicles. Standards-based methods for configuration, monitoring,
and fault management are necessary for this deployment option. and fault management are necessary for this deployment option.
Here we provide an example of the simplest of configurations to Here we provide an example of the simplest of configurations to
establish an operational multicast forwarding capability in a MANET. establish an operational multicast forwarding capability in a MANET.
This discussion only identifies the configuration necessary through This discussion only identifies the configuration necessary through
the SMF-MIB module and assumes that other configuration has occurred. the SMF-MIB module and assumes that other configuration has occurred.
Assume that the MANET is to support only IPv4 addressing and that the Assume that the MANET is to support only IPv4 addressing and that the
MANET nodes are to be configured in the context of the Parking Lot MANET nodes are to be configured in the context of the Parking Lot
Initialization case above. Then the SMF-MIB module defines ten Initialization case above. Then, the SMF-MIB module defines ten
configuration OIDs and two configuration tables, i.e., the configuration OIDs and two configuration tables, i.e., the
smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten
OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL
clauses which allow for a functional configuration of the SMF process clauses that allow for a functional configuration of the SMF process
within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the
smfCfgRouterID can be set as, e.g. (assuming the use of the Net-SNMP smfCfgRouterID can be set as, e.g., (assuming the use of the Net-SNMP
toolkit),: toolkit),:
snmpset [options] <smfCfgRouterID_OID>.0 a 192.0.2.100 snmpset [options] <smfCfgRouterID_OID>.0 a 192.0.2.100
If the smfCfgAddrForwardingTable is left empty, then the SMF local If the smfCfgAddrForwardingTable is left empty, then the SMF local
forwarder will forward all multicast addresses. So this table does forwarder will forward all multicast addresses. So this table does
not require configuration if you want to have the MANET forward all not require configuration if you want to have the MANET forward all
multicast addresses. multicast addresses.
All that remains is to configure at least one row in the All that remains is to configure at least one row in the
smfCfgInterfaceTable. Assume that the node has a wireless interface smfCfgInterfaceTable. Assume that the node has a wireless interface
with an <ifName>='wlan0' and an <ifIndex>='1'. All of the objects in with an <ifName>='wlan0' and an <ifIndex>='1'. All of the objects in
the rows of the smfCfgInterfaceTable have a DEFVAL clause, hence only the rows of the smfCfgInterfaceTable have a DEFVAL clause; hence,
the RowStatus object needs to be set. So the SMF process will be only the RowStatus object needs to be set. So the SMF process will
activated on the 'wlan0' interface by the following network manager be activated on the 'wlan0' interface by the following network
snmpset command: manager snmpset command:
snmpset [options] <smfCfgIfRowStatus>.1 i active(1) snmpset [options] <smfCfgIfRowStatus>.1 i active(1)
At this point, the configured forwarder will begin a Classical At this point, the configured forwarder will begin a Classical
Flooding algorithm to forward all multicast addresses IPv4 packets it Flooding algorithm to forward all multicast addresses IPv4 packets it
receives. receives.
To provide a more efficient multicast forwarding within the MANET, To provide a more efficient multicast forwarding within the MANET,
the network manager could walk the smfCapabilitiesTable to identify the network manager could walk the smfCapabilitiesTable to identify
other SMF operational modes, e.g.,: other SMF Operational Modes, for example:
snmpwalk [options] <smfCapabilitiesTable> snmpwalk [options] <smfCapabilitiesTable>
SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1 SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1
SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2 SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2
SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1) SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1)
SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2) SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2)
skipping to change at page 62, line 4 skipping to change at page 61, line 36
snmpwalk [options] <smfCapabilitiesTable> snmpwalk [options] <smfCapabilitiesTable>
SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1 SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1
SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2 SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2
SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1) SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1)
SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2) SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2)
SMF-MIB::smfCapabilitiesRssaID.1 = INTEGER: cF(1) SMF-MIB::smfCapabilitiesRssaID.1 = INTEGER: cF(1)
SMF-MIB::smfCapabilitiesRssaID.2 = INTEGER: eCDS(3) SMF-MIB::smfCapabilitiesRssaID.2 = INTEGER: eCDS(3)
In this example, the forwarding device also supports the Extended In this example, the forwarding device also supports the Essential
Connected Dominating Set (eCDS) RSSA with the forwarder in the Connected Dominating Set (eCDS) RSSA with the forwarder in the
'independent(2)' operational mode. If the network manager were to 'independent(2)' operational mode. If the network manager were to
then issue an snmpset, e.g.,: then issue an snmpset, for example:
snmpset [options] <smfCfgOperationalMode>.0 i 2 snmpset [options] <smfCfgOperationalMode>.0 i 2
then the local forwarder would switch if forwarding behavior from then the local forwarder would switch its forwarding behavior from
Classical Flooding to the more efficient eCDS flooding. Classical Flooding to the more efficient eCDS flooding.
11. IANA Considerations 11. IANA Considerations
This document defines two MIB modules: This document defines two MIB modules:
o SMF-MIB is defined in Section 7 and is an experimental MIB module. 1. SMF-MIB is defined in Section 7 and is an experimental MIB
module.
o IANA-SMF-MIB is defined in Section 8 and is an IANA MIB module 2. IANA-SMF-MIB is defined in Section 8 and is an IANA MIB module
that IANA is requested to maintain. that IANA maintains.
Thus, there are three actions requested of IANA: Thus, IANA has completed three actions:
1. IANA is requested to allocate an OBJECT IDENTIFIER value and IANA has allocated an OBJECT IDENTIFIER value and recorded it in the
record it in the SMI Numbers registry in the sub-registry called "SMI SMI Numbers registry in the subregistry called "SMI Experimental
Experimental Codes" under the experimental branch (1.3.6.1.3). Codes" under the experimental branch (1.3.6.1.3).
Decimal | Name | Description | Reference Decimal | Name | Description | Reference
--------+---------+---------------+------------ --------+---------+---------------+------------
xxxx | smfMib | SMF-MIB | [This.I-D] 126 | smfMib | SMF-MIB | [RFC7367]
[RFC Editor Note: Please replace the tag "xxxx" in
this document with the value assigned by IANA and
remove this note.]
2. IANA is requested to allocate an OBJECT IDENTIFIER value and IANA has allocated an OBJECT IDENTIFIER value and recorded it in the
record it in the SMI Numbers registry in the sub-registry called "SMI SMI Numbers registry in the subregistry called "SMI Network
Network Management MGMT Codes Internet-standard MIB" under the mib-2 Management MGMT Codes Internet-standard MIB" under the mib-2 branch
branch (1.3.6.1.2.1). (1.3.6.1.2.1).
Decimal | Name | Description | Reference Decimal | Name | Description | Reference
--------+---------------+-----------------+------------ --------+---------------+-----------------+------------
kkkk | ianaSmfMIB | IANA-SMF-MIB | [This.I-D] 225 | ianaSmfMIB | IANA-SMF-MIB | [RFC7367]
IANA maintains a MIB module called ianaSmfMIB and has populated it
[RFC Editor Note: Please replace the tag "kkkk" in with the initial MIB module defined in Section 8 of this document by
this document with the value assigned by IANA and creating a new entry in the registry "IANA Maintained MIBs" called
remove this note.] "IANA-SMF-MIB".
3. IANA is requested to maintain a MIB module called ianaSmfMIB and
populate it with the initial MIB module defined in Section 8 of this
document by creating a new entry in the registry "IANA Maintained
MIBs" called "IANA-SMF-MIB".
12. Contributors 12. References
This MIB document uses the template authored by D. Harrington which 12.1. Normative References
is based on contributions from the MIB Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn.
13. Acknowledgements [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
The authors would like to acknowledge the valuable comments from Sean [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Harnedy in the early phases of the development of this MIB module. Schoenwaelder, Ed., "Structure of Management Information
The authors would like to thank Adrian Farrel, Dan Romascanu, Juergen Version 2 (SMIv2)", STD 58, RFC 2578, April 1999,
Shoenwaelder, Stephen Hanna, and Brian Haberman for their careful <http://www.rfc-editor.org/info/rfc2578>.
review of this documenti and their insightful comments. We also wish
to thank the entire MANET WG for many reviews of this document.
Further the authors would like to thank James Nguyen for his careful
review and comments on this MIB module and his work on the
definitions of the follow-on MIB modules to configure specific RSSA
algorithms related to SMF. Further, the authors would like to
acknowledge to work of James Nguyen, Brian Little, Ryan Morgan and
Justin Dean on their software development of the SMF-MIB.
14. References [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
58, RFC 2579, April 1999,
<http://www.rfc-editor.org/info/rfc2579>.
14.1. Normative References [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999, <http://www.rfc-editor.org/info/rfc2580>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000,
<http://www.rfc-editor.org/info/rfc2863>.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002, <http://www.rfc-editor.org/info/rfc3411>.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (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 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. [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
Schoenwaelder, Ed., "Textual Conventions for SMIv2", (USM) for version 3 of the Simple Network Management
STD 58, RFC 2579, April 1999. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002,
<http://www.rfc-editor.org/info/rfc3414>.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
"Conformance Statements for SMIv2", STD 58, RFC 2580, Simple Network Management Protocol (SNMP)", STD 62, RFC
April 1999. 3418, December 2002,
<http://www.rfc-editor.org/info/rfc3418>.
[RFC3626] Clausen, T. and P. Jacquet, "Optimized Link State Routing [RFC3626] Clausen, T. and P. Jacquet, "Optimized Link State Routing
Protocol (OLSR)", RFC 3626, October 2003. Protocol (OLSR)", RFC 3626, October 2003,
<http://www.rfc-editor.org/info/rfc3626>.
[RFC5742] Alvestrand, H. and R. Housley, "IESG Procedures for
Handling of Independent and IRTF Stream Submissions",
BCP 92, RFC 5742, December 2009.
[RFC5614] Ogier, R. and P. Spagnolo, "Mobile Ad Hoc Network (MANET)
Extension of OSPF Using Connected Dominating Set (CDS)
Flooding", RFC 5614, August 2009.
[RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621,
May 2012.
14.2. Informative References
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, June 2004. SNMP User-based Security Model", RFC 3826, June 2004,
<http://www.rfc-editor.org/info/rfc3826>.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005,
<http://www.rfc-editor.org/info/rfc4001>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", for the Simple Network Management Protocol (SNMP)", STD
STD 78, RFC 5591, June 2009. 78, RFC 5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, June 2009. Protocol (SNMP)", RFC 5592, June 2009,
<http://www.rfc-editor.org/info/rfc5592>.
[RFC5614] Ogier, R. and P. Spagnolo, "Mobile Ad Hoc Network (MANET)
Extension of OSPF Using Connected Dominating Set (CDS)
Flooding", RFC 5614, August 2009,
<http://www.rfc-editor.org/info/rfc5614>.
[RFC5742] Alvestrand, H. and R. Housley, "IESG Procedures for
Handling of Independent and IRTF Stream Submissions", BCP
92, RFC 5742, December 2009,
<http://www.rfc-editor.org/info/rfc5742>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, July 2011. STD 78, RFC 6353, July 2011,
<http://www.rfc-editor.org/info/rfc6353>.
[RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621,
May 2012, <http://www.rfc-editor.org/info/rfc6621>.
[RFC7181] Clausen, T., Dearlove, C., Jacquet, P., and U. Herberg,
"The Optimized Link State Routing Protocol Version 2", RFC
7181, April 2014,
<http://www.rfc-editor.org/info/rfc7181>.
12.2. Informative References
[RFC4293] Routhier, S., "Management Information Base for the [RFC4293] Routhier, S., "Management Information Base for the
Internet Protocol (IP)", RFC 4293, April 2006. Internet Protocol (IP)", RFC 4293, April 2006,
<http://www.rfc-editor.org/info/rfc4293>.
[RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast
MIB", RFC 5132, December 2007. MIB", RFC 5132, December 2007,
<http://www.rfc-editor.org/info/rfc5132>.
Appendix A. Acknowledgements
*************************************************************** The authors would like to acknowledge the valuable comments from Sean
* Note to the RFC Editor (to be removed prior to publication) * Harnedy in the early phases of the development of this MIB module.
* * The authors would like to thank Adrian Farrel, Dan Romascanu, Juergen
* 1) The reference to RFCXXXX throughout this document point * Shoenwaelder, Stephen Hanna, and Brian Haberman for their careful
* to the current draft-ietf-manet-smf-xx.txt. This needs * review of this document and their insightful comments. We also wish
* to be replaced with the XXXX RFC number for the SMF * to thank the entire MANET WG for many reviews of this document.
* publication. * Further, the authors would like to thank James Nguyen for his careful
* * review and comments on this MIB module and his work on the
* 2) This document also contains the IANA-SMF-MIB module * definitions of the follow-on MIB modules to configure specific RSSAs
* which is defined by this specification above. IANA should * related to SMF. Further, the authors would like to acknowledge the
* take over the IANA-SMF-MIB and keep it synchronized with * work of James Nguyen, Brian Little, Ryan Morgan, and Justin Dean on
* the registries identified within the contained * their software development of the SMF-MIB.
* IANAsmfOpModeIdTC and IANAsmfRssaIdTC TEXTUAL-CONVENTIONs. *
* * Contributors
***************************************************************
This MIB document uses the template authored by D. Harrington that
is based on contributions from the MIB Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn.
Authors' Addresses Authors' Addresses
Robert G. Cole Robert G. Cole
US Army CERDEC US Army CERDEC
6010 Frankford Road 6010 Frankford Road
Aberdeen Proving Ground, Maryland 21005 Aberdeen Proving Ground, Maryland 21005
USA United States
Phone: +1 443 395 8744 Phone: +1 443 395 8744
EMail: robert.g.cole@us.army.mil EMail: robert.g.cole@us.army.mil
Joseph Macker Joseph Macker
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
USA United States
EMail: macker@itd.nrl.navy.mil EMail: macker@itd.nrl.navy.mil
Brian Adamson Brian Adamson
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
USA United States
EMail: adamson@itd.nrl.navy.mil EMail: adamson@itd.nrl.navy.mil
 End of changes. 316 change blocks. 
693 lines changed or deleted 715 lines changed or added

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