Internet Engineering Task Force J. Nguyen Internet-Draft R. Cole Intended status: Experimental US Army CERDEC Expires: May 9, 2013 November 5, 2012 Definition of Managed Objects for the Manet Essential Connected Dominating Set (E-CDS) Process draft-nguyen-manet-ecds-mib-01 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 Essential Connected Dominating Set (E-CDS) Process for Mobile Ad-Hoc Networks (MANETs). The ECDS-MIB also reports state information, performance metrics, and notifications. In addition to configuration, the additional state and performance information is useful to operators troubleshooting multicast forwarding problems. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on May 9, 2013. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect Nguyen & Cole Expires May 9, 2013 [Page 1] Internet-Draft The ECDS-MIB November 2012 to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. ECDS-MIB Management Model . . . . . . . . . . . . . . . . 4 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 5 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 5 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 5 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 6 5.5. The Notifications Group . . . . . . . . . . . . . . . . . 6 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 6 6.2. Relationship to the SMF-MIB . . . . . . . . . . . . . . . 6 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 6 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. Security Considerations . . . . . . . . . . . . . . . . . . . 14 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 11.1. Normative References . . . . . . . . . . . . . . . . . . . 14 11.2. Informative References . . . . . . . . . . . . . . . . . . 14 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 14 Nguyen & Cole Expires May 9, 2013 [Page 2] Internet-Draft The ECDS-MIB November 2012 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects for configuring aspects of a process implementing Essential Connected Dominating Set (E-CDS) [RFC 5614] for Mobile Ad-Hoc Networks (MANETs). E-CDS transforms 2-hop neighborhood topology information for routers to dynamically perform relay self election to form CDS. The ECDS-MIB, an extension to SMF- MIB [draft-ietf-manet-smf-mib-03], reports state information, performance metrics, and notifications. In addition to configuration, this additional state and performance information is useful to operators troubleshooting multicast forwarding 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 RFC3410 [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. 4. Overview E-CDS provides method for implementing selection of Multipoint Relay nodes that define an estimate of the Minimum Connected Dominating Set (MCDS) flooding. The MCDS provides an efficient and complete coverage of the nodes comprising the MANET. The packet forwarding rules does not require knowledge of previous hop discovery. Routers that run Simplified Multicast Forwarding (SMF) and have E-CDS enabled can be mixed with routers that run SMF [RFC6621] and Classic Flooding (CF) enabled without a problem, even those are not participating in Neighborhood Discovery Protocol (NHDP) [RFC6130]. Another benefit is that packets opportunistically received from non-symmetric neighbors may be forwarded without compromising flooding efficiency or correctness. Furthermore, multicast sources not participating in NHDP may freely inject their traffic and any neighboring E-CDS relays Nguyen & Cole Expires May 9, 2013 [Page 3] Internet-Draft The ECDS-MIB November 2012 will properly forward the traffic. The E-CDS based relay set selection algorithm is based upon [RFC5614]. 4.1. ECDS-MIB Management Model As mentioned in Overview section, ECDS-MIB is an extension to SMF- MIB. Meaning, the overall architecture is based on SMF. ______________ _____________ | | | | | Neighborhood | | Relay Set | | Discovery |------------->| Selection | | | neighbor | Algorithm | |______________| info |_____________| \ / \ / neighbor\ /forwarding info* \ ____________ / status \ | | / `-->| Forwarding |<--' | Process | ~~~~~~~~~~~~~~~~~>|____________|~~~~~~~~~~~~~~~~~> incoming packet, forwarded packets interface id*, and previous hop* Figure 1: SMF router Architecture. The Relay Set Selection Algorithm (RSSA) can rely upon topology information gotten from the MANET NHDP, from the specific MANET routing protocol running on the node, or from Layer 2 information passed up to the higher layer protocol processes. As for ECDS, nodes, which select themselves as relays using router identifier and a nodal metric known as "Router Priority" for all one-hop and two-hop neighbors. Differing Router Priority can result in different CDSs for a given network. 4.2. Terms The following definitions apply throughout this document: o Control Objects - Objects which are initialized to default settings or set through the management interface defined by this MIB. o State Objects - objects are automatically generated values which define the current operating state of the E-CDS process in the Nguyen & Cole Expires May 9, 2013 [Page 4] Internet-Draft The ECDS-MIB November 2012 router. o Performance Objects - objects are automatically generated values which help an administrator or automated tool to assess the performance of the CDS multicast process on the router and the overall multicasting performance within the MANET routing domain. 5. Structure of the MIB Module This section presents the structure of the ECDS-MIB module. The objects are arranged into the following groups: 5.1. Textual Conventions The textual conventions defined within the ECDS-MIB are as follows: o EcdsStatus is defined within the ECDS-MIB. This contains the current operational status of the E-CDS process on an interface. o EcdsID represents an index that identifies a specific E-CDS operational mode. 5.2. The Configuration Group The E-CDS device is configured with a set of controls. Some of the prominent configuration controls for the SMF E-CDS device follow: o E-CDS Operational Mode: indicates router has E-CDS enabled o Router Identifier: indicates router's unique identifier in E-CDS neighborhood o Router Priority: indicates nodal metric value for all one-hop and two-hop neighbors. o Configuration method that computes Router Priority: indicates what method Router Priority is computed: dynamically configured, management configured, or other. 5.3. The State Group The state of an ECDS device can be retrieved from the followings: o E-CDS Operational State - is the node currently in or out of the Relay Set o Current Router Priority value Nguyen & Cole Expires May 9, 2013 [Page 5] Internet-Draft The ECDS-MIB November 2012 5.4. The Performance Group The E-CDS performance counters consist of per node objects: o Counter of times the given node changed into or out of E-CDS. o Counter of times the Router Priority has been changed. 5.5. The Notifications Group The Notifications Subtree contains the list of notifications supported within the ECDS-MIB and their intended purpose or utility. 6. Relationship to Other MIB Modules 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 ECDS-MIB does not duplicate those objects. 6.2. Relationship to the SMF-MIB TBD 6.3. MIB modules required for IMPORTS The textual conventions imported for use in the SMF-MIB are as follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Unsigned32, Integer32 and mib-2 textual conventions are imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus and TruthValue textual conventions are imported from RFC 2579 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATIONGROUP textual conventions are imported from RFC 2580 [RFC2580]. The InterfaceIndexOrZero textual convention is imported from RFC 2863 [RFC2863]. The SnmpAdminString textual convention is imported from RFC 3411 [RFC3411]. The InetAddress, InetAddressType and InetAddressPrefixLength textual conventions are imported from RFC 4001 [RFC4001]. 7. Definitions MANET-ECDS-MIB DEFINITIONS ::= BEGIN Nguyen & Cole Expires May 9, 2013 [Page 6] Internet-Draft The ECDS-MIB November 2012 IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Integer32, TimeTicks, experimental FROM SNMPv2-SMI --[RFC2578] TEXTUAL-CONVENTION, RowStatus, TruthValue FROM SNMPv2-TC -- [RFC2579] MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] InterfaceIndexOrZero FROM IF-MIB -- [RFC2863] SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411] InetAddress, InetAddressType, InetAddressPrefixLength FROM INET-ADDRESS-MIB -- [RFC4001] ; manetEcdsMIB MODULE-IDENTITY ORGANIZATION "IETF MANET Working Group" CONTACT-INFO "WG E-Mail: manet@ietf.org WG Chairs: jmacker@nrl.navy.mil sratliff@cisco.com Editors: James H. Nguyen US Army CERDEC Space and Terrestrial Communications 6010 Frankford Road Aberdeen Proving Ground, MD 21005 USA +1 443 395-5628 Robert G. Cole US Army CERDEC Space and Terrestrial Communications Aberdeen Proving Ground, MD 21005 USA +1 443 395-8744" DESCRIPTION Nguyen & Cole Expires May 9, 2013 [Page 7] Internet-Draft The ECDS-MIB November 2012 "This MIB module contains managed object definitions for the Manet E-CDS process defined in: [RFC5614] 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." -- -- TEXTUAL CONVENTIONs -- EcdsStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An indication of the operability of a E-CDS function or feature or example, the status of an node: - 'enabled' indicates that it is performing E-CDS functions - 'disabled' indicates that it is not." SYNTAX INTEGER { enabled (1), disabled (2) } -- -- Top-Level Object Identifier Assignments -- ecdsMIBNotifications OBJECT IDENTIFIER ::= { manetEcdsMIB 0 } ecdsMIBObjects OBJECT IDENTIFIER ::= { manetEcdsMIB 1 } ecdsMIBConformance OBJECT IDENTIFIER ::= { manetEcdsMIB 2 } -- -- ecdsMIBObjects Assignments: -- ecdsConfigurationGroup - 1 -- ecdsStateGroup - 2 -- ecdsPerformanceGroup - 3 -- ecdsNotificationGroup - 4 -- -- -- ecdsConfigurationGroup -- -- This group contains the E-CDS objects that configure specific -- options that determine the overall performance and operation -- of the multicast forwarding process for the router device -- ecdsConfigurationGroup OBJECT IDENTIFIER ::= { ecdsMIBObjects 1 } ecdsAdminStatus OBJECT-TYPE Nguyen & Cole Expires May 9, 2013 [Page 8] Internet-Draft The ECDS-MIB November 2012 SYNTAX EcdsStatus MAX-ACCESS read-write STATUS current DESCRIPTION "The configured status of the E-CDS process on this device. - Enabled(1) means that E-CDS is configured to run on this device. - Disabled(2) mean that the E-CDS process is configured off. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." ::= { ecdsConfigurationGroup 1 } ecdsRouterID OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-write STATUS current DESCRIPTION "The IP address used as the E-CDS router ID. This can be set by the management station. If not explicitly set, then the device should select a routable IP address assigned to this router for use as the 'ecdsRouterID'. The ecdsRouterID is a logical identification that MUST be consistent across interoperating E-CDS neighborhoods and it is RECOMMENDED to be chosen as the numerically largest address contained in a node's 'Neighbor Address List' as defined in NHDP. A ecdsRouterID MUST be unique within the scope of the operating MANET network regardless of the method used for selecting it. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." ::= { ecdsConfigurationGroup 2 } ecdsConfiguredRtrPriMethod OBJECT-TYPE SYNTAX INTEGER { dynamically_configured (1), management_configured (2), other (3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object indicates which method Router Priority value is computed." ::= { ecdsConfiguredRtrPriMethod 3 } ecdsConfiguredRouterPriority OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "a nodal metric for all 1-hop and 2-hop neighbors. Relay routers use tuple of router identifier and router priority to compute self-election of MPR." ::= { ecdsConfigurationGroup 4 } ecdsConfiguredMember OBJECT-TYPE SYNTAX INTEGER { potential(1), always(2), never(3) } Nguyen & Cole Expires May 9, 2013 [Page 9] Internet-Draft The ECDS-MIB November 2012 MAX-ACCESS read-write STATUS current DESCRIPTION "The E-CDS downselects a set of forwarders for multicast forwarding. Sometimes, it is useful to force an agent to be included or excluded from the resulting CDS. This object is a switch to allow for this behavior. - The value potential(1) allows the selected E-CDS to determine if this agent is included or excluded from the E-CDS. - The value always(1) forces the selected E-CDS process - The value never(3) forces not to use E-CDS process - The default setting for this object is 'potential(1)'. Other settings could pose operational risks under certain conditions. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." DEFVAL { 1 } ::= { ecdsConfigurationGroup 5 } -- -- E-CDS State Group -- ecdsStateGroup OBJECT IDENTIFIER ::= { ecdsMIBObjects 2 } ecdsOperationStatus OBJECT-VALUE SYNTAX EcdsStatus MAX-ACCESS read-only STATUS current DESCRIPTION "The configured status of the E-CDS process on this device. - Enabled(1) means that E-CDS is configured to run on this device. - Disabled(2) mean that the E-CDS process is configured off. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." ::= { ecdsStateGroup 1 } ecdsCurrentRtrPriValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "current Router Priority value" :: { ecdsStateGroup 2 } ecdsCurrentInEcds OBJECT-TYPE SYNTAX INTEGER { true (0), Nguyen & Cole Expires May 9, 2013 [Page 10] Internet-Draft The ECDS-MIB November 2012 false (1) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates that the current node has E-CDS configured and in E-CDS." :: { ecdsStateGroup 3 } -- -- E-CDS Performance Group -- ecdsPerformanceGroup OBJECT IDENTIFIER ::= { ecdsMIBObjects 3 } ecdsInEcdsChange OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates how many times the current node is configured to be in E-CDS." :: { ecdsPerformanceGroup 1 } ecdsCurrentRtrPriValueChange SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates how many times the Router Priority of the current node has been changed." :: { ecdsPerformanceGroup 2 } -- -- E-CDS Notification -- ecdsMIBNotifObjects OBJECT IDENTIFIER ::= { ecdsMIBNotifications 1 } -- -- E-CDS Notification Objects -- ecdsAdminStatusChange NOTIFICATION-TYPE OBJECTS { ecdsRouterID, -- the originator of notification ecdsAdminStatus -- the new status of E-CDS process } STATUS current Nguyen & Cole Expires May 9, 2013 [Page 11] Internet-Draft The ECDS-MIB November 2012 DESCRIPTION "ecdsAdminStatusChange notification is sent when ecdsAdminStatus is changed." ::= { ecdsMIBNotifObjects 1 } ecdsConfiguredMemberChange NOTIFICATION-TYPE OBJECTS { ecdsRouterID, ecdsConfiguredMember } STATUS current DESCRIPTION "ecdsConfiguredMemberChange notification is sent when ecdsConfiguredMember is changed." ::= { ecdsMIBNotifObjects 2 } ecdsRtrPriChange NOTIFICATION-TYPE OBJECTS { ecdsRouterID, ecdsConfiguredRouterPriority } STATUS current DESCRIPTION "ecdsIfRtrPriChange notification is sent when ecdsIfRtrPri value is changed." ::= { ecdsMIBNotifObjects 3 } ecdsRtrPriMethodChange NOTIFICATION-TYPE OBJECTS { ecdsRouterID, ecdsConfiguredRtrPriMethod } STATUS current DESCRIPTION "ecdsRtrPriMethodChange notification is sent when ecdsConfiguredRtrPriMethod is changed." ::= { ecdsMIBNotifObjects 3 } -- -- Compliance Statements -- ecdsCompliances OBJECT IDENTIFIER ::= { ecdsMIBConformance 1 } ecdsMIBGroups OBJECT IDENTIFIER ::= { ecdsMIBConformance 2 } ecdsBasicCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The basic implementation requirements for managed network entities that implement the E-CDS process." MODULE -- this module MANDATORY-GROUPS { ecdsConfigurationObjectsGroup Nguyen & Cole Expires May 9, 2013 [Page 12] Internet-Draft The ECDS-MIB November 2012 } ::= { ecdsCompliances 1 } ecdsFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The full implementation requirements for managed network entities that implement the E-CDS process." MODULE -- this module MANDATORY-GROUPS { ecdsConfigurationObjectsGroup, ecdsStateObjectsGroup, ecdsPerformanceObjectsGroup, ecdsNotificationsGroup } ::= { ecdsCompliances 2 } ecdsConfigObjectsGroup OBJECT-GROUP OBJECTS { ecdsAdminStatus, ecdsRouterID, ecdsConfiguredRouterPriority, ecdsConfiguredMember, ecdsConfiguredRtrPriMethod } STATUS current DESCRIPTION "Set of configuration objects implemented in this module" ::= { ecdsMIBGroups 1 } ecdsStateObjectsGroup OBJECT-GROUP OBJECTS { ecdsOperationStatus, ecdsCurrentRtrPri, ecdsCurrentInEcds } STATUS current DESCRIPTION "set of state objects implemented in this module" ::= { ecdsMIBGroups 2 } ecdsPerformanceObjectsGroup OBJECT-GROUP OBJECTS { ecdsAdminStatusChange, ecdsCurrentRirPriValueChange } STATUS current DESCRIPTION "set of performance objects implemented in this module" Nguyen & Cole Expires May 9, 2013 [Page 13] Internet-Draft The ECDS-MIB November 2012 ::= { ecdsMIBGroups 3 } ecdsNotificationsGroup OBJECT-GROUP OBJECTS { ecdsAdminStatusChange, ecdsConfiguredMemberChange, ecdsRtrPriChange, ecdsRtrPriMethodChange } STATUS current DESCRIPTION "set of notification objects implemented in this module" ::= { ecdsMIBGroups 4 } END 8. Security Considerations TBD 9. Contributors TTBD 10. Acknowledgements TBD 11. References 11.1. Normative References 11.2. Informative References Appendix A. Change Log Appendix B. Open Issues Nguyen & Cole Expires May 9, 2013 [Page 14] Internet-Draft The ECDS-MIB November 2012 Authors' Addresses James H. Nguyen US Army CERDEC 6010 Frankford Road Aberdeen Proving Ground, Maryland 21005 USA Phone: +1 443 395 5628 EMail: james.h.nguyen4.civ@mail.mil Robert G. Cole US Army CERDEC 6010 Frankford Road Aberdeen Proving Ground, Maryland 21005 USA Phone: +1 443 395 8744 EMail: robert.g.cole@us.army.mil Nguyen & Cole Expires May 9, 2013 [Page 15]