Internet Engineering Task Force R. Cole, Ed.
Internet-Draft Johns Hopkins University
Intended status: Standards Track I. Chakeres
Expires: September 15, 2008 Motorola
March 14, 2008
Definition of Managed Objects for the DYMO Manet Routing Protocol
draft-cole-manet-dymo-mib-00
Status of This Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
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
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 15, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the
DYMO routing process. The DYMO MIB also reports state information,
performance metrics, and notifications. In addition to
configuration, this additional state and performance information is
useful to management stations troubleshooting routing problems.
Cole & Chakeres Expires September 15, 2008 [Page 1]
Internet-Draft The DYMO MIB March 2008
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. DYMO Management Model . . . . . . . . . . . . . . . . . . 4
4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4
5.2. The General Information Group . . . . . . . . . . . . . . 4
5.3. The Configuration Group . . . . . . . . . . . . . . . . . 5
5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 5
5.4.1. Peers Table . . . . . . . . . . . . . . . . . . . . . 5
5.5. The Performance Group . . . . . . . . . . . . . . . . . . 6
5.6. The Notifications Group . . . . . . . . . . . . . . . . . 7
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7
6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7
6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 7
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 21
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 24
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
12.1. Normative References . . . . . . . . . . . . . . . . . . . 24
12.2. Informative References . . . . . . . . . . . . . . . . . . 24
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 25
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 25
Cole & Chakeres Expires September 15, 2008 [Page 2]
Internet-Draft The DYMO MIB March 2008
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of a
Dynamic MANET On-demand (DYMO) routing [I-D.ietf-manet-dymo] process.
The DYMO MIB also reports state information, performance metrics, and
notifications. In addition to configuration, this additional state
and performance information is useful to management stations
troubleshooting routing problems.
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
4. Overview
The Dynamic MANET On-demand (DYMO) routing protocol
[I-D.ietf-manet-dymo] is intended for use by mobile nodes in
wireless, multihop networks. DYMO determines unicast routes among
DYMO routers within the network in an on-demand fashion, offering
improved convergence in dynamic topologies.
A DYMO routers' MIB contains DYMO process configuration parameters
(e.g. interfaces), state information (e.g. sequence number),
performance metrics (e.g. number of control messages), and
notifications.
Cole & Chakeres Expires September 15, 2008 [Page 3]
Internet-Draft The DYMO MIB March 2008
4.1. DYMO Management Model
This section describes the management model for the DYMO routing
protocol.
4.2. Terms
The following definitions apply throughout this document:
o Configuration Objects - switches, tables, objects which are
initialized to default settings or set through the management
interface defined by this MIB.
o Tunable Configuration Objects - objects whose values affect timing
or attempt bounds on the DYMO protocol.
o State Objects - automatically generated values which define the
current operating state of the DYMO protocol process in the
router.
o Performance Objects - automatically generated values which help an
administrator or automated tool to assess the performance of the
DYMO protocol process on the router and the overall routing
performance within the DYMO routing domain.
5. Structure of the MIB Module
This section presents the structure of the DYMO MIB module. The
objects are arranged into the following groups:
o General Information Group - ...
o Configuration Group - ...
o State Group - ...
o Performance Group - ...
o Notification Group - ...
5.1. Textual Conventions
This section is TBD.
5.2. The General Information Group
This section provides general information about the capabilities of
the routing device. ...
Cole & Chakeres Expires September 15, 2008 [Page 4]
Internet-Draft The DYMO MIB March 2008
5.3. The Configuration Group
The DYMO device is configured with a set of controls. The list of
configuration controls for the DYMO device follow.
Protocol Configuration Parameters and Tables:
o DymoInterfaces - If DYMO_INTERFACES is set to other than all, then
the DYMO router must be told which interfaces to run the DYMO
protocol over. This would be a table containing the interfaces
and associated information.
o LocalHosts - If RESPONSIBLE_ADDRESSES is set to other than self
address, then the DYMO router must be configured with the set of
local host addresses for which it is to generate RREP messages.
Protocol Tuning Configuration Parameters:
o MSG_HOPLIMIT
o RREQ_RETRIES
Timer Configuration:
o ROUTE_TIMEOUT
o ROUTE_AGE_MIN_TIMEOUT
o ROUTE_AGE_MAX_TIMEOUT
o ROUTE_USED_TIMEOUT
o ROUTE_DELETE_TIMEOUT
5.4. The State Group
The State Subtree reports current state information. State
information from the DYMO-MIB is contained in the 'Peers' Table.
5.4.1. Peers Table
The DYMO peers table consists of the following entries:
o Network Address (IP address and prefix)
o Sequence Number
Cole & Chakeres Expires September 15, 2008 [Page 5]
Internet-Draft The DYMO MIB March 2008
o Next-hop?
o Next-hop interface?
o Distance?
5.5. The Performance Group
The Performance subtree reports statistics that relate to DYMO
protocol activity. The DYMO performance statistics consists of the
following objects and tables:
o OwnSequenceNumber
o RREQ initiated
o RREQ sent
o RREQ received
o RREP initiated
o RREP sent
o RREP received
o RRER initiated
o RRER sent
o RRER received
o Per interface statistics table with the following entries:
* RREQ initiated
* RREQ sent
* RREQ received
* RREP initiated
* RREP sent
* RREP received
* RRER initiated
Cole & Chakeres Expires September 15, 2008 [Page 6]
Internet-Draft The DYMO MIB March 2008
* RRER sent
* RRER received
5.6. The Notifications Group
The Notifications Subtree contains the list of notifications
supported within the DYMO-MIB and their intended purpose or utility.
This group is currently empty.
6. Relationship to Other MIB Modules
[TODO]: The text of this section specifies the relationship of the
MIB modules contained in this document to other standards,
particularly to standards containing other MIB modules. Definitions
imported from other MIB modules and other MIB modules that SHOULD be
implemented in conjunction with the MIB module contained within this
document are identified in this section.
6.1. Relationship to the SNMPv2-MIB
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
whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The DYMO-MIB does not
duplicate those objects.
6.2. Relationship to the IF-MIB
[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
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB
[RFC2863]
Cole & Chakeres Expires September 15, 2008 [Page 7]
Internet-Draft The DYMO MIB March 2008
7. Definitions
DYMO-MIB DEFINITIONS ::= BEGIN
-- This MIB is currently in a very initial stage.
-- Not all proposed objects have been identified yet
-- in the current draft. The MIB have not been
-- formally checked by any MIB checkers yet.
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32,
Gauge32, Integer32, Unsigned32
FROM SNMPv2-SMI --[RFC2578]
TEXTUAL-CONVENTION, StorageType, TimeStamp,
TruthValue, RowStatus
FROM SNMPv2-TC --[RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF --[STD58]
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB --[RFC3291]
InterfaceIndexOrZero
FROM IF-MIB --[RFC2863]
dymoMIB MODULE-IDENTITY
LAST-UPDATED "200803101500Z" -- March 10, 2008
ORGANIZATION "IETF MANET working group"
CONTACT-INFO
"WG E-Mail: manet@ietf.org
WG Chairs: ian.chakeres@gmail.com
jmacker@nrl.navy.mil
Editors: Robert G. Cole
Johns Hopkins University
Applied Physics Lab and
Department of Computer Science
11000 Johns Hopkins Road
Room 02-257
Laurel, MD 22014
USA
+1 443 778-6951
robert.cole@jhuapl.edu
Ian D Chakeres
Motorola
Cole & Chakeres Expires September 15, 2008 [Page 8]
Internet-Draft The DYMO MIB March 2008
Bagmane Tech Park
66/1, Plot 5, CV Raman Nagar
Bangalore, Karnataka 560093
India
ian.chakeres@gmail.com"
DESCRIPTION
"This DYMO MIB module is applicable to devices
implementing ...
Copyright (C) The IETF Trust (2008). This version
of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices."
-- revision
REVISION "200802151500Z" -- February 15, 2008
DESCRIPTION
"The original draft of this MIB module. Published
as draft-cole-dymo-mib-00.txt"
REVISION "20080310100Z" -- March 10, 2008
DESCRIPTION
"The second draft of this MIB module. Simplified
MIB significantly; reducing configuration option
per the current DYMO protocol draft. Removed
overlap with MIB-II."
-- RFC-Editor assigns XXXX
::= { manet XX } -- to be assigned by IANA
--
-- Object Identifier Assignments
--
dymoMIBObjects OBJECT IDENTIFIER ::= { dymoMIB 1 }
dymoMIBNotifications OBJECT IDENTIFIER ::= { dymoMIB 2 }
dymoMIBConformance OBJECT IDENTIFIER ::= { dymoMIB 3 }
--
-- Textual Conventions
--
--
-- dymoConfigurationGroup
--
-- Contains the DYMO objects which configure specific options
-- which determine the overall performance and operation of the
-- routing protocol.
Cole & Chakeres Expires September 15, 2008 [Page 9]
Internet-Draft The DYMO MIB March 2008
dymoConfigurationGroup OBJECT IDENTIFIER ::= { dymo 2 }
--Configuration Tables
--DymoInterfaces
--LocalHosts
--Protocol Tuning Configuration Parameter Objects:
--MSG_HOPLIMIT
--RREQ_RETRIES
--Timer Configuration Objects
--ROUTE_TIMEOUT
--ROUTE_AGE_MIN_TIMEOUT
--ROUTE_AGE_MAX_TIMEOUT
--ROUTE_USED_TIMEOUT
--ROUTE_DELETE_TIMEOUT
--Configuration Tables:
--DymoInterfaces Table
dymoIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO Interface Table describes the interfaces
from the viewpoint of DYMO. This should augment the
IfGroup and IpGroup from MIB-II."
REFERENCE
""
::= { dymoConfigurationGroup 1 }
dymoIfEntry OBJECT-TYPE
SYNTAX DymoIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO interface entry describes one interface
from the viewpoint of DYMO.
Information in this table is persistent and when this object
is written the entity SHOULD save the change to non-volatile
storage."
INDEX { dymoIfIpAddress }
::= { dymoIfTable 1 }
Cole & Chakeres Expires September 15, 2008 [Page 10]
Internet-Draft The DYMO MIB March 2008
DymoIfEntry ::=
SEQUENCE {
dymoIfIpAddress
InetAddress,
dymoIfState
INTEGER,
dymoIfStatus
RowStatus
}
dymoIfIpAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"The IP address of this DYMO interface."
::= { dymoIfEntry 1 }
dymoIfState OBJECT-TYPE
SYNTAX INTEGER {
down (1),
loopback (2),
waiting (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The DYMO Interface State."
DEFVAL { down }
::= { dymoIfEntry 2 }
dymoIfStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object permits management of the table by
facilitating actions such as row creation,
construction, and destruction.
The value of this object has no effect on
whether other objects in this conceptual row can be
modified."
::= { dymoIfEntry 3 }
--LocalHosts Table
Cole & Chakeres Expires September 15, 2008 [Page 11]
Internet-Draft The DYMO MIB March 2008
-- (insert LocalHosts Table here.)
dymoLocalHostsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoLocalHostsEntry
MAX-ACCESS not-accessible
STATUS obsolete
DESCRIPTION
"The Dymo Local Hosts Table identifies
the addresses for which responsibility
lies within the local DYMO device.
It contains a set of IP address ranges
specified by an IP address/IP network mask pair.
For example, class B address range of X.X.X.X
with a network mask of 255.255.0.0 includes all IP
addresses from X.X.0.0 to X.X.255.255."
REFERENCE
""
::= { dymoConfigurationGroup 2 }
dymoLocalHostsEntry OBJECT-TYPE
SYNTAX dymoLocalHostsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A single local host address range.
Information in this table is persistent and when this object
is written the entity SHOULD save the change to non-volatile
storage."
REFERENCE
""
INDEX { dymoLocalHostNet }
::= { dymoLocalHostsTable 1 }
DymoLocalHostsEntry ::=
SEQUENCE {
dymoLocalHostNet InetAddress,
dymoLocalHostMask InetAddress,
dymoLocalHostStatus RowStatus
}
dymoLocalHostNet OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address of the net or subnet indicated
by the range."
Cole & Chakeres Expires September 15, 2008 [Page 12]
Internet-Draft The DYMO MIB March 2008
REFERENCE
""
::= { dymoLocalHostsEntry 1 }
dymoLocalHostMask OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The subnet mask that pertains to the net or
subnet."
REFERENCE
""
::= { dymoLocalHostsEntry 2 }
dymoLocalHostStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object permits management of the table by
facilitating actions such as row creation,
construction, and destruction.
The value of this object has no effect on
whether other objects in this conceptual row can be
modified."
::= { dymoLocalHostEntry 3 }
--Protocol Tuning Configuration Parameter Objects:
-- (insert Protocol Config Parameter Ojects here.)
dymoMsgHopLimit OBJECT-TYPE
SYNTAX Integer32 (1..1024)
UNITS ""
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The DYMO MSG_HOPLIMIT parameter value."
REFERENCE
""
DEFVAL { 10 }
::= { dymoConfigurationGroup 3 }
dymoRreqRetries OBJECT-TYPE
SYNTAX Integer32 (1..1024)
Cole & Chakeres Expires September 15, 2008 [Page 13]
Internet-Draft The DYMO MIB March 2008
UNITS ""
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The DYMO RREQ_TRIES parameter value."
REFERENCE
""
DEFVAL { 3 }
::= { dymoConfigurationGroup 4 }
--Timer Configuration Objects
-- (insert Timer Configuration Objects here.)
dymoRouteTimeout OBJECT-TYPE
SYNTAX Integer32 (1..1024)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The DYMO ROUTE_TIMEOUT parameter value."
REFERENCE
""
DEFVAL { 5 }
::= { dymoConfigurationGroup 5 }
dymoRouteAgeMinimumTimeout OBJECT-TYPE
SYNTAX Integer32 (1..1024)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The DYMO ROUTE_AGE_MIN_TIMEOUT
parameter value. The default
value for this object should
be equal to the
dymoNetworkTraversalTime."
REFERENCE
""
DEFVAL { 1 }
::= { dymoConfigurationGroup 6 }
dymoRouteAgeMaximumTimeout OBJECT-TYPE
SYNTAX Integer32 (1..1024)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
Cole & Chakeres Expires September 15, 2008 [Page 14]
Internet-Draft The DYMO MIB March 2008
"The DYMO ROUTE_AGE_MAX_TIMEOUT
parameter value."
REFERENCE
""
DEFVAL { 60 }
::= { dymoConfigurationGroup 7 }
dymoRouteUsedTimeout OBJECT-TYPE
SYNTAX Integer32 (1..1024)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The DYMO ROUTE_USED_TIMEOUT parameter
value. The default value for this object
should be the
dymoRouteTimeout value."
REFERENCE
""
DEFVAL { 5 }
::= { dymoConfigurationGroup 8 }
dymoRouteDeleteTimeout OBJECT-TYPE
SYNTAX Integer32 (1..1800)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The DYMO ROUTE_DELETE_TIMEOUT
parameter value. The default
setting for this object should
be set to 2*dymoRouteTimeout."
REFERENCE
""
DEFVAL { 10 }
::= { dymoConfigurationGroup 9 }
--
-- dymoStateGroup
--
-- Contains information describing the current state of the DYMO
-- process.
dymoStateGroup OBJECT IDENTIFIER ::= { dymo 3 }
Cole & Chakeres Expires September 15, 2008 [Page 15]
Internet-Draft The DYMO MIB March 2008
--General State Information, i.e.,
--Peers Table
--table entries with the following mandatory objects, i.e.,
--Peers.Address
--Peers.SeqNum
--Peers.NextHopAddress
--Peers.NextHopInterface
--Peers.Distance
--Peers Table
dymoPeersTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoPeersEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO Peers
Table describes the current Peers that this
devices has overhead within the past xxx seconds."
REFERENCE
""
::= { dymoStateGroup 1 }
dymoPeersEntry OBJECT-TYPE
SYNTAX DymoPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO Peers entry describes
a peer that this devices has
recently overheard."
INDEX { dymoPeerIpAddress } -- not sure best
-- indexing
::= { dymoPeersTable 1 }
DymoPeerEntry ::=
SEQUENCE {
dymoPeerIpAddress
InetAddress,
dymoPeerSeqNo
INTEGER,
dymoPeerNextHopIpAddress
InetAddress,
dymoPeerNextHopInterface
InetAddress,
dymoPeerDist
Cole & Chakeres Expires September 15, 2008 [Page 16]
Internet-Draft The DYMO MIB March 2008
INTEGER
}
dymoPeerIpAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the peer."
::= { dymoPeerEntry 1 }
dymoPeerSeqNo OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ..."
::= { dymoPeerEntry 2 }
dymoPeerNextHopIPAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of ..."
::= { dymoPeerEntry 3 }
dymoPeerNextHopInterface OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of ..."
::= { dymoPeerEntry 4 }
dymoPeerDist OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ..."
::= { dymoPeerEntry 5 }
--
-- dymoPerformanceGroup
--
Cole & Chakeres Expires September 15, 2008 [Page 17]
Internet-Draft The DYMO MIB March 2008
-- Contains objects which help to characterize the performance of
-- the DYMO process, typically counters.
dymoPerformanceGroup OBJECT IDENTIFIER ::= { dymo 4 }
--Aggregate Objects
--OwnSequenceNumber
--RREQ initiated
--RREQ sent
--RREQ received
--RREP initiated
--RREP sent
--RREP received
--RRER initiated
--RRER sent
--RRER received
--Per Interface Table
--RREQ initiated
--RREQ sent
--RREQ received
--RREP initiated
--RREP sent
--RREP received
--RRER initiated
--RRER sent
--RRER received
dymoRreqInitiated OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREQ messages that this DYMO
device has initiated."
::= { dymoPerformanceGroup 1 }
dymoRreqSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREQ messages that this DYMO
device has sent."
::= { dymoPerformanceGroup 2 }
Cole & Chakeres Expires September 15, 2008 [Page 18]
Internet-Draft The DYMO MIB March 2008
dymoRreqReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREQ messages that this DYMO
device has received."
::= { dymoPerformanceGroup 3 }
dymoRrepInitiated OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREP messages that this DYMO
device has initiated."
::= { dymoPerformanceGroup 4 }
dymoRrepSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREP messages that this DYMO
device has sent."
::= { dymoPerformanceGroup 5 }
dymoRrepReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREP messages that this DYMO
device has received."
::= { dymoPerformanceGroup 6 }
dymoRrerInitiated OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RRER messages that this DYMO
device has initiated."
Cole & Chakeres Expires September 15, 2008 [Page 19]
Internet-Draft The DYMO MIB March 2008
::= { dymoPerformanceGroup 7 }
dymoRrerSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RRER messages that this DYMO
device has sent."
::= { dymoPerformanceGroup 8 }
dymoRrerReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RRER messages that this DYMO
device has received."
::= { dymoPerformanceGroup 9 }
--Per Interface Table
-- include per interface table here (tbd)
--
-- Notifications
--
--What are the valuable notification information for the
--DYMO-MIB? (tbd)
--
-- Conformance information
--
-- To be determined.
dymoCompliances OBJECT IDENTIFIER ::= { dymoConformance 1 }
dymoGroups OBJECT IDENTIFIER ::= { dymoConformance 2 }
-- Compliance Statements
dymoGeneralCompliance MODULE-COMPLIANCE
Cole & Chakeres Expires September 15, 2008 [Page 20]
Internet-Draft The DYMO MIB March 2008
STATUS current
DESCRIPTION
"A general compliance which allows ...."
MODULE -- this module
MANDATORY-GROUPS { dymoGeneralGroup }
::= { dymoCompliances 1 }
--
-- DYMO Group Compliance
--
--
-- Groups
--
END
8. Security Considerations
[TODO] Each specification that defines one or more MIB modules MUST
contain a section that discusses security considerations relevant to
those modules. This section MUST be patterned after the latest
approved template (available at
http://www.ops.ietf.org/mib-security.html). Remember that the
objective is not to blindly copy text from the template, but rather
to think and evaluate the risks/vulnerabilities and then state/
document the result of this evaluation.
[TODO] if you have any read-write and/or read-create objects, please
include the following boilerplate paragraph.
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
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
o [TODO] writeable MIB objects that could be especially disruptive
if abused MUST be explicitly listed by name and the associated
security risks MUST be spelled out; RFC 2669 has a very good
example.
o [TODO] list the writable tables and objects and state why they are
sensitive.
Cole & Chakeres Expires September 15, 2008 [Page 21]
Internet-Draft The DYMO MIB March 2008
[TODO] else if there are no read-write objects in your MIB module,
use the following boilerplate paragraph.
There are no management objects defined in this MIB module that have
a MAX-ACCESS clause of read-write and/or read-create. So, if this
MIB module is implemented correctly, then there is no risk that an
intruder can alter or create any management objects of this MIB
module via direct SNMP SET operations.
[TODO] if you have any sensitive readable objects, please include the
following boilerplate paragraph.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
o [TODO] you must explicitly list by name any readable objects that
are sensitive or vulnerable and the associated security risks MUST
be spelled out (for instance, if they might reveal customer
information or violate personal privacy laws such as those of the
European Union if exposed to unathorized parties)
o [TODO] list the tables and objects and state why they are
sensitive.
[TODO] discuss what security the protocol used to carry the
information should have. The following three boilerplate paragraphs
should not be changed without very good reason. Changes will almost
certainly require justification during IESG review.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
Cole & Chakeres Expires September 15, 2008 [Page 22]
Internet-Draft The DYMO MIB March 2008
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
9. IANA Considerations
[TODO] In order to comply with IESG policy as set forth in
http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is
submitted to the IESG for publication MUST contain an IANA
Considerations section. The requirements for this section vary
depending what actions are required of the IANA. see RFC4181 section
3.5 for more information on writing an IANA clause for a MIB module
document.
[TODO] select an option and provide the necessary details.
Option #1:
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
sampleMIB { mib-2 XXX }
Option #2:
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
to record the assignment in the SMI Numbers registry. When the
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
this note.
Note well: prior to official assignment by the IANA, a draft document
MUST use placeholders (such as "XXX" above) rather than actual
numbers. See RFC4181 Section 4.5 for an example of how this is done
in a draft MIB module.
Option #3:
This memo includes no request to IANA.
Cole & Chakeres Expires September 15, 2008 [Page 23]
Internet-Draft The DYMO MIB March 2008
10. Contributors
This MIB document uses the template authored by D. Harrington which
is based on contributions from the MIb Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn.
11. Acknowledgements
12. References
12.1. Normative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The
Interfaces Group MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base
(MIB) for the Simple Network Management
Protocol (SNMP)", STD 62, RFC 3418,
December 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14,
RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management
Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J.
Schoenwaelder, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[I-D.ietf-manet-dymo] Chakeres, I. and C. Perkins, "Dynamic MANET
On-demand (DYMO) Routing",
draft-ietf-manet-dymo-12 (work in progress),
February 2008.
12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction and Applicability
Statements for Internet-Standard Management
Framework", RFC 3410, December 2002.
Cole & Chakeres Expires September 15, 2008 [Page 24]
Internet-Draft The DYMO MIB March 2008
Appendix A. Change Log
The following changes have been made from draft-cole-dymo-mib-00 .
Not applicable to draft 00
1.
Appendix B. Open Issues
This section contains the set of open issues related to the
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
the open issues have been resolved.
1. Agree on set of configuration options to be supported, e.g.,
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?
3. Is support for addresses-less interfaces required?
4. Incorporate MIB-II IfGroup interworking with DymoIfTable.
5. Incorporate MIB-II IpGroup interworking with DymoIfTable.
6. Incorporate MIB-II IpForwardingGroup interworking with
DymoRIBTable.
7. What performance objects are of interest and utility?
8. What notifications are of interest and utility?
9. Work on the Security Section. This MIB does have settable
objects, but not sensitive objects (true?).
10. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB.
11. Identify all objects requiring non-volatile storage in their
DESCRIPTION clauses.
12. Incorporate parameter relationship conditions into their
DESCRIPTION clauses.
13. Work up a better management model in the textual description of
the DYMO-MIB. Perhaps include management usecases.
Cole & Chakeres Expires September 15, 2008 [Page 25]
Internet-Draft The DYMO MIB March 2008
14. Cleanup all the [TODOs] from the MIB template.
***************************************************************
* Note to the RFC Editor (to be removed prior to publication) *
* *
* 1) The reference to RFCXXXX within the DESCRIPTION clauses *
* of the MIB module point to this draft and are to be *
* assigned by the RFC Editor. *
* *
* 2) The reference to RFCXXX2 throughout this document point *
* to the current draft-cole-dymo-xx.txt. This *
* need to be replaced with the XXX RFC number. *
* *
***************************************************************
Authors' Addresses
Robert G. Cole (editor)
Johns Hopkins University
11100 Johns Hopkins Road, Room 257
Laurel, Maryland 21073
USA
Phone: +1 443 778 6951
EMail: robert.cole@jhuapl.edu
URI: http://www.cs.jhu.edu/~rgcole/
Ian D Chakeres
Motorola
Bagmane Tech Park
66/1, Plot 5, CV Raman Nagar
Bangalore, Karnataka 560093
India
EMail: ian.chakeres@gmail.com
URI: http://www.ianchak.com/
Cole & Chakeres Expires September 15, 2008 [Page 26]
Internet-Draft The DYMO MIB March 2008
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).
Cole & Chakeres Expires September 15, 2008 [Page 27]