draft-ietf-manet-rfc6779bis-07.txt   rfc7939.txt 
Network Working Group U. Herberg Internet Engineering Task Force (IETF) U. Herberg
Internet-Draft Request for Comments: 7939
Obsoletes: 6779 (if approved) R. Cole Obsoletes: 6779 R. Cole
Intended status: Standards Track US Army CERDEC Category: Standards Track US Army CERDEC
Expires: December 4, 2016 I. Chakeres ISSN: 2070-1721 I. Chakeres
Delvin Delvin
T. Clausen T. Clausen
Ecole Polytechnique Ecole Polytechnique
June 2, 2016 August 2016
Definition of Managed Objects for the Neighborhood Discovery Protocol Definition of Managed Objects for the Neighborhood Discovery Protocol
draft-ietf-manet-rfc6779bis-07
Abstract Abstract
This document revises, extends, and replaces RFC 6779. It defines a This document replaces RFC 6779; it contains revisions and extensions
portion of the Management Information Base (MIB) for use with network to the original document. It defines a portion of the Management
management protocols in the Internet community. In particular, it Information Base (MIB) for use with network management protocols in
describes objects for configuring parameters of the Neighborhood the Internet community. In particular, it describes objects for
Discovery Protocol (NHDP) process on a router. The extensions configuring parameters of the Neighborhood Discovery Protocol (NHDP)
described in this document add objects and values to support the NHDP process on a router. The extensions described in this document add
optimization specified in RFC 7466. The MIB module defined in this objects and values to support the NHDP optimization specified in RFC
document, denoted NHDP-MIB, also reports state, performance 7466. The MIB module defined in this document, denoted NHDP-MIB,
information, and notifications about NHDP. This additional state and also reports state, performance information, and notifications about
performance information is useful to troubleshoot problems and NHDP. This additional state and performance information is useful to
performance issues during neighbor discovery. 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 is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on December 4, 2016. 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/rfc7939.
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 Provisions Relating to IETF
This document is subject to BCP 78 and the IETF Trust's Legal Documents (http://trustee.ietf.org/license-info) in effect on the
Provisions Relating to IETF Documents date of publication of this document. Please review these 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 carefully, as they describe your rights and restrictions with respect
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. Differences from RFC 6779 . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 5 5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 5
5.1.1. Introduction . . . . . . . . . . . . . . . . . . . . . 5 5.1.1. Introduction . . . . . . . . . . . . . . . . . . . . 5
5.1.2. Notification Generation . . . . . . . . . . . . . . . 5 5.1.2. Notification Generation . . . . . . . . . . . . . . . 5
5.1.3. Limiting Frequency of Notifications . . . . . . . . . 5 5.1.3. Limiting Frequency of Notifications . . . . . . . . . 5
5.2. The Configuration Group . . . . . . . . . . . . . . . . . 7 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 7
5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7
5.4. The Performance Group . . . . . . . . . . . . . . . . . . 8 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 8
5.5. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 5.5. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 10 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 10
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 10 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . 10
6.2. Relationship to Routing Protocol MIB Modules Relying 6.2. Relationship to Routing Protocol MIB Modules Relying on
on the NHDP-MIB Module . . . . . . . . . . . . . . . . . . 10 the NHDP-MIB Module . . . . . . . . . . . . . . . . . . . 10
6.3. Relationship to the If-MIB . . . . . . . . . . . . . . . . 10 6.3. Relationship to the If-MIB . . . . . . . . . . . . . . . 10
6.4. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 11 6.4. MIB Modules Required for IMPORTS . . . . . . . . . . . . 11
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 66 8. Security Considerations . . . . . . . . . . . . . . . . . . . 66
9. Applicability Statement . . . . . . . . . . . . . . . . . . . 68 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 68
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 68 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 69 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 69
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 11.1. Normative References . . . . . . . . . . . . . . . . . . 69
12.1. Normative References . . . . . . . . . . . . . . . . . . . 69 11.2. Informative References . . . . . . . . . . . . . . . . . 71
12.2. Informative References . . . . . . . . . . . . . . . . . . 70 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 72
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 72
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. Differences 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]. This revision to specification of the MIB module for [RFC6130]. This revision to
[RFC6779] is necessitated by the update to [RFC6130] specified in [RFC6779] is necessitated by the update to [RFC6130] specified in
[RFC7466]. [RFC7466].
The MIB module for [RFC6130], specified in this document, captures The MIB module for [RFC6130], specified in this document, captures
the new information and states for each symmetric 2-hop neighbor, the new information and states for each symmetric 2-hop neighbor,
recorded in the Neighbor Information Base of a router and to be recorded in the Neighbor Information Base of a router and to be
reflected in the appropriate tables, introduced by [RFC7466], reflected in the appropriate tables, introduced by [RFC7466],
skipping to change at page 4, line 25 skipping to change at page 4, line 25
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.
4.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 predefined 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 to
administrator or automated tool to assess the performance of the assess the performance of the NHDP instance on the router and the
NHDP instance on the router and the overall discovery performance overall discovery performance within the MANET.
within the Mobile Ad Hoc Network (MANET).
4.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.
5. 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:
skipping to change at page 5, line 29 skipping to change at page 5, line 29
requirements for implementations of this MIB module. requirements for implementations of this MIB module.
5.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.
5.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 an
network manager to efficiently determine the source of problems or observer of these events to efficiently determine the source of
significant changes of configuration or topology, instead of polling problems or significant changes of configuration or topology, instead
a possibly large number of routers. of polling a possibly large number of routers.
5.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 7 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 source of the
determine the source of the notification. notification may be determined.
5.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].
5.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 2-hop neighbors of
of the router are discovered. During this initial period, a the router are discovered. During this initial period, a potential
potential flood of notifications is unnecessary since the events are flood of notifications is unnecessary since the events are expected.
expected. To avoid unnecessary notifications, a router SHOULD NOT To avoid unnecessary notifications, a router SHOULD NOT originate
originate expected notifications until a certain time interval has expected notifications until a predefined and administratively
elapsed, which is to be predefined by the network manager. It is configured time interval has elapsed. It is RECOMMENDED that this
RECOMMENDED that this time interval is at least 3 x time interval be at least 3 times nhdpHelloInterval so that symmetric
nhdpHelloInterval, so that symmetric neighbors are discovered. The neighbors are discovered. The suppression window for notifications
suppression window for notifications is started when the nhdpIfStatus is started when the nhdpIfStatus transitions from its default value
transitions from its default value of 'false(2)' to 'true(1)'. of 'false(2)' to 'true(1)'.
5.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 administratively configured 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
running NHDP (i.e., where each router has many neighbors), a change running NHDP (i.e., where each router has many neighbors), a change
of the local topology may trigger many notifications at the same of the local topology may trigger many notifications at the same
time. [RFC4750] recommends "7 traps with a window time of 10 time. [RFC4750] recommends "7 traps with a window time of 10
seconds" as the upper bound. As NHDP is expected to be deployed in seconds" as the upper bound. As NHDP is expected to be deployed in
more lossy channels than OSPF, it is RECOMMENDED to choose a lower more lossy channels than OSPF, it is RECOMMENDED to choose a lower
threshold for the number of notifications per time than that. threshold for the number of notifications per time than that.
Specifically, it is RECOMMENDED that the threshold value for the Specifically, it is RECOMMENDED that the threshold value for the
objects reflecting the change be set to a value of '10' and the objects reflecting the change be set to a value of '10' and the
DEFAULT values for these objects within the Notifications Group be DEFAULT values for these objects within the Notifications Group be
set to this value. Further, a time window for the change objects is set to this value. Further, a time window for the change objects is
defined within this MIB module. It is RECOMMENDED that if the number defined within this MIB module. If the number of occurrences exceeds
of occurrences exceeds the change threshold within the previous the change threshold within the previous change window, then it is
change window, then the notification is to be sent. Furthermore, it RECOMMENDED that the notification be sent. Furthermore, it is
is RECOMMENDED that the value for this window be set to at least 5 RECOMMENDED that the value for this window be set to at least 5 times
times the nhdpHelloInterval. 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.
5.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.
skipping to change at page 8, line 12 skipping to change at page 8, line 12
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.
5.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 an observer determining unusual topology changes or other changes
other changes that affect stability and reliability of the MANET. that affect stability and reliability of the MANET.
5.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 one hop removed from the local router,
o interfaces on other routers that are 1 hop removed from the local o interfaces on other routers that are one hop removed from the
router, and local router, and
o other routers that are 2 hops removed from the local router. o other routers that are two hops removed from the local router.
The NHDP-MIB module's tables are indexed via the following The NHDP-MIB module's tables are indexed via the following
constructs: constructs:
o nhdpIfIndex - the IfIndex of the local router on which NHDP is o nhdpIfIndex - the IfIndex of the local router on which NHDP is
configured. configured.
o nhdpDiscIfIndex - a locally managed index representing a known o nhdpDiscIfIndex - a locally managed index representing a known
interface on a neighboring router. interface on a neighboring router.
skipping to change at page 10, line 20 skipping to change at page 10, line 20
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.
6.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.
6.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
skipping to change at page 10, line 48 skipping to change at page 10, line 48
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.
6.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
[RFC2863] specifically when NHDP is to be configured to operate over ifTable [RFC2863] specifically when NHDP is to be configured to
this interface. The interface is identified by the ifIndex from the operate over this interface. The interface is identified by the
interfaces group defined in the Interfaces Group MIB module ifIndex from the Interfaces Group defined in the Interfaces Group MIB
[RFC2863]. module [RFC2863].
A conceptual row in the nhdpInterfaceTable exists if and only if A conceptual row in the nhdpInterfaceTable exists if and only if
either a manager has explicitly created the row or there is an either the row has been administratively created or there is an
interface on the managed device that supports and runs NHDP. interface on the managed device that supports and runs NHDP. This
implies that for each entry in the nhdpInterfaceTable, there is a
If the corresponding entry with ifIndex value is deleted from the corresponding entry in the Interface Table where nhdpIfIndex and
Interface Table, then the entry in this table is automatically ifIndex are equal. If that corresponding entry in the Interface
deleted, NHDP is disabled on this interface, and all configuration Table is deleted, then the entry in nhdpInterfaceTable is
and state information related to this interface is to be removed from automatically deleted, NHDP is disabled on this interface, and all
memory. configuration and state information related to this interface is to
be removed from memory.
6.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], SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001],
and FLOAT-TC-MIB [RFC6340].
7. 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),
skipping to change at page 12, line 13 skipping to change at page 12, line 17
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 "201606021100Z" -- 02 June 2016 LAST-UPDATED "201607120000Z" -- 12 July 2016
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG Email: 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 United States of America
ulrich@herberg.name ulrich@herberg.name
http://www.herberg.name/ http://www.herberg.name/
Robert G. Cole Robert G. Cole
US Army CERDEC US Army CERDEC
Space and Terrestrial Communications Space and Terrestrial Communications
6010 Frankford Street 6010 Frankford Street
Aberdeen Proving Ground, Maryland 21005 Aberdeen Proving Ground, Maryland 21005
USA United States of America
+1 443 395-8744 +1 443 395-8744
robert.g.cole@us.army.mil robert.g.cole@us.army.mil
http://www.cs.jhu.edu/~rgcole/ http://www.cs.jhu.edu/~rgcole/
Ian D Chakeres Ian D Chakeres
Delvin Delvin
Ellicott City, Maryland 21042 Ellicott City, Maryland 21042
USA United States of America
ian.chakeres@gmail.com ian.chakeres@gmail.com
http://www.ianchak.com/ http://www.ianchak.com/
Thomas Heide Clausen Thomas Heide Clausen
Ecole Polytechnique Ecole Polytechnique
LIX LIX
91128 Palaiseau Cedex 91128 Palaiseau Cedex
France France
Email: T.Clausen@computer.org Email: T.Clausen@computer.org
URI: http://www.thomasclausen.org/" URI: http://www.thomasclausen.org/"
DESCRIPTION DESCRIPTION
"This NHDP-MIB module is applicable to routers "This NHDP-MIB module is applicable to routers
implementing the Mobile Ad Hoc Network (MANET) implementing the Mobile Ad Hoc Network (MANET)
Neighborhood Discovery Protocol (NHDP) Neighborhood Discovery Protocol (NHDP)
defined in RFC 6130. defined in RFC 6130.
Copyright (c) 2014 IETF Trust and the persons Copyright (c) 2016 IETF Trust and the persons identified
identified as authors of the code. All rights reserved. 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 xxxx; see
the RFC itself for full legal notices."
-- revision -- revision
REVISION "201606021100Z" -- 02 June 2016 REVISION "201607120000Z" -- 12 July 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 7939."
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 }
-- --
-- Top-Level Components of this MIB Module -- Top-Level Components of this MIB Module
-- --
nhdpNotifications OBJECT IDENTIFIER ::= { nhdpMIB 0 } nhdpNotifications OBJECT IDENTIFIER ::= { nhdpMIB 0 }
skipping to change at page 14, line 40 skipping to change at page 14, line 38
DESCRIPTION DESCRIPTION
"An arbitrary, locally unique identifier associated with a "An arbitrary, locally unique identifier associated with a
virtual interface of a discovered NHDP neighbor. virtual interface of a discovered NHDP neighbor.
Due to the nature of NHDP, the local router Due to the nature of NHDP, the local router
may not know if two distinct addresses belong to the may not know if two distinct addresses belong to the
same interface of a neighbor or to two different same interface of a neighbor or to two different
interfaces. As the local router gains more interfaces. As the local router gains more
knowledge of its neighbors, its local view may change, and knowledge of its neighbors, its local view may change, and
this table will be updated to reflect the local router's this table will be updated to reflect the local router's
current understanding, associating address sets to neighbor current understanding, associating address sets to neighbor
interfaces. The local router identifies a virtual neighbor interfaces. The local router identifies a virtual neighbor
interface through the receipt of address lists advertised interface through the receipt of address lists advertised
through an NHDP HELLO message. through an NHDP HELLO message.
All objects of type NeighborIfIndex are assigned by the agent All objects of type NeighborIfIndex are assigned by the agent
out of a common number space. out of a common number space.
The value for each discovered virtual neighbor The value for each discovered virtual neighbor
interface may not remain constant from interface may not remain constant from
one re-initialization of the entity's network management one re-initialization of the entity's network management
agent to the next re-initialization. If the agent to the next re-initialization. If the
skipping to change at page 16, line 34 skipping to change at page 16, line 33
SYNTAX SEQUENCE OF NhdpInterfaceEntry SYNTAX SEQUENCE OF NhdpInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpInterfaceTable describes the "The nhdpInterfaceTable describes the
configuration of the interfaces of this router configuration of the interfaces of this router
that are intended to use MANET control protocols. that are intended to use MANET control protocols.
As such, this table 'sparse augments' the ifTable As such, this table 'sparse augments' the ifTable
specifically when NHDP is to be configured to specifically when NHDP is to be configured to
operate over this interface. The interface is operate over this interface. The interface is
identified by the ifIndex from the interfaces identified by the ifIndex from the Interfaces
group defined in the Interfaces Group MIB module. Group defined in the Interfaces Group MIB module.
A conceptual row in this table exists if and only A conceptual row in this table exists if and only
if either a manager has explicitly created the row if the row has been administratively created
or there is an interface on the managed device or there is an interface on the managed device
that supports and runs NHDP. that supports and runs NHDP.
The manager can create a row by setting A row can be administratively created by setting
rowStatus to 'createAndGo' or 'createAndWait'. rowStatus to 'createAndGo' or 'createAndWait'.
Row objects having associated DEFVAL clauses are During the row creation, objects having associated
automatically defined by the agent with these DEFVAL clauses are automatically defined by
values during row creation, unless the manager the agent if not explicitly administratively defined.
explicitly defines these object values during the
row creation.
If the corresponding entry with ifIndex value For each entry in the nhdpInterfaceTable, there is a
is deleted from the Interface Table, then the entry corresponding entry in the Interface Table where
in this table is automatically deleted, nhdpIfIndex and ifIndex are equal. If that corresponding
NHDP is disabled on this interface, entry in the Interface Table is deleted, then the entry in
and all configuration and state information the nhdpInterfaceTable is automatically deleted,
related to this interface is to be removed NHDP is disabled on this interface, and all configuration
from memory." and state information related to this interface is to be
removed from memory."
REFERENCE REFERENCE
"RFC 2863 - The Interfaces Group MIB, McCloghrie, "RFC 2863 - The Interfaces Group MIB, McCloghrie,
K., and F. Kastenholtz, June 2000" K., and F. Kastenholtz, June 2000"
::= { nhdpConfigurationObjGrp 1 } ::= { nhdpConfigurationObjGrp 1 }
nhdpInterfaceEntry OBJECT-TYPE nhdpInterfaceEntry OBJECT-TYPE
SYNTAX NhdpInterfaceEntry SYNTAX NhdpInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpInterfaceEntry describes one NHDP "The nhdpInterfaceEntry describes one NHDP
local interface configuration as indexed by local interface configuration as indexed by
its ifIndex as defined in the Standard MIB II its ifIndex as defined in the Standard MIB II
Interface Table (RFC 2863). Interface Table (RFC 2863).
The objects in this table are persistent, and when The objects in this table are persistent, and when
written, the device SHOULD save the change to written, the device SHOULD save the change to
non-volatile storage. For further information nonvolatile storage. For further information
on the storage behavior for these objects, refer on the storage behavior for these objects, refer
to the description for the nhdpIfRowStatus to the description for the nhdpIfRowStatus
object." object."
INDEX { nhdpIfIndex } INDEX { nhdpIfIndex }
::= { nhdpInterfaceTable 1 } ::= { nhdpInterfaceTable 1 }
NhdpInterfaceEntry ::= NhdpInterfaceEntry ::=
SEQUENCE { SEQUENCE {
nhdpIfIndex nhdpIfIndex
InterfaceIndex, InterfaceIndex,
skipping to change at page 21, line 51 skipping to change at page 22, line 4
to indicate the validity of the information taken to indicate the validity of the information taken
from that HELLO message and recorded in the receiving from that HELLO message and recorded in the receiving
router's Information Bases. router's Information Bases.
Guidance for setting this object may be found Guidance for setting this object may be found
in Section 5 of the NHDP specification (RFC 6130), in Section 5 of the NHDP specification (RFC 6130),
which indicates that it should be assigned a which indicates that it should be assigned a
value significantly greater than the refresh interval value significantly greater than the refresh interval
held by nhdpRefreshInterval and must be representable held by nhdpRefreshInterval and must be representable
as described in RFC 5497." as described in RFC 5497."
REFERENCE REFERENCE
"Section 5 on Protocol Parameters and "RFC 5497 - Representing Multi-Value Time in Mobile Ad
Hoc Networks (MANETs), Clausen, T., and C. Dearlove,
March 2009.
Section 5 on Protocol Parameters and
Constraints of RFC 6130 - Mobile Ad Hoc Network Constraints of RFC 6130 - Mobile Ad Hoc Network
(MANET) Neighborhood Discovery Protocol (NHDP), (MANET) Neighborhood Discovery Protocol (NHDP),
Clausen, T., Dearlove, C., and J. Dean, April 2011" Clausen, T., Dearlove, C., and J. Dean, April 2011"
DEFVAL { 6000 } DEFVAL { 6000 }
::= { nhdpInterfaceEntry 8 } ::= { nhdpInterfaceEntry 8 }
-- --
-- Interface Parameters - Link Quality -- Interface Parameters - Link Quality
-- --
skipping to change at page 22, line 34 skipping to change at page 22, line 40
Guidance for setting this object may be found Guidance for setting this object may be found
in Section 5 of the NHDP specification (RFC 6130), in Section 5 of the NHDP specification (RFC 6130),
which indicates that: which indicates that:
o 0 <= nhdpHystRejectQuality o 0 <= nhdpHystRejectQuality
<= nhdpHystAcceptQuality <= 1.0 <= nhdpHystAcceptQuality <= 1.0
The default value for this object is 1.0. According to The default value for this object is 1.0. According to
RFC 6340: RFC 6340:
Since these textual conventions are defined in terms Since these textual conventions are defined in terms
of the OCTET STRING type, the SMI's mechanism for of the OCTET STRING type, the SMI's mechanisms for
formally setting range constraints are not available. formally setting range constraints are not available.
MIB designers using these textual conventions will need MIB designers using these textual conventions will need
to use DESCRIPTION clauses to spell out any applicable to use DESCRIPTION clauses to spell out any applicable
range constraints beyond those implied by the underlying range constraints beyond those implied by the underlying
IEEE types. IEEE types.
Therefore, this object does not have a DEFVAL clause." Therefore, this object does not have a DEFVAL clause."
REFERENCE REFERENCE
"Section 5 on Protocol Parameters and "Section 5 on Protocol Parameters and
Constraints of RFC 6130 - Mobile Ad Hoc Network Constraints of RFC 6130 - Mobile Ad Hoc Network
(MANET) Neighborhood Discovery Protocol (NHDP), (MANET) Neighborhood Discovery Protocol (NHDP),
skipping to change at page 23, line 21 skipping to change at page 23, line 26
Guidance for setting this object may be found Guidance for setting this object may be found
in Section 5 of the NHDP specification (RFC 6130), in Section 5 of the NHDP specification (RFC 6130),
which indicates that: which indicates that:
o 0 <= nhdpHystRejectQuality o 0 <= nhdpHystRejectQuality
<= nhdpHystAcceptQuality <= 1.0 <= nhdpHystAcceptQuality <= 1.0
The default value for this object is 0.0. According to The default value for this object is 0.0. According to
RFC 6340: RFC 6340:
Since these textual conventions are defined in terms Since these textual conventions are defined in terms
of the OCTET STRING type, the SMI's mechanism for of the OCTET STRING type, the SMI's mechanisms for
formally setting range constraints are not available. formally setting range constraints are not available.
MIB designers using these textual conventions will need MIB designers using these textual conventions will need
to use DESCRIPTION clauses to spell out any applicable to use DESCRIPTION clauses to spell out any applicable
range constraints beyond those implied by the underlying range constraints beyond those implied by the underlying
IEEE types. IEEE types.
Therefore, this object does not have a DEFVAL clause." Therefore, this object does not have a DEFVAL clause."
REFERENCE REFERENCE
"Section 5 on Protocol Parameters and "Section 5 on Protocol Parameters and
Constraints of RFC 6130 - Mobile Ad Hoc Network Constraints of RFC 6130 - Mobile Ad Hoc Network
(MANET) Neighborhood Discovery Protocol (NHDP), (MANET) Neighborhood Discovery Protocol (NHDP),
skipping to change at page 24, line 4 skipping to change at page 24, line 9
INITIAL_QUALITY of NHDP and represents the INITIAL_QUALITY of NHDP and represents the
initial quality of a newly identified link. initial quality of a newly identified link.
Guidance for setting this object may be found Guidance for setting this object may be found
in Section 5 of the NHDP specification (RFC 6130), in Section 5 of the NHDP specification (RFC 6130),
which indicates that: which indicates that:
o 0 <= nhdpInitialQuality <= 1.0 o 0 <= nhdpInitialQuality <= 1.0
The default value for this object is 1.0. According to The default value for this object is 1.0. According to
RFC 6340: RFC 6340:
Since these textual conventions are defined in terms Since these textual conventions are defined in terms
of the OCTET STRING type, the SMI's mechanism for of the OCTET STRING type, the SMI's mechanisms for
formally setting range constraints are not available. formally setting range constraints are not available.
MIB designers using these textual conventions will need MIB designers using these textual conventions will need
to use DESCRIPTION clauses to spell out any applicable to use DESCRIPTION clauses to spell out any applicable
range constraints beyond those implied by the underlying range constraints beyond those implied by the underlying
IEEE types. IEEE types.
Therefore, this object does not have a DEFVAL clause." Therefore, this object does not have a DEFVAL clause."
REFERENCE REFERENCE
"Section 5 on Protocol Parameters and "Section 5 on Protocol Parameters and
Constraints of RFC 6130 - Mobile Ad Hoc Network Constraints of RFC 6130 - Mobile Ad Hoc Network
(MANET) Neighborhood Discovery Protocol (NHDP), (MANET) Neighborhood Discovery Protocol (NHDP),
Clausen, T., Dearlove, C., and J. Dean, April 2011" Clausen, T., Dearlove, C., and J. Dean, April 2011"
-- DEFVAL { 1.0 } see DESCRIPTION -- DEFVAL { 1.0 } see DESCRIPTION
::= { nhdpInterfaceEntry 11 } ::= { nhdpInterfaceEntry 11 }
nhdpInitialPending OBJECT-TYPE nhdpInitialPending OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpInitialPending corresponds to "nhdpInitialPending corresponds to
INITIAL_PENDING of NHDP. If the value of this object INITIAL_PENDING of NHDP. If the value of this object
is 'true(1)', then a newly identified link is considered is 'true(1)', then a newly identified link is considered
pending and is not usable until the link quality pending and is not usable until the link quality
has reached or exceeded the nhdpHystAcceptQuality has reached or exceeded the nhdpHystAcceptQuality
threshold. threshold.
Guidance for setting this object may be found Guidance for setting this object may be found
in Section 5 of the NHDP specification (RFC 6130), in Section 5 of the NHDP specification (RFC 6130),
which indicates that: which indicates that:
o If nhdpInitialQuality >= nhdpHystAcceptQuality, o If nhdpInitialQuality >= nhdpHystAcceptQuality,
then nhdpInitialPending := false(2). then nhdpInitialPending := false(2).
skipping to change at page 26, line 30 skipping to change at page 26, line 35
this object has no effect on whether other this object has no effect on whether other
objects in this conceptual row can be objects in this conceptual row can be
modified. modified.
An entry may not exist in the 'active(1)' state unless all An entry may not exist in the 'active(1)' state unless all
objects in the entry have a defined appropriate value. For objects in the entry have a defined appropriate value. For
objects with DEFVAL clauses, the management station objects with DEFVAL clauses, the management station
does not need to specify the value of this object in order does not need to specify the value of this object in order
for the row to transit to the 'active(1)' state; the default for the row to transit to the 'active(1)' state; the default
value for this object is used. For objects that do not value for this object is used. For objects that do not
have DEFVAL clauses, then the network manager MUST have DEFVAL clauses, the value of this object prior
specify the value of this object prior to this row to this row transitioning to the 'active(1)' state MUST be
transitioning to the 'active(1)' state. administratively specified.
When this object transitions to 'active(1)', all objects When this object transitions to 'active(1)', all objects
in this row SHOULD be written to non-volatile (stable) in this row SHOULD be written to nonvolatile (stable)
storage. Read-create objects in this row MAY be modified. storage. Read-create objects in this row MAY be modified.
When an object in a row with nhdpIfRowStatus of 'active(1)' When an object in a row with nhdpIfRowStatus of 'active(1)'
is changed, then the updated value MUST be reflected in NHDP, is changed, then the updated value MUST be reflected in NHDP,
and this new object value MUST be written to non-volatile and this new object value MUST be written to nonvolatile
storage. storage.
If the value of this object is not equal to 'active(1)', If the value of this object is not equal to 'active(1)',
all associated entries in the nhdpLibLocalIfSetTable, all associated entries in the nhdpLibLocalIfSetTable,
nhdpInterfaceStateTable, nhdpIibLinkSetTable, and nhdpInterfaceStateTable, nhdpIibLinkSetTable, and
nhdpInterfacePerfTable MUST be deleted." nhdpInterfacePerfTable MUST be deleted."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
DEFVAL { active } DEFVAL { active }
::= { nhdpInterfaceEntry 15 } ::= { nhdpInterfaceEntry 15 }
-- --
-- Router Parameters - Information Validity Time -- Router Parameters - Information Validity Time
-- --
nhdpNHoldTime OBJECT-TYPE nhdpNHoldTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpNHoldTime corresponds to "nhdpNHoldTime corresponds to
skipping to change at page 27, line 23 skipping to change at page 27, line 31
"nhdpNHoldTime corresponds to "nhdpNHoldTime corresponds to
N_HOLD_TIME of NHDP and is used as the period N_HOLD_TIME of NHDP and is used as the period
during which former 1-hop neighbor network during which former 1-hop neighbor network
addresses are advertised as lost in HELLO addresses are advertised as lost in HELLO
messages, allowing recipients of these HELLO messages, allowing recipients of these HELLO
messages to accelerate removal of this information messages to accelerate removal of this information
from their 2-Hop Sets. from their 2-Hop Sets.
This object is persistent, and when written, This object is persistent, and when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." nonvolatile storage."
REFERENCE REFERENCE
"Section 5 on Protocol Parameters and "Section 5 on Protocol Parameters and
Constraints of RFC 6130 - Mobile Ad Hoc Network Constraints of RFC 6130 - Mobile Ad Hoc Network
(MANET) Neighborhood Discovery Protocol (NHDP), (MANET) Neighborhood Discovery Protocol (NHDP),
Clausen, T., Dearlove, C., and J. Dean, April 2011" Clausen, T., Dearlove, C., and J. Dean, April 2011"
DEFVAL { 6000 } DEFVAL { 6000 }
::= { nhdpConfigurationObjGrp 2 } ::= { nhdpConfigurationObjGrp 2 }
nhdpIHoldTime OBJECT-TYPE nhdpIHoldTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
skipping to change at page 27, line 45 skipping to change at page 28, line 7
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpIHoldTime corresponds to "nhdpIHoldTime corresponds to
I_HOLD_TIME of NHDP and represents the period I_HOLD_TIME of NHDP and represents the period
for which a recently used local interface network for which a recently used local interface network
address is recorded. address is recorded.
This object is persistent, and when written, This object is persistent, and when written,
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." nonvolatile storage."
REFERENCE REFERENCE
"Section 5 on Protocol Parameters and "Section 5 on Protocol Parameters and
Constraints of RFC 6130 - Mobile Ad Hoc Network Constraints of RFC 6130 - Mobile Ad Hoc Network
(MANET) Neighborhood Discovery Protocol (NHDP), (MANET) Neighborhood Discovery Protocol (NHDP),
Clausen, T., Dearlove, C., and J. Dean, April 2011" Clausen, T., Dearlove, C., and J. Dean, April 2011"
DEFVAL { 6000 } DEFVAL { 6000 }
::= { nhdpConfigurationObjGrp 3 } ::= { nhdpConfigurationObjGrp 3 }
-- A router's Local Information Base (LIB) -- A router's Local Information Base (LIB)
-- --
-- Local Interface Set Table -- Local Interface Set Table
-- --
nhdpLibLocalIfSetTable OBJECT-TYPE nhdpLibLocalIfSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpLibLocalIfSetEntry SYNTAX SEQUENCE OF NhdpLibLocalIfSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's Local Interface Set records all "A router's Local Interface Set records all
skipping to change at page 28, line 34 skipping to change at page 28, line 41
being defined for the interfaces existing within being defined for the interfaces existing within
the nhdpInterfaceTable. The local interface the nhdpInterfaceTable. The local interface
is defined by the nhdpIfIndex. is defined by the nhdpIfIndex.
The Local Interface Set consists of Local Interface The Local Interface Set consists of Local Interface
Address Tuples per MANET interface and their prefix Address Tuples per MANET interface and their prefix
lengths (in order to determine the network addresses lengths (in order to determine the network addresses
related to the interface). related to the interface).
A conceptual row in this table exists if and only A conceptual row in this table exists if and only
if a manager has explicitly created the row. The if one has been administratively created. This can be done
manager can create a row by setting rowStatus by setting rowStatus to 'createAndGo' or 'createAndWait'.
to 'createAndGo' or 'createAndWait'.
Further guidance on the addition or removal of Further guidance on the addition or removal of
local addresses and network addresses is found local addresses and network addresses is found
in Section 9 of RFC 6130." in Section 9 of RFC 6130."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpConfigurationObjGrp 4 } ::= { nhdpConfigurationObjGrp 4 }
nhdpLibLocalIfSetEntry OBJECT-TYPE nhdpLibLocalIfSetEntry OBJECT-TYPE
SYNTAX NhdpLibLocalIfSetEntry SYNTAX NhdpLibLocalIfSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's Local Interface Set consists "A router's Local Interface Set consists
of Local Interface Tuples for each network of Local Interface Tuples for each network
interface. interface.
The objects in this table are persistent, and when The objects in this table are persistent, and when
skipping to change at page 29, line 10 skipping to change at page 29, line 15
SYNTAX NhdpLibLocalIfSetEntry SYNTAX NhdpLibLocalIfSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's Local Interface Set consists "A router's Local Interface Set consists
of Local Interface Tuples for each network of Local Interface Tuples for each network
interface. interface.
The objects in this table are persistent, and when The objects in this table are persistent, and when
written, the device SHOULD save the change to written, the device SHOULD save the change to
non-volatile storage. For further information nonvolatile storage. For further information
on the storage behavior for these objects, refer on the storage behavior for these objects, refer
to the description for the nhdpLibLocalIfSetRowStatus to the description for the nhdpLibLocalIfSetRowStatus
object." object."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
INDEX { nhdpLibLocalIfSetIndex } INDEX { nhdpLibLocalIfSetIndex }
::= { nhdpLibLocalIfSetTable 1 } ::= { nhdpLibLocalIfSetTable 1 }
skipping to change at page 31, line 39 skipping to change at page 31, line 49
modified. modified.
An entry may not exist in the 'active(1)' state unless all An entry may not exist in the 'active(1)' state unless all
read-create objects in the entry have a defined read-create objects in the entry have a defined
appropriate value. As no objects in this table have appropriate value. As no objects in this table have
DEFVAL clauses, the management station MUST specify DEFVAL clauses, the management station MUST specify
the values of all read-create objects prior to this row the values of all read-create objects prior to this row
transitioning to the 'active(1)' state. transitioning to the 'active(1)' state.
When this object transitions to 'active(1)', all objects When this object transitions to 'active(1)', all objects
in this row SHOULD be written to non-volatile (stable) in this row SHOULD be written to nonvolatile (stable)
storage. Read-create objects in this row MAY be modified. storage. Read-create objects in this row MAY be modified.
When an object in a row with nhdpIfRowStatus of 'active(1)' When an object in a row with nhdpIfRowStatus of 'active(1)'
is changed, then the updated value MUST be reflected in NHDP, is changed, then the updated value MUST be reflected in NHDP,
and this new object value MUST be written to non-volatile and this new object value MUST be written to nonvolatile
storage." storage."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
DEFVAL { notReady } DEFVAL { notReady }
::= { nhdpLibLocalIfSetEntry 6 } ::= { nhdpLibLocalIfSetEntry 6 }
-- --
-- Removed Interface Addr Set Table -- Removed Interface Addr Set Table
skipping to change at page 32, line 40 skipping to change at page 33, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's Removed Interface Address Set consists "A router's Removed Interface Address Set consists
of Removed Interface Address Tuples, one per network of Removed Interface Address Tuples, one per network
address: address:
(IR_local_iface_addr, IR_time) (IR_local_iface_addr, IR_time)
The association between these addresses and the The association between these addresses and the
router's Interface is found in RFC 4293 (ipAddressTable)" router's Interface is found in RFC 4293 (ipAddressTable)"
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 4293 - Management Information Base for the Internet
Protocol (IP), S. Routhier, Ed., April 2006.
RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
INDEX { nhdpLibRemovedIfAddrSetIndex } INDEX { nhdpLibRemovedIfAddrSetIndex }
::= { nhdpLibRemovedIfAddrSetTable 1 } ::= { nhdpLibRemovedIfAddrSetTable 1 }
NhdpLibRemovedIfAddrSetEntry ::= NhdpLibRemovedIfAddrSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpLibRemovedIfAddrSetIndex nhdpLibRemovedIfAddrSetIndex
Integer32, Integer32,
nhdpLibRemovedIfAddrSetIpAddrType nhdpLibRemovedIfAddrSetIpAddrType
skipping to change at page 34, line 48 skipping to change at page 35, line 17
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpLibRemovedIfAddrSetEntry 5 } ::= { nhdpLibRemovedIfAddrSetEntry 5 }
nhdpLibRemovedIfAddrSetIRTime OBJECT-TYPE nhdpLibRemovedIfAddrSetIRTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpLibRemovedIfAddrSetIRTime specifies the value "nhdpLibRemovedIfAddrSetIRTime specifies the value
of sysUptime when this entry should expire and be of sysUpTime when this entry should expire and be
removed from the nhdpLibRemovedIfAddrSetTable." removed from the nhdpLibRemovedIfAddrSetTable."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpLibRemovedIfAddrSetEntry 6 } ::= { nhdpLibRemovedIfAddrSetEntry 6 }
-- --
-- nhdpStateObjGrp -- nhdpStateObjGrp
-- --
skipping to change at page 35, line 34 skipping to change at page 35, line 51
::= { nhdpStateObjGrp 1 } ::= { nhdpStateObjGrp 1 }
nhdpInterfaceStateTable OBJECT-TYPE nhdpInterfaceStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpInterfaceStateEntry SYNTAX SEQUENCE OF NhdpInterfaceStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpInterfaceStateTable lists state information "nhdpInterfaceStateTable lists state information
related to specific interfaces of this router. related to specific interfaces of this router.
The value of nhdpIfIndex is an ifIndex from the The value of nhdpIfIndex is an ifIndex from the
interfaces group defined in the Interfaces Group Interfaces Group defined in the Interfaces Group
MIB. MIB.
The objects in this table are persistent, and when The objects in this table are persistent, and when
written, the entity SHOULD save the change to written, the entity SHOULD save the change to
non-volatile storage." nonvolatile storage."
REFERENCE REFERENCE
"RFC 2863 - The Interfaces Group MIB, McCloghrie, "RFC 2863 - The Interfaces Group MIB, McCloghrie,
K., and F. Kastenholtz, June 2000." K., and F. Kastenholtz, June 2000"
::= { nhdpStateObjGrp 2 } ::= { nhdpStateObjGrp 2 }
nhdpInterfaceStateEntry OBJECT-TYPE nhdpInterfaceStateEntry OBJECT-TYPE
SYNTAX NhdpInterfaceStateEntry SYNTAX NhdpInterfaceStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpInterfaceStateEntry describes one NHDP "nhdpInterfaceStateEntry describes one NHDP
local interface state as indexed by local interface state as indexed by
its nhdpIfIndex." its nhdpIfIndex."
skipping to change at page 42, line 24 skipping to change at page 42, line 41
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpIibLinkSetEntry 4 } ::= { nhdpIibLinkSetEntry 4 }
nhdpIibLinkSetLTime OBJECT-TYPE nhdpIibLinkSetLTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpIibLinkSetLTime specifies the value "nhdpIibLinkSetLTime specifies the value
of sysUptime when this entry should expire and be of sysUpTime when this entry should expire and be
removed from the nhdpIibLinkSetTable." removed from the nhdpIibLinkSetTable."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpIibLinkSetEntry 5 } ::= { nhdpIibLinkSetEntry 5 }
-- --
-- 2-Hop Set -- 2-Hop Set
-- --
nhdpIib2HopSetTable OBJECT-TYPE nhdpIib2HopSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpIib2HopSetEntry SYNTAX SEQUENCE OF NhdpIib2HopSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A 2-Hop Set of an interface records network "A 2-Hop Set of an interface records network
addresses of symmetric 2-hop neighbors and addresses of symmetric 2-hop neighbors and
skipping to change at page 43, line 19 skipping to change at page 43, line 38
"nhdpIib2HopSetTable consists of 2-Hop Tuples, each "nhdpIib2HopSetTable consists of 2-Hop Tuples, each
representing a single network address of a symmetric representing a single network address of a symmetric
2-hop neighbor and a single MANET interface of a 2-hop neighbor and a single MANET interface of a
symmetric 1-hop neighbor. symmetric 1-hop neighbor.
(N2_neighbor_iface_addr_list, (N2_neighbor_iface_addr_list,
N2_2hop_addr, N2_lost, N2_time). N2_2hop_addr, N2_lost, N2_time).
The entries include: The entries include:
- the 2-hop neighbor addresses - the 2-hop neighbor addresses
('N2_neighbor_iface_addr_list'), which ('N2_neighbor_iface_addr_list'), which
act as the table index, act as the table index,
- the associated symmetric 1-hop - the associated symmetric 1-hop
neighbor address set ('N2_2hop_addr'), designated neighbor address set ('N2_2hop_addr'), designated
through nhdpDiscIfIndex, through nhdpDiscIfIndex,
- a flag indicating if the 1-hop neighbor - a flag indicating if the 1-hop neighbor
through which this 2-hop neighbor is reachable through which this 2-hop neighbor is reachable
('N2_lost') is considered lost due to link quality, ('N2_lost') is considered lost due to link quality,
or not, or not,
- and the expiration time ('N2_time'). - and the expiration time ('N2_time').
The nhdpIfIndex in the INDEX is the interface index of The nhdpIfIndex in the INDEX is the interface index of
the local interface through which these 2-hop addresses the local interface through which these 2-hop addresses
are accessible. The nhdpDiscIfIndex in the INDEX are accessible. The nhdpDiscIfIndex in the INDEX
represents the 1-hop neighbor interface through which represents the 1-hop neighbor interface through which
these 2-hop neighbor addresses are reachable." these 2-hop neighbor addresses are reachable."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011, C., and J. Dean, April 2011
and and
RFC 7466 - RFC 7466 - An Optimization for the Mobile Ad Hoc
An Optimization for the Mobile Ad Hoc Network (MANET) Network (MANET) Neighborhood Discovery Protocol (NHDP),
Neighborhood Discovery Protocol (NHDP), Dearlove, C., and T. Clausen, March 2015"
Dearlove, C., and T. Clausen,
March 2015"
INDEX { nhdpIfIndex, INDEX { nhdpIfIndex,
nhdpDiscIfIndex, nhdpDiscIfIndex,
nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddressType,
nhdpIib2HopSetIpAddress nhdpIib2HopSetIpAddress
} }
::= { nhdpIib2HopSetTable 1 } ::= { nhdpIib2HopSetTable 1 }
NhdpIib2HopSetEntry ::= NhdpIib2HopSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpIib2HopSetIpAddressType nhdpIib2HopSetIpAddressType
InetAddressType, InetAddressType,
nhdpIib2HopSetIpAddress nhdpIib2HopSetIpAddress
InetAddress, InetAddress,
nhdpIib2HopSetIpAddrPrefixLen nhdpIib2HopSetIpAddrPrefixLen
InetAddressPrefixLength, InetAddressPrefixLength,
nhdpIib2HopSet1HopIfIndex nhdpIib2HopSet1HopIfIndex
NeighborIfIndex, NeighborIfIndex,
skipping to change at page 45, line 43 skipping to change at page 46, line 18
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpIib2HopSetEntry 4 } ::= { nhdpIib2HopSetEntry 4 }
nhdpIib2HopSetN2Time OBJECT-TYPE nhdpIib2HopSetN2Time OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpIib2HopSetN2Time specifies the value "nhdpIib2HopSetN2Time specifies the value
of sysUptime when this entry should expire and be of sysUpTime when this entry should expire and be
removed from the nhdpIib2HopSetTable." removed from the nhdpIib2HopSetTable."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpIib2HopSetEntry 5 } ::= { nhdpIib2HopSetEntry 5 }
nhdpIib2HopSetN2Lost OBJECT-TYPE nhdpIib2HopSetN2Lost OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and "nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and
is a boolean flag, describing if for a 2-Hop Tuple, the is a boolean flag, describing if for a 2-Hop Tuple, the
corresponding Link Tuple currently is considered lost corresponding Link Tuple currently is considered lost
due to link quality." due to link quality."
skipping to change at page 46, line 15 skipping to change at page 46, line 37
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and "nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and
is a boolean flag, describing if for a 2-Hop Tuple, the is a boolean flag, describing if for a 2-Hop Tuple, the
corresponding Link Tuple currently is considered lost corresponding Link Tuple currently is considered lost
due to link quality." due to link quality."
REFERENCE REFERENCE
"RFC 7466 - "RFC 7466 - An Optimization for the Mobile Ad Hoc
An Optimization for the Mobile Ad Hoc Network (MANET) Network (MANET) Neighborhood Discovery Protocol (NHDP),
Neighborhood Discovery Protocol (NHDP), Dearlove, C., and T. Clausen, March 2015"
Dearlove, C., and T. Clausen,
March 2015"
::= {nhdpIib2HopSetEntry 6} ::= {nhdpIib2HopSetEntry 6}
-- --
-- Neighbor Information Base (NIB) -- Neighbor Information Base (NIB)
-- --
-- Each router maintains a Neighbor Information Base -- Each router maintains a Neighbor Information Base
-- that records information about addresses of -- that records information about addresses of
-- current and recently symmetric 1-hop neighbors. -- current and recently symmetric 1-hop neighbors.
-- --
skipping to change at page 48, line 41 skipping to change at page 49, line 16
nhdpNibLostNeighborSetNLTime nhdpNibLostNeighborSetNLTime
TimeStamp TimeStamp
} }
nhdpNibLostNeighborSetNLTime OBJECT-TYPE nhdpNibLostNeighborSetNLTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpNibLostNeighborSetNLTime "nhdpNibLostNeighborSetNLTime
specifies the value of sysUptime when this entry specifies the value of sysUpTime when this entry
should expire and be removed from the should expire and be removed from the
nhdpNibLostNeighborSetTable." nhdpNibLostNeighborSetTable."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpNibLostNeighborSetEntry 1 } ::= { nhdpNibLostNeighborSetEntry 1 }
-- --
-- nhdpPerformanceObjGrp -- nhdpPerformanceObjGrp
skipping to change at page 50, line 29 skipping to change at page 51, line 4
} }
nhdpIfHelloMessageXmits OBJECT-TYPE nhdpIfHelloMessageXmits OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "messages" UNITS "messages"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter is incremented each time a HELLO "A counter is incremented each time a HELLO
message has been transmitted on that interface." message has been transmitted on that interface."
::= { nhdpInterfacePerfEntry 1 } ::= { nhdpInterfacePerfEntry 1 }
nhdpIfHelloMessageRecvd OBJECT-TYPE nhdpIfHelloMessageRecvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "messages" UNITS "messages"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter is incremented each time a "A counter is incremented each time a HELLO
HELLO message has been received on that interface." message has been received on that interface."
::= { nhdpInterfacePerfEntry 2 } ::= { nhdpInterfacePerfEntry 2 }
nhdpIfHelloMessageXmitAccumulatedSize OBJECT-TYPE nhdpIfHelloMessageXmitAccumulatedSize OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter is incremented by the number of octets in "A counter is incremented by the number of octets in
a HELLO message each time a a HELLO message each time a HELLO message has been sent."
HELLO message has been sent."
::= { nhdpInterfacePerfEntry 3 } ::= { nhdpInterfacePerfEntry 3 }
nhdpIfHelloMessageRecvdAccumulatedSize OBJECT-TYPE nhdpIfHelloMessageRecvdAccumulatedSize OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter is incremented by the number of octets in "A counter is incremented by the number of octets in
a HELLO message each time a a HELLO message each time a HELLO message has been received."
HELLO message has been received."
::= { nhdpInterfacePerfEntry 4 } ::= { nhdpInterfacePerfEntry 4 }
nhdpIfHelloMessageTriggeredXmits OBJECT-TYPE nhdpIfHelloMessageTriggeredXmits OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "messages" UNITS "messages"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter is incremented each time a triggered "A counter is incremented each time a triggered
HELLO message has been sent." HELLO message has been sent."
skipping to change at page 52, line 26 skipping to change at page 52, line 48
message has been sent." message has been sent."
::= { nhdpInterfacePerfEntry 9 } ::= { nhdpInterfacePerfEntry 9 }
nhdpIfPerfCounterDiscontinuityTime OBJECT-TYPE nhdpIfPerfCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
any one or more of this interface's counters suffered a any one or more of this interface's counters suffered a
discontinuity. If no such discontinuities have occurred discontinuity. If no such discontinuities have occurred
since the last reinitialization of the local management since the last reinitialization of the local management
subsystem, then this object contains a zero value." subsystem, then this object contains a zero value."
::= { nhdpInterfacePerfEntry 10 } ::= { nhdpInterfacePerfEntry 10 }
-- --
-- Objects per discovered neighbor interface -- Objects per discovered neighbor interface
-- --
nhdpDiscIfSetPerfTable OBJECT-TYPE nhdpDiscIfSetPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpDiscIfSetPerfEntry SYNTAX SEQUENCE OF NhdpDiscIfSetPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's set of performance properties for "A router's set of performance properties for
each discovered interface of a neighbor." each discovered interface of a neighbor."
skipping to change at page 55, line 35 skipping to change at page 56, line 4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object returns the number of changes "This object returns the number of changes
to the given Neighbor Tuple." to the given Neighbor Tuple."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpDiscNeighborSetPerfEntry 1 } ::= { nhdpDiscNeighborSetPerfEntry 1 }
nhdpDiscNeighborNibNeighborSetUpTime OBJECT-TYPE nhdpDiscNeighborNibNeighborSetUpTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object returns the sysUpTime when "This object returns the sysUpTime when a new
a new nhdpNibNeighborSetEntry nhdpNibNeighborSetEntry has been created for a
has been created for a particular particular nhdpNibNeighborSetRouterIndex."
nhdpNibNeighborSetRouterIndex."
REFERENCE REFERENCE
"RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood
Discovery Protocol (NHDP), Clausen, T., Dearlove, Discovery Protocol (NHDP), Clausen, T., Dearlove,
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpDiscNeighborSetPerfEntry 2 } ::= { nhdpDiscNeighborSetPerfEntry 2 }
nhdpDiscNeighborNibNeighborSetReachableLinkChanges OBJECT-TYPE nhdpDiscNeighborNibNeighborSetReachableLinkChanges OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "changes" UNITS "changes"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 61, line 22 skipping to change at page 61, line 34
nhdp2HopNbrState OBJECT-TYPE nhdp2HopNbrState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
down(0), down(0),
up(1), up(1),
notconsidered(2) notconsidered(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"NHDP 2-hop neighbor states. In NHDP, it is not necessary "NHDP 2-hop neighbor states. In NHDP, it is not necessary
to remove Protocol Tuples from Protocol Sets at the to remove Protocol Tuples from Protocol Sets at the
exact time indicated, only to behave as if the Protocol exact time indicated, only to behave as if the Protocol
Tuples were removed at that time. This case is indicated Tuples were removed at that time. This case is indicated
here as 'down(0)'; otherwise, it is either 'up(1)', if here as 'down(0)'; otherwise, it is either 'up(1)', if
N2_lost for the 2-Hop Tuple is equal to false, or N2_lost for the 2-Hop Tuple is equal to false, or
'notconsidered(2)' otherwise." 'notconsidered(2)' otherwise."
::= { nhdpNotificationsStates 2 } ::= { nhdpNotificationsStates 2 }
-- --
-- nhdpConformance information -- nhdpConformance information
-- --
nhdpCompliances OBJECT IDENTIFIER ::= { nhdpConformance 1 } nhdpCompliances OBJECT IDENTIFIER ::= { nhdpConformance 1 }
skipping to change at page 66, line 4 skipping to change at page 66, line 16
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 8. 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.
There are a number of management objects defined in this MIB module 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 with a MAX-ACCESS clause of read-write and/or read-create. Such
skipping to change at page 67, line 14 skipping to change at page 67, line 27
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o nhdpDiscIfSetTable - The object contains information on discovered o nhdpDiscIfSetTable - The object contains information on discovered
neighbors, specifically their IP address in the neighbors, specifically their IP address in the
nhdpDiscIfSetIpAddr object. This information provides an nhdpDiscIfSetIpAddr object. This information provides an
adversary broad information on the members of the MANET, located adversary broad information on the members of the MANET, located
within this single table. This information can be used to within this single table. This information can be used to
expedite attacks on the other members of the MANET without having expedite attacks on the other members of the MANET without having
to go through a laborious discovery process on their own. This to go through a laborious discovery process on their own. This
object is the index into the table and has a MAX-ACCESS of 'not- object is the index into the table and has a MAX-ACCESS of
accessible'. However, this information can be exposed using SNMP 'not-accessible'. However, this information can be exposed using
operations. SNMP operations.
MANET technology is often deployed to support communications of MANET technology is often deployed to support communications of
emergency services or military tactical applications. In these emergency services or military tactical applications. In these
applications, it is imperative to maintain the proper operation of applications, it is imperative to maintain the proper operation of
the communications network and to protect sensitive information the communications network and to protect sensitive information
related to its operation. Therefore, it is RECOMMENDED to provide related to its operation. Therefore, it is RECOMMENDED to provide
support for the Transport Security Model (TSM) [RFC5591] in support for the Transport Security Model (TSM) [RFC5591] in
combination with TLS/DTLS [RFC6353]. combination with TLS/DTLS [RFC6353].
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
skipping to change at page 68, line 16 skipping to change at page 68, line 24
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. MANET network deployments.
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 "2-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
for the vehicles comprising the MANET being forward deployed at a for the vehicles comprising the MANET being forward deployed at a
remote location, e.g., the site of a natural disaster, to be off- remote location, e.g., the site of a natural disaster, to be off-
loaded in a parking lot where an initial configuration of the loaded in a parking lot where an initial configuration of the
networking devices is performed. The configuration is loaded into networking devices is performed. The configuration is loaded into
the devices from a fixed location Network Operation Center (NOC) the devices from a fixed location Network Operations Center (NOC)
at the parking lot, and the vehicles are stationary at the parking at the parking lot, and the vehicles are stationary at the parking
lot while the configuration changes are made. Standards-based lot while the configuration changes are made. Standards-based
methods for configuration management from the co-located NOC are methods for configuration management from the co-located NOC are
necessary for this deployment option. necessary for this deployment option.
o For Mobile Vehicles with Low-Bandwidth Satellite Link to a Fixed o For Mobile Vehicles with Low-Bandwidth Satellite Link to a Fixed
NOC - Here, the vehicles carrying the MANET routers carry multiple NOC - Here, the vehicles carrying the MANET routers carry multiple
wireless interfaces, one of which is a relatively low-bandwidth, wireless interfaces, one of which is a relatively low-bandwidth,
on-the-move satellite connection that interconnects a fix NOC to on-the-move satellite connection that interconnects a fix NOC to
the nodes of the MANET. Standards-based methods for monitoring the nodes of the MANET. Standards-based methods for monitoring
skipping to change at page 69, line 5 skipping to change at page 69, line 12
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.
10. 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 Description OBJECT IDENTIFIER value
---------- ----------------------- ----------- -----------------------
NHDP-MIB { mib-2 213 } NHDP-MIB { mib-2 213 }
11. Acknowledgements 11. References
The authors wish to thank Benoit Claise, Elwyn Davies, Justin Dean,
Adrian Farrel, Joel Halpern, Michael MacFaden, Al Morton, and Thomas
Nadeau for their detailed reviews and insightful comments regarding
RFC6779 and this document.
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.
12. References
12.1. Normative References 11.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,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[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,
DOI 10.17487/RFC2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>.
[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",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
<http://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Conformance Statements for SMIv2", STD 58, RFC 2580, Schoenwaelder, Ed., "Conformance Statements for SMIv2",
April 1999. STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
<http://www.rfc-editor.org/info/rfc2580>.
[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, DOI 10.17487/RFC2863, June 2000,
<http://www.rfc-editor.org/info/rfc2863>.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
Simple Network Management Protocol (SNMP)", STD 62, (USM) for version 3 of the Simple Network Management
RFC 3418, December 2002. Protocol (SNMPv3)", STD 62, RFC 3414,
DOI 10.17487/RFC3414, December 2002,
<http://www.rfc-editor.org/info/rfc3414>.
[RFC3418] Presuhn, R., Ed., "Management Information Base (MIB) for
the Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, DOI 10.17487/RFC3418, December 2002,
<http://www.rfc-editor.org/info/rfc3418>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826,
DOI 10.17487/RFC3826, June 2004,
<http://www.rfc-editor.org/info/rfc3826>.
[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, DOI 10.17487/RFC4001, February 2005,
<http://www.rfc-editor.org/info/rfc4001>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June
2009, <http://www.rfc-editor.org/info/rfc5592>.
[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, DOI 10.17487/RFC6130, April 2011,
<http://www.rfc-editor.org/info/rfc6130>.
[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,
DOI 10.17487/RFC6340, August 2011,
<http://www.rfc-editor.org/info/rfc6340>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,
<http://www.rfc-editor.org/info/rfc6353>.
[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, DOI 10.17487/RFC7466, March
2015, <http://www.rfc-editor.org/info/rfc7466>.
12.2. Informative References 11.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,
DOI 10.17487/RFC3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>.
[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", STD 62, RFC 3411,
December 2002. DOI 10.17487/RFC3411, December 2002,
<http://www.rfc-editor.org/info/rfc3411>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, June 2004.
[RFC4293] Routhier, S., "Management Information Base for the
Internet Protocol (IP)", RFC 4293, April 2006.
[RFC4750] Joyal, D., Galecki, P., Giacalone, S., Coltun, R., and F. [RFC4750] Joyal, D., Ed., Galecki, P., Ed., Giacalone, S., Ed.,
Baker, "OSPF Version 2 Management Information Base", Coltun, R., and F. Baker, "OSPF Version 2 Management
RFC 4750, December 2006. Information Base", RFC 4750, DOI 10.17487/RFC4750,
December 2006, <http://www.rfc-editor.org/info/rfc4750>.
[RFC5148] Clausen, T., Dearlove, C., and B. Adamson, "Jitter [RFC5148] Clausen, T., Dearlove, C., and B. Adamson, "Jitter
Considerations in Mobile Ad Hoc Networks (MANETs)", Considerations in Mobile Ad Hoc Networks (MANETs)",
RFC 5148, February 2008. RFC 5148, DOI 10.17487/RFC5148, February 2008,
<http://www.rfc-editor.org/info/rfc5148>.
[RFC5497] Clausen, T. and C. Dearlove, "Representing Multi-Value
Time in Mobile Ad Hoc Networks (MANETs)", RFC 5497,
March 2009.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC6779] Herberg, U., Cole, R., and I. Chakeres, "Definition of
for the Simple Network Management Protocol (SNMP)", Managed Objects for the Neighborhood Discovery Protocol",
RFC 5591, June 2009. RFC 6779, DOI 10.17487/RFC6779, October 2012,
<http://www.rfc-editor.org/info/rfc6779>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Acknowledgements
Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, June 2009.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport The authors wish to thank Benoit Claise, Elwyn Davies, Justin Dean,
Model for the Simple Network Management Protocol (SNMP)", Adrian Farrel, Joel Halpern, Michael MacFaden, Al Morton, and Thomas
RFC 6353, July 2011. Nadeau for their detailed reviews and insightful comments regarding
RFC 6779 and this document.
[RFC6779] Herberg, U., Cole, R., and I. Chakeres, "Definition of This MIB document uses the template authored by D. Harrington, which
Managed Objects for the Neighborhood Discovery Protocol", is based on contributions from the MIB Doctors, especially Juergen
RFC 6779, October 2012. Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn.
Authors' Addresses Authors' Addresses
Ulrich Herberg Ulrich Herberg
United States United States of America
EMail: ulrich@herberg.name Email: ulrich@herberg.name
URI: http://www.herberg.name/ URI: http://www.herberg.name/
Robert G. Cole Robert G. Cole
US Army CERDEC US Army CERDEC
Space and Terrestrial Communications Space and Terrestrial Communications
6010 Frankford Road 6010 Frankford Road
Aberdeen Proving Ground, Maryland 21005 Aberdeen Proving Ground, Maryland 21005
United States United States of America
Phone: +1 443 395-8744 Phone: +1 443 395-8744
EMail: robert.g.cole@us.army.mil Email: rgcole01@comcast.net
URI: http://www.cs.jhu.edu/~rgcole/ URI: http://www.cs.jhu.edu/~rgcole/
Ian D Chakeres Ian D Chakeres
Delvin Delvin
Ellicott City, Maryland 21042 Ellicott City, Maryland 21042
United States United States of America
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
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. 125 change blocks. 
288 lines changed or deleted 300 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/