draft-ietf-manet-dymo-mib-02.txt   draft-ietf-manet-dymo-mib-03.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: August 28, 2009 Johns Hopkins University Expires: April 28, 2010 Johns Hopkins University
I. Chakeres I. Chakeres
CenGen CenGen
February 24, 2009 October 25, 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-02 draft-ietf-manet-dymo-mib-03
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 August 28, 2009. 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) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
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 information, 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 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 Statistics 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. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 9 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 9
6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 9
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Security Considerations . . . . . . . . . . . . . . . . . . . 32 8. Security Considerations . . . . . . . . . . . . . . . . . . . 32
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 35 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 35
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35
12.1. Normative References . . . . . . . . . . . . . . . . . . . 35 12.1. Normative References . . . . . . . . . . . . . . . . . . . 35
12.2. Informative References . . . . . . . . . . . . . . . . . . 36 12.2. Informative References . . . . . . . . . . . . . . . . . . 36
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 36 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 36
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 36 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 37
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 38
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
troubleshooting routing problems. 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].
skipping to change at page 3, line 45 skipping to change at page 3, line 45
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
4. Overview 4. Overview
The Dynamic MANET On-demand (DYMO) routing protocol The Dynamic MANET On-demand (DYMO) routing protocol
[I-D.ietf-manet-dymo] is intended for use by mobile nodes in [I-D.ietf-manet-dymo] is intended for use by mobile nodes in
wireless, multihop networks. DYMO determines unicast routes among wireless, multihop networks. DYMO determines unicast routes among
DYMO routers within the network in an on-demand fashion, offering DYMO routers within the network in an on-demand fashion, offering
improved convergence in dynamic topologies. improved convergence in dynamic topologies.
A DYMO routers' 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,
skipping to change at page 4, line 22 skipping to change at page 4, line 22
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 information in the remaining The Configuration Objects drive the behavior of the managed DYMO
groups, i.e., State, Statistics and Notifications. The State objects device and hence determines the information in the remaining groups,
primarily address the resulting routing table objects. The i.e., State, Statistics and Notifications. The State objects
primarily present the resulting routing table objects. The
Statistics group primarily is comprised of counters for monitoring Statistics group primarily is comprised of counters for monitoring
the number of DYMO routing messages received locally. The the number of DYMO routing messages received locally, per node and
Notifications group only contains two objects which monitor changes per interface. The Notifications group only contains objects which
to the interface configuration and the gateway prefixes monitor changes to the interface configuration and the gateway
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| |
skipping to change at page 5, line 41 skipping to change at page 5, line 41
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 Statistics Objects - automatically generated values which help an
administrator or automated tool to assess the performance of the operator or automated tool to assess the performance of the DYMO
DYMO protocol process on the router and the overall routing protocol process on the router and the overall routing performance
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
the DYMO MIB. These are currently limited to notifications of the DYMO-MIB. These are currently limited to notifications of
interface state changes and gateway prefix 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 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 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 Tuning Configuration Parameters:
o MSG_HOPLIMIT o MSG_HOPLIMIT
skipping to change at page 8, line 48 skipping to change at page 8, line 48
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 two notification objects, one This group is currently contains two notification objects, one
related to status changes in DYMO interfaces and one related to related to status changes in DYMO interfaces and one related to
changes in the gateway prefixes table. 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 The text of this section specifies the relationship of the MIB
MIB modules contained in this document to other standards, modules contained in this document to other standards, particularly
particularly to standards containing other MIB modules. Definitions to standards containing other MIB modules. Definitions imported from
imported from other MIB modules and other MIB modules that SHOULD be other MIB modules and other MIB modules that SHOULD be implemented in
implemented in conjunction with the MIB module contained within this conjunction with the MIB module contained within this document are
document are identified in this section. identified in this section.
6.1. Relationship to the SNMPv2-MIB 6.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The DYMO-MIB does not entity and certain other system-wide data. The DYMO-MIB does not
duplicate those objects. duplicate those objects.
6.2. Relationship to the IF-MIB 6.2. MIB modules required for IMPORTS
[TODO] This section is included as an example; If the MIB module is
not an adjunct of the Interface MIB, then this section should be
removed.
6.3. MIB modules required for IMPORTS
[TODO]: Citations are not permitted within a MIB module, but any
module mentioned in an IMPORTS clause or document mentioned in a
REFERENCE clause is a Normative reference, and must be cited
someplace within the narrative sections. If there are imported items
in the MIB module, such as Textual Conventions, that are not already
cited, they can be cited in text here. Since relationships to other
MIB modules should be described in the narrative text, this section
is typically used to cite modules from which Textual Conventions are
imported.
The following DYMO-MIB module IMPORTS objects from SNMPv2-SMI The DYMO-MIB module IMPORTS objects from SNMPv2-SMI [RFC2578],
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], INET-ADDRESS-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, Unsigned32, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
skipping to change at page 10, line 16 skipping to change at page 9, line 47
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 "200902241200Z" -- February 24, 2009 LAST-UPDATED "200910251200Z" -- October 25, 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
skipping to change at page 11, line 13 skipping to change at page 10, line 44
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 "200910251200Z" -- October 25, 2009
DESCRIPTION
"Fourth draft of this MIB module published as
draft-ietf-manet-dymo-mib-03.txt.
- Minor changes to textual material, including
additions to the IMPORTS text.
- Added DEFVAL clauses to all read-write
configuration objects with defaults identified
in the DYMO draft."
REVISION "200902241200Z" -- February 24, 2009 REVISION "200902241200Z" -- February 24, 2009
DESCRIPTION DESCRIPTION
"Third draft of this MIB module published as "Third draft of this MIB module published as
draft-ietf-manet-dymo-mib-02.txt. draft-ietf-manet-dymo-mib-02.txt.
- Minor changes to dymoInterfacesTable and - Minor changes to dymoInterfacesTable and
dymoResponsibleAddrTable. dymoResponsibleAddrTable.
- Added global dymoAdminStatus and interface - Added global dymoAdminStatus and interface
specific dymoIfAdminStatus. specific dymoIfAdminStatus.
- Imported InterfaceIndexOrZero type from - Imported InterfaceIndexOrZero type from
IF-MIB." IF-MIB."
skipping to change at page 13, line 7 skipping to change at page 12, line 46
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."
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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
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, April 2008. Table 2 Suggested
Parameter Values." Parameter Values."
DEFVAL { 1000 }
::= { dymoRouterConfigGroup 4 } ::= { 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."
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 5000
milliseconds (the same default as milliseconds (the same default as
the dymoRouteTimeout value). This the dymoRouteTimeout value). This
skipping to change at page 14, line 24 skipping to change at page 14, line 20
"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."
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 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."
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
skipping to change at page 15, line 4 skipping to change at page 14, line 50
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."
DEFVAL { 2000 }
::= { dymoRouterConfigGroup 8 } ::= { 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."
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."
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."
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
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 35, line 36 skipping to change at page 35, line 36
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.
[RFC3418] Presuhn, R., "Management Information Base [RFC3418] Presuhn, R., "Management Information Base
(MIB) for the Simple Network Management (MIB) for the Simple Network Management
Protocol (SNMP)", STD 62, RFC 3418, Protocol (SNMP)", STD 62, RFC 3418,
December 2002. December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and
J. Schoenwaelder, "Textual Conventions for
Internet Network Addresses", RFC 4001,
February 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to [RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14, Indicate Requirement Levels", BCP 14,
RFC 2119, March 1997. RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Schoenwaelder, Ed., "Structure of Management
Information Version 2 (SMIv2)", STD 58, Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999. RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for Schoenwaelder, Ed., "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2580] McCloghrie, K., Perkins, D., and J.
Schoenwaelder, "Conformance Statements for Schoenwaelder, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[I-D.ietf-manet-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-16 (work in progress), draft-ietf-manet-dymo-17 (work in progress),
December 2008. March 2009.
12.2. Informative References 12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. [RFC3410] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction and Applicability Stewart, "Introduction and Applicability
Statements for Internet-Standard Management Statements for Internet-Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
Appendix A. Change Log Appendix A. Change Log
skipping to change at page 36, line 42 skipping to change at page 36, line 47
Routing Table. Routing Table.
2. Added the TruthValue Textual Convention to handle the new Routing 2. Added the TruthValue Textual Convention to handle the new Routing
Table objects. Table objects.
3. Added the DYMO device management model to the introductory 3. Added the DYMO device management model to the introductory
sections of this draft. sections of this draft.
4. General clean up of the introductory sections of this draft. 4. General clean up of the introductory sections of this draft.
These changes were made from draft-ietf-manet-dymo-mib-02 to
draft-ietf-manet-dymo-mib-03.
1. Minor changes to the textual material and added to the IMPORTS
text in the introductory material.
2. Added DEFVAL clauses to all read-write configuration objects
having default values identified in the DYMO specification.
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. 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: 2. Incorporate MIB-II IpGroup interworking with DymoIfTable. (Note:
We have looked into the current IpForwarding Table and it is not We have looked into the current IpForwarding Table and it is not
clear how this table can be extended through a 'delta' table clear how this table can be extended through a 'delta' table
within this MIB. Hence, we currently have a full DYMO forwarding within this MIB. Hence, we currently have a full DYMO forwarding
table in this MIB.) table in this MIB.)
3. What notifications are of interest and utility? 3. 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?).
5. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 4. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB.
6. Identify all objects requiring non-volatile storage in their 5. Identify all objects requiring non-volatile storage in their
DESCRIPTION clauses. DESCRIPTION clauses.
7. Add DEFAULT clauses to the appropriate Configuration Objects. 6. Incorporate parameter relationship conditions into their
8. Incorporate parameter relationship conditions into their
DESCRIPTION clauses. DESCRIPTION clauses.
9. Cleanup all the [TODOs] from the MIB template. 7. Cleanup all the [TODOs] from the MIB template.
Appendix C. Appendix C.
*************************************************************** ***************************************************************
* Note to the RFC Editor (to be removed prior to publication) * * Note to the RFC Editor (to be removed prior to publication) *
* * * *
* 1) The reference to RFCXXXX within the DESCRIPTION clauses * * 1) The reference to RFCXXXX within the DESCRIPTION clauses *
* of the MIB module point to this draft and are to be * * of the MIB module point to this draft and are to be *
* assigned by the RFC Editor. * * assigned by the RFC Editor. *
* * * *
 End of changes. 44 change blocks. 
74 lines changed or deleted 82 lines changed or added

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