draft-ietf-manet-dymo-mib-01.txt   draft-ietf-manet-dymo-mib-02.txt 
Internet Engineering Task Force S. Harnedy, Ed. Internet Engineering Task Force S. Harnedy
Internet-Draft Booze Allen Hamilton Internet-Draft Booz Allen Hamilton
Intended status: Standards Track R. Cole Intended status: Standards Track R. Cole
Expires: May 7, 2009 Johns Hopkins University Expires: August 28, 2009 Johns Hopkins University
I. Chakeres I. Chakeres
CenGen CenGen
November 3, 2008 February 24, 2009
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-01 draft-ietf-manet-dymo-mib-02
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 7, 2009. This Internet-Draft will expire on August 28, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the In particular, it describes objects for configuring aspects of the
DYMO routing process. The DYMO MIB also reports state information, DYMO routing process. The DYMO MIB also reports state information,
performance metrics, and notifications. In addition to performance metrics, and notifications. In addition to
configuration, this additional state and performance information is configuration, this additional state and performance information is
useful to management stations troubleshooting routing problems. useful to management stations troubleshooting 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 5 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6
5.2. The Configuration Group . . . . . . . . . . . . . . . . . 5 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 6
5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 6 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7
5.3.1. Peers Table . . . . . . . . . . . . . . . . . . . . . 6 5.3.1. Routing Table . . . . . . . . . . . . . . . . . . . . 7
5.3.2. Routing Table . . . . . . . . . . . . . . . . . . . . 6 5.4. The Statistics Group . . . . . . . . . . . . . . . . . . . 7
5.4. The Statistics Group . . . . . . . . . . . . . . . . . . . 6 5.5. The Notifications Group . . . . . . . . . . . . . . . . . 8
5.5. The Notifications Group . . . . . . . . . . . . . . . . . 7 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 9
6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 9
6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Security Considerations . . . . . . . . . . . . . . . . . . . 32
8. Security Considerations . . . . . . . . . . . . . . . . . . . 29 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 35
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 32 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32 12.1. Normative References . . . . . . . . . . . . . . . . . . . 35
12.1. Normative References . . . . . . . . . . . . . . . . . . . 32 12.2. Informative References . . . . . . . . . . . . . . . . . . 36
12.2. Informative References . . . . . . . . . . . . . . . . . . 33 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 36
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 33 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 36
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 33 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 37
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 and performance information is useful to management stations
skipping to change at page 4, line 10 skipping to change at page 4, line 10
A DYMO routers' MIB contains DYMO process configuration parameters A DYMO routers' 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,
Configuration, State and Statistics. The configuration of the
managed devices is controlled by the objects in the Configuration
Group. These are divided into Nodal and Interface objects. The bulk
of the DYMO configuration is in the Nodal objects which control
protocol behavior. The Interface objects merely identify/configure
interfaces to enable DYMO routing over their interface. The Nodal
objects are further divided into routing (or protocol) objects and
Gateway objects. Gateway objects define other routing prefixes for
which the node acts as a routing proxy on behalf of these non-local
prefixes.
The Configuration Objects drive the information in the remaining
groups, i.e., State, Statistics and Notifications. The State objects
primarily address the resulting routing table objects. The
Statistics group primarily is comprised of counters for monitoring
the number of DYMO routing messages received locally. The
Notifications group only contains two objects which monitor changes
to the interface configuration and the gateway prefixes
configuration.
See the below diagram outlining the DYMO-MIB device management model.
+------------------------------------------+
| CONFIGURATION GROUP |
| |
| Nodal Interface |
| |
| +-------+ +-------+ +-------+ |
| |Gateway| |Routing| |Routing| |
| +-------+ +-------+ +-------+ |
| |
+------------------------------------------+
|| || ||
|| || ||
|| || ||
\ / \ / \ /
\/ \/ \/
+-------+ +------------+ +---------------+
| STATE | | STATISTICS | | NOTIFICATIONS |
| 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.
skipping to change at page 4, line 37 skipping to change at page 5, line 52
DYMO protocol process on the router and the overall routing DYMO protocol process on the router and the overall routing
performance within the DYMO routing domain. performance 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
the DYMO MIB. These are currently limited to notifications of the DYMO MIB. These are currently limited to notifications of
interface state changes. interface state changes and gateway prefix changes.
o dymoMIBObjects - defines the objects forming the basis for the o dymoMIBObjects - defines the objects forming the basis for the
DYMO MIB. These objects are divided up by function into the DYMO MIB. These objects are divided up by function into the
following groups: following groups:
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 * Statistics 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 textual convention is imported from RFC 2579 [RFC2579]. RowStatus and TruthValue textual conventions are imported from RFC
The DymoInterfaceOperStatus is defined within the DYMO MIB. This 2579 [RFC2579]. The DymoInterfaceOperStatus is defined within the
contains the current operational status of the DYMO interface. DYMO MIB. This contains the current operational status of the DYMO
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 Tuning Configuration Parameters:
o MSG_HOPLIMIT o MSG_HOPLIMIT
skipping to change at page 6, line 8 skipping to change at page 7, line 26
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 o Responsible Hosts - If RESPONSIBLE_ADDRESSES is set to other than
self address, then the DYMO router must be configured with the set self address, then the DYMO router must be configured with the set
of host addresses for which it is to generate RREP messages. 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 contained in the 'Peers' Table. information from the DYMO-MIB is primarily contained in the 'Routing'
Table.
5.3.1. Peers Table
The DYMO peers table contains a list of recently known DYMO peer
nodes participating in the rotuing within the DYMO MANET. These
entries age out after a preset time.
5.3.2. Routing Table 5.3.1. Routing Table
The DYMO routing table contains DYMO specific information related to The DYMO routing table contains DYMO specific information related to
IP forwarding entries found in the node's IP forwarding table MIB. IP forwarding entries found in the node's IP forwarding table MIB.
DYMO additional information includes the sequence number associated DYMO additional information includes the sequence number associated
with the DYMO message which generated the forwarding table entry. 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 Statistics Group
The Statisctics subtree reports primarily counters that relate to The Statistics subtree reports primarily counters that relate to DYMO
DYMO protocol activity. The DYMO performance statistics consists of protocol activity. The DYMO performance statistics consists of per
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
o RREP sent o RREP sent
o RREP received o RREP received
o RRER initiated o RRER initiated
o RRER sent o RRER sent
skipping to change at page 6, line 51 skipping to change at page 8, line 18
o RREP received o RREP received
o RRER initiated o RRER initiated
o RRER sent o RRER sent
o RRER received o RRER received
o Per interface statistics table with the following entries: o Per interface statistics table with the following entries:
o
* RREQ initiated * RREQ initiated
* RREQ sent * RREQ sent
* RREQ received * RREQ received
* RREP initiated * RREP initiated
* RREP sent * RREP sent
* RREP received * RREP received
skipping to change at page 7, line 24 skipping to change at page 8, line 42
* RRER initiated * RRER initiated
* RRER sent * RRER sent
* RRER received * RRER received
5.5. The Notifications Group 5.5. The Notifications Group
The Notifications Subtree contains the list of notifications The Notifications Subtree contains the list of notifications
supported within the DYMO-MIB and their intended purpose or utility. supported within the DYMO-MIB and their intended purpose or utility.
This group is currently contains a single notification object related This group is currently contains two notification objects, one
to status changes in DYMO interfaces. related to status changes in DYMO interfaces and one related to
changes in the gateway prefixes table.
6. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
[TODO]: The text of this section specifies the relationship of the [TODO]: The text of this section specifies the relationship of the
MIB modules contained in this document to other standards, MIB modules contained in this document to other standards,
particularly to standards containing other MIB modules. Definitions particularly to standards containing other MIB modules. Definitions
imported from other MIB modules and other MIB modules that SHOULD be imported from other MIB modules and other MIB modules that SHOULD be
implemented in conjunction with the MIB module contained within this implemented in conjunction with the MIB module contained within this
document are identified in this section. document are identified in this section.
skipping to change at page 8, line 26 skipping to change at page 9, line 42
The following DYMO-MIB module IMPORTS objects from SNMPv2-SMI The following DYMO-MIB module IMPORTS objects from SNMPv2-SMI
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB
[RFC2863] [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, Unsigned32, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, RowStatus
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]
InterfaceIndex
InterfaceIndexOrZero
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
; ;
manetDymoMIB MODULE-IDENTITY manetDymoMIB MODULE-IDENTITY
LAST-UPDATED "200811031200Z" -- November 03, 2008 LAST-UPDATED "200902241200Z" -- February 24, 2009
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG Chairs: ian.chakeres@gmail.com WG Chairs: ian.chakeres@gmail.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: 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 Johns Hopkins University
Applied Physics Lab and Applied Physics Lab and
Department of Computer Science Department of Computer Science
11000 Johns Hopkins Road 11000 Johns Hopkins Road
Room 02-257
Laurel, MD 22014 Laurel, MD 22014
USA USA
+1 443 778-6951 +1 443 778-6951
robert.cole@jhuapl.edu robert.cole@jhuapl.edu
Ian D Chakeres Ian D Chakeres
Motorola CenGen
Bagmane Tech Park 9250 Bendix Road North
66/1, Plot 5, CV Raman Nagar Columbia, Maryland 21045
Bangalore, Karnataka 560093 USA
India
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: Charkeres,I., and C. Perkins, Dynamic MANET
On-demand (DYMO) Routing, draft-ietf-manet-dymo-13, On-demand (DYMO) Routing, draft-ietf-manet-dymo-13,
April 10, 2008. April 10, 2008.
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 "200902241200Z" -- February 24, 2009
DESCRIPTION
"Third draft of this MIB module published as
draft-ietf-manet-dymo-mib-02.txt.
- Minor changes to dymoInterfacesTable and
dymoResponsibleAddrTable.
- Added global dymoAdminStatus and interface
specific dymoIfAdminStatus.
- Imported InterfaceIndexOrZero type from
IF-MIB."
REVISION "200811031200Z" -- November 03, 2008 REVISION "200811031200Z" -- November 03, 2008
DESCRIPTION DESCRIPTION
"Second draft of this MIB module published as "Second draft of this MIB module published as
draft-ietf-manet-dymo-mib-01.txt. Minor changes to draft-ietf-manet-dymo-mib-01.txt. Minor changes to
dymoInterfacesTable and dymoResponsibleAddrTable." dymoInterfacesTable and dymoResponsibleAddrTable."
REVISION "200805141200Z" -- May 14, 2008 REVISION "200805141200Z" -- May 14, 2008
DESCRIPTION DESCRIPTION
"Initial draft of this MIB module published as "Initial draft of this MIB module published as
draft-ietf-manet-dymo-mib-00.txt." draft-ietf-manet-dymo-mib-00.txt."
-- RFC-Editor assigns XXXX -- RFC-Editor assigns XXXX
skipping to change at page 10, line 4 skipping to change at page 11, line 34
DESCRIPTION DESCRIPTION
"Second draft of this MIB module published as "Second draft of this MIB module published as
draft-ietf-manet-dymo-mib-01.txt. Minor changes to draft-ietf-manet-dymo-mib-01.txt. Minor changes to
dymoInterfacesTable and dymoResponsibleAddrTable." dymoInterfacesTable and dymoResponsibleAddrTable."
REVISION "200805141200Z" -- May 14, 2008 REVISION "200805141200Z" -- May 14, 2008
DESCRIPTION DESCRIPTION
"Initial draft of this MIB module published as "Initial draft of this MIB module published as
draft-ietf-manet-dymo-mib-00.txt." draft-ietf-manet-dymo-mib-00.txt."
-- RFC-Editor assigns XXXX -- RFC-Editor assigns XXXX
::= { mib-2 999 } -- to be assigned by IANA ::= { mib-2 999 } -- to be assigned by IANA
-- --
-- TEXTUAL CONVENTIONs -- TEXTUAL CONVENTIONs
-- --
-- Note: Need to determine the appropriate set of states Status ::= TEXTUAL-CONVENTION
-- for the DymoInterfacesOperStatus textual convention.
DymoInterfaceOperStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational status of the "An indication of the operability of a DYMO
DYMO interface." function or feature. For example, the status
SYNTAX INTEGER { of an interface: 'enabled' indicates that
up(1), it is willing to communicate with other DYMO routers,
down(2), and 'disabled' indicates that it is not."
waiting(3), SYNTAX INTEGER { enabled (1), disabled (2) }
loopback(4),
unknown(5)
}
-- --
-- Top-Level Object Identifier Assignments -- Top-Level Object Identifier Assignments
-- --
dymoMIBNotifications OBJECT IDENTIFIER ::= { manetDymoMIB 0 } dymoMIBNotifications OBJECT IDENTIFIER ::= { manetDymoMIB 0 }
dymoMIBObjects OBJECT IDENTIFIER ::= { manetDymoMIB 1 } dymoMIBObjects OBJECT IDENTIFIER ::= { manetDymoMIB 1 }
dymoMIBConformance OBJECT IDENTIFIER ::= { manetDymoMIB 2 } dymoMIBConformance OBJECT IDENTIFIER ::= { manetDymoMIB 2 }
-- --
skipping to change at page 10, line 48 skipping to change at page 12, line 27
-- --
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
SYNTAX Status
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The administrative status of DYMO in the
router. The value 'enabled' denotes that the
DYMO Process is active on at least one interface;
'disabled' disables it on all interfaces.
This object is persistent and when written
the entity SHOULD save the change to non-volatile storage."
::= { dymoRouterConfigGroup 1 }
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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoRouterConfigGroup 1 } ::= { 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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoRouterConfigGroup 2 } ::= { 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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoRouterConfigGroup 3 } ::= { dymoRouterConfigGroup 4 }
dymoRouteAgeMaxTimeout OBJECT-TYPE dymoRouteAgeMaxTimeout 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_AGE_MAX_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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoRouterConfigGroup 4 } ::= { 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 5000
milliseconds (the same default as milliseconds (the same default as
the dymoRouteTimeout value). This the dymoRouteTimeout value). 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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoRouterConfigGroup 5 } ::= { 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 10,000
milliseconds (this is 2 * dymoRouteTimeout milliseconds (this is 2 * dymoRouteTimeout
value). This is the DYMO ROUTE_DELETE_TIMEOUT value). This is the DYMO ROUTE_DELETE_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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoRouterConfigGroup 6 } ::= { 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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoRouterConfigGroup 7 } ::= { dymoRouterConfigGroup 8 }
dymoRREQTries OBJECT-TYPE dymoRreqTries 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 RREQ_TRIES 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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoRouterConfigGroup 8 } ::= { 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."
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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
::= { dymoRouterConfigGroup 9 } ::= { dymoRouterConfigGroup 10 }
-- --
-- DYMO Interfaces Configuration Table -- DYMO Interfaces Configuration Table
-- --
dymoInterfaceTable OBJECT-TYPE dymoInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoInterfaceEntry SYNTAX SEQUENCE OF DymoInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 14, line 34 skipping to change at page 16, line 27
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DYMO interface entry describes one DYMO "The DYMO interface entry describes one DYMO
interface as indexed by its ifIndex." interface as indexed by its ifIndex."
INDEX { dymoIfIndex } INDEX { dymoIfIndex }
::= { dymoInterfaceTable 1 } ::= { dymoInterfaceTable 1 }
DymoInterfaceEntry ::= DymoInterfaceEntry ::=
SEQUENCE { SEQUENCE {
dymoIfIndex dymoIfIndex
InterfaceIndex, InterfaceIndexOrZero,
dymoIfOperStatus dymoIfAdminStatus
DymoInterfaceOperStatus, Status,
dymoIfRowStatus dymoIfRowStatus
RowStatus RowStatus
} }
dymoIfIndex OBJECT-TYPE dymoIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex 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."
::= { dymoInterfaceEntry 1 } ::= { dymoInterfaceEntry 1 }
dymoIfOperStatus OBJECT-TYPE dymoIfAdminStatus OBJECT-TYPE
SYNTAX DymoInterfaceOperStatus SYNTAX Status
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational status of this "The DYMO interface's administrative status.
DYMO interface. The default value is The value 'enabled' denotes that the interface
down(2)." is running the DYMO routing protocol.
The value 'disabled' denotes that the interface is
external to DYMO."
::= { dymoInterfaceEntry 2 } ::= { dymoInterfaceEntry 2 }
dymoIfRowStatus OBJECT-TYPE dymoIfRowStatus 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,
construction, and destruction. The value of construction, and destruction. The value of
skipping to change at page 16, line 36 skipping to change at page 18, line 31
dymoResponsibleAddrIndex OBJECT-TYPE dymoResponsibleAddrIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the index into this table." "This object is the index into this table."
::= { dymoResponsibleAddrEntry 1 } ::= { dymoResponsibleAddrEntry 1 }
dymoResponsibleAddrType OBJECT-TYPE dymoResponsibleAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-write 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, April 2008. Table 3 Important
Settings." Settings."
::= { dymoResponsibleAddrEntry 2 } ::= { dymoResponsibleAddrEntry 2 }
dymoResponsibleAddr OBJECT-TYPE dymoResponsibleAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write 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, April 2008. Table 3 Important
Settings." Settings."
::= { dymoResponsibleAddrEntry 3 } ::= { dymoResponsibleAddrEntry 3 }
dymoResponsibleAddrPrefixLen OBJECT-TYPE dymoResponsibleAddrPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-write 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-ANDed 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, April 2008. Table 3 Important
Settings." Settings."
skipping to change at page 19, line 17 skipping to change at page 21, line 13
InetAddress, InetAddress,
dymoRoutingPrefixLen dymoRoutingPrefixLen
InetAddressPrefixLength, InetAddressPrefixLength,
dymoRoutingSeqNum dymoRoutingSeqNum
Unsigned32, Unsigned32,
dymoRoutingNextHopIpAddrType dymoRoutingNextHopIpAddrType
InetAddressType, InetAddressType,
dymoRoutingNextHopIpAddress dymoRoutingNextHopIpAddress
InetAddress, InetAddress,
dymoRoutingNextHopInterface dymoRoutingNextHopInterface
InterfaceIndex, InterfaceIndexOrZero,
dymoRoutingForwardingFlag
TruthValue,
dymoRoutingBrokenFlag
TruthValue,
dymoRoutingDist dymoRoutingDist
Unsigned32 Unsigned32
} }
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."
skipping to change at page 20, line 40 skipping to change at page 22, line 40
dymoRoutingNextHopIpAddress OBJECT-TYPE dymoRoutingNextHopIpAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the next hop." "The IP address of the next hop."
::= { dymoRoutingEntry 6 } ::= { dymoRoutingEntry 6 }
dymoRoutingNextHopInterface OBJECT-TYPE dymoRoutingNextHopInterface OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface ifIndex for sending "The interface ifIndex for sending
packets toward the destination route packets toward the destination route
address." address."
::= { dymoRoutingEntry 7 } ::= { dymoRoutingEntry 7 }
dymoRoutingForwardingFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Forwarding Flag indicates whether
this route can be used for forwarding
data packets. A value 'true(1)'
indicates that this route is being used
for forwarding of data packets, while
a value 'false(2)' indicates that it is
not being used for forwarding."
::= { dymoRoutingEntry 8 }
dymoRoutingBrokenFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Broken Flag indicates whether
this Route is broken. This flag is set
if the next-hop becomes unreachable or
in response to processing a RERR. A value
'true(1)' indicates that this route is
broken, while a value 'false(2)'
indicates that it is not broken."
::= { dymoRoutingEntry 9 }
dymoRoutingDist OBJECT-TYPE dymoRoutingDist OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..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."
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 8 } ::= { dymoRoutingEntry 10 }
-- --
-- DYMO Statistics Group (Performance Management) -- DYMO Statistics 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.
-- --
skipping to change at page 24, line 17 skipping to change at page 26, line 49
DESCRIPTION DESCRIPTION
"The DYMO Interface Statistics entry "The DYMO Interface Statistics entry
describes the statistics for a particular describes the statistics for a particular
DYMO interface." DYMO interface."
INDEX { dymoIfStatsIfIndex } INDEX { dymoIfStatsIfIndex }
::= { dymoInterfaceStatsTable 1 } ::= { dymoInterfaceStatsTable 1 }
DymoInterfaceStatsEntry ::= DymoInterfaceStatsEntry ::=
SEQUENCE { SEQUENCE {
dymoIfStatsIfIndex dymoIfStatsIfIndex
InterfaceIndex, InterfaceIndexOrZero,
dymoIfRreqOriginated dymoIfRreqOriginated
Counter32, Counter32,
dymoIfRreqForwarded dymoIfRreqForwarded
Counter32, Counter32,
dymoIfRreqReceived dymoIfRreqReceived
Counter32, Counter32,
dymoIfRrepOriginated dymoIfRrepOriginated
Counter32, Counter32,
dymoIfRrepForwarded dymoIfRrepForwarded
Counter32, Counter32,
skipping to change at page 24, line 39 skipping to change at page 27, line 23
Counter32, Counter32,
dymoIfRrerOriginated dymoIfRrerOriginated
Counter32, Counter32,
dymoIfRrerForwarded dymoIfRrerForwarded
Counter32, Counter32,
dymoIfRrerReceived dymoIfRrerReceived
Counter32 Counter32
} }
dymoIfStatsIfIndex OBJECT-TYPE dymoIfStatsIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex 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 } ::= { dymoInterfaceStatsEntry 1 }
dymoIfRreqOriginated OBJECT-TYPE dymoIfRreqOriginated OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 27, line 7 skipping to change at page 29, line 39
"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 } ::= { dymoInterfaceStatsEntry 10 }
-- --
-- Notifications -- Notifications
-- --
dymoInterfaceOperStatusChange NOTIFICATION-TYPE dymoAdminStatusChange NOTIFICATION-TYPE
OBJECTS { dymoIfOperStatus } OBJECTS { dymoAdminStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the "This notification is generated when the
operational status of a DYMO interface changes." administrative status of a DYMO router changes."
::= { dymoMIBNotifications 1 } ::= { dymoMIBNotifications 1 }
dymoInterfaceAdminStatusChange NOTIFICATION-TYPE
OBJECTS { dymoIfAdminStatus }
STATUS current
DESCRIPTION
"This notification is generated when the
administrative status of a DYMO interface changes."
::= { dymoMIBNotifications 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 2 } ::= { dymoMIBNotifications 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 28, line 4 skipping to change at page 30, line 44
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, dymoStatsObjectsGroup,
dymoNotifObjectsGroup } dymoNotifObjectsGroup }
::= { dymoCompliances 2 } ::= { dymoCompliances 2 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
dymoConfigObjectsGroup OBJECT-GROUP dymoConfigObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dymoAdminStatus,
dymoMaxHopLimit, dymoMaxHopLimit,
dymoRouteTimeout, dymoRouteTimeout,
dymoRouteAgeMinTimeout, dymoRouteAgeMinTimeout,
dymoRouteAgeMaxTimeout, dymoRouteAgeMaxTimeout,
dymoRouteUsedTimeout, dymoRouteUsedTimeout,
dymoRouteDeleteTimeout, dymoRouteDeleteTimeout,
dymoRouteRREQWaitTime, dymoRouteRreqWaitTime,
dymoRREQTries, dymoRreqTries,
dymoUnicastMsgSentTimeout, dymoUnicastMsgSentTimeout,
dymoIfOperStatus, dymoIfAdminStatus,
dymoIfRowStatus,
dymoResponsibleAddrType,
dymoResponsibleAddr,
dymoResponsibleAddrPrefixLen,
dymoResponsibleAddrRowStatus dymoResponsibleAddrRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of DYMO configuration objects implemented "Set of DYMO configuration objects implemented
in this module." in this module."
::= { dymoMIBGroups 1 } ::= { dymoMIBGroups 1 }
dymoStateObjectsGroup OBJECT-GROUP dymoStateObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dymoCurrentSeqNum, dymoCurrentSeqNum,
dymoRoutingSeqNum, dymoRoutingSeqNum,
dymoRoutingNextHopIpAddrType, dymoRoutingNextHopIpAddrType,
dymoRoutingNextHopIpAddress, dymoRoutingNextHopIpAddress,
dymoRoutingNextHopInterface, dymoRoutingNextHopInterface,
dymoRoutingForwardingFlag,
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 dymoStatsObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 29, line 24 skipping to change at page 32, line 24
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 NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
dymoInterfaceOperStatusChange, dymoAdminStatusChange,
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 4 }
END END
skipping to change at page 30, line 9 skipping to change at page 33, line 10
include the following boilerplate paragraph. include the following boilerplate paragraph.
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
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o [TODO] writeable MIB objects that could be especially disruptive o [TODO] writable MIB objects that could be especially disruptive if
if abused MUST be explicitly listed by name and the associated abused MUST be explicitly listed by name and the associated
security risks MUST be spelled out; RFC 2669 has a very good security risks MUST be spelled out; RFC 2669 has a very good
example. example.
o [TODO] list the writable tables and objects and state why they are o [TODO] list the writable tables and objects and state why they are
sensitive. sensitive.
[TODO] else if there are no read-write objects in your MIB module, [TODO] else if there are no read-write objects in your MIB module,
use the following boilerplate paragraph. use the following boilerplate paragraph.
There are no management objects defined in this MIB module that have There are no management objects defined in this MIB module that have
skipping to change at page 30, line 41 skipping to change at page 33, line 42
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 [TODO] you must explicitly list by name any readable objects that o [TODO] you must explicitly list by name any readable objects that
are sensitive or vulnerable and the associated security risks MUST are sensitive or vulnerable and the associated security risks MUST
be spelled out (for instance, if they might reveal customer be spelled out (for instance, if they might reveal customer
information or violate personal privacy laws such as those of the information or violate personal privacy laws such as those of the
European Union if exposed to unathorized parties) European Union if exposed to unauthorized parties)
o [TODO] list the tables and objects and state why they are o [TODO] list the tables and objects and state why they are
sensitive. sensitive.
[TODO] discuss what security the protocol used to carry the [TODO] discuss what security the protocol used to carry the
information should have. The following three boilerplate paragraphs information should have. The following three boilerplate paragraphs
should not be changed without very good reason. Changes will almost should not be changed without very good reason. Changes will almost
certainly require justification during IESG review. certainly require justification during IESG review.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
skipping to change at page 32, line 7 skipping to change at page 35, line 8
Option #2: Option #2:
Editor's Note (to be removed prior to publication): the IANA is Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note. this note.
Note well: prior to official assignment by the IANA, a draft document Note well: prior to official assignment by the IANA, a draft document
MUST use placeholders (such as "XXX" above) rather than actual MUST use place-holders (such as "XXX" above) rather than actual
numbers. See RFC4181 Section 4.5 for an example of how this is done numbers. See RFC4181 Section 4.5 for an example of how this is done
in a draft MIB module. in a draft MIB module.
Option #3: Option #3:
This memo includes no request to IANA. This memo includes no request to IANA.
10. Contributors 10. Contributors
This MIB document uses the template authored by D. Harrington which This MIB document uses the template authored by D. Harrington which
is based on contributions from the MIb Doctors, especially Juergen is based on contributions from the MIB Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn.
11. Acknowledgements 11. Acknowledgements
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The [RFC2863] McCloghrie, K. and F. Kastenholz, "The
Interfaces Group MIB", RFC 2863, June 2000. Interfaces Group MIB", RFC 2863, June 2000.
skipping to change at page 33, line 7 skipping to change at page 36, line 7
[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-14 (work in progress), draft-ietf-manet-dymo-16 (work in progress),
June 2008. December 2008.
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
The following changes have been made from This section identifies the changes that have been made from
draft-ietf-manet-dymo-mib-00 . draft-ietf-manet-dymo-mib-00 .
Not applicable to draft 00 These changes were made from draft-ietf-manet-dymo-mib-00 to
draft-ietf-manet-dymo-mib-01.
1. 1. Only minor changes of a typographic nature, e.g., read-only to
read-write on MAX_ACCESS clauses of a few configuration objects.
These changes were made from draft-ietf-manet-dymo-mib-01 to
draft-ietf-manet-dymo-mib-02.
1. Added the ForwardingFlag and BrokenFlag objects to the DYMO
Routing Table.
2. Added the TruthValue Textual Convention to handle the new Routing
Table objects.
3. Added the DYMO device management model to the introductory
sections of this draft.
4. General clean up of the introductory sections of this draft.
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. Agree on set of configuration options to be supported, e.g., 1. Will DYMO require an MANET_ID (Instance ID) for running multiple
Gateway config, local hosts, responsible addresses, etc.
2. Will DYMO require an MANET_ID (Instance ID) for running multiple
DYMO processes over the same interfaces? 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. Incorporate MIB-II IfGroup interworking with DymoIfTable. 3. What notifications are of interest and utility?
4. Incorporate MIB-II IpGroup interworking with DymoIfTable.
5. Incorporate MIB-II IpForwardingGroup interworking with
DymoRoutingTable.
6. What performance objects are of interest and utility?
7. What notifications are of interest and utility?
8. Work on the Security Section. This MIB does have settable 4. Work on the Security Section. This MIB does have settable
objects, but not sensitive objects (true?). objects, but not sensitive objects (true?).
9. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 5. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB.
10. Identify all objects requiring non-volatile storage in their 6. Identify all objects requiring non-volatile storage in their
DESCRIPTION clauses. DESCRIPTION clauses.
11. Incorporate parameter relationship conditions into their 7. Add DEFAULT clauses to the appropriate Configuration Objects.
8. Incorporate parameter relationship conditions into their
DESCRIPTION clauses. DESCRIPTION clauses.
12. Cleanup all the [TODOs] from the MIB template. 9. Cleanup all the [TODOs] from the MIB template.
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. *
* * * *
* 2) The reference to RFCXXX2 throughout this document point * * 2) The reference to RFCXXX2 throughout this document point *
* to the current draft-ietf-manet-dymo-xx.txt. This * * to the current draft-ietf-manet-dymo-xx.txt. This *
* need to be replaced with the XXX RFC number. * * need to be replaced with the XXX RFC number. *
* * * *
*************************************************************** ***************************************************************
Authors' Addresses Authors' Addresses
Sean Harnedy (editor) Sean Harnedy
Booze 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 Johns Hopkins University
11100 Johns Hopkins Road, Room 257 11100 Johns Hopkins Road, Room 257
skipping to change at page 35, line 4 skipping to change at page 38, line 25
Robert G. Cole Robert G. Cole
Johns Hopkins University Johns Hopkins University
11100 Johns Hopkins Road, Room 257 11100 Johns Hopkins Road, Room 257
Laurel, Maryland 21073 Laurel, Maryland 21073
USA USA
Phone: +1 443 778 6951 Phone: +1 443 778 6951
EMail: robert.cole@jhuapl.edu EMail: robert.cole@jhuapl.edu
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/
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 86 change blocks. 
142 lines changed or deleted 281 lines changed or added

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