Tech-invite3GPPspaceIETF RFCsSIP
93929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 7367

Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set Process

Pages: 65
Experimental
Part 1 of 4 – Pages 1 to 10
None   None   Next

Top   ToC   RFC7367 - Page 1
Internet Engineering Task Force (IETF)                           R. Cole
Request for Comments: 7367                                US Army CERDEC
Category: Experimental                                         J. Macker
ISSN: 2070-1721                                               B. Adamson
                                               Naval Research Laboratory
                                                            October 2014


  Definition of Managed Objects for the Mobile Ad Hoc Network (MANET)
            Simplified Multicast Framework Relay Set Process

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 Simplified Multicast Forwarding (SMF) process for Mobile Ad Hoc Networks (MANETs). The SMF-MIB module also reports state information, performance information, 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 document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7367.
Top   ToC   RFC7367 - Page 2
Copyright Notice

   Copyright (c) 2014 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
   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. SMF Management Model .......................................4 4.2. Terms ......................................................5 5. Structure of the MIB Module .....................................5 5.1. Textual Conventions ........................................6 5.2. The Capabilities Group .....................................6 5.3. The Configuration Group ....................................6 5.4. The State Group ............................................7 5.5. The Performance Group ......................................7 5.6. The Notifications Group ....................................7 5.7. Tables and Indexing ........................................8 6. Relationship to Other MIB Modules ...............................9 6.1. Relationship to the SNMPv2-MIB .............................9 6.2. Relationship to the IP-MIB .................................9 6.3. Relationship to the IPMCAST-MIB ............................9 6.4. MIB Modules Required for IMPORTS ..........................10 6.5. Relationship to Future RSSA-MIB Modules ...................10 7. SMF-MIB Definitions ............................................10 8. IANA-SMF-MIB Definitions .......................................51 9. Security Considerations ........................................56 10. Applicability Statement .......................................59 11. IANA Considerations ...........................................62 12. References ....................................................62 12.1. Normative References .....................................62 12.2. Informative References ...................................64 Acknowledgements ..................................................65 Contributors ......................................................65 Authors' Addresses ................................................65
Top   ToC   RFC7367 - Page 3

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 Simplified Multicast Forwarding (SMF) [RFC6621] for Mobile Ad Hoc Networks (MANETs). SMF provides multicast Duplicate Packet Detection (DPD) and supports algorithms for constructing an estimate of a MANET Minimum Connected Dominating Set (MCDS) for efficient multicast forwarding. The SMF-MIB module also reports state information, performance information, 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 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", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

4. Overview

SMF provides methods for implementing DPD-based multicast forwarding with the optional use of CDS-based relay sets. The CDS provides a complete connected coverage of the nodes comprising the MANET. The MCDS is the smallest set of MANET nodes (comprising a connected cluster) that cover all the nodes in the cluster with their transmissions. As the density of the MANET nodes increase, the fraction of nodes required in an MCDS decreases. Using the MCDS as a multicast forwarding set then becomes an efficient multicast mechanism for MANETs.
Top   ToC   RFC7367 - Page 4
   Various algorithms for the construction of estimates of the MCDS
   exist.  The Simplified Multicast Framework [RFC6621] describes some
   of these.  It further defines various operational modes for a node
   that is participating in the collective creation of the MCDS
   estimates.  These modes depend upon the set of related MANET routing
   and discovery protocols and mechanisms in operation in the specific
   MANET node.

   A SMF router's MIB module contains SMF process configuration
   parameters (e.g., specific CDS algorithm), state information (e.g.,
   current membership in the CDS), performance counters (e.g., packet
   counters), and notifications.

4.1. SMF Management Model

This section describes the management model for the SMF node process. Figure 1 (reproduced from Figure 1 of [RFC6621]) shows the relationship between the SMF Relay Set Selection Algorithm and the related algorithms, processes, and protocols running in the MANET nodes. The Relay Set Selection Algorithm (RSSA) can rely upon topology information acquired from the MANET Neighborhood Discovery Protocol (NHDP), from the specific MANET routing protocol running on the node, or from Layer 2 information passed up to the higher layer protocol processes. ______________ ____________ | | | | | Neighborhood | | Relay Set | | Discovery |------------->| Selection | | | neighbor | | |______________| info |____________| \ / neighbor\ / forwarding info* \ _____________ / status \ | | / `-->| Forwarding |<--' | Process | ----------------->|_____________|-----------------> incoming packet, forwarded packets interface id*, and previous hop* Figure 1: SMF Router Architecture The asterisks (*) mark the primitives and relationships needed by relay set algorithms requiring previous-hop packet-forwarding knowledge.
Top   ToC   RFC7367 - Page 5

4.2. Terms

The following definitions apply throughout this document: Configuration Objects: switches, tables, and objects that are initialized to default settings or set through the management interfaces such as defined by this MIB module. Tunable Configuration Objects: objects whose values affect timing or attempt bounds on the SMF Relay Set (RS) process. State Objects: automatically generated values that define the current operating state of the SMF RS process in the router. Performance Objects: automatically generated values that help an administrator or automated tool to assess the performance of the CDS multicast process on the router and the overall multicast performance within the MANET routing domain.

5. Structure of the MIB Module

This section presents the structure of the SMF-MIB module. The objects are arranged into the following groups: o smfMIBNotifications - defines the notifications associated with the SMF process. o smfMIBObjects - defines the objects forming the basis for the SMF- MIB module. These objects are divided up by function into the following groups: * Capabilities Group - This group contains the SMF objects that the device uses to advertise its local capabilities with respect to, e.g., the supported RSSAs. * Configuration Group - This group contains the SMF objects that configure specific options that determine the overall operation of the SMF process and the resulting multicast performance. * State Group - Contains information describing the current state of the SMF process such as the Neighbor Table. * Performance Group - Contains objects that help to characterize the performance of the SMF process, typically counters for statistical computations. o smfMIBConformance - defines two, i.e., minimal and full, conformance implementations for the SMF-MIB module.
Top   ToC   RFC7367 - Page 6

5.1. Textual Conventions

The Textual Conventions defined within the SMF-MIB module: o The SmfStatus is defined within the SMF-MIB module. This contains the current operational status of the SMF process on an interface. The Textual Conventions defined for the SMF-MIB module and maintained by IANA are: o The IANAsmfOpModeIdTC represents an index that identifies a specific SMF operational mode. This Textual Convention is maintained by IANA in the IANA-SMF-MIB. o The IANAsmfRssaIdTC represents an index that identifies, through reference, a specific RSSA available for operation on the device. This Textual Convention is maintained by IANA also in the IANA- SMF-MIB.

5.2. The Capabilities Group

The SMF device supports a set of capabilities. The list of capabilities that the device can advertise is as follows: o Operational Mode - topology information from NHDP, CDS-aware unicast routing, or Cross-layer from Layer 2. o SMF RSSA - the specific RSSA operational on the device. Note that configuration, state, and performance objects related to a specific RSSA must be defined within a separate MIB module.

5.3. The Configuration Group

The SMF device is configured with a set of controls. Some of the prominent configuration controls for the SMF device are: o Operational Mode - determines from where topology information is derived, e.g., NHDP, CDS-aware unicast routing, or Cross-layer from Layer 2. o SMF RSSA - the specific RSSA operational on the device. o Duplicate Packet detection for IPv4 - Identification-based or Hash-based DPD (I-DPD or H-DPD, respectively). o Duplicate Packet detection for IPv6 - Identification-based or Hash-based DPD.
Top   ToC   RFC7367 - Page 7
   o  SMF Type Message TLV - if NHDP mode is selected, then the SMF Type
      Message TLV MAY be included in the NHDP exchanges.

   o  SMF Address Block TLV - if NHDP mode is selected, then the SMF
      Address Block TLV SHOULD be included in the NHDP exchanges.

   o  SMF Address Forwarding Table - a table identifying configured
      multicast addresses to be forwarded by the SMF process.

5.4. The State Group

The State sub-tree reports current state information, for example, o Node RSSA State - identifies whether the node is currently in or out of the Relay Set. o Neighbors Table - a table containing current one-hop neighbors and their operational RSSA.

5.5. The Performance Group

The Performance sub-tree primarily reports counters that relate to SMF RSSA performance. The SMF performance counters consist of per- node and per-interface objects: o Total multicast packets received. o Total multicast packets forwarded. o Total duplicate multicast packets detected. o Per interface statistics table with the following entries: * Multicast packets received. * Multicast packets forwarded. * Duplicate multicast packets detected.

5.6. The Notifications Group

The Notifications sub-tree contains the list of notifications supported within the SMF-MIB module and their intended purpose and utility.
Top   ToC   RFC7367 - Page 8

5.7. Tables and Indexing

The SMF-MIB module contains a number of tables that record data related to: o configuration and operation of packet forwarding on the local router, o configuration and operation of local MANET interfaces on the router, and o configuration and operation of various RSSAs for packet forwarding. The SMF-MIB module's tables are indexed via the following constructs: o smfCapabilitiesIndex - the index identifying the combination of SMF mode and SMF RSSA available on this device. o smfCfgAddrForwardingIndex - the index to configured multicast address lists that are forwarded by the SMF process. o smfCfgIfIndex - the IfIndex of the interface on the local router on which SMF is configured. o smfStateNeighborIpAddrType, smfStateNeighborIpAddr, and smfStateNeighborPrefixLen - the interface index set of specific one-hop neighbor nodes to this local router. These tables and their associated indexing are defined in the SMF-MIB module: o smfCapabilitiesTable - identifies the resident set of (SMF Operational Modes, SMF RSSA algorithms) available on this router. This table has 'INDEX { smfCapabilitiesIndex }'. o smfCfgAddrForwardingTable - contains information on multicast addresses that are to be forwarded by the SMF process on this device. This table has 'INDEX { smfCfgAddrForwardingIndex }'. o smfCfgInterfaceTable - describes the SMF interfaces on this device that are participating in the SMF packet forwarding process. This table has 'INDEX { smfCfgIfIndex }'.
Top   ToC   RFC7367 - Page 9
   o  smfStateNeighborTable - describes the current neighbor nodes,
      their addresses and the SMF RSSA and the interface on which they
      can be reached.  This table has 'INDEX {
      smfStateNeighborIpAddrType, smfStateNeighborIpAddr,
      smfStateNeighborPrefixLen }'.

   o  smfPerfIpv4InterfacePerfTable - contains the IPv4-related SMF
      statistics per each SMF interface on this device.  This table has
      'INDEX { smfCfgIfIndex }'.

   o  smfPerfIpv6InterfacePerfTable - contains the IPv6-related SMF
      statistics per each SMF interface on this device.  This table has
      'INDEX { smfCfgIfIndex }'.

6. Relationship to Other MIB Modules

6.1. Relationship to the SNMPv2-MIB

The 'system' group in the SNMPv2-MIB module [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 SMF-MIB module does not duplicate those objects.

6.2. Relationship to the IP-MIB

It is an expectation that SMF devices will implement the standard IP- MIB module [RFC4293]. Exactly how to integrate SMF packet handling and management into the standard IP-MIB module management are part of the experiment. The SMF-MIB module counters within the smfPerformanceGroup count packets handled by the system and interface local SMF process (as discussed above). Not all IP (unicast and multicast) packets on a device interface are handled by the SMF process. So the counters are tracking different packet streams in the IP-MIB and SMF-MIB modules.

6.3. Relationship to the IPMCAST-MIB

The smfCfgAddrForwardingTable is essentially a filter table (if populated) that identifies addresses/packets to be forwarded via the local SMF flooding process. The IP Multicast MIB module in RFC 5132 [RFC5132] manages objects related to standard IP multicast, which could be running in parallel to SMF on the device. RFC 5132 manages traditional IP-based multicast (based upon multicast routing mechanisms). The SMF-MIB module provides management for a MANET subnet-based flooding mechanism which, may be used for
Top   ToC   RFC7367 - Page 10
   multicast transport (through SMF broadcast) depending upon the MANET
   dynamics and other factors regarding the MANET subnet.  Further, they
   may coexist in certain MANET deployments using the
   smfCfgAddrForwardingTable to hand certain IP multicast addresses to
   the SMF process and other IP multicast packets to be forwarded by
   other multicast mechanisms that are IP route based.  SMF and the
   associated SMF-MIB module are experimental and these are some of the
   experiments to be had with SMF and the SMF-MIB module.

6.4. MIB Modules Required for IMPORTS

The objects imported for use in the SMF-MIB module are as follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Integer32, TimeTicks and experimental macros are imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus, and TruthValue macros are imported from RFC 2579 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP, and NOTIFICATION-GROUP macros are imported from RFC 2580 [RFC2580]. The InterfaceIndexOrZero and ifName textual conventions are 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].

6.5. Relationship to Future RSSA-MIB Modules

In a sense, the SMF-MIB module is a general front-end to a set of yet-to-be developed RSSA-specific MIB modules. These RSSA-specific MIB modules will define the objects for the configuration, state, performance and notification required for the operation of these specific RSSAs. The SMF-MIB module Capabilities Group allows the remote management station the ability to query the router to discover the set of supported RSSAs.


(page 10 continued on part 2)

Next Section