Internet Engineering Task Force R. Cole, Ed. Internet-Draft Johns Hopkins University Intended status: Standards Track I. Chakeres, Ed. Expires: August 21, 2008 Motorola February 18, 2008 Definition of Managed Objects for the DYMO Manet Routing Protocol draft-cole-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 August 21, 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 MANET Routing process on a router. The DYMO MIB also reports state information, i.e., Routing Information Base entries, performance metrics, i.e., counter of the number Routing Messages, and notifications. In addition to configuration, this additional Cole & Chakeres Expires August 21, 2008 [Page 1] Internet-Draft The DYMO MIB February 2008 state and performance information is useful to management stations troubleshooting routing problems. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Organization . . . . . . . . . . . . . . . . . . . . . . . 5 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 5.2. The General Information Group . . . . . . . . . . . . . . 6 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 6 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 8 5.4.1. General State Information . . . . . . . . . . . . . . 8 5.4.2. Routing Information Base . . . . . . . . . . . . . . . 8 5.4.3. Current NextHop Table . . . . . . . . . . . . . . . . 9 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 9 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 9 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 10 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 10 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 10 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Security Considerations . . . . . . . . . . . . . . . . . . . 27 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 29 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 12.1. Normative References . . . . . . . . . . . . . . . . . . . 29 12.2. Informative References . . . . . . . . . . . . . . . . . . 30 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 30 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 30 Cole & Chakeres Expires August 21, 2008 [Page 2] Internet-Draft The DYMO MIB February 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 the Dynamic MANET On-demand (DYMO) routing [I-D:ietf-manet-dymo] process on a router. The DYMO MIB also reports state information, i.e., Routing Information Base (RIB) entries, performance metrics, i.e., counter of the number Routing Messages, 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 DYMO routing protocol allows routers in a Mobile Ad-Hoc network (MANET) setting to discover forwarding paths through the network. The DYMO routing protocol is an On-Demand protocol in the sense that it only discovers paths when there is end system data traffic to transmit. When a Source Node (SN) has traffic to send to a Target Node (TN), the SN floods the MANET with a route_request (RREQ) message containing the SN and TN addresses. Intermediate Nodes (IN) rebroadcast the RREQ message, appending path information as the message propagates throughout the MANET. When the RREQ message reaches the TN, it replies with a route_reply (RREP) message to the SN. Once the SN receives the RREP message from the TN, path information in the form of path entries in the Source, Intermediate Cole & Chakeres Expires August 21, 2008 [Page 3] Internet-Draft The DYMO MIB February 2008 and Target nodes' Routing Information Base (RIB) is embedded and affords packet forwarding of the data packets. Further, off-path forwarding information towards the SN is embedded as the RREQ messages propagate throughout the MANET. As nodes move about, links to next hop nodes along routing paths will break. In this case intermediate nodes can issue route_error (RERR) messages to notify nodes relying on the broken forwarding path to discover new paths. Hence, DYMO nodes are required to monitor the availability of next hop links being used in forwarding paths. This may be accomplished via the Next Hop Discovery Protocol (NHDP) [I-D: ietf-manet-nhdp]. Routers can be configured to run the DYMO routing protocol over all or a subset of local interfaces. Further, DYMO routers can be configured to trigger RREP messages based upon receiving any data destine to all unknown TN addresses or only to a subset of addresses. DYMO routers can act as proxy, gateway nodes between DYMO routing domains and non-DYMO routing domains. Finally, the DYMO protocol process can be tuned through a set of configurable settings. Hence, DYMO routers are configured to maintain: o A list of potential DYMO target addresses for route discovery, o A list of DYMO-enabled local interfaces, o A list of addresses to act as a proxy gateway, and o A set of configurable parameters, e.g., timers, to tune the performance of the routing protocol. Once in operation, the DYMO routers will maintain a set of state information, which is temporal in nature. E.g., to prevent the creation of routing loops, DYMO routers maintain, increment and append sequence numbers to Routing Messages (RMs). The current router sequence number is an example of local state information. Further, as the router discovers and overhears path information to various TNs in the MANET, the DYMO router populates this knowledge in it's local Routing Information Base (RIP). Entries in the RIB tell the local routing the next hop and interface to forward data packets destine for a given TN. The DYMO routers are responsible for tracking the availability of the next hop links which are registered in their RIB. Hence, DYMO routers dynamically maintain a set of state objects, including: o Routing in a MANET is a tricky endeavor. The DYMO routing process Cole & Chakeres Expires August 21, 2008 [Page 4] Internet-Draft The DYMO MIB February 2008 contains numerous configurable parameters which impact the overall performance of the MANET. Hence, the DYMO MIB defines a set of Performance and Notification objects to aid network administrators to track the overall health of the routing process and to aid in fault isolation and correction of routing related problems. 4.1. 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. 4.2. Organization This document is organized as ... 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 - ... Cole & Chakeres Expires August 21, 2008 [Page 5] Internet-Draft The DYMO MIB February 2008 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. ... 5.3. The Configuration Group The device is configured with a set of controls. These will serve as the object descriptions once they are discussed and refined. A potential list of configuration controls for the DYMO-MIB, include: Protocol Configuration Parameters: o RREP_GENERATION, 0=all unknown, 1=following list o IS_GATEWAY, 0=no, 1=yes o RESPONSIBLE_ADDRESSES, Self or Prefix, 0=self, 1=user specified o DYMO_INTERFACES, User Specified, 0=all, 1=user specified o INCLUDE_TARGET_INFORMATION, Yes - TargetNode.AddTLV.SeqNum, TargetNode.AddTLV.Dist, TargetNode.AddTLV.Prefix o APPEND_OWN_ADDRESSES, Yes for RREQ o INCREMENT_OWN_SEQNUM_ON_APPEND, Yes for RREQ o INCLUDE_OWN_INFORMATION_ON_APPEND, Yes for RREQ, OrigNode.AddTLV.Dist and OrigNode.AddTLV.Prefix o APPEND_OTHER_ADDRESSES, Yes - RREQ & RREP, AddBlk.AdditionalNode.Address o INCLUDE_OTHER_INFORMATION, Yes - RREQ & RREP, AdditionalNode.AddTLV.SeqNum, AdditionalNode.AddTLV.Dist, AdditionalNode.AddTLV.Prefix o GENERATE_RERR_IMMEDIATELY, No o RERR_INCLUDE_ALL_UNREACHABLES, Yes o UNKNOWN_TYPE_HANDLING, Ignore Cole & Chakeres Expires August 21, 2008 [Page 6] Internet-Draft The DYMO MIB February 2008 Protocol Tuning Configuration Parameters: o MAX_HOPLIMIT - 10 hops ([I-D:ietf-manet-dymo], sect. 5.3.1) o BUFFER_SIZE_PACKETS, 50 packets o BUFFER_SIZE, 1500 * BUFFER_SIZE_PACKETS o PACKET_RATE_THROTTLE - ([I-D:ietf-manet-dymo], sect. 5.9) Timer Configuration - ([I-D:ietf-manet-dymo], sect. 5.2.3): o ROUTE_TIMEOUT - 5 seconds ([I-D:ietf-manet-dymo], sect. 6) o NET_TRANSVERSAL_TIME - 1000 msec ([I-D:ietf-manet-dymo], sect. 6) o ROUTE_DELETE_TIMEOUT - 2*ROUTE_TIMEOUT o ROUTE_AGE_MAX_TIMEOUT - 60 sec o ROUTE_AGE_MIN_TIMEOUT - NET_TRAVERSAL_TIME o ROUTE_NEW_TIMEOUT - ROUTE_TIMEOUT o ROUTE_USED_TIMEOUT - ROUTE_TIMEOUT o RREQ_WAIT_TIME - 2*NET_TRAVERSAL_TIME ([I-D:ietf-manet-dymo], sect. 5.4) o RREQ_TRIES - 3 retries ([I-D:ietf-manet-dymo], sect. 5.4) o UNICAST_MESSAGE_SENT_TIMEOUT - 1 sec ([I-D:ietf-manet-dymo], sect. 6) Configuration Tables: 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. o TargetAddresses - If RREP_GENERATION is set to other than all, then the DYMO router must be configured with a set of addresses for which it is to generate RREQ messages. 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. ([I-D:ietf-manet-dymo], sect. 5.9). This would be a table containing the interfaces and associated information. Cole & Chakeres Expires August 21, 2008 [Page 7] Internet-Draft The DYMO MIB February 2008 o GatewayResponsibleAddresses - If IS_GATEWAY is set, then the DYMO router requires Dymo-gateway configuration parameters, e.g., addresses to proxy RM ([I-D:ietf-manet-dymo], sect. 5.8). This would be a table containing the addresses and associated information. 5.4. The State Group The State Subtree reports current state information, including forwarding tables. State information falls into 'General', 'Routing Information Base (RIB)', and 'Current Neighbors Table'. These are separately discussed below. (Note: these will serve as the object descriptions once they are discussed and refined.) 5.4.1. General State Information General state information could include: o DYMO Version Number - o Current Sequence Number - ([I-D:ietf-manet-dymo], sect. 3) 5.4.2. Routing Information Base The Routing Information Base (RIB) - ([I-D:ietf-manet-dymo], sect. 4.1), includes table entries with the following mandatory objects, i.e., o Route.Address o Route.SeqNum o Route.NextHopAddress o Route.NextHopInterface o Route.Broken and the following optional objects, i.e., o Route.Distance o Route.Prefix One consideration is how to handle RREQ which are in progress. The DYMO-MIB may want to populate a row in the RIB with the target Cole & Chakeres Expires August 21, 2008 [Page 8] Internet-Draft The DYMO MIB February 2008 address and have an indication that a RREQ is pending. Another option is to have a separate table containing pending information. 5.4.3. Current NextHop Table The current nexthop table - ([I-D:ietf-manet-dymo], sect. 5.5.1), includes a table of active (i.e., currently found as Next Hop addresses in the router's RIB) links to neighbors. This table could be populated by various means, including the use of the NHDP [I-D: ietf-manet-nhdp]. 5.5. The Performance Group Reports values relevant to system performance. These will serve as the object descriptions once they are discussed and refined.) Not sure this is something that would be useful to network managers. But it may be useful to have a set of performance related counters available through the DYMO-MIB. These could also be potentially useful in conjunction with traps or informs. One set of potential performance counters can be derived from the various configuration limits and timeout values. These performance counters would register the number of faults related to these configurable parameters. These would potentially aid in parameter tuning and routing protocol optimization. Another specific example would be the number of data packets awaiting a route, or a counter indicating the number of buffer overflows, etc. Another set, is the initial set of performance parameters written into this version of the DYMO-MIB draft are counters related to the number of RMs, RREQs, RREPs, and RERR messages. We could expose only aggregate information in the form of counters as shown below. Or could build tables indexed by InetAddress of targets. 5.6. The Notifications Group The Notifications Subtree contains the list of notifications supported within the DYMO-MIB and their intended purpose or utility. What would be a potential list of notifications for the DYMO-MIB, e.g., o Cole & Chakeres Expires August 21, 2008 [Page 9] Internet-Draft The DYMO MIB February 2008 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] 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. Cole & Chakeres Expires August 21, 2008 [Page 10] Internet-Draft The DYMO MIB February 2008 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 "200802151500Z" -- February 15, 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 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 ... Cole & Chakeres Expires August 21, 2008 [Page 11] Internet-Draft The DYMO MIB February 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 REVISION "200802151500Z" -- February 15, 2008 DESCRIPTION "The original version of this MIB module, published as RFCXXXX." -- 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 -- -- (are these necessary to or used in DYMO?) InstanceID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An identifier for the instance of the DYMO routing protocol running on the routing. Multiple instances of the DYMO protocol may run concurrently on the same device." SYNTAX InetAddress RouterID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A DYMO Router Identifier. Note that the Router ID, in DYMO, has the same format as an IP address, but identifies the router independent of its IP address." SYNTAX InetAddress -- -- dymoGeneralGroup -- Cole & Chakeres Expires August 21, 2008 [Page 12] Internet-Draft The DYMO MIB February 2008 -- Note: These objects apply globally to the router's -- DYMO routing process. dymoGeneralGroup OBJECT IDENTIFIER ::= { dymo 1 } --RouterID --AdministrativeStatus --DymoVersion --GatewayEnabled --NHDPEnabled dymoRouterId OBJECT-TYPE SYNTAX RouterID MAX-ACCESS read-write STATUS current DESCRIPTION "A 32-bit integer uniquely identifying the router in the DYMO routing domain. By convention, to ensure uniqueness, this should default to the value of one of the router's IP interface addresses. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." REFERENCE "" ::= { dymoGeneralGroup 1 } dymoAdminStat 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." ::= { dymoGeneralGroup 2 } dymoVersionNumber OBJECT-TYPE SYNTAX INTEGER { version1 (1) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current version number of the DYMO protocol is X." Cole & Chakeres Expires August 21, 2008 [Page 13] Internet-Draft The DYMO MIB February 2008 REFERENCE "" ::= { dymoGeneralGroup 3 } dymoGatewayRtrStatus OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "A flag to note whether this router is configured as an DYMO Gateway Router. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." REFERENCE "" ::= { dymoGeneralGroup 4 } dymoNhdpStatus OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "A flag to note whether this router is configured as to run the NHDP for next hop status tracking. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." REFERENCE "" ::= { dymoGeneralGroup 5 } -- -- dymoConfigurationGroup -- -- Contains the DYMO objects which configure specific options -- which determine the overall performance and operation of the -- routing protocol. dymoConfigurationGroup OBJECT IDENTIFIER ::= { dymo 2 } --Protocol Configuration Parameter Objects: --RREP_GENERATION --IS_GATEWAY --RESPONSIBLE_ADDRESSES Cole & Chakeres Expires August 21, 2008 [Page 14] Internet-Draft The DYMO MIB February 2008 --DYMO_INTERFACES --INCLUDE_TARGET_INFORMATION --APPEND_OWN_ADDRESSES --INCREMENT_OWN_SEQNUM_ON_APPEND --INCLUDE_OWN_INFORMATION_ON_APPEND --APPEND_OTHER_ADDRESSES --INCLUDE_OTHER_INFORMATION --GENERATE_RERR_IMMEDIATELY --RERR_INCLUDE_ALL_UNREACHABLES --UNKNOWN_TYPE_HANDLING --Timer Configuration Objects --ROUTE_TIMEOUT --NET_TRANVERSAL_TIME --ROUTE_DELETE_TIMEOUT --ROUTE_AGE_MAX_TIMEOUT --ROUTE_AGE_MIN_TIMEOUT --ROUTE_NEW_TIMEOUT --ROUTE_USED_TIMEOUT --RREQ_WAIT_TIME --RREQ_TRIES --UNICAST_MESSAGE_SENT_TIMEOUT --Configuration Tables --LocalHosts --TargetAddresses --DymoInterfaces --GatewayResponsibleAddresses --Protocol Configuration Parameter Objects: -- (insert Protocol Config Parameter Ojects here.) --Timer Configuration Objects -- (insert Timer Configuration Objects here.) dymoRouteTimeout OBJECT-TYPE SYNTAX Integer32 (1..1024) UNITS "seconds" MAX-ACCESS read-write STATUS current Cole & Chakeres Expires August 21, 2008 [Page 15] Internet-Draft The DYMO MIB February 2008 DESCRIPTION "The DYMO ROUTE_TIMEOUT parameter value." REFERENCE "" DEFVAL { 5 } ::= { dymoConfigurationGroup 15 } dymoNetworkTranversalTime OBJECT-TYPE SYNTAX Integer32 (1..65536) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The DYMO NET_TRANVERSAL_TIME parameter value." REFERENCE "" DEFVAL { 1000 } ::= { dymoConfigurationGroup 16 } 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 17 } dymoRouteAgeMaximumTimeout OBJECT-TYPE SYNTAX Integer32 (1..1024) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The DYMO ROUTE_AGE_MAX_TIMEOUT parameter value." REFERENCE "" Cole & Chakeres Expires August 21, 2008 [Page 16] Internet-Draft The DYMO MIB February 2008 DEFVAL { 60 } ::= { dymoConfigurationGroup 18 } 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 19 } dymoRouteNewTimeout OBJECT-TYPE SYNTAX Integer32 (1..1024) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The DYMO ROUTE_NEW_TIMEOUT parameter value. The default value for this object should be the dymoRouteTimeout value." REFERENCE "" DEFVAL { 5 } ::= { dymoConfigurationGroup 20 } 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 Cole & Chakeres Expires August 21, 2008 [Page 17] Internet-Draft The DYMO MIB February 2008 "" DEFVAL { 5 } ::= { dymoConfigurationGroup 21 } dymoRreqWaitTime OBJECT-TYPE SYNTAX Integer32 (1..65536) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The DYMO RREQ_WAIT_TIME parameter value. The default setting for this object is the 2*dymoNetworkTraversalTime." REFERENCE "" DEFVAL { 2000 } ::= { dymoConfigurationGroup 22 } dymoRreqRetries OBJECT-TYPE SYNTAX Integer32 (1..1024) UNITS "" MAX-ACCESS read-write STATUS current DESCRIPTION "The DYMO RREQ_TRIES parameter value." REFERENCE "" DEFVAL { 3 } ::= { dymoConfigurationGroup 23 } dymoUnicastMessageSentTimeout OBJECT-TYPE SYNTAX Integer32 (1..1024) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The DYMO UNICAST_MESSAGE_SENT_TIMEOUT parameter value." REFERENCE "" DEFVAL { 1 } ::= { dymoConfigurationGroup 24 } Cole & Chakeres Expires August 21, 2008 [Page 18] Internet-Draft The DYMO MIB February 2008 --Configuration Tables -- (insert Configuration Table here.) --LocalHosts Table -- (insert LocalHosts Table here.) --TargetAddresses Table dymoAddrDiscRangeTable OBJECT-TYPE SYNTAX SEQUENCE OF DymoAddrDiscRangeEntry MAX-ACCESS not-accessible STATUS obsolete DESCRIPTION "The Dymo Address Discovery Range Table identifies the target addresses to issue RREP messages. 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 "" ::= { ospf 5 } dymoAddrDiscRangeEntry OBJECT-TYPE SYNTAX dymoAddrDiscRangeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A single target 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 { dymoAddrDiscRangeNet } ::= { dymoAddrDiscRangeTable 1 } DymoAddrDiscRangeEntry ::= SEQUENCE { dymoAddrDiscRangeNet InetAddress, dymoAddrDiscRangeMask InetAddress, dymoAddrDiscRangeStatus RowStatus, dymoAddrDiscRangeEffect INTEGER } dymoAddrDiscRangeNet OBJECT-TYPE Cole & Chakeres Expires August 21, 2008 [Page 19] Internet-Draft The DYMO MIB February 2008 SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP address of the net or subnet indicated by the range." REFERENCE "" ::= { dymoAddrDiscRangeEntry 1 } dymoAddrDiscRangeMask OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The subnet mask that pertains to the net or subnet." REFERENCE "" ::= { dymoAddrDiscRangeEntry 2 } dymoAddrDiscRangeStatus 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." ::= { dymoAddrDiscRangeEntry 4 } --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 Cole & Chakeres Expires August 21, 2008 [Page 20] Internet-Draft The DYMO MIB February 2008 "" ::= { dymoConfigurationGroup XX } 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 } DymoIfEntry ::= SEQUENCE { dymoIfIpAddress InetAddress, dymoIfType INTEGER, 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 } dymoIfType OBJECT-TYPE -- Is this necessary for dymo SYNTAX INTEGER { type1 (1), type2 (2), } MAX-ACCESS read-create STATUS current DESCRIPTION "The DYMO interface type. By way of a default, this field may be intuited Cole & Chakeres Expires August 21, 2008 [Page 21] Internet-Draft The DYMO MIB February 2008 from the corresponding value of ifType." ::= { dymoIfEntry 3 } 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 4 } 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 5 } --GatewayResponsibleAddresses Table -- (insert GatewayResponsibleAddresses Table here.) -- -- dymoStateGroup -- -- Contains information describing the current state of the DYMO -- process. dymoStateGroup OBJECT IDENTIFIER ::= { dymo 3 } --General State Information, i.e., Cole & Chakeres Expires August 21, 2008 [Page 22] Internet-Draft The DYMO MIB February 2008 --CURRENT_SEQ_NUMBER --Routing Information Base (RIB) Table --table entries with the following mandatory objects, i.e., --Route.Address --Route.SeqNum --Route.NextHopAddress --Route.NextHopInterface --Route.Broken --and the following optional objects, i.e., --Route.Distance --Route.Prefix --Current NextHop Table --Routing Information Base (RIB) Table dymoRIBTable OBJECT-TYPE SYNTAX SEQUENCE OF DymoRIBEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The DYMO Routing Information Base (RIB) Table describes the current entries which enable packet forwarding. This table should augment the MIB-II IpForwardingGroup." REFERENCE "" ::= { dymoStateGroup XX } dymoRIBEntry OBJECT-TYPE SYNTAX DymoRIBEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The DYMO RIB entry describes the forwarding table entries currently active in the Router." INDEX { dymoRouteIpAddress } -- not sure best -- indexing ::= { dymoRIBTable 1 } DymoRIBEntry ::= SEQUENCE { dymoRouteIpAddress InetAddress, Cole & Chakeres Expires August 21, 2008 [Page 23] Internet-Draft The DYMO MIB February 2008 dymoRouteSeqNo INTEGER, dymoRouteNextHopIpAddress InetAddress, dymoRouteNextHopInterface InetAddress, dymoRouteBroken INTEGER, dymoRouteDist INTEGER, dymoRouteIpPrefix InetAddress } dymoRouteIpAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of this Route Target." ::= { dymoRIBEntry 1 } dymoRouteSeqNo OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "The ..." ::= { dymoRIBEntry 2 } dymoRouteNextHopIPAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of ..." ::= { dymoRIBEntry 3 } dymoRouteNextHopInterface OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of ..." ::= { dymoRIBEntry 4 } dymoRouteBroken OBJECT-TYPE Cole & Chakeres Expires August 21, 2008 [Page 24] Internet-Draft The DYMO MIB February 2008 SYNTAX INTEGER { down (0), up (1) } MAX-ACCESS read-only STATUS current DESCRIPTION "The ..." DEFVAL { down } ::= { dymoIfEntry 5 } dymoRouteDist OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "The ..." ::= { dymoRIBEntry 6 } dymoRouteIpPrefix OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP prefix of this Route entry." ::= { dymoRIBEntry 7 } --Current NextHop Table -- (insert Current NextHop Table here.) -- -- dymoPerformanceGroup -- -- Contains objects which help to characterize the performance of -- the DYMO process, typically counters. dymoPerformanceGroup OBJECT IDENTIFIER ::= { dymo 4 } --Could expose only aggregate information in the form of --counters as shown below. Or could build tables indexed --by InetAddress of targets. Cole & Chakeres Expires August 21, 2008 [Page 25] Internet-Draft The DYMO MIB February 2008 --Number RMs sent/recv --Number RREQs sent/recv --Number RREPs sent/recv --Number Intermediate RREQs responded to --Other performance tuning objects, e.g., --Buffer Overflows -- -- Notifications -- --What are the valuable notification information for the --DYMO-MIB? -- -- Conformance information -- -- To be determined. dymoCompliances OBJECT IDENTIFIER ::= { dymoConformance 1 } dymoGroups OBJECT IDENTIFIER ::= { dymoConformance 2 } -- Compliance Statements dymoGeneralCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "A general compliance which allows ...." MODULE -- this module MANDATORY-GROUPS { dymoGeneralGroup } ::= { dymoCompliances 1 } -- -- DYMO Group Compliance -- Cole & Chakeres Expires August 21, 2008 [Page 26] Internet-Draft The DYMO MIB February 2008 -- -- 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. [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. Cole & Chakeres Expires August 21, 2008 [Page 27] Internet-Draft The DYMO MIB February 2008 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 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 Cole & Chakeres Expires August 21, 2008 [Page 28] Internet-Draft The DYMO MIB February 2008 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. 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. Cole & Chakeres Expires August 21, 2008 [Page 29] Internet-Draft The DYMO MIB February 2008 [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. 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. 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 InstanceID for running multiple, concurrent DYMO domains within a single router? 3. Is support for addresses-less interfaces required? Cole & Chakeres Expires August 21, 2008 [Page 30] Internet-Draft The DYMO MIB February 2008 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. 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. * * * *************************************************************** Cole & Chakeres Expires August 21, 2008 [Page 31] Internet-Draft The DYMO MIB February 2008 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 (editor) 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 August 21, 2008 [Page 32] Internet-Draft The DYMO MIB February 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 August 21, 2008 [Page 33]