draft-ietf-manet-rfc6779bis-05.txt   draft-ietf-manet-rfc6779bis-06.txt 
Network Working Group U. Herberg Network Working Group U. Herberg
Internet-Draft Internet-Draft
Obsoletes: 6779 (if approved) R. Cole Obsoletes: 6779 (if approved) R. Cole
Intended status: Standards Track US Army CERDEC Intended status: Standards Track US Army CERDEC
Expires: October 10, 2016 I. Chakeres Expires: November 24, 2016 I. Chakeres
Delvin Delvin
T. Clausen T. Clausen
LIX, Ecole Polytechnique Ecole Polytechnique
April 8, 2016 May 23, 2016
Definition of Managed Objects for the Neighborhood Discovery Protocol Definition of Managed Objects for the Neighborhood Discovery Protocol
draft-ietf-manet-rfc6779bis-05 draft-ietf-manet-rfc6779bis-06
Abstract Abstract
This document revises, extends, and replaces RFC 6779. It defines a This document revises, extends, and replaces RFC 6779. It defines a
portion of the Management Information Base (MIB) for use with network portion of the Management Information Base (MIB) for use with network
management protocols in the Internet community. In particular, it management protocols in the Internet community. In particular, it
describes objects for configuring parameters of the Neighborhood describes objects for configuring parameters of the Neighborhood
Discovery Protocol (NHDP) process on a router. The MIB module Discovery Protocol (NHDP) process on a router. The extensions
defined in this document, denoted NHDP-MIB, also reports state, described in this document add objects and values to support the NHDP
performance information, and notifications about NHDP. This optimization specified in RFC 7466. The MIB module defined in this
additional state and performance information is useful to document, denoted NHDP-MIB, also reports state, performance
troubleshoot problems and performance issues during neighbor information, and notifications about NHDP. This additional state and
discovery. performance information is useful to troubleshoot problems and
performance issues during neighbor discovery.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 10, 2016. This Internet-Draft will expire on November 24, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 20 skipping to change at page 2, line 21
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Difference from RFC 6779 . . . . . . . . . . . . . . . . . 3 1.1. Difference from RFC 6779 . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Intellectual Property . . . . . . . . . . . . . . . . . . . . 4 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 5 5.1.1. Introduction . . . . . . . . . . . . . . . . . . . . . 5
6.1.1. Introduction . . . . . . . . . . . . . . . . . . . . . 5 5.1.2. Notification Generation . . . . . . . . . . . . . . . 5
6.1.2. Notification Generation . . . . . . . . . . . . . . . 5 5.1.3. Limiting Frequency of Notifications . . . . . . . . . 5
6.1.3. Limiting Frequency of Notifications . . . . . . . . . 5 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 7
6.2. The Configuration Group . . . . . . . . . . . . . . . . . 7 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7
6.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 8
6.4. The Performance Group . . . . . . . . . . . . . . . . . . 7 5.5. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8
6.5. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 10
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 10
7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 10 6.2. Relationship to Routing Protocol MIB Modules Relying
7.2. Relationship to Routing Protocol MIB Modules Relying
on the NHDP-MIB Module . . . . . . . . . . . . . . . . . . 10 on the NHDP-MIB Module . . . . . . . . . . . . . . . . . . 10
7.3. Relationship to the If-MIB . . . . . . . . . . . . . . . . 10 6.3. Relationship to the If-MIB . . . . . . . . . . . . . . . . 10
7.4. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 11 6.4. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 11
8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. Security Considerations . . . . . . . . . . . . . . . . . . . 65 8. Security Considerations . . . . . . . . . . . . . . . . . . . 66
10. Applicability Statement . . . . . . . . . . . . . . . . . . . 67 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 68
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 68 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 68
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 68 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 69
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
13.1. Normative References . . . . . . . . . . . . . . . . . . . 69 12.1. Normative References . . . . . . . . . . . . . . . . . . . 69
13.2. Informative References . . . . . . . . . . . . . . . . . . 70 12.2. Informative References . . . . . . . . . . . . . . . . . . 70
1. Introduction 1. Introduction
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it describes objects for configuring community. In particular, it describes objects for configuring
parameters of the Mobile Ad Hoc Network (MANET) Neighborhood parameters of the Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP) [RFC6130] process on a router. The MIB Discovery Protocol (NHDP) [RFC6130] process on a router. The MIB
module defined in this document, denoted NHDP-MIB, also reports module defined in this document, denoted NHDP-MIB, also reports
state, performance information, and notifications about NHDP. This state, performance information, and notifications about NHDP. This
additional state and performance information is useful to additional state and performance information is useful to
troubleshoot problems and performance issues during neighbor troubleshoot problems and performance issues during neighbor
discovery. discovery.
1.1. Difference from RFC 6779 1.1. Difference from RFC 6779
This document obsoletes [RFC6779], replacing that document as the This document obsoletes [RFC6779], replacing that document as the
specification of the MIB module for [RFC6130]. specification of the MIB module for [RFC6130].
Specifically, the MIB module for [RFC6130], specified in this The MIB module for [RFC6130], specified in this document, captures
document, captures the new information and states for each symmetric the new information and states for each symmetric 2-hop neighbor,
2-hop neighbor, recorded in the Neighbor Information Base of a router recorded in the Neighbor Information Base of a router and to be
and to be reflected in the appropriate tables, introduced by reflected in the appropriate tables, introduced by [RFC7466],
[RFC7466]. specifically:
o Addition of objects nhdpIib2HopSetN2Lost and
nhdpIfPerfCounterDiscontinuityTime.
o Addition of extra value (notconsidered) to nhdp2HopNbrState.
o Revised full compliance state.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 5 skipping to change at page 4, line 12
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Conventions 3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
OPTIONAL" in this document are to be interpreted as described in OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
4. Intellectual Property 4. Overview
The authors are not aware of any IPR related to anything specified in
this document (as per [RFC3979] and [RFC5378]).
5. Overview
[RFC6130] allows a router to discover and track topological [RFC6130] allows a router to discover and track topological
information of routers up to two hops away by virtue of exchanging information of routers up to two hops away by virtue of exchanging
HELLO messages. This information is useful for routers running HELLO messages. This information is useful for routers running
various routing and multicast flooding protocols developed within the various routing and multicast flooding protocols developed within the
IETF MANET Working Group. IETF MANET Working Group.
5.1. Terms 4.1. Terms
The following definitions apply throughout this document: The following definitions apply throughout this document:
o Notification Objects - triggers and associated notification o Notification Objects - triggers and associated notification
messages allowing for asynchronous tracking of pre-defined events messages allowing for asynchronous tracking of pre-defined events
on the managed router. on the managed router.
o Configuration Objects - switches, tables, and objects that are o Configuration Objects - switches, tables, and objects that are
initialized to default settings or set through the management initialized to default settings or set through the management
interface defined by this MIB module. interface defined by this MIB module.
o State Objects - automatically generated values that define the o State Objects - automatically generated values that define the
current operating state of the NHDP instance in the router. current operating state of the NHDP instance in the router.
o Performance Objects - automatically generated values that help an o Performance Objects - automatically generated values that help an
administrator or automated tool to assess the performance of the administrator or automated tool to assess the performance of the
NHDP instance on the router and the overall discovery performance NHDP instance on the router and the overall discovery performance
within the Mobile Ad Hoc Network (MANET). within the Mobile Ad Hoc Network (MANET).
5.2. Notation 4.2. Notation
The same notations as defined in [RFC6130] are used throughout this The same notations as defined in [RFC6130] are used throughout this
document. document.
6. Structure of the MIB Module 5. Structure of the MIB Module
This section presents the structure of the NHDP-MIB module. The MIB This section presents the structure of the NHDP-MIB module. The MIB
module is arranged into the following structure: module is arranged into the following structure:
o nhdpNotifications - objects defining NHDP-MIB notifications. o nhdpNotifications - objects defining NHDP-MIB notifications.
o nhdpObjects - defining objects within this MIB module. The o nhdpObjects - defining objects within this MIB module. The
objects are arranged into the following groups: objects are arranged into the following groups:
* Configuration Group - defining objects related to the * Configuration Group - defining objects related to the
skipping to change at page 5, line 18 skipping to change at page 5, line 21
* State Group - defining objects that reflect the current state * State Group - defining objects that reflect the current state
of the NHDP instance running on the router. of the NHDP instance running on the router.
* Performance Group - defining objects that are useful to a * Performance Group - defining objects that are useful to a
management station when characterizing the performance of NHDP management station when characterizing the performance of NHDP
on the router and in the MANET. on the router and in the MANET.
o nhdpConformance - defining the minimal and maximal conformance o nhdpConformance - defining the minimal and maximal conformance
requirements for implementations of this MIB module. requirements for implementations of this MIB module.
6.1. Notifications 5.1. Notifications
This section describes the use of notifications and mechanisms to This section describes the use of notifications and mechanisms to
enhance the ability to manage NHDP routing domains. enhance the ability to manage NHDP routing domains.
6.1.1. Introduction 5.1.1. Introduction
Notifications can be emitted by a router running an instance of this Notifications can be emitted by a router running an instance of this
specification as a reaction to a specific event. This allows a specification as a reaction to a specific event. This allows a
network manager to efficiently determine the source of problems or network manager to efficiently determine the source of problems or
significant changes of configuration or topology, instead of polling significant changes of configuration or topology, instead of polling
a possibly large number of routers. a possibly large number of routers.
6.1.2. Notification Generation 5.1.2. Notification Generation
When an exception event occurs, the application notifies the local When an exception event occurs, the application notifies the local
agent, which sends a notification to the appropriate SNMP management agent, which sends a notification to the appropriate SNMP management
stations. The message includes the notification type and may include stations. The message includes the notification type and may include
a list of notification-specific variables. Section 8 contains the a list of notification-specific variables. Section 7 contains the
notification definitions, which includes the variable lists. At notification definitions, which includes the variable lists. At
least one IP address of the router that originates the notification least one IP address of the router that originates the notification
is included in the variable list so that the network manager may is included in the variable list so that the network manager may
determine the source of the notification. determine the source of the notification.
6.1.3. Limiting Frequency of Notifications 5.1.3. Limiting Frequency of Notifications
To limit the frequency of notifications, the following additional To limit the frequency of notifications, the following additional
mechanisms are suggested, similar to those in [RFC4750]. mechanisms are suggested, similar to those in [RFC4750].
6.1.3.1. Ignoring Initial Activity 5.1.3.1. Ignoring Initial Activity
The majority of critical events occur when NHDP is first enabled on a The majority of critical events occur when NHDP is first enabled on a
router, at which time the symmetric neighbors and two-hop neighbors router, at which time the symmetric neighbors and two-hop neighbors
of the router are discovered. During this initial period, a of the router are discovered. During this initial period, a
potential flood of notifications is unnecessary since the events are potential flood of notifications is unnecessary since the events are
expected. To avoid unnecessary notifications, a router SHOULD NOT expected. To avoid unnecessary notifications, a router SHOULD NOT
originate expected notifications until a certain time interval has originate expected notifications until a certain time interval has
elapsed, which is to be predefined by the network manager. It is elapsed, which is to be predefined by the network manager. It is
RECOMMENDED that this time interval is at least 3 x RECOMMENDED that this time interval is at least 3 x
nhdpHelloInterval, so that symmetric neighbors are discovered. The nhdpHelloInterval, so that symmetric neighbors are discovered. The
suppression window for notifications is started when the nhdpIfStatus suppression window for notifications is started when the nhdpIfStatus
transitions from its default value of 'false(2)' to 'true(1)'. transitions from its default value of 'false(2)' to 'true(1)'.
6.1.3.2. Throttling Notifications 5.1.3.2. Throttling Notifications
The mechanism for throttling the notifications is the same as in The mechanism for throttling the notifications is the same as in
[RFC4750] (i.e., the number of transmitted notifications per time is [RFC4750] (i.e., the number of transmitted notifications per time is
bounded). bounded).
Appropriate values for the window time and upper bound are to be Appropriate values for the window time and upper bound are to be
selected by the network manager and depend on the deployment of the selected by the network manager and depend on the deployment of the
MANET. If NHDP is deployed on a lossy, wireless medium, sending too MANET. If NHDP is deployed on a lossy, wireless medium, sending too
many notifications in a short time interval may lead to collisions many notifications in a short time interval may lead to collisions
and dropped packets. In particular, in dense deployments of routers and dropped packets. In particular, in dense deployments of routers
skipping to change at page 6, line 44 skipping to change at page 7, line 5
of occurrences exceeds the change threshold within the previous of occurrences exceeds the change threshold within the previous
change window, then the notification is to be sent. Furthermore, it change window, then the notification is to be sent. Furthermore, it
is RECOMMENDED that the value for this window be set to at least 5 is RECOMMENDED that the value for this window be set to at least 5
times the nhdpHelloInterval. times the nhdpHelloInterval.
The following objects are used to define the thresholds and time The following objects are used to define the thresholds and time
windows for specific notifications defined in the NHDP-MIB module: windows for specific notifications defined in the NHDP-MIB module:
nhdpNbrStateChangeThreshold, nhdpNbrStateChangeWindow, nhdpNbrStateChangeThreshold, nhdpNbrStateChangeWindow,
nhdp2HopNbrStateChangeThreshold, and nhdp2HopNbrStateChangeWindow. nhdp2HopNbrStateChangeThreshold, and nhdp2HopNbrStateChangeWindow.
6.1.3.3. One Notification per Event 5.1.3.3. One Notification per Event
Similar to the mechanism in [RFC4750], only one notification is sent Similar to the mechanism in [RFC4750], only one notification is sent
per event. per event.
6.2. The Configuration Group 5.2. The Configuration Group
The router running NHDP is configured with a set of controls. The The router running NHDP is configured with a set of controls. The
authoritative list of configuration controls within the NHDP-MIB authoritative list of configuration controls within the NHDP-MIB
module are found within the MIB module itself. Generally, an attempt module are found within the MIB module itself. Generally, an attempt
was made in developing the NHDP-MIB module to support all was made in developing the NHDP-MIB module to support all
configuration objects defined in [RFC6130]. For all of the configuration objects defined in [RFC6130]. For all of the
configuration parameters, the same constraints and default values of configuration parameters, the same constraints and default values of
these parameters as defined in [RFC6130] are followed. Refer to these parameters as defined in [RFC6130] are followed. Refer to
[RFC5148] for guidance on setting jitter-related parameters, e.g., [RFC5148] for guidance on setting jitter-related parameters, e.g.,
nhdpMaxJitter. nhdpMaxJitter.
6.3. The State Group 5.3. The State Group
The State Group reports current state information of a router running The State Group reports current state information of a router running
NHDP. The NHDP-MIB State Group tables were designed to contain the NHDP. The NHDP-MIB State Group tables were designed to contain the
complete set of state information defined within the information complete set of state information defined within the information
bases specified in Sections 6, 7, and 8 of [RFC6130]. bases specified in Sections 6, 7, and 8 of [RFC6130].
Two constructs, i.e., TEXTUAL-CONVENTIONs, are defined to support the Two constructs, i.e., TEXTUAL-CONVENTIONs, are defined to support the
tables in the State Group. NHDP stores and indexes information tables in the State Group. NHDP stores and indexes information
through sets of (dynamically defined) addresses, i.e., address sets. through sets of (dynamically defined) addresses, i.e., address sets.
Within SMIv2, it is not possible to index tables with variably Within SMIv2, it is not possible to index tables with variably
skipping to change at page 7, line 46 skipping to change at page 8, line 5
distinct address sets may, in fact, be related to a common neighbor distinct address sets may, in fact, be related to a common neighbor
interface. This ambiguity may also hold with respect to the interface. This ambiguity may also hold with respect to the
assignment of the NeighborRouterIndex. The local MIB agent is assignment of the NeighborRouterIndex. The local MIB agent is
responsible for managing, aggregating, and retiring the defined responsible for managing, aggregating, and retiring the defined
indexes and for updating MIB tables using these indexes as the local indexes and for updating MIB tables using these indexes as the local
router learns more about its neighbors' topologies. These constructs router learns more about its neighbors' topologies. These constructs
are used to define indexes to the appropriate State Group tables and are used to define indexes to the appropriate State Group tables and
to correlate table entries to address sets, virtual neighbor to correlate table entries to address sets, virtual neighbor
interfaces, and virtual neighbors within the MANET. interfaces, and virtual neighbors within the MANET.
6.4. The Performance Group 5.4. The Performance Group
The Performance Group reports values relevant to system performance. The Performance Group reports values relevant to system performance.
Unstable neighbors or 2-hop neighbors and frequent changes of sets Unstable neighbors or 2-hop neighbors and frequent changes of sets
can have a negative influence on the performance of NHDP. This MIB can have a negative influence on the performance of NHDP. This MIB
module defines several objects that can be polled in order to, e.g., module defines several objects that can be polled in order to, e.g.,
calculate histories or monitor frequencies of changes. This may help calculate histories or monitor frequencies of changes. This may help
the network administrator to determine unusual topology changes or the network administrator to determine unusual topology changes or
other changes that affect stability and reliability of the MANET. other changes that affect stability and reliability of the MANET.
6.5. Tables and Indexing 5.5. Tables and Indexing
The NHDP-MIB module contains a number of tables that record data The NHDP-MIB module contains a number of tables that record data
related to: related to:
o the local router, o the local router,
o a local MANET interface on the router, o a local MANET interface on the router,
o other routers that are 1 hop removed from the local router, o other routers that are 1 hop removed from the local router,
skipping to change at page 9, line 47 skipping to change at page 10, line 9
router. This table has INDEX { nhdpDiscIfIndex }. router. This table has INDEX { nhdpDiscIfIndex }.
o nhdpDiscNeighborSetPerfTable - records performance objects that o nhdpDiscNeighborSetPerfTable - records performance objects that
are measured for discovered neighbors of this router. This table are measured for discovered neighbors of this router. This table
has INDEX { nhdpDiscRouterIndex }. has INDEX { nhdpDiscRouterIndex }.
o nhdpIib2HopSetPerfTable - records performance objects that are o nhdpIib2HopSetPerfTable - records performance objects that are
measured for discovered 2-hop neighbors of this router. This measured for discovered 2-hop neighbors of this router. This
table has INDEX { nhdpDiscRouterIndex }. table has INDEX { nhdpDiscRouterIndex }.
7. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
This section specifies the relationship of the MIB module contained This section specifies the relationship of the MIB module contained
in this document to other standards, particularly to standards in this document to other standards, particularly to standards
containing other MIB modules. MIB modules and specific definitions containing other MIB modules. MIB modules and specific definitions
imported from MIB modules that SHOULD be implemented in conjunction imported from MIB modules that SHOULD be implemented in conjunction
with the MIB module contained within this document are identified in with the MIB module contained within this document are identified in
this section. this section.
7.1. Relationship to the SNMPv2-MIB 6.1. Relationship to the SNMPv2-MIB
The System group in the SNMPv2-MIB module [RFC3418] is defined as The System group in the SNMPv2-MIB module [RFC3418] is defined as
being mandatory for all systems, and the objects apply to the entity being mandatory for all systems, and the objects apply to the entity
as a whole. The System group provides identification of the as a whole. The System group provides identification of the
management entity and certain other system-wide data. The NHDP-MIB management entity and certain other system-wide data. The NHDP-MIB
module does not duplicate those objects. module does not duplicate those objects.
7.2. Relationship to Routing Protocol MIB Modules Relying on the NHDP- 6.2. Relationship to Routing Protocol MIB Modules Relying on the NHDP-
MIB Module MIB Module
[RFC6130] allows routing protocols to rely on the neighborhood [RFC6130] allows routing protocols to rely on the neighborhood
information that is discovered by means of HELLO message exchange. information that is discovered by means of HELLO message exchange.
In order to allow for troubleshooting, fault isolation, and In order to allow for troubleshooting, fault isolation, and
management of such routing protocols through a routing protocol MIB management of such routing protocols through a routing protocol MIB
module, it may be desired to align the State Group tables of the module, it may be desired to align the State Group tables of the
NHDP-MIB module and the routing protocol MIB module. This is NHDP-MIB module and the routing protocol MIB module. This is
accomplished through the definition of two TEXTUAL-CONVENTIONs in the accomplished through the definition of two TEXTUAL-CONVENTIONs in the
NHDP-MIB module: the NeighborIfIndex and the NeighborRouterIndex. NHDP-MIB module: the NeighborIfIndex and the NeighborRouterIndex.
These object types are used to develop indexes into common NHDP-MIB These object types are used to develop indexes into common NHDP-MIB
module and routing protocol State Group tables. These objects are module and routing protocol State Group tables. These objects are
locally significant but should be locally common to the NHDP-MIB locally significant but should be locally common to the NHDP-MIB
module and the routing protocol MIB module implemented on a common module and the routing protocol MIB module implemented on a common
networked router. This will allow for improved cross-referencing of networked router. This will allow for improved cross-referencing of
information across the two MIB modules. information across the two MIB modules.
7.3. Relationship to the If-MIB 6.3. Relationship to the If-MIB
The nhdpInterfaceTable in this MIB module describes the configuration The nhdpInterfaceTable in this MIB module describes the configuration
of the interfaces of this router that are intended to use MANET of the interfaces of this router that are intended to use MANET
control protocols. As such, this table 'sparse augments' the ifTable control protocols. As such, this table 'sparse augments' the ifTable
[RFC2863] specifically when NHDP is to be configured to operate over [RFC2863] specifically when NHDP is to be configured to operate over
this interface. The interface is identified by the ifIndex from the this interface. The interface is identified by the ifIndex from the
interfaces group defined in the Interfaces Group MIB module interfaces group defined in the Interfaces Group MIB module
[RFC2863]. [RFC2863].
A conceptual row in this table exists if and only if either a manager A conceptual row in the nhdpInterfaceTable exists if and only if
has explicitly created the row or there is an interface on the either a manager has explicitly created the row or there is an
managed device that supports and runs NHDP. interface on the managed device that supports and runs NHDP.
If the corresponding entry with ifIndex value is deleted from the If the corresponding entry with ifIndex value is deleted from the
Interface Table, then the entry in this table is automatically Interface Table, then the entry in this table is automatically
deleted, NHDP is disabled on this interface, and all configuration deleted, NHDP is disabled on this interface, and all configuration
and state information related to this interface is to be removed from and state information related to this interface is to be removed from
memory. memory.
7.4. MIB Modules Required for IMPORTS 6.4. MIB Modules Required for IMPORTS
The following NHDP-MIB module IMPORTS objects from SNMPv2-SMI The following NHDP-MIB module IMPORTS objects from SNMPv2-SMI
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB
[RFC2863], INET-ADDRESS-MIB [RFC4001], and FLOAT-TC-MIB [RFC6340]. [RFC2863], INET-ADDRESS-MIB [RFC4001], and FLOAT-TC-MIB [RFC6340].
8. Definitions 7. Definitions
This section contains the MIB module defined by the specification. This section contains the MIB module defined by the specification.
NHDP-MIB DEFINITIONS ::= BEGIN NHDP-MIB DEFINITIONS ::= BEGIN
-- This MIB module defines objects for the management of -- This MIB module defines objects for the management of
-- NHDP (RFC 6130) - Mobile Ad Hoc Network (MANET) -- NHDP (RFC 6130) - Mobile Ad Hoc Network (MANET)
-- Neighborhood Discovery Protocol (NHDP), -- Neighborhood Discovery Protocol (NHDP),
-- Clausen, T., Dearlove, C., and J. Dean, January 2011. -- Clausen, T., Dearlove, C., and J. Dean, January 2011.
skipping to change at page 11, line 51 skipping to change at page 12, line 13
FROM INET-ADDRESS-MIB -- RFC 4001 FROM INET-ADDRESS-MIB -- RFC 4001
InterfaceIndex InterfaceIndex
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
Float32TC Float32TC
FROM FLOAT-TC-MIB -- RFC 6340 FROM FLOAT-TC-MIB -- RFC 6340
; ;
nhdpMIB MODULE-IDENTITY nhdpMIB MODULE-IDENTITY
LAST-UPDATED "201602201100Z" -- 20 February 2016 LAST-UPDATED "201605231100Z" -- 23 May 2016
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG web page: https://datatracker.ietf.org/wg/manet WG web page: https://datatracker.ietf.org/wg/manet
Editors: Ulrich Herberg Editors: Ulrich Herberg
USA USA
ulrich@herberg.name ulrich@herberg.name
http://www.herberg.name/ http://www.herberg.name/
skipping to change at page 13, line 8 skipping to change at page 13, line 18
Copyright (c) 2014 IETF Trust and the persons Copyright (c) 2014 IETF Trust and the persons
identified as authors of the code. All rights reserved. identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this MIB module is part of RFC 6779; see This version of this MIB module is part of RFC xxxx; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- revision -- revision
REVISION "201602201100Z" -- 20 Feburary 2016 REVISION "201605231100Z" -- 23 May 2016
DESCRIPTION DESCRIPTION
"Updated version of this MIB module, "Updated version of this MIB module,
including updates made to NHDP by including updates made to NHDP by
RFC 7466, published as RFC xxxx." RFC 7466, published as RFC xxxx."
REVISION "201210221000Z" -- 22 October 2012 REVISION "201210221000Z" -- 22 October 2012
DESCRIPTION DESCRIPTION
"Initial version of this MIB module, "Initial version of this MIB module,
published as RFC 6779." published as RFC 6779."
::= { mib-2 213 } ::= { mib-2 213 }
skipping to change at page 63, line 14 skipping to change at page 63, line 21
OBJECTS { OBJECTS {
nhdpIfHelloMessageXmits, nhdpIfHelloMessageXmits,
nhdpIfHelloMessageRecvd, nhdpIfHelloMessageRecvd,
nhdpIfHelloMessageXmitAccumulatedSize, nhdpIfHelloMessageXmitAccumulatedSize,
nhdpIfHelloMessageRecvdAccumulatedSize, nhdpIfHelloMessageRecvdAccumulatedSize,
nhdpIfHelloMessageTriggeredXmits, nhdpIfHelloMessageTriggeredXmits,
nhdpIfHelloMessagePeriodicXmits, nhdpIfHelloMessagePeriodicXmits,
nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount, nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount,
nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount, nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount,
nhdpIfHelloMessageXmitAccumulatedLostNeighborCount, nhdpIfHelloMessageXmitAccumulatedLostNeighborCount,
nhdpIfPerfCounterDiscontinuityTime,
nhdpDiscIfRecvdPackets, nhdpDiscIfRecvdPackets,
nhdpDiscIfExpectedPackets, nhdpDiscIfExpectedPackets,
nhdpNibNeighborSetChanges, nhdpNibNeighborSetChanges,
nhdpDiscNeighborNibNeighborSetChanges, nhdpDiscNeighborNibNeighborSetChanges,
nhdpDiscNeighborNibNeighborSetUpTime, nhdpDiscNeighborNibNeighborSetUpTime,
nhdpDiscNeighborNibNeighborSetReachableLinkChanges, nhdpDiscNeighborNibNeighborSetReachableLinkChanges,
nhdpIib2HopSetPerfChanges, nhdpIib2HopSetPerfChanges,
nhdpIib2HopSetPerfUpTime nhdpIib2HopSetPerfUpTime
} }
STATUS current STATUS current
skipping to change at page 65, line 41 skipping to change at page 66, line 4
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Set of NHDP state objects implemented "Set of NHDP state objects implemented
in this module. in this module.
For version-independence, this compliance statement For version-independence, this compliance statement
is deprecated in favor of nhdpStateGroup2." is deprecated in favor of nhdpStateGroup2."
::= { nhdpMIBGroups 3 } ::= { nhdpMIBGroups 3 }
END END
8. Security Considerations
9. Security Considerations
This MIB module defines objects for the configuration, monitoring, This MIB module defines objects for the configuration, monitoring,
and notification of the Mobile Ad Hoc Network (MANET) Neighborhood and notification of the Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP) [RFC6130]. NHDP allows routers to acquire Discovery Protocol (NHDP) [RFC6130]. NHDP allows routers to acquire
topological information up to two hops away by virtue of exchanging topological information up to two hops away by virtue of exchanging
HELLO messages. The information acquired by NHDP may be used by HELLO messages. The information acquired by NHDP may be used by
routing protocols. The neighborhood information, exchanged between routing protocols. The neighborhood information, exchanged between
routers using NHDP, serves these routing protocols as a baseline for routers using NHDP, serves these routing protocols as a baseline for
calculating paths to all destinations in the MANET, relay set calculating paths to all destinations in the MANET, relay set
selection for network-wide transmissions, etc. selection for network-wide transmissions, etc.
skipping to change at page 67, line 40 skipping to change at page 68, line 5
[RFC5592] or TLS/DTLS [RFC6353]. [RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
10. Applicability Statement 9. Applicability Statement
This document describes objects for configuring parameters of the This document describes objects for configuring parameters of the
Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP) Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)
[RFC6130] process on a router. This MIB module, denoted NHDP-MIB, [RFC6130] process on a router. This MIB module, denoted NHDP-MIB,
also reports state, performance information, and notifications. This also reports state, performance information, and notifications. This
section provides some examples of how this MIB module can be used in section provides some examples of how this MIB module can be used in
MANET network deployments. A fuller discussion of MANET network MANET network deployments.
management use cases and challenges will be provided elsewhere.
NHDP is designed to allow routers to automatically discover and track NHDP is designed to allow routers to automatically discover and track
routers one hop remote (denoted "neighbors") and routers two hops routers one hop remote (denoted "neighbors") and routers two hops
remote (denoted "two-hop neighbors"). This information is used by remote (denoted "two-hop neighbors"). This information is used by
other MANET protocols in operation on the router to perform routing, other MANET protocols in operation on the router to perform routing,
multicast forwarding, and other functions with ad hoc and mobile multicast forwarding, and other functions with ad hoc and mobile
networks. In the following, three example scenarios are listed where networks. In the following, three example scenarios are listed where
this MIB module is useful: this MIB module is useful:
o For a Parking Lot Initial Configuration Situation - It is common o For a Parking Lot Initial Configuration Situation - It is common
skipping to change at page 68, line 36 skipping to change at page 68, line 48
and fault management from the fixed NOC are necessary for this and fault management from the fixed NOC are necessary for this
deployment option. deployment option.
o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for
larger vehicles, a hierarchical network management arrangement is larger vehicles, a hierarchical network management arrangement is
useful. Centralized network management is performed from a fixed useful. Centralized network management is performed from a fixed
NOC while local management is performed locally from within the NOC while local management is performed locally from within the
vehicles. Standards-based methods for configuration, monitoring, vehicles. Standards-based methods for configuration, monitoring,
and fault management are necessary for this deployment option. and fault management are necessary for this deployment option.
11. IANA Considerations 10. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER value recorded in the SMI Numbers registry: OBJECT IDENTIFIER value recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
NHDP-MIB { mib-2 213 } NHDP-MIB { mib-2 213 }
12. Acknowledgements 11. Acknowledgements
The authors wish to thank Benoit Claise, Justin Dean, Adrian Farrel, The authors wish to thank Benoit Claise, Elwyn Davies, Justin Dean,
Joel Halpern, Al Morton, and Thomas Nadeau for their detailed reviews Adrian Farrel, Joel Halpern, Michael MacFaden, Al Morton, and Thomas
and insightful comments regarding RFC6779 and this document. Nadeau for their detailed reviews and insightful comments regarding
RFC6779 and this document.
This MIB document uses the template authored by D. Harrington, which This MIB document uses the template authored by D. Harrington, which
is based on contributions from the MIB Doctors, especially Juergen is based on contributions from the MIB Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn. Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn.
13. References 12. References
13.1. Normative References 12.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
skipping to change at page 69, line 33 skipping to change at page 69, line 46
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002. RFC 3418, December 2002.
[RFC3979] Bradner, S., Ed., "Intellectual Property Rights in IETF
Technology", BCP 79, RFC 3979, DOI 10.17487/RFC3979,
March 2005, <http://www.rfc-editor.org/info/rfc3979>.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights
Contributors Provide to the IETF Trust", BCP 78, RFC 5378,
DOI 10.17487/RFC5378, November 2008,
<http://www.rfc-editor.org/info/rfc5378>.
[RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc [RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc
Network (MANET) Neighborhood Discovery Protocol (NHDP)", Network (MANET) Neighborhood Discovery Protocol (NHDP)",
RFC 6130, April 2011. RFC 6130, April 2011.
[RFC6340] Presuhn, R., "Textual Conventions for the Representation [RFC6340] Presuhn, R., "Textual Conventions for the Representation
of Floating-Point Numbers", RFC 6340, August 2011. of Floating-Point Numbers", RFC 6340, August 2011.
[RFC7466] Dearlove, C. and T. Clausen, "An Optimization for the [RFC7466] Dearlove, C. and T. Clausen, "An Optimization for the
Mobile Ad Hoc Network (MANET) Neighborhood Discovery Mobile Ad Hoc Network (MANET) Neighborhood Discovery
Protocol (NHDP)", RFC 7466, March 2015. Protocol (NHDP)", RFC 7466, March 2015.
13.2. Informative References 12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", RFC 3411, Protocol (SNMP) Management Frameworks", RFC 3411,
December 2002. December 2002.
skipping to change at page 71, line 38 skipping to change at page 71, line 41
Ian D Chakeres Ian D Chakeres
Delvin Delvin
Ellicott City, Maryland 21042 Ellicott City, Maryland 21042
United States United States
EMail: ian.chakeres@gmail.com EMail: ian.chakeres@gmail.com
URI: http://www.ianchak.com/ URI: http://www.ianchak.com/
Thomas Heide Clausen Thomas Heide Clausen
LIX, Ecole Polytechnique Ecole Polytechnique
Phone: +33 6 6058 9349 Phone: +33 6 6058 9349
EMail: T.Clausen@computer.org EMail: T.Clausen@computer.org
URI: http://www.ThomasClausen.org/ URI: http://www.ThomasClausen.org/
 End of changes. 47 change blocks. 
99 lines changed or deleted 92 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/