draft-ietf-manet-dymo-mib-03.txt   draft-ietf-manet-dymo-mib-04.txt 
Internet Engineering Task Force S. Harnedy Internet Engineering Task Force S. Harnedy
Internet-Draft Booz Allen Hamilton Internet-Draft Booz Allen Hamilton
Intended status: Standards Track R. Cole Intended status: Standards Track R. Cole
Expires: April 28, 2010 Johns Hopkins University Expires: July 23, 2011 US Army CERDEC
I. Chakeres I. Chakeres
CenGen CenGen
October 25, 2009 January 19, 2011
Definition of Managed Objects for the DYMO Manet Routing Protocol Definition of Managed Objects for the DYMO Manet Routing Protocol
draft-ietf-manet-dymo-mib-03 draft-ietf-manet-dymo-mib-04
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the
DYMO routing process. The DYMO-MIB also reports state information,
performance information, and notifications. In addition to
configuration, this additional state, performance and notification
information is useful to management operators troubleshooting DYMO
routing problems.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on July 23, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 28, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This memo defines a portion of the Management Information Base (MIB) described in the Simplified BSD License.
for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the
DYMO routing process. The DYMO-MIB also reports state information,
performance information, and notifications. In addition to
configuration, this additional state and performance information is
useful to management operators troubleshooting DYMO routing problems.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. DYMO Management Model . . . . . . . . . . . . . . . . . . 4 4.1. DYMO 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 Configuration Group . . . . . . . . . . . . . . . . . 6 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 6
5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7
5.3.1. Routing Table . . . . . . . . . . . . . . . . . . . . 7 5.3.1. Routing Table . . . . . . . . . . . . . . . . . . . . 7
5.4. The Statistics Group . . . . . . . . . . . . . . . . . . . 7 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 7
5.5. The Notifications Group . . . . . . . . . . . . . . . . . 8 5.5. The Notifications Group . . . . . . . . . . . . . . . . . 8
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9
6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 9
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Security Considerations . . . . . . . . . . . . . . . . . . . 32 8. Security Considerations . . . . . . . . . . . . . . . . . . . 35
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 35 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 37
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 38
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 38
12.1. Normative References . . . . . . . . . . . . . . . . . . . 35 12.1. Normative References . . . . . . . . . . . . . . . . . . . 38
12.2. Informative References . . . . . . . . . . . . . . . . . . 36 12.2. Informative References . . . . . . . . . . . . . . . . . . 38
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 36 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 39
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 37 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 40
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 40
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
Dynamic MANET On-demand (DYMO) routing [I-D.ietf-manet-dymo] process. Dynamic MANET On-demand (DYMO) routing [I-D.ietf-manet-dymo] process.
The DYMO-MIB also reports state information, performance metrics, and The DYMO-MIB also reports state information, performance metrics, and
notifications. In addition to configuration, this additional state notifications. In addition to configuration, this additional state,
and performance information is useful to management stations performance and notification information is useful to management
troubleshooting routing problems. stations troubleshooting routing problems.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 10 skipping to change at page 4, line 10
A DYMO router's MIB contains DYMO process configuration parameters A DYMO router's MIB contains DYMO process configuration parameters
(e.g. interfaces), state information (e.g. sequence number), (e.g. interfaces), state information (e.g. sequence number),
performance counters (e.g. number of control messages), and performance counters (e.g. number of control messages), and
notifications. notifications.
4.1. DYMO Management Model 4.1. DYMO Management Model
This section describes the management model for the DYMO routing This section describes the management model for the DYMO routing
protocol. protocol.
The MIB is comprised of four Groups, i.e., Notifications, The MIB is comprised of four groups, i.e., Notifications,
Configuration, State and Statistics. The configuration of the Configuration, State and Performance. The configuration of the
managed devices is controlled by the objects in the Configuration managed devices is controlled by the objects in the Configuration
Group. These are divided into Nodal and Interface objects. The bulk Group. These are divided into Nodal and Interface objects. The bulk
of the DYMO configuration is in the Nodal objects which control of the DYMO configuration is in the Nodal objects which control
protocol behavior. The Interface objects merely identify/configure protocol behavior. The Interface objects merely identify/configure
interfaces to enable DYMO routing over their interface. The Nodal interfaces to enable DYMO routing over their interface. The Nodal
objects are further divided into routing (or protocol) objects and objects are further divided into routing (or protocol) objects and
Gateway objects. Gateway objects define other routing prefixes for Gateway objects. Gateway objects define other routing prefixes for
which the node acts as a routing proxy on behalf of these non-local which the node acts as a routing proxy on behalf of these non-local
prefixes. prefixes.
The Configuration Objects drive the behavior of the managed DYMO The Configuration Objects drive the behavior of the managed DYMO
device and hence determines the information in the remaining groups, device and hence determines the information in the remaining groups,
i.e., State, Statistics and Notifications. The State objects i.e., State, Performance and Notifications. The State objects
primarily present the resulting routing table objects. The primarily present the resulting forwarding table objects. The
Statistics group primarily is comprised of counters for monitoring Performance group primarily is comprised of counters for monitoring
the number of DYMO routing messages received locally, per node and the number of DYMO routing messages received locally, per node and
per interface. The Notifications group only contains objects which per interface. The Notifications group contains objects which
monitor changes to the interface configuration and the gateway monitor changes to the interface configuration and the gateway
prefixes configuration. prefixes configuration.
See the below diagram outlining the DYMO-MIB device management model. See the below diagram outlining the DYMO-MIB device management model.
+------------------------------------------+ +------------------------------------------+
| CONFIGURATION GROUP | | CONFIGURATION GROUP |
| | | |
| Nodal Interface | | Nodal Interface |
| | | |
| +-------+ +-------+ +-------+ | | +-------+ +-------+ +-------+ |
| |Gateway| |Routing| |Routing| | | |Gateway| |Routing| |Routing| |
| +-------+ +-------+ +-------+ | | +-------+ +-------+ +-------+ |
| | | |
+------------------------------------------+ +------------------------------------------+
|| || || || || ||
|| || || || || ||
|| || || || || ||
\ / \ / \ / \ / \ / \ /
\/ \/ \/ \/ \/ \/
+-------+ +------------+ +---------------+ +-------+ +-------------+ +---------------+
| STATE | | STATISTICS | | NOTIFICATIONS | | STATE | | PERFORMANCE | | NOTIFICATIONS |
| GROUP | | GROUP | | GROUP | | GROUP | | GROUP | | GROUP |
+-------+ +------------+ +---------------+ +-------+ +-------------+ +---------------+
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 o Configuration Objects - switches, tables, objects which are
initialized to default settings or set through the management initialized to default settings or set through the management
interface defined by this MIB. interface defined by this MIB.
o Tunable Configuration Objects - objects whose values affect timing o Tunable Configuration Objects - objects whose values affect timing
or attempt bounds on the DYMO protocol. or attempt bounds on the DYMO protocol.
o State Objects - automatically generated values which define the o State Objects - automatically generated values which define the
current operating state of the DYMO protocol process in the current operating state of the DYMO protocol process in the
router. router.
o Statistics Objects - automatically generated values which help an o Performance Objects - automatically generated values which help an
operator or automated tool to assess the performance of the DYMO operator or automated tool to assess the performance of the DYMO
protocol process on the router and the overall routing performance protocol process on the router and the overall routing performance
within the DYMO routing domain. within the DYMO routing domain.
5. Structure of the MIB Module 5. Structure of the MIB Module
This section presents the structure of the DYMO MIB module. The This section presents the structure of the DYMO MIB module. The
objects are arranged into the following groups: objects are arranged into the following groups:
o dymoMIBNotifications - defines the notifications associated with o dymoMIBNotifications - defines the notifications associated with
skipping to change at page 6, line 19 skipping to change at page 6, line 19
o o
* Configuration Group - This group contains the DYMO objects that * Configuration Group - This group contains the DYMO objects that
configure specific options that determine the overall configure specific options that determine the overall
performance and operation of the routing protocol for the performance and operation of the routing protocol for the
router device and its interfaces. router device and its interfaces.
* State Group - Contains information describing the current state * State Group - Contains information describing the current state
of the DYMO process such as the DYMO routing table. of the DYMO process such as the DYMO routing table.
* Statistics Group - Contains objects which help to characterize * Performance Group - Contains objects which help to characterize
the performance of the DYMO process, typically statistics the performance of the DYMO process, typically statistics
counters. There are two types of DYMO statistics: global counters. There are two types of DYMO statistics: global
counters and per interface counters. counters and per interface counters.
o dymoMIBConformance - defines minimal and full conformance of o dymoMIBConformance - defines minimal and full conformance of
implementations to this DYMO-MIB. implementations to this DYMO-MIB.
5.1. Textual Conventions 5.1. Textual Conventions
The textual conventions used in the DYMO-MIB are as follows. The The textual conventions used in the DYMO-MIB are as follows. The
RowStatus and TruthValue textual conventions are imported from RFC RowStatus and TruthValue textual conventions are imported from RFC
2579 [RFC2579]. The DymoInterfaceOperStatus is defined within the 2579 [RFC2579]. The DymoInterfaceOperStatus is defined within the
DYMO-MIB. This contains the current operational status of the DYMO DYMO-MIB. This contains the current operational status of the DYMO
interface. interface.
5.2. The Configuration Group 5.2. The Configuration Group
The DYMO device is configured with a set of controls. The list of The DYMO device is configured with a set of controls. The list of
configuration controls for the DYMO device follow. configuration controls for the DYMO device follow.
Protocol Tuning Configuration Parameters: Protocol Configuration Parameters:
o DID
o MSG_HOPLIMIT o MSG_HOPLIMIT
o ROUTE_TIMEOUT o ROUTE_TIMEOUT
o ROUTE_AGE_MIN_TIMEOUT o ROUTE_AGE_MIN_TIMEOUT
o ROUTE_AGE_MAX_TIMEOUT o ROUTE_SEQNUM_AGE_MAX_TIMEOUT
o ROUTE_USED_TIMEOUT o ROUTE_USED_TIMEOUT
o ROUTE_DELETE_TIMEOUT o ROUTE_DELETE_TIMEOUT
o ROUTE_RREQ_WAIT_TIME o ROUTE_RREQ_WAIT_TIME
o RREQ_RETRIES
o UNICAST_MESSAGE_SENT_TIMEOUT o UNICAST_MESSAGE_SENT_TIMEOUT
o MSG_HOPLIMIT
o DISCOVERY_ATTEMPTS_MAX
Protocol Configuration Tables: Protocol Configuration Tables:
o Responsible Hosts - If RESPONSIBLE_ADDRESSES is set to other than
self address, then the DYMO router must be configured with the set
of host addresses for which it is to generate RREP messages.
o Interfaces - If DYMO_INTERFACES is set to other than all, then the o Interfaces - If DYMO_INTERFACES is set to other than all, then the
DYMO router must be told which interfaces to run the DYMO protocol DYMO router must be told which interfaces to run the DYMO protocol
over. This is a table containing the interfaces and associated over. This is a table containing the interfaces and associated
information. information.
o Responsible Hosts - If RESPONSIBLE_ADDRESSES is set to other than
self address, then the DYMO router must be configured with the set
of host addresses for which it is to generate RREP messages.
5.3. The State Group 5.3. The State Group
The State Subtree reports current state information. State The State Subtree reports current state information. State
information from the DYMO-MIB is primarily contained in the 'Routing' information from the DYMO-MIB is primarily contained in the 'Routing'
Table. Table.
5.3.1. Routing Table 5.3.1. Routing Table
The DYMO routing table contains DYMO specific information related to The DYMO routing table contains information related to IP forwarding
IP forwarding entries found in the node's IP forwarding table MIB. entries found by the node's DYMO processes.
DYMO additional information includes the sequence number associated
with the DYMO message which generated the forwarding table entry and
various flags indicating the viability of the routing entry.
5.4. The Statistics Group 5.4. The Performance Group
The Statistics subtree reports primarily counters that relate to DYMO The Performance subtree reports primarily counters that relate to
protocol activity. The DYMO performance statistics consists of per DYMO protocol activity. The DYMO performance objects consists of per
node and per interface objects: node and per interface objects:
o OwnSequenceNumber o OwnSequenceNumber
o RREQ initiated o RREQ initiated
o RREQ sent o RREQ sent
o RREQ received o RREQ received
o RREP initiated o RREP initiated
skipping to change at page 9, line 19 skipping to change at page 9, line 19
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The DYMO-MIB does not entity and certain other system-wide data. The DYMO-MIB does not
duplicate those objects. duplicate those objects.
6.2. MIB modules required for IMPORTS 6.2. MIB modules required for IMPORTS
The DYMO-MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], The DYMO-MIB module IMPORTS objects from SNMPv2-SMI [RFC2578],
SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], INET-ADDRESS-MIB SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], INET-ADDRESS-MIB
[RFC4001] and IF-MIB [RFC2863] [RFC4001] and IF-MIB [RFC2863].
7. Definitions 7. Definitions
MANET-DYMO-MIB DEFINITIONS ::= BEGIN MANET-DYMO-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, mib-2 Counter32, Integer32, Unsigned32, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, RowStatus, TruthValue TEXTUAL-CONVENTION, RowStatus, TruthValue
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
InetAddress, InetAddressType, InetAddress, InetAddressType,
InetAddressPrefixLength InetAddressPrefixLength
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- [RFC4001]
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
; ;
manetDymoMIB MODULE-IDENTITY manetDymoMIB MODULE-IDENTITY
LAST-UPDATED "200910251200Z" -- October 25, 2009 LAST-UPDATED "201101191200Z" -- January 19, 2011
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG Chairs: ian.chakeres@gmail.com WG Chairs: ian.chakeres@gmail.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Sean Harnedy Editors: Sean Harnedy
Booz Allen Hamilton Booz Allen Hamilton
333 City Boulevard West 333 City Boulevard West
Orange, CA 92868 Orange, CA 92868
USA USA
+1 714 938-3898 +1 714 938-3898
harnedy_sean@bah.com harnedy_sean@bah.com
Robert G. Cole Robert G. Cole
Johns Hopkins University US Army CERDEC
Applied Physics Lab and Space and Terrestrial Communications
Department of Computer Science 328 Hopkins Road
11000 Johns Hopkins Road Aberdeen Proving Ground, MD 21005
Laurel, MD 22014
USA USA
+1 443 778-6951 +1 410 278-6779
robert.cole@jhuapl.edu robert.g.cole@us.army.mil
Ian D Chakeres Ian D Chakeres
CenGen CenGen
9250 Bendix Road North 9250 Bendix Road North
Columbia, Maryland 21045 Columbia, Maryland 21045
USA USA
ian.chakeres@gmail.com" ian.chakeres@gmail.com"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions for "This MIB module contains managed object definitions for
the Dynamic MANET On-demand (DYMO) routing protocol as the Dynamic MANET On-demand (DYMO) routing protocol as
defined in: Charkeres,I., and C. Perkins, Dynamic MANET defined in: Chakeres,I., and C. Perkins, Dynamic MANET
On-demand (DYMO) Routing, draft-ietf-manet-dymo-13, On-demand (DYMO) Routing, draft-ietf-manet-dymo-21,
April 10, 2008. July 26, 2010.
Copyright (C) The IETF Trust (2008). This version Copyright (C) The IETF Trust (2008). This version
of this MIB module is part of RFC xxxx; see the RFC of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices." itself for full legal notices."
-- Revision History -- Revision History
REVISION "201101191200Z" -- January 19, 2011
DESCRIPTION
"Fifth draft of this MIB module published as
draft-ietf-manet-dymo-mib-04.txt.
Changes include:
- Incorporated the DYMO ID by adding Instance
Table.
- Added dymoSetNotification for improved control
of DYMO Notifications.
- Updated various object names to be consistent
with current draft-ietf-manet-dymo-21.
"
REVISION "200910251200Z" -- October 25, 2009 REVISION "200910251200Z" -- October 25, 2009
DESCRIPTION DESCRIPTION
"Fourth draft of this MIB module published as "Fourth draft of this MIB module published as
draft-ietf-manet-dymo-mib-03.txt. draft-ietf-manet-dymo-mib-03.txt.
- Minor changes to textual material, including - Minor changes to textual material, including
additions to the IMPORTS text. additions to the IMPORTS text.
- Added DEFVAL clauses to all read-write - Added DEFVAL clauses to all read-write
configuration objects with defaults identified configuration objects with defaults identified
in the DYMO draft." in the DYMO draft."
REVISION "200902241200Z" -- February 24, 2009 REVISION "200902241200Z" -- February 24, 2009
skipping to change at page 12, line 19 skipping to change at page 12, line 30
-- --
dymoConfigurationGroup OBJECT IDENTIFIER ::= { dymoMIBObjects 1 } dymoConfigurationGroup OBJECT IDENTIFIER ::= { dymoMIBObjects 1 }
-- --
-- DYMO Global Router Configuration Group -- DYMO Global Router Configuration Group
-- --
dymoRouterConfigGroup OBJECT IDENTIFIER ::= {dymoConfigurationGroup 1} dymoRouterConfigGroup OBJECT IDENTIFIER ::= {dymoConfigurationGroup 1}
dymoAdminStatus OBJECT-TYPE dymoInstanceTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoInstanceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO Instance Table describes the DYMO
...."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, July 2010. The DID."
::= { dymoRouterConfigGroup 1 }
dymoInstanceEntry OBJECT-TYPE
SYNTAX DymoInstanceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO instance entry describes one DYMO
process as indexed by its DID."
INDEX { dymoInstanceIndex }
::= { dymoInstanceTable 1 }
DymoInstanceEntry ::=
SEQUENCE {
dymoInstanceIndex
Integer32,
dymoInstanceDid
Integer32,
dymoInstanceAdminStatus
Status,
dymoInstanceRowStatus
RowStatus
}
dymoInstanceIndex OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The instance index for this DYMO process."
::= { dymoInstanceEntry 1 }
dymoInstanceDid OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The DYMO ID of this instance of the
DYMO process.
"
::= { dymoInstanceEntry 2 }
dymoInstanceAdminStatus OBJECT-TYPE
SYNTAX Status SYNTAX Status
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative status of DYMO in the "The administrative status of this DYMO
router. The value 'enabled' denotes that the process in the router. Multiple processes are
allowed. The value 'enabled' denotes that the
DYMO Process is active on at least one interface; DYMO Process is active on at least one interface;
'disabled' disables it on all interfaces. 'disabled' disables it on all interfaces.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to non-volatile storage." the entity SHOULD save the change to non-volatile storage."
::= { dymoRouterConfigGroup 1 } ::= { dymoInstanceEntry 3 }
dymoInstanceRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object permits management of the table
by facilitating actions such as row creation,
construction, and destruction. The value of
this object has no effect on whether other
objects in this conceptual row can be
modified."
::= { dymoInstanceEntry 4 }
dymoMaxHopLimit OBJECT-TYPE dymoMaxHopLimit OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
UNITS "hops" UNITS "hops"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of hops. The suggested value "The maximum number of hops. The suggested value
default is 10 hops. This is the DYMO MSG_HOPLIMIT default is 10 hops. This is the DYMO MSG_HOPLIMIT
parameter value." parameter value."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 10 } DEFVAL { 10 }
::= { dymoRouterConfigGroup 2 } ::= { dymoRouterConfigGroup 2 }
dymoRouteTimeout OBJECT-TYPE dymoRouteTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The route timeout value. The suggested default "The route timeout value. The suggested default
value is 5000 milliseconds. This is the value is 5000 milliseconds. This is the
DYMO ROUTE_TIMEOUT parameter value." DYMO ROUTE_TIMEOUT parameter value."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 5000 } DEFVAL { 5000 }
::= { dymoRouterConfigGroup 3 } ::= { dymoRouterConfigGroup 3 }
dymoRouteAgeMinTimeout OBJECT-TYPE dymoRouteAgeMinTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum route age timeout value. The "The minimum route age timeout value. The
suggested default value is 1000 milliseconds. suggested default value is 1000 milliseconds.
This is the DYMO ROUTE_AGE_MIN_TIMEOUT parameter This is the DYMO ROUTE_AGE_MIN_TIMEOUT parameter
value." value."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 1000 } DEFVAL { 1000 }
::= { dymoRouterConfigGroup 4 } ::= { dymoRouterConfigGroup 4 }
dymoRouteAgeMaxTimeout OBJECT-TYPE dymoRouteSeqnumAgeMaxTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum route age timeout value. The "The maximum route age timeout value. The
suggested default value is 60,000 milliseconds. suggested default value is 60,000 milliseconds.
This is the DYMO ROUTE_AGE_MAX_TIMEOUT parameter This is the DYMO ROUTE_SEQNUM_AGE_MAX_TIMEOUT
value." parameter value."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 60000 } DEFVAL { 60000 }
::= { dymoRouterConfigGroup 5 } ::= { dymoRouterConfigGroup 5 }
dymoRouteUsedTimeout OBJECT-TYPE dymoRouteUsedTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The route used timeout value. The "The route used timeout value. The
suggested default value is 5000 suggested default value is to set this
milliseconds (the same default as to the dymoRouteTimeout object value
the dymoRouteTimeout value). This (whose default is 5000 milliseconds). This
is the DYMO ROUTE_USED_TIMEOUT parameter is the DYMO ROUTE_USED_TIMEOUT parameter
value." value."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 5000 } DEFVAL { 5000 }
::= { dymoRouterConfigGroup 6 } ::= { dymoRouterConfigGroup 6 }
dymoRouteDeleteTimeout OBJECT-TYPE dymoRouteDeleteTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The route delete timeout value. The "The route delete timeout value. The
suggested default value is 10,000 suggested default value is 2 * dymoRouteTimeout
milliseconds (this is 2 * dymoRouteTimeout value (which is equal to 10000 milliseconds
value). This is the DYMO ROUTE_DELETE_TIMEOUT if using the default value for the
parameter value." dymoRouteTimeout value). This is the
DYMO ROUTE_DELETE_TIMEOUT parameter value."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 10000 } DEFVAL { 10000 }
::= { dymoRouterConfigGroup 7 } ::= { dymoRouterConfigGroup 7 }
dymoRouteRreqWaitTime OBJECT-TYPE dymoRouteRreqWaitTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Route Request wait time. The suggested default "The Route Request wait time. The suggested default
value is 2000 milliseconds. This is the DYMO value is 2000 milliseconds. This is the DYMO
ROUTE_RREQ_WAIT_TIME parameter value." ROUTE_RREQ_WAIT_TIME parameter value."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 2000 } DEFVAL { 2000 }
::= { dymoRouterConfigGroup 8 } ::= { dymoRouterConfigGroup 8 }
dymoRreqTries OBJECT-TYPE dymoDiscoveryAttemptsMax OBJECT-TYPE
SYNTAX Unsigned32 (1..16) SYNTAX Unsigned32 (1..16)
UNITS "attempts" UNITS "attempts"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Route Request retry attempts. The "The number of Route Request retry attempts. The
suggested default value is 3. This is the suggested default value is 3. This is the
DYMO RREQ_TRIES parameter value." DYMO DISCOVERY_ATTEMPTS_MAX parameter value."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 3 } DEFVAL { 3 }
::= { dymoRouterConfigGroup 9 } ::= { dymoRouterConfigGroup 9 }
dymoUnicastMsgSentTimeout OBJECT-TYPE dymoUnicastMsgSentTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The message sent timeout value for unicast packets. "The message sent timeout value for unicast packets.
The suggested default value is 1000 milliseconds. The suggested default value is 1000 milliseconds.
This is the DYMO UNICAST_MESSAGE_SENT_TIMEOUT This is the DYMO UNICAST_MESSAGE_SENT_TIMEOUT
parameter value." parameter value."
skipping to change at page 15, line 37 skipping to change at page 17, line 16
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The message sent timeout value for unicast packets. "The message sent timeout value for unicast packets.
The suggested default value is 1000 milliseconds. The suggested default value is 1000 milliseconds.
This is the DYMO UNICAST_MESSAGE_SENT_TIMEOUT This is the DYMO UNICAST_MESSAGE_SENT_TIMEOUT
parameter value." parameter value."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 1000 } DEFVAL { 1000 }
::= { dymoRouterConfigGroup 10 } ::= { dymoRouterConfigGroup 10 }
-- --
-- DYMO Interfaces Configuration Table -- DYMO Interfaces Configuration Table
-- --
dymoInterfaceTable OBJECT-TYPE dymoInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoInterfaceEntry SYNTAX SEQUENCE OF DymoInterfaceEntry
skipping to change at page 17, line 35 skipping to change at page 19, line 15
SYNTAX SEQUENCE OF DymoResponsibleAddrEntry SYNTAX SEQUENCE OF DymoResponsibleAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DYMO Responsible Address Table is a "The DYMO Responsible Address Table is a
list of IP address prefixes, and their list of IP address prefixes, and their
associated prefix length for which the associated prefix length for which the
DYMO router is responsible." DYMO router is responsible."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, July 2010. Table 3 Important
Settings." Settings."
::= { dymoConfigurationGroup 3 } ::= { dymoConfigurationGroup 3 }
dymoResponsibleAddrEntry OBJECT-TYPE dymoResponsibleAddrEntry OBJECT-TYPE
SYNTAX DymoResponsibleAddrEntry SYNTAX DymoResponsibleAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A single host address range. Information "A single host address range. Information
in this table is persistent and when this object in this table is persistent and when this object
is written, the entity SHOULD save the change to is written, the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, July 2010. Table 3 Important
Settings." Settings."
INDEX { dymoResponsibleAddrIndex } INDEX { dymoResponsibleAddrIndex }
::= { dymoResponsibleAddrTable 1 } ::= { dymoResponsibleAddrTable 1 }
DymoResponsibleAddrEntry ::= DymoResponsibleAddrEntry ::=
SEQUENCE { SEQUENCE {
dymoResponsibleAddrIndex dymoResponsibleAddrIndex
Unsigned32, Unsigned32,
dymoResponsibleAddrType dymoResponsibleAddrType
InetAddressType, InetAddressType,
skipping to change at page 18, line 39 skipping to change at page 20, line 18
dymoResponsibleAddrType OBJECT-TYPE dymoResponsibleAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the dymoResponsibleAddr, as defined "The type of the dymoResponsibleAddr, as defined
in the InetAddress MIB [RFC 4001]." in the InetAddress MIB [RFC 4001]."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, July 2010. Table 3 Important
Settings." Settings."
::= { dymoResponsibleAddrEntry 2 } ::= { dymoResponsibleAddrEntry 2 }
dymoResponsibleAddr OBJECT-TYPE dymoResponsibleAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination IP address of this route. The type "The destination IP address of this route. The type
of this address is determined by the value of the of this address is determined by the value of the
dymoResponsibleAddrType object." dymoResponsibleAddrType object."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, July 2010. Table 3 Important
Settings." Settings."
::= { dymoResponsibleAddrEntry 3 } ::= { dymoResponsibleAddrEntry 3 }
dymoResponsibleAddrPrefixLen OBJECT-TYPE dymoResponsibleAddrPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of leading one bits that form the "Indicates the number of leading one bits that form the
mask to be logical-ANDed with the destination address mask to be logical-AND'd with the destination address
before being compared to the value in the dymoResonsibleAddr before being compared to the value in the dymoResonsibleAddr
field." field."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, July 2010. Table 3 Important
Settings." Settings."
::= { dymoResponsibleAddrEntry 4 } ::= { dymoResponsibleAddrEntry 4 }
dymoResponsibleAddrRowStatus OBJECT-TYPE dymoResponsibleAddrRowStatus 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 the table "This object permits management of the table
by facilitating actions such as row creation, by facilitating actions such as row creation,
skipping to change at page 20, line 30 skipping to change at page 22, line 9
dymoRoutingTable OBJECT-TYPE dymoRoutingTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoRoutingEntry SYNTAX SEQUENCE OF DymoRoutingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DYMO Routing Table describes the "The DYMO Routing Table describes the
current routing information learned current routing information learned
via DYMO control messages." via DYMO control messages."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested I., and C. Perkins, July 2010. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoStateGroup 2 } ::= { dymoStateGroup 2 }
dymoRoutingEntry OBJECT-TYPE dymoRoutingEntry OBJECT-TYPE
SYNTAX DymoRoutingEntry SYNTAX DymoRoutingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DYMO routing entry contains a "The DYMO routing entry contains a
piece of routing information for a piece of routing information for a
skipping to change at page 21, line 31 skipping to change at page 23, line 10
} }
dymoRoutingIpAddrType OBJECT-TYPE dymoRoutingIpAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The routing table address IP address type." "The routing table address IP address type."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, July 2010. Table 3 Important
Settings." Settings."
::= { dymoRoutingEntry 1 } ::= { dymoRoutingEntry 1 }
dymoRoutingIpAddr OBJECT-TYPE dymoRoutingIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The routing table Inet IPv4 or IPv6 address." "The routing table Inet IPv4 or IPv6 address."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, July 2010. Table 3 Important
Settings." Settings."
::= { dymoRoutingEntry 2 } ::= { dymoRoutingEntry 2 }
dymoRoutingPrefixLen OBJECT-TYPE dymoRoutingPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
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."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, July 2010. Table 3 Important
Settings." Settings."
::= { dymoRoutingEntry 3 } ::= { dymoRoutingEntry 3 }
dymoRoutingSeqNum OBJECT-TYPE dymoRoutingSeqNum OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface sequence number. This "The interface sequence number. This
is the DYMO SeqNum associated with this is the DYMO SeqNum associated with this
skipping to change at page 23, line 31 skipping to change at page 25, line 10
"The Broken Flag indicates whether "The Broken Flag indicates whether
this Route is broken. This flag is set this Route is broken. This flag is set
if the next-hop becomes unreachable or if the next-hop becomes unreachable or
in response to processing a RERR. A value in response to processing a RERR. A value
'true(1)' indicates that this route is 'true(1)' indicates that this route is
broken, while a value 'false(2)' broken, while a value 'false(2)'
indicates that it is not broken." indicates that it is not broken."
::= { dymoRoutingEntry 9 } ::= { dymoRoutingEntry 9 }
dymoRoutingDist OBJECT-TYPE dymoRoutingDist OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (0..65535)
UNITS "hops" UNITS "hops"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The distance to the destination address's "The distance to the destination address's
DYMO router. This is a metric of the DYMO router. This is a metric of the
distance a message or piece of information distance a message or piece of information
has traversed. The minimum value of distance has traversed. The minimum value of distance
is the number of IP hops traversed. The is the number of IP hops traversed. The
maximum value is 65,535." maximum value is 65,535.
This parameter is an optional field in the
DYMO routing table. If the DYMO Route.Dist
is not supported by this device, then this
object should be set to '0'."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, "Dynamic MANET On-demand (DYMO) Routing,
Chakeres, I., and C. Perkins, April Chakeres, I., and C. Perkins, April
2008. Section 3 Terminology." 2008. Section 3 Terminology."
::= { dymoRoutingEntry 10 } ::= { dymoRoutingEntry 10 }
-- --
-- DYMO Statistics Group (Performance Management) -- DYMO Performance Group (Performance Management)
-- --
-- Contains objects which help to characterize the -- Contains objects which help to characterize the
-- performance of the DYMO process, typically statistics -- performance of the DYMO process, typically statistics
-- counters. There are two types of DYMO statistics: -- counters. There are two types of DYMO statistics:
-- global counters and per interface counters. -- global counters and per interface counters.
-- --
dymoStatisticsGroup OBJECT IDENTIFIER ::= { dymoMIBObjects 3 } dymoPerformanceGroup OBJECT IDENTIFIER ::= { dymoMIBObjects 3 }
dymoGlobalStatsGroup OBJECT IDENTIFIER ::= { dymoStatisticsGroup 1 } dymoGlobalPerfGroup OBJECT IDENTIFIER ::= { dymoPerformanceGroup 1 }
dymoRreqOriginated OBJECT-TYPE dymoRreqOriginated OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREQ messages that this DYMO RREQ messages that this DYMO
device has initiated." device has initiated."
::= { dymoGlobalStatsGroup 1 } ::= { dymoGlobalPerfGroup 1 }
dymoRreqForwarded OBJECT-TYPE dymoRreqForwarded OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREQ messages that this DYMO RREQ messages that this DYMO
device has forwarded, i.e., this device has forwarded, i.e., this
device neither originated or device neither originated or
terminated the RREQ message." terminated the RREQ message."
::= { dymoGlobalStatsGroup 2 } ::= { dymoGlobalPerfGroup 2 }
dymoRreqReceived OBJECT-TYPE dymoRreqReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREQ messages that this DYMO RREQ messages that this DYMO
device has received as the device has received as the
target of the message." target of the message."
::= { dymoGlobalStatsGroup 3 } ::= { dymoGlobalPerfGroup 3 }
dymoRrepOriginated OBJECT-TYPE dymoRrepOriginated OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREP messages that this DYMO RREP messages that this DYMO
device has initiated." device has initiated."
::= { dymoGlobalStatsGroup 4 } ::= { dymoGlobalPerfGroup 4 }
dymoRrepForwarded OBJECT-TYPE dymoRrepForwarded OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREP messages that this DYMO RREP messages that this DYMO
device has forwarded, i.e, this device has forwarded, i.e, this
device neither originated or device neither originated or
terminated the RREP message." terminated the RREP message."
::= { dymoGlobalStatsGroup 5 } ::= { dymoGlobalPerfGroup 5 }
dymoRrepReceived OBJECT-TYPE dymoRrepReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREP messages that this DYMO RREP messages that this DYMO
device has received as the device has received as the
target of the message." target of the message."
::= { dymoGlobalStatsGroup 6 } ::= { dymoGlobalPerfGroup 6 }
dymoRrerOriginated OBJECT-TYPE dymoRrerOriginated OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RRER messages that this DYMO RRER messages that this DYMO
device has initiated." device has initiated."
::= { dymoGlobalStatsGroup 7 } ::= { dymoGlobalPerfGroup 7 }
dymoRrerForwarded OBJECT-TYPE dymoRrerForwarded OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RRER messages that this DYMO RRER messages that this DYMO
device has forwarded, i.e., this device has forwarded, i.e., this
device neither originated or device neither originated or
terminated the RRER message." terminated the RRER message."
::= { dymoGlobalStatsGroup 8 } ::= { dymoGlobalPerfGroup 8 }
dymoRrerReceived OBJECT-TYPE dymoRrerReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RRER messages that this DYMO RRER messages that this DYMO
device has received as the device has received as the
target of the message." target of the message."
::= { dymoGlobalStatsGroup 9 } ::= { dymoGlobalPerfGroup 9 }
-- --
-- Per DYMO Interface Statistics Table -- Per DYMO Interface Performance Table
-- --
dymoInterfaceStatsGroup OBJECT IDENTIFIER ::= {dymoStatisticsGroup 2} dymoInterfacePerfGroup OBJECT IDENTIFIER ::= {dymoPerformanceGroup 2}
dymoInterfaceStatsTable OBJECT-TYPE dymoInterfacePerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoInterfaceStatsEntry SYNTAX SEQUENCE OF DymoInterfacePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DYMO Interface Statistics Table "The DYMO Interface Performance Table
describes the DYMO statistics per describes the DYMO statistics per
interface." interface."
::= { dymoInterfaceStatsGroup 1 } ::= { dymoInterfacePerfGroup 1 }
dymoInterfaceStatsEntry OBJECT-TYPE dymoInterfacePerfEntry OBJECT-TYPE
SYNTAX DymoInterfaceStatsEntry SYNTAX DymoInterfacePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DYMO Interface Statistics entry "The DYMO Interface Performance entry
describes the statistics for a particular describes the statistics for a particular
DYMO interface." DYMO interface."
INDEX { dymoIfStatsIfIndex } INDEX { dymoIfPerfIfIndex }
::= { dymoInterfaceStatsTable 1 } ::= { dymoInterfacePerfTable 1 }
DymoInterfaceStatsEntry ::= DymoInterfacePerfEntry ::=
SEQUENCE { SEQUENCE {
dymoIfStatsIfIndex dymoIfPerfIfIndex
InterfaceIndexOrZero, InterfaceIndexOrZero,
dymoIfRreqOriginated dymoIfRreqOriginated
Counter32, Counter32,
dymoIfRreqForwarded dymoIfRreqForwarded
Counter32, Counter32,
dymoIfRreqReceived dymoIfRreqReceived
Counter32, Counter32,
dymoIfRrepOriginated dymoIfRrepOriginated
Counter32, Counter32,
dymoIfRrepForwarded dymoIfRrepForwarded
skipping to change at page 27, line 23 skipping to change at page 29, line 7
dymoIfRrepReceived dymoIfRrepReceived
Counter32, Counter32,
dymoIfRrerOriginated dymoIfRrerOriginated
Counter32, Counter32,
dymoIfRrerForwarded dymoIfRrerForwarded
Counter32, Counter32,
dymoIfRrerReceived dymoIfRrerReceived
Counter32 Counter32
} }
dymoIfStatsIfIndex OBJECT-TYPE dymoIfPerfIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex for this DYMO interface "The ifIndex for this DYMO interface
that is collecting this set of that is collecting this set of
performance management statistics." performance management statistics."
::= { dymoInterfaceStatsEntry 1 } ::= { dymoInterfacePerfEntry 1 }
dymoIfRreqOriginated OBJECT-TYPE dymoIfRreqOriginated OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREQ messages that this DYMO RREQ messages that this DYMO
interface has initiated." interface has initiated."
::= { dymoInterfaceStatsEntry 2 } ::= { dymoInterfacePerfEntry 2 }
dymoIfRreqForwarded OBJECT-TYPE dymoIfRreqForwarded OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREQ messages that this DYMO RREQ messages that this DYMO
interface has forwarded, i.e., this interface has forwarded, i.e., this
interface neither originated nor interface neither originated nor
terminated the RREQ message." terminated the RREQ message."
::= { dymoInterfaceStatsEntry 3 } ::= { dymoInterfacePerfEntry 3 }
dymoIfRreqReceived OBJECT-TYPE dymoIfRreqReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREQ messages that this DYMO RREQ messages that this DYMO
interface has received as the interface has received as the
target of the message." target of the message."
::= { dymoInterfaceStatsEntry 4 } ::= { dymoInterfacePerfEntry 4 }
dymoIfRrepOriginated OBJECT-TYPE dymoIfRrepOriginated OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREP messages that this DYMO RREP messages that this DYMO
interface has initiated." interface has initiated."
::= { dymoInterfaceStatsEntry 5 } ::= { dymoInterfacePerfEntry 5 }
dymoIfRrepForwarded OBJECT-TYPE dymoIfRrepForwarded OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREP messages that this DYMO RREP messages that this DYMO
interface has forwarded, i.e., this interface has forwarded, i.e., this
interface neither originated nor interface neither originated nor
terminated the RREP message." terminated the RREP message."
::= { dymoInterfaceStatsEntry 6 } ::= { dymoInterfacePerfEntry 6 }
dymoIfRrepReceived OBJECT-TYPE dymoIfRrepReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RREP messages that this DYMO RREP messages that this DYMO
interface has received as the interface has received as the
target of the message." target of the message."
::= { dymoInterfaceStatsEntry 7 } ::= { dymoInterfacePerfEntry 7 }
dymoIfRrerOriginated OBJECT-TYPE dymoIfRrerOriginated OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RRER messages that this DYMO RRER messages that this DYMO
interface has initiated." interface has initiated."
::= { dymoInterfaceStatsEntry 8 } ::= { dymoInterfacePerfEntry 8 }
dymoIfRrerForwarded OBJECT-TYPE dymoIfRrerForwarded OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RRER messages that this DYMO RRER messages that this DYMO
interface has forwarded, i.e., this interface has forwarded, i.e., this
interface neither originated nor interface neither originated nor
terminated the RRER message." terminated the RRER message."
::= { dymoInterfaceStatsEntry 9 } ::= { dymoInterfacePerfEntry 9 }
dymoIfRrerReceived OBJECT-TYPE dymoIfRrerReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
RRER messages that this DYMO RRER messages that this DYMO
interface has received as the interface has received as the
target of the message." target of the message."
::= { dymoInterfaceStatsEntry 10 } ::= { dymoInterfacePerfEntry 10 }
-- --
-- Notifications -- Notifications
-- --
dymoAdminStatusChange NOTIFICATION-TYPE dymoMIBNotifControl OBJECT IDENTIFIER ::= { dymoMIBNotifications 1 }
OBJECTS { dymoAdminStatus } dymoMIBNotifObjects OBJECT IDENTIFIER ::= { dymoMIBNotifications 2 }
-- dymoMIBNotifControl
dymoSetNotification OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(4))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A 4-octet string serving as a bit map for
the notification events defined by the DYMO
notifications. This object is used to enable
and disable specific DYMO notifications where
a 1 in the bit field represents enabled. The
right-most bit (least significant) represents
notification 0.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { dymoMIBNotifControl 1 }
-- dymoMIBNotifObjects
dymoInstanceAdminStatusChange NOTIFICATION-TYPE
OBJECTS { dymoInstanceAdminStatus,
dymoInstanceDid
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the "This notification is generated when the
administrative status of a DYMO router changes." administrative status of a DYMO process changes."
::= { dymoMIBNotifications 1 } ::= { dymoMIBNotifObjects 1 }
dymoInterfaceAdminStatusChange NOTIFICATION-TYPE dymoInterfaceAdminStatusChange NOTIFICATION-TYPE
OBJECTS { dymoIfAdminStatus } OBJECTS { dymoIfAdminStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the "This notification is generated when the
administrative status of a DYMO interface changes." administrative status of a DYMO interface changes."
::= { dymoMIBNotifications 2 } ::= { dymoMIBNotifObjects 2 }
dymoResponsibleAddrEntryChange NOTIFICATION-TYPE dymoResponsibleAddrEntryChange NOTIFICATION-TYPE
OBJECTS { dymoResponsibleAddrRowStatus } OBJECTS { dymoResponsibleAddrRowStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the status "This notification is generated when the status
of an entry in the DYMO Responsible Address of an entry in the DYMO Responsible Address
Table changes. This includes the creation or Table changes. This includes the creation or
deletion of a row." deletion of a row."
::= { dymoMIBNotifications 3 } ::= { dymoMIBNotifObjects 3 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
dymoCompliances OBJECT IDENTIFIER ::= { dymoMIBConformance 1 } dymoCompliances OBJECT IDENTIFIER ::= { dymoMIBConformance 1 }
dymoMIBGroups OBJECT IDENTIFIER ::= { dymoMIBConformance 2 } dymoMIBGroups OBJECT IDENTIFIER ::= { dymoMIBConformance 2 }
dymoBasicCompliance MODULE-COMPLIANCE dymoBasicCompliance MODULE-COMPLIANCE
STATUS current STATUS current
skipping to change at page 30, line 42 skipping to change at page 33, line 10
::= { dymoCompliances 1 } ::= { dymoCompliances 1 }
dymoFullCompliance MODULE-COMPLIANCE dymoFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The full implementation requirements for managed DESCRIPTION "The full implementation requirements for managed
network entities that implement the DYMO routing network entities that implement the DYMO routing
protocol." protocol."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dymoConfigObjectsGroup, MANDATORY-GROUPS { dymoConfigObjectsGroup,
dymoStateObjectsGroup, dymoStateObjectsGroup,
dymoStatsObjectsGroup, dymoPerfObjectsGroup,
dymoNotifObjectsGroup } dymoNotifObjectsGroup,
dymoNotificationGroup }
::= { dymoCompliances 2 } ::= { dymoCompliances 2 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
dymoConfigObjectsGroup OBJECT-GROUP dymoConfigObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dymoAdminStatus, dymoInstanceAdminStatus,
dymoInstanceDid,
dymoInstanceRowStatus,
dymoMaxHopLimit, dymoMaxHopLimit,
dymoRouteTimeout, dymoRouteTimeout,
dymoRouteAgeMinTimeout, dymoRouteAgeMinTimeout,
dymoRouteAgeMaxTimeout, dymoRouteSeqnumAgeMaxTimeout,
dymoRouteUsedTimeout, dymoRouteUsedTimeout,
dymoRouteDeleteTimeout, dymoRouteDeleteTimeout,
dymoRouteRreqWaitTime, dymoRouteRreqWaitTime,
dymoRreqTries, dymoDiscoveryAttemptsMax,
dymoUnicastMsgSentTimeout, dymoUnicastMsgSentTimeout,
dymoIfAdminStatus, dymoIfAdminStatus,
dymoIfRowStatus, dymoIfRowStatus,
dymoResponsibleAddrType, dymoResponsibleAddrType,
dymoResponsibleAddr, dymoResponsibleAddr,
dymoResponsibleAddrPrefixLen, dymoResponsibleAddrPrefixLen,
dymoResponsibleAddrRowStatus dymoResponsibleAddrRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 31, line 44 skipping to change at page 34, line 15
dymoRoutingForwardingFlag, dymoRoutingForwardingFlag,
dymoRoutingBrokenFlag, dymoRoutingBrokenFlag,
dymoRoutingDist dymoRoutingDist
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of DYMO state objects implemented "Set of DYMO state objects implemented
in this module." in this module."
::= { dymoMIBGroups 2 } ::= { dymoMIBGroups 2 }
dymoStatsObjectsGroup OBJECT-GROUP dymoPerfObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dymoRreqOriginated, dymoRreqOriginated,
dymoRreqForwarded, dymoRreqForwarded,
dymoRreqReceived, dymoRreqReceived,
dymoRrepOriginated, dymoRrepOriginated,
dymoRrepForwarded, dymoRrepForwarded,
dymoRrepReceived, dymoRrepReceived,
dymoRrerOriginated, dymoRrerOriginated,
dymoRrerForwarded, dymoRrerForwarded,
dymoRrerReceived, dymoRrerReceived,
skipping to change at page 32, line 23 skipping to change at page 34, line 42
dymoIfRrerOriginated, dymoIfRrerOriginated,
dymoIfRrerForwarded, dymoIfRrerForwarded,
dymoIfRrerReceived dymoIfRrerReceived
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of DYMO statistic objects implemented "Set of DYMO statistic objects implemented
in this module for performance management." in this module for performance management."
::= { dymoMIBGroups 3 } ::= { dymoMIBGroups 3 }
dymoNotifObjectsGroup NOTIFICATION-GROUP dymoNotifObjectsGroup OBJECT-GROUP
OBJECTS {
dymoSetNotification
}
STATUS current
DESCRIPTION
"Set of DYMO notifications objects implemented
in this module."
::= { dymoMIBGroups 4 }
dymoNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
dymoAdminStatusChange, dymoInstanceAdminStatusChange,
dymoInterfaceAdminStatusChange, dymoInterfaceAdminStatusChange,
dymoResponsibleAddrEntryChange dymoResponsibleAddrEntryChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of DYMO notifications implemented in this "Set of DYMO notifications implemented in this
module." module."
::= { dymoMIBGroups 4 } ::= { dymoMIBGroups 5 }
END END
8. Security Considerations 8. Security Considerations
[TODO] Each specification that defines one or more MIB modules MUST [TODO] Each specification that defines one or more MIB modules MUST
contain a section that discusses security considerations relevant to contain a section that discusses security considerations relevant to
those modules. This section MUST be patterned after the latest those modules. This section MUST be patterned after the latest
approved template (available at approved template (available at
http://www.ops.ietf.org/mib-security.html). Remember that the http://www.ops.ietf.org/mib-security.html). Remember that the
skipping to change at page 36, line 12 skipping to change at page 38, line 43
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for Schoenwaelder, Ed., "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2580] McCloghrie, K., Perkins, D., and J.
Schoenwaelder, "Conformance Statements for Schoenwaelder, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[I-D.ietf-manet-dymo] Chakeres, I. and C. Perkins, "Dynamic MANET [I-D.ietf-manet-dymo] Chakeres, I. and C. Perkins, "Dynamic MANET
On-demand (DYMO) Routing", On-demand (DYMO) Routing",
draft-ietf-manet-dymo-17 (work in progress), draft-ietf-manet-dymo-21 (work in progress),
March 2009. July 2010.
12.2. Informative References 12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. [RFC3410] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction and Applicability Stewart, "Introduction and Applicability
Statements for Internet-Standard Management Statements for Internet-Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
Appendix A. Change Log Appendix A. Change Log
skipping to change at page 37, line 11 skipping to change at page 39, line 39
These changes were made from draft-ietf-manet-dymo-mib-02 to These changes were made from draft-ietf-manet-dymo-mib-02 to
draft-ietf-manet-dymo-mib-03. draft-ietf-manet-dymo-mib-03.
1. Minor changes to the textual material and added to the IMPORTS 1. Minor changes to the textual material and added to the IMPORTS
text in the introductory material. text in the introductory material.
2. Added DEFVAL clauses to all read-write configuration objects 2. Added DEFVAL clauses to all read-write configuration objects
having default values identified in the DYMO specification. having default values identified in the DYMO specification.
These changes were made from draft-ietf-manet-dymo-mib-03 to
draft-ietf-manet-dymo-mib-04.
1. Incorporated the DID into the Configuration Group by changing the
dymoAdminStatus object to an Instance Table. This allows for the
presence of multiple DYMO processes concurrent on the same
router.
2. Added the dymoNotifObjectsGroup and its dymoSetNotifications
object to allow for individual control of the DYMO Notifications.
Updated the Conformance sections accordingly.
3. Renamed several of the Configuration Objects to be consistent
with the naming within the current draft-ietf-manet-dymo-21.
Appendix B. Open Issues Appendix B. Open Issues
This section contains the set of open issues related to the This section contains the set of open issues related to the
development and design of the DYMO-MIB. This section will not be development and design of the DYMO-MIB. This section will not be
present in the final version of the MIB and will be removed once all present in the final version of the MIB and will be removed once all
the open issues have been resolved. the open issues have been resolved.
1. Will DYMO require an MANET_ID (Instance ID) for running multiple 1. Work on the Security Section. This MIB does have settable
DYMO processes over the same interfaces?
2. Incorporate MIB-II IpGroup interworking with DymoIfTable. (Note:
We have looked into the current IpForwarding Table and it is not
clear how this table can be extended through a 'delta' table
within this MIB. Hence, we currently have a full DYMO forwarding
table in this MIB.)
3. Work on the Security Section. This MIB does have settable
objects, but not sensitive objects (true?). objects, but not sensitive objects (true?).
4. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 2. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB.
5. Identify all objects requiring non-volatile storage in their
DESCRIPTION clauses.
6. Incorporate parameter relationship conditions into their
DESCRIPTION clauses.
7. Cleanup all the [TODOs] from the MIB template. 3. Cleanup all the [TODOs] from the MIB template.
Appendix C. Appendix C.
*************************************************************** ***************************************************************
* Note to the RFC Editor (to be removed prior to publication) * * Note to the RFC Editor (to be removed prior to publication) *
* * * *
* 1) The reference to RFCXXXX within the DESCRIPTION clauses * * 1) The reference to RFCXXXX within the DESCRIPTION clauses *
* of the MIB module point to this draft and are to be * * of the MIB module point to this draft and are to be *
* assigned by the RFC Editor. * * assigned by the RFC Editor. *
* * * *
skipping to change at page 38, line 30 skipping to change at page 41, line 4
Authors' Addresses Authors' Addresses
Sean Harnedy Sean Harnedy
Booz Allen Hamilton Booz Allen Hamilton
333 City Boulevard West 333 City Boulevard West
Orange, California 92868 Orange, California 92868
USA USA
Phone: +1 714 938-3898 Phone: +1 714 938-3898
EMail: harnedy_sean@bah.com EMail: harnedy_sean@bah.com
Robert G. Cole Robert G. Cole
Johns Hopkins University US Army CERDEC
11100 Johns Hopkins Road, Room 257 328 Hopkins Road, Bldg 245
Laurel, Maryland 21073 Aberdeen Proving Ground, Maryland 21005
USA USA
Phone: +1 443 778 6951 Phone: +1 410 278 6779
EMail: robert.cole@jhuapl.edu EMail: robert.g.cole@us.army.mil
URI: http://www.cs.jhu.edu/~rgcole/ URI: http://www.cs.jhu.edu/~rgcole/
Ian D Chakeres Ian D Chakeres
CenGen CenGen
9250 Bendix Road North 9250 Bendix Road North
Columbia, Maryland 21045 Columbia, Maryland 21045
USA USA
EMail: ian.chakeres@gmail.com EMail: ian.chakeres@gmail.com
URI: http://www.ianchak.com/ URI: http://www.ianchak.com/
 End of changes. 119 change blocks. 
206 lines changed or deleted 328 lines changed or added

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