One document matched: draft-ietf-manet-dymo-mib-03.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2863 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2863.xml">
<!ENTITY rfc3418 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3418.xml">
<!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc2578 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2578.xml">
<!ENTITY rfc2579 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2579.xml">
<!ENTITY rfc2580 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2580.xml">
<!ENTITY rfc3410 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3410.xml">
<!ENTITY rfc4001 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4001.xml">
<!ENTITY dymo SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-manet-dymo.xml">
]>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc strict="no"?>
<?rfc rfcedstyle="yes"?>
<rfc category="std" docName="draft-ietf-manet-dymo-mib-03" ipr="trust200902">
<front>
<title abbrev="The DYMO-MIB">Definition of Managed Objects for the
DYMO Manet Routing Protocol</title>
<author fullname="Sean Harnedy" initials="S." role="" surname="Harnedy">
<organization>Booz Allen Hamilton</organization>
<address>
<postal>
<street>333 City Boulevard West</street>
<city>Orange</city>
<region>California</region>
<code>92868</code>
<country>USA</country>
</postal>
<phone>+1 714 938-3898</phone>
<email>harnedy_sean@bah.com</email>
</address>
</author>
<author fullname="Robert G. Cole" initials="R.G." surname="Cole">
<organization>Johns Hopkins University</organization>
<address>
<postal>
<street>11100 Johns Hopkins Road, Room 257</street>
<city>Laurel</city>
<region>Maryland</region>
<code>21073</code>
<country>USA</country>
</postal>
<phone>+1 443 778 6951</phone>
<email>robert.cole@jhuapl.edu</email>
<uri>http://www.cs.jhu.edu/~rgcole/</uri>
</address>
</author>
<author fullname="Ian D Chakeres" initials="I.D." surname="Chakeres">
<organization>CenGen</organization>
<address>
<postal>
<street>9250 Bendix Road North</street>
<city>Columbia</city>
<region>Maryland</region>
<code>21045</code>
<country>USA</country>
</postal>
<email>ian.chakeres@gmail.com</email>
<uri>http://www.ianchak.com/</uri>
</address>
</author>
<date/>
<area>Routing</area>
<workgroup>Internet Engineering Task Force</workgroup>
<keyword>Network Management</keyword>
<keyword>Management Information base</keyword>
<keyword>MIB</keyword>
<keyword>SMIv2</keyword>
<keyword>Routing</keyword>
<keyword>MANET</keyword>
<abstract>
<t>This memo defines a portion of the Management Information
Base (MIB) for use with network management protocols in the
Internet community. In particular, it describes objects for
configuring aspects of the DYMO routing process. The DYMO-MIB
also reports state information, performance information, and
notifications. In addition to configuration, this additional
state and performance information is useful to management
operators troubleshooting DYMO routing problems.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>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
<xref target="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.</t>
</section>
<section title="The Internet-Standard Management Framework">
<t>For a detailed overview of the documents that describe the
current Internet-Standard Management Framework, please refer to
section 7 of RFC 3410 <xref target="RFC3410"></xref>.</t>
<t>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 <xref
target="RFC2578"></xref>, STD 58, RFC 2579 <xref
target="RFC2579"></xref> and STD 58, RFC 2580 <xref
target="RFC2580"></xref>.</t>
</section>
<section title="Conventions">
<t>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 <xref target="RFC2119"></xref>.</t>
</section>
<section title="Overview">
<t>The Dynamic MANET On-demand (DYMO) routing protocol <xref
target="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.</t>
<t>A DYMO router's MIB contains DYMO process configuration
parameters (e.g. interfaces), state information (e.g. sequence
number), performance counters (e.g. number of control messages),
and notifications.</t>
<section title="DYMO Management Model">
<t>This section describes the management model for the DYMO
routing protocol.</t>
<t>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.</t>
<t>The Configuration Objects drive the behavior of the managed DYMO
device and hence determines the information in the remaining
groups, 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 the
number of DYMO routing messages received locally, per node and per
interface. The Notifications
group only contains objects which monitor changes to the
interface configuration and the gateway prefixes configuration.</t>
<t>See the below diagram outlining the DYMO-MIB device management model.</t>
<t><figure>
<preamble></preamble>
<artwork>
+------------------------------------------+
| CONFIGURATION GROUP |
| |
| Nodal Interface |
| |
| +-------+ +-------+ +-------+ |
| |Gateway| |Routing| |Routing| |
| +-------+ +-------+ +-------+ |
| |
+------------------------------------------+
|| || ||
|| || ||
|| || ||
\ / \ / \ /
\/ \/ \/
+-------+ +------------+ +---------------+
| STATE | | STATISTICS | | NOTIFICATIONS |
| GROUP | | GROUP | | GROUP |
+-------+ +------------+ +---------------+
</artwork>
<postamble></postamble>
</figure></t>
</section>
<section title="Terms">
<t>The following definitions apply throughout this document:</t>
<t><list style='symbols'>
<t>Configuration Objects - switches, tables, objects
which are initialized to default settings or set
through the management interface defined by this MIB.</t>
<t>Tunable Configuration Objects - objects whose
values affect timing or attempt bounds on the
DYMO protocol.</t>
<t>State Objects - automatically generated values which
define the current operating state of the DYMO
protocol process in the router.</t>
<t>Statistics Objects - automatically generated values
which help an operator 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.</t>
</list></t>
</section>
</section>
<section title="Structure of the MIB Module">
<t>This section presents the structure of the DYMO
MIB module. The objects are
arranged into the following groups:</t>
<t><list style='symbols'>
<t>dymoMIBNotifications - defines the notifications associated with the
DYMO-MIB. These are currently limited to notifications of interface
state changes and gateway prefix changes.</t>
<t>dymoMIBObjects - defines the objects forming the basis for the DYMO-MIB.
These objects are divided up by function into the following groups:</t>
<t><list style='symbols'>
<t>Configuration Group - This group contains the DYMO objects that configure specific
options that determine the overall performance and operation
of the routing protocol for the router device and its interfaces.</t>
<t>State Group - Contains information describing the current state of the DYMO
process such as the DYMO routing table.</t>
<t>Statistics Group - Contains objects which help to characterize the
performance of the DYMO process, typically statistics
counters. There are two types of DYMO statistics:
global counters and per interface counters.</t>
</list></t>
<t>dymoMIBConformance - defines minimal and full conformance of implementations
to this DYMO-MIB.</t>
</list></t>
<section title="Textual Conventions">
<!--Generic and Common Textual Conventions
can be found summarized at
http://www.ops.ietf.org/mib-common-tcs.html-->
<t>The textual conventions used in the DYMO-MIB are as follows.
The RowStatus and TruthValue textual conventions are imported from
RFC 2579 <xref target="RFC2579"></xref>.
The DymoInterfaceOperStatus is defined within the DYMO-MIB.
This contains the current operational status of the
DYMO interface.</t>
</section>
<section title="The Configuration Group">
<t>The DYMO device is configured with a set of controls.
The list of configuration controls for
the DYMO device follow.</t>
<t>Protocol Tuning Configuration Parameters:</t>
<t><list style='symbols'>
<t>MSG_HOPLIMIT</t>
<t>ROUTE_TIMEOUT</t>
<t>ROUTE_AGE_MIN_TIMEOUT</t>
<t>ROUTE_AGE_MAX_TIMEOUT</t>
<t>ROUTE_USED_TIMEOUT</t>
<t>ROUTE_DELETE_TIMEOUT</t>
<t>ROUTE_RREQ_WAIT_TIME</t>
<t>RREQ_RETRIES</t>
<t>UNICAST_MESSAGE_SENT_TIMEOUT</t>
</list></t>
<t>Protocol Configuration Tables:</t>
<t><list style='symbols'>
<t>Interfaces - 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 is a table containing the interfaces
and associated information.</t>
<t>Responsible Hosts - If RESPONSIBLE_ADDRESSES is set to other
than self address, then the DYMO router must be configured
with the set of host addresses for which
it is to generate RREP messages.</t>
</list></t>
</section>
<section title="The State Group">
<t>The State Subtree reports current state information.
State information from the DYMO-MIB is primarily contained
in the 'Routing' Table.</t>
<section title="Routing Table">
<t>The DYMO routing table contains DYMO specific information
related to IP forwarding entries found in the node's
IP forwarding table MIB. DYMO additional information includes
the sequence number associated with the DYMO message which
generated the forwarding table entry and various flags
indicating the viability of the routing entry.</t>
</section>
</section>
<section title="The Statistics Group">
<t>The Statistics subtree reports primarily counters that
relate to DYMO protocol activity.
The DYMO performance statistics consists of per node and per interface
objects:</t>
<t><list style='symbols'>
<t>OwnSequenceNumber</t>
<t>RREQ initiated</t>
<t>RREQ sent</t>
<t>RREQ received</t>
<t>RREP initiated</t>
<t>RREP sent</t>
<t>RREP received</t>
<t>RRER initiated</t>
<t>RRER sent</t>
<t>RRER received</t>
<t>Per interface statistics table with the following entries:</t>
<t><list style='symbols'>
<t>RREQ initiated</t>
<t>RREQ sent</t>
<t>RREQ received</t>
<t>RREP initiated</t>
<t>RREP sent</t>
<t>RREP received</t>
<t>RRER initiated</t>
<t>RRER sent</t>
<t>RRER received</t>
</list></t>
</list></t>
</section>
<section title="The Notifications Group">
<t>The Notifications Subtree contains the
list of notifications supported
within the DYMO-MIB and their intended purpose or utility.
This group is currently contains two notification objects, one
related to status changes in DYMO interfaces and one related to
changes in the gateway prefixes table.</t>
</section>
</section>
<section title="Relationship to Other MIB Modules">
<t>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.</t>
<section title="Relationship to the SNMPv2-MIB">
<t>The 'system' group in the SNMPv2-MIB <xref target="RFC3418"></xref>
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.</t>
</section>
<!-- <section title="Relationship to the IF-MIB">
<t>[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.</t>
</section> -->
<section title="MIB modules required for IMPORTS">
<!-- <t>[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.</t> -->
<t>The DYMO-MIB module IMPORTS objects from SNMPv2-SMI <xref
target="RFC2578"></xref>, SNMPv2-TC <xref target="RFC2579"></xref>,
SNMPv2-CONF <xref target="RFC2580"></xref>, INET-ADDRESS-MIB
<xref target="RFC4001"></xref> and IF-MIB <xref
target="RFC2863"></xref></t>
</section>
</section>
<!-- Definitions section -->
<!-- This section contains the MIB module(s) defined by the specification.
These MIB modules MUST be written in SMIv2 [RFC2578] [RFC2579]
[RFC2580].
See Section 4 of RFC 4181 for guidelines on SMIv2 usage.
See Appendix C of RFC 4181 for suggested naming conventions
A list of tools that can help automate the process of
checking mib definitions can be found at
http://www.ops.ietf.org/mib-review-tools.html
-->
<section title="Definitions">
<t></t>
<figure>
<artwork>
MANET-DYMO-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, RowStatus, TruthValue
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
InetAddress, InetAddressType,
InetAddressPrefixLength
FROM INET-ADDRESS-MIB -- [RFC4001]
InterfaceIndexOrZero
FROM IF-MIB -- [RFC2863]
;
manetDymoMIB MODULE-IDENTITY
LAST-UPDATED "200910251200Z" -- October 25, 2009
ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO
"WG E-Mail: manet@ietf.org
WG Chairs: ian.chakeres@gmail.com
jmacker@nrl.navy.mil
Editors: Sean Harnedy
Booz Allen Hamilton
333 City Boulevard West
Orange, CA 92868
USA
+1 714 938-3898
harnedy_sean@bah.com
Robert G. Cole
Johns Hopkins University
Applied Physics Lab and
Department of Computer Science
11000 Johns Hopkins Road
Laurel, MD 22014
USA
+1 443 778-6951
robert.cole@jhuapl.edu
Ian D Chakeres
CenGen
9250 Bendix Road North
Columbia, Maryland 21045
USA
ian.chakeres@gmail.com"
DESCRIPTION
"This MIB module contains managed object definitions for
the Dynamic MANET On-demand (DYMO) routing protocol as
defined in: Charkeres,I., and C. Perkins, Dynamic MANET
On-demand (DYMO) Routing, draft-ietf-manet-dymo-13,
April 10, 2008.
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 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
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
DESCRIPTION
"Second draft of this MIB module published as
draft-ietf-manet-dymo-mib-01.txt. Minor changes to
dymoInterfacesTable and dymoResponsibleAddrTable."
REVISION "200805141200Z" -- May 14, 2008
DESCRIPTION
"Initial draft of this MIB module published as
draft-ietf-manet-dymo-mib-00.txt."
-- RFC-Editor assigns XXXX
::= { mib-2 999 } -- to be assigned by IANA
--
-- TEXTUAL CONVENTIONs
--
Status ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An indication of the operability of a DYMO
function or feature. For example, the status
of an interface: 'enabled' indicates that
it is willing to communicate with other DYMO routers,
and 'disabled' indicates that it is not."
SYNTAX INTEGER { enabled (1), disabled (2) }
--
-- Top-Level Object Identifier Assignments
--
dymoMIBNotifications OBJECT IDENTIFIER ::= { manetDymoMIB 0 }
dymoMIBObjects OBJECT IDENTIFIER ::= { manetDymoMIB 1 }
dymoMIBConformance OBJECT IDENTIFIER ::= { manetDymoMIB 2 }
--
-- dymoConfigurationGroup
--
-- This group contains the DYMO objects that configure specific
-- options that determine the overall performance and operation
-- of the routing protocol for the router device and its
-- interfaces.
--
dymoConfigurationGroup OBJECT IDENTIFIER ::= { dymoMIBObjects 1 }
--
-- DYMO Global Router Configuration Group
--
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
SYNTAX Unsigned32 (0..255)
UNITS "hops"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of hops. The suggested value
default is 10 hops. This is the DYMO MSG_HOPLIMIT
parameter value."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
DEFVAL { 10 }
::= { dymoRouterConfigGroup 2 }
dymoRouteTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The route timeout value. The suggested default
value is 5000 milliseconds. This is the
DYMO ROUTE_TIMEOUT parameter value."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
DEFVAL { 5000 }
::= { dymoRouterConfigGroup 3 }
dymoRouteAgeMinTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The minimum route age timeout value. The
suggested default value is 1000 milliseconds.
This is the DYMO ROUTE_AGE_MIN_TIMEOUT parameter
value."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
DEFVAL { 1000 }
::= { dymoRouterConfigGroup 4 }
dymoRouteAgeMaxTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum route age timeout value. The
suggested default value is 60,000 milliseconds.
This is the DYMO ROUTE_AGE_MAX_TIMEOUT parameter
value."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
DEFVAL { 60000 }
::= { dymoRouterConfigGroup 5 }
dymoRouteUsedTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The route used timeout value. The
suggested default value is 5000
milliseconds (the same default as
the dymoRouteTimeout value). This
is the DYMO ROUTE_USED_TIMEOUT parameter
value."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
DEFVAL { 5000 }
::= { dymoRouterConfigGroup 6 }
dymoRouteDeleteTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The route delete timeout value. The
suggested default value is 10,000
milliseconds (this is 2 * dymoRouteTimeout
value). This is the DYMO ROUTE_DELETE_TIMEOUT
parameter value."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
DEFVAL { 10000 }
::= { dymoRouterConfigGroup 7 }
dymoRouteRreqWaitTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The Route Request wait time. The suggested default
value is 2000 milliseconds. This is the DYMO
ROUTE_RREQ_WAIT_TIME parameter value."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
DEFVAL { 2000 }
::= { dymoRouterConfigGroup 8 }
dymoRreqTries OBJECT-TYPE
SYNTAX Unsigned32 (1..16)
UNITS "attempts"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of Route Request retry attempts. The
suggested default value is 3. This is the
DYMO RREQ_TRIES parameter value."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
DEFVAL { 3 }
::= { dymoRouterConfigGroup 9 }
dymoUnicastMsgSentTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The message sent timeout value for unicast packets.
The suggested default value is 1000 milliseconds.
This is the DYMO UNICAST_MESSAGE_SENT_TIMEOUT
parameter value."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
DEFVAL { 1000 }
::= { dymoRouterConfigGroup 10 }
--
-- DYMO Interfaces Configuration Table
--
dymoInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO Interface Table describes the DYMO
interfaces that are participating in the
DYMO routing protocol. The ifIndex is from
the interfaces group defined in the Interfaces
Group MIB."
REFERENCE
"RFC 2863 - The Interfaces Group MIB, McCloghrie,
K., and F. Kastenholtz, June 2000."
::= { dymoConfigurationGroup 2 }
dymoInterfaceEntry OBJECT-TYPE
SYNTAX DymoInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO interface entry describes one DYMO
interface as indexed by its ifIndex."
INDEX { dymoIfIndex }
::= { dymoInterfaceTable 1 }
DymoInterfaceEntry ::=
SEQUENCE {
dymoIfIndex
InterfaceIndexOrZero,
dymoIfAdminStatus
Status,
dymoIfRowStatus
RowStatus
}
dymoIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex for this DYMO interface."
::= { dymoInterfaceEntry 1 }
dymoIfAdminStatus OBJECT-TYPE
SYNTAX Status
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The DYMO interface's administrative status.
The value 'enabled' denotes that the interface
is running the DYMO routing protocol.
The value 'disabled' denotes that the interface is
external to DYMO."
::= { dymoInterfaceEntry 2 }
dymoIfRowStatus 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."
::= { dymoInterfaceEntry 3 }
--
-- DYMO Responsible Address Table
--
dymoResponsibleAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoResponsibleAddrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO Responsible Address Table is a
list of IP address prefixes, and their
associated prefix length for which the
DYMO router is responsible."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important
Settings."
::= { dymoConfigurationGroup 3 }
dymoResponsibleAddrEntry OBJECT-TYPE
SYNTAX DymoResponsibleAddrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A single 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
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important
Settings."
INDEX { dymoResponsibleAddrIndex }
::= { dymoResponsibleAddrTable 1 }
DymoResponsibleAddrEntry ::=
SEQUENCE {
dymoResponsibleAddrIndex
Unsigned32,
dymoResponsibleAddrType
InetAddressType,
dymoResponsibleAddr
InetAddress,
dymoResponsibleAddrPrefixLen
InetAddressPrefixLength,
dymoResponsibleAddrRowStatus
RowStatus
}
dymoResponsibleAddrIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is the index into this table."
::= { dymoResponsibleAddrEntry 1 }
dymoResponsibleAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of the dymoResponsibleAddr, as defined
in the InetAddress MIB [RFC 4001]."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important
Settings."
::= { dymoResponsibleAddrEntry 2 }
dymoResponsibleAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The destination IP address of this route. The type
of this address is determined by the value of the
dymoResponsibleAddrType object."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important
Settings."
::= { dymoResponsibleAddrEntry 3 }
dymoResponsibleAddrPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the number of leading one bits that form the
mask to be logical-ANDed with the destination address
before being compared to the value in the dymoResonsibleAddr
field."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important
Settings."
::= { dymoResponsibleAddrEntry 4 }
dymoResponsibleAddrRowStatus 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."
::= { dymoResponsibleAddrEntry 5 }
--
-- dymoStateGroup
--
-- Contains information describing the current state of the DYMO
-- process such as the DYMO routing table.
--
dymoStateGroup OBJECT IDENTIFIER ::= { dymoMIBObjects 2 }
dymoCurrentSeqNum OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current DYMO sequence number. The DYMO sequence
numbers allow nodes to judge the freshness of routing
information and ensures loop freedom. If the sequence
number has been assigned to be the largest possible
number representable as a 16-bit unsigned integer
(i.e., 65,535), then the sequence number is set to
256 when incremented. Setting the sequence number
to 256 allows other nodes to detect that the number
has rolled over and the node has not lost its sequence
number (e.g., via reboot)."
::= { dymoStateGroup 1 }
--
-- DYMO Routing Table
--
dymoRoutingTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoRoutingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO Routing Table describes the
current routing information learned
via DYMO control messages."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 2 Suggested
Parameter Values."
::= { dymoStateGroup 2 }
dymoRoutingEntry OBJECT-TYPE
SYNTAX DymoRoutingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO routing entry contains a
piece of routing information for a
particular set of addresses."
INDEX { dymoRoutingIpAddrType,
dymoRoutingIpAddr,
dymoRoutingPrefixLen }
::= { dymoRoutingTable 1 }
DymoRoutingEntry ::=
SEQUENCE {
dymoRoutingIpAddrType
InetAddressType,
dymoRoutingIpAddr
InetAddress,
dymoRoutingPrefixLen
InetAddressPrefixLength,
dymoRoutingSeqNum
Unsigned32,
dymoRoutingNextHopIpAddrType
InetAddressType,
dymoRoutingNextHopIpAddress
InetAddress,
dymoRoutingNextHopInterface
InterfaceIndexOrZero,
dymoRoutingForwardingFlag
TruthValue,
dymoRoutingBrokenFlag
TruthValue,
dymoRoutingDist
Unsigned32
}
dymoRoutingIpAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The routing table address IP address type."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important
Settings."
::= { dymoRoutingEntry 1 }
dymoRoutingIpAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The routing table Inet IPv4 or IPv6 address."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important
Settings."
::= { dymoRoutingEntry 2 }
dymoRoutingPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The prefix length. This is a decimal value that
indicates the number of contiguous, higher-order
bits of the address that make up the network
portion of the address."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important
Settings."
::= { dymoRoutingEntry 3 }
dymoRoutingSeqNum OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interface sequence number. This
is the DYMO SeqNum associated with this
routing information."
::= { dymoRoutingEntry 4 }
dymoRoutingNextHopIpAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address type of the next hop."
::= { dymoRoutingEntry 5 }
dymoRoutingNextHopIpAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the next hop."
::= { dymoRoutingEntry 6 }
dymoRoutingNextHopInterface OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interface ifIndex for sending
packets toward the destination route
address."
::= { 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
SYNTAX Unsigned32 (1..65535)
UNITS "hops"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The distance to the destination address's
DYMO router. This is a metric of the
distance a message or piece of information
has traversed. The minimum value of distance
is the number of IP hops traversed. The
maximum value is 65,535."
REFERENCE
"Dynamic MANET On-demand (DYMO) Routing,
Chakeres, I., and C. Perkins, April
2008. Section 3 Terminology."
::= { dymoRoutingEntry 10 }
--
-- DYMO Statistics Group (Performance Management)
--
-- Contains objects which help to characterize the
-- performance of the DYMO process, typically statistics
-- counters. There are two types of DYMO statistics:
-- global counters and per interface counters.
--
dymoStatisticsGroup OBJECT IDENTIFIER ::= { dymoMIBObjects 3 }
dymoGlobalStatsGroup OBJECT IDENTIFIER ::= { dymoStatisticsGroup 1 }
dymoRreqOriginated 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."
::= { dymoGlobalStatsGroup 1 }
dymoRreqForwarded OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREQ messages that this DYMO
device has forwarded, i.e., this
device neither originated or
terminated the RREQ message."
::= { dymoGlobalStatsGroup 2 }
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 as the
target of the message."
::= { dymoGlobalStatsGroup 3 }
dymoRrepOriginated 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."
::= { dymoGlobalStatsGroup 4 }
dymoRrepForwarded OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREP messages that this DYMO
device has forwarded, i.e, this
device neither originated or
terminated the RREP message."
::= { dymoGlobalStatsGroup 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 as the
target of the message."
::= { dymoGlobalStatsGroup 6 }
dymoRrerOriginated 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."
::= { dymoGlobalStatsGroup 7 }
dymoRrerForwarded OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RRER messages that this DYMO
device has forwarded, i.e., this
device neither originated or
terminated the RRER message."
::= { dymoGlobalStatsGroup 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 as the
target of the message."
::= { dymoGlobalStatsGroup 9 }
--
-- Per DYMO Interface Statistics Table
--
dymoInterfaceStatsGroup OBJECT IDENTIFIER ::= {dymoStatisticsGroup 2}
dymoInterfaceStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoInterfaceStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO Interface Statistics Table
describes the DYMO statistics per
interface."
::= { dymoInterfaceStatsGroup 1 }
dymoInterfaceStatsEntry OBJECT-TYPE
SYNTAX DymoInterfaceStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DYMO Interface Statistics entry
describes the statistics for a particular
DYMO interface."
INDEX { dymoIfStatsIfIndex }
::= { dymoInterfaceStatsTable 1 }
DymoInterfaceStatsEntry ::=
SEQUENCE {
dymoIfStatsIfIndex
InterfaceIndexOrZero,
dymoIfRreqOriginated
Counter32,
dymoIfRreqForwarded
Counter32,
dymoIfRreqReceived
Counter32,
dymoIfRrepOriginated
Counter32,
dymoIfRrepForwarded
Counter32,
dymoIfRrepReceived
Counter32,
dymoIfRrerOriginated
Counter32,
dymoIfRrerForwarded
Counter32,
dymoIfRrerReceived
Counter32
}
dymoIfStatsIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex for this DYMO interface
that is collecting this set of
performance management statistics."
::= { dymoInterfaceStatsEntry 1 }
dymoIfRreqOriginated OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREQ messages that this DYMO
interface has initiated."
::= { dymoInterfaceStatsEntry 2 }
dymoIfRreqForwarded OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREQ messages that this DYMO
interface has forwarded, i.e., this
interface neither originated nor
terminated the RREQ message."
::= { dymoInterfaceStatsEntry 3 }
dymoIfRreqReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREQ messages that this DYMO
interface has received as the
target of the message."
::= { dymoInterfaceStatsEntry 4 }
dymoIfRrepOriginated OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREP messages that this DYMO
interface has initiated."
::= { dymoInterfaceStatsEntry 5 }
dymoIfRrepForwarded OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREP messages that this DYMO
interface has forwarded, i.e., this
interface neither originated nor
terminated the RREP message."
::= { dymoInterfaceStatsEntry 6 }
dymoIfRrepReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RREP messages that this DYMO
interface has received as the
target of the message."
::= { dymoInterfaceStatsEntry 7 }
dymoIfRrerOriginated OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RRER messages that this DYMO
interface has initiated."
::= { dymoInterfaceStatsEntry 8 }
dymoIfRrerForwarded OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RRER messages that this DYMO
interface has forwarded, i.e., this
interface neither originated nor
terminated the RRER message."
::= { dymoInterfaceStatsEntry 9 }
dymoIfRrerReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A counter of the number of
RRER messages that this DYMO
interface has received as the
target of the message."
::= { dymoInterfaceStatsEntry 10 }
--
-- Notifications
--
dymoAdminStatusChange NOTIFICATION-TYPE
OBJECTS { dymoAdminStatus }
STATUS current
DESCRIPTION
"This notification is generated when the
administrative status of a DYMO router changes."
::= { 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
OBJECTS { dymoResponsibleAddrRowStatus }
STATUS current
DESCRIPTION
"This notification is generated when the status
of an entry in the DYMO Responsible Address
Table changes. This includes the creation or
deletion of a row."
::= { dymoMIBNotifications 3 }
--
-- Compliance Statements
--
dymoCompliances OBJECT IDENTIFIER ::= { dymoMIBConformance 1 }
dymoMIBGroups OBJECT IDENTIFIER ::= { dymoMIBConformance 2 }
dymoBasicCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The basic implementation requirements for
managed network entities that implement
the DYMO routing protocol."
MODULE -- this module
MANDATORY-GROUPS { dymoConfigObjectsGroup }
::= { dymoCompliances 1 }
dymoFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The full implementation requirements for managed
network entities that implement the DYMO routing
protocol."
MODULE -- this module
MANDATORY-GROUPS { dymoConfigObjectsGroup,
dymoStateObjectsGroup,
dymoStatsObjectsGroup,
dymoNotifObjectsGroup }
::= { dymoCompliances 2 }
--
-- Units of Conformance
--
dymoConfigObjectsGroup OBJECT-GROUP
OBJECTS {
dymoAdminStatus,
dymoMaxHopLimit,
dymoRouteTimeout,
dymoRouteAgeMinTimeout,
dymoRouteAgeMaxTimeout,
dymoRouteUsedTimeout,
dymoRouteDeleteTimeout,
dymoRouteRreqWaitTime,
dymoRreqTries,
dymoUnicastMsgSentTimeout,
dymoIfAdminStatus,
dymoIfRowStatus,
dymoResponsibleAddrType,
dymoResponsibleAddr,
dymoResponsibleAddrPrefixLen,
dymoResponsibleAddrRowStatus
}
STATUS current
DESCRIPTION
"Set of DYMO configuration objects implemented
in this module."
::= { dymoMIBGroups 1 }
dymoStateObjectsGroup OBJECT-GROUP
OBJECTS {
dymoCurrentSeqNum,
dymoRoutingSeqNum,
dymoRoutingNextHopIpAddrType,
dymoRoutingNextHopIpAddress,
dymoRoutingNextHopInterface,
dymoRoutingForwardingFlag,
dymoRoutingBrokenFlag,
dymoRoutingDist
}
STATUS current
DESCRIPTION
"Set of DYMO state objects implemented
in this module."
::= { dymoMIBGroups 2 }
dymoStatsObjectsGroup OBJECT-GROUP
OBJECTS {
dymoRreqOriginated,
dymoRreqForwarded,
dymoRreqReceived,
dymoRrepOriginated,
dymoRrepForwarded,
dymoRrepReceived,
dymoRrerOriginated,
dymoRrerForwarded,
dymoRrerReceived,
dymoIfRreqOriginated,
dymoIfRreqForwarded,
dymoIfRreqReceived,
dymoIfRrepOriginated,
dymoIfRrepForwarded,
dymoIfRrepReceived,
dymoIfRrerOriginated,
dymoIfRrerForwarded,
dymoIfRrerReceived
}
STATUS current
DESCRIPTION
"Set of DYMO statistic objects implemented
in this module for performance management."
::= { dymoMIBGroups 3 }
dymoNotifObjectsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
dymoAdminStatusChange,
dymoInterfaceAdminStatusChange,
dymoResponsibleAddrEntryChange
}
STATUS current
DESCRIPTION
"Set of DYMO notifications implemented in this
module."
::= { dymoMIBGroups 4 }
END
</artwork>
</figure>
</section>
<section title="Security Considerations">
<!--[TODO] Remember to consider security from the start. -->
<t>[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.</t>
<t></t>
<t>[TODO] if you have any read-write and/or read-create objects, please
include the following boilerplate paragraph.</t>
<t>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:</t>
<t><list style="symbols">
<t>[TODO] writable 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.</t>
<t>[TODO] list the writable tables and objects and state why they
are sensitive.</t>
</list></t>
<t>[TODO] else if there are no read-write objects in your MIB module,
use the following boilerplate paragraph.</t>
<t>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.</t>
<t>[TODO] if you have any sensitive readable objects, please include the
following boilerplate paragraph.</t>
<t>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: <list style="symbols">
<t>[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 unauthorized parties)</t>
<t>[TODO] list the tables and objects and state why they are
sensitive.</t>
</list></t>
<t>[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.</t>
<t>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.</t>
<t>It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see <xref target="RFC3410"></xref>,
section 8), including full support for the SNMPv3 cryptographic
mechanisms (for authentication and privacy).</t>
<t>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 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.</t>
</section>
<section title="IANA Considerations">
<t>[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.</t>
<t>[TODO] select an option and provide the necessary details.</t>
<t>Option #1:</t>
<figure>
<preamble></preamble>
<artwork><![CDATA[
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 }
]]></artwork>
<postamble></postamble>
</figure>
<t></t>
<t>Option #2:</t>
<t>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.</t>
<t>Note well: prior to official assignment by the IANA, a draft document
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 in a draft
MIB module.</t>
<t>Option #3:</t>
<!-- If no IANA work is required, an explicit note must be included.-->
<t>This memo includes no request to IANA.</t>
</section>
<!-- The Author's Addresses section will be generated
automatically by XML2RFC from the front information -->
<section title="Contributors">
<t>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.</t>
<t><!--[TODO] Change this section to mention contributors to your
MIB module document.--></t>
</section>
<section title="Acknowledgements">
<t></t>
</section>
</middle>
<back>
<!-- References Section -->
<!-- Section 4.7f of [RFC2223bis] specifies the requirements for the
references sections. In particular, there MUST be separate lists of
normative and informative references, each in a separate section.
The style SHOULD follow that of recently published RFCs.
The standard MIB boilerplate available at
http://www.ops.ietf.org/mib-boilerplate.html includes lists of
normative and informative references that MUST appear in all IETF
specifications that contain MIB modules. If items from other MIB
modules appear in an IMPORTS statement in the Definitions section,
then the specifications containing those MIB modules MUST be included
in the list of normative references. When items are imported from an
IANA-maintained MIB module the corresponding normative reference
SHALL point to the on-line version of that MIB module. It is the
policy of the RFC Editor that all references must be cited in the
text; such citations MUST appear in the overview section where
documents containing imported definitions (other those already
mentioned in the MIB boilerplate) are required to be mentioned (cf.
Section 3.2).
In general, each normative reference SHOULD point to the most recent
version of the specification in question.
-->
<references title="Normative References">
<!-- <t>[TODO] rfc2629, 2863, 3418, and 4181 are normative references that
are required only to support this template, and which can be removed
from your final document, if not used for other purposes.</t>-->
<!--
&rfc2629;
&rfc4181;
-->
&rfc2863;
&rfc3418;
&rfc4001;
<!-- <t>[TODO] rfc2119, 2578, 2579, and 2580 are required to support MIB
module boilerplate text.</t> -->
&rfc2119;
&rfc2578;
&rfc2579;
&rfc2580;
&dymo;
<!-- <t>[TODO]: Add your own normative references.</t>-->
</references>
<references title="Informative References">
<!-- <t>[TODO] RFC3410 is required to support the boilerplate text.</t>-->
&rfc3410;
<!-- <t>[TODO] Add your own informative references</t>-->
</references>
<!--
<section anchor="appendix" title="Appendix A">
<t>You can add appendices just as regular sections, the only
difference is that they go under "back" element, and get letters
instead of numbers</t>
</section>
-->
<section title="Change Log ">
<t>This section identifies the changes that have been made
from draft-ietf-manet-dymo-mib-00 .</t>
<t>These changes were made from draft-ietf-manet-dymo-mib-00 to
draft-ietf-manet-dymo-mib-01. </t>
<t><list style="numbers">
<t>Only minor changes of a typographic nature, e.g., read-only
to read-write on MAX_ACCESS clauses of a few configuration
objects.</t>
</list></t>
<t>These changes were made from draft-ietf-manet-dymo-mib-01 to
draft-ietf-manet-dymo-mib-02. </t>
<t><list style="numbers">
<t>Added the ForwardingFlag and BrokenFlag objects to the DYMO
Routing Table.</t>
<t>Added the TruthValue Textual Convention to handle the new Routing
Table objects.</t>
<t>Added the DYMO device management model to the introductory
sections of this draft.</t>
<t>General clean up of the introductory sections of this draft.</t>
</list></t>
<t>These changes were made from draft-ietf-manet-dymo-mib-02 to
draft-ietf-manet-dymo-mib-03. </t>
<t><list style="numbers">
<t>Minor changes to the textual material and added to the IMPORTS text
in the introductory material.</t>
<t>Added DEFVAL clauses to all read-write configuration objects having
default values identified in the DYMO specification.</t>
</list></t>
</section>
<section title="Open Issues">
<t>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.</t>
<t><list style="numbers">
<t>Will DYMO require an MANET_ID (Instance ID) for running
multiple DYMO processes over the same interfaces?</t>
<t>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.)</t>
<t>Work on the Security Section. This MIB does have
settable objects, but not sensitive objects (true?).</t>
<t>Work on the relationship to other MIBs, IF-MIB, NHDP-MIB.</t>
<t>Identify all objects requiring non-volatile storage
in their DESCRIPTION clauses.</t>
<t>Incorporate parameter relationship conditions into
their DESCRIPTION clauses.</t>
<t>Cleanup all the [TODOs] from the MIB template.</t>
</list></t>
</section>
<section title="">
<figure>
<preamble></preamble>
<artwork>
***************************************************************
* 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-ietf-manet-dymo-xx.txt. This *
* need to be replaced with the XXX RFC number. *
* *
***************************************************************
</artwork>
<postamble></postamble>
</figure>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 09:00:08 |