draft-ietf-manet-nhdp-mib-15.txt   draft-ietf-manet-nhdp-mib-16.txt 
Internet Engineering Task Force U. Herberg Internet Engineering Task Force U. Herberg
Internet-Draft LIX, Ecole Polytechnique Internet-Draft LIX, Ecole Polytechnique
Intended status: Standards Track R. Cole Intended status: Standards Track R. Cole
Expires: January 15, 2013 US Army CERDEC Expires: March 1, 2013 US Army CERDEC
I. Chakeres I. Chakeres
CenGen CenGen
July 14, 2012 August 28, 2012
Definition of Managed Objects for the Neighborhood Discovery Protocol Definition of Managed Objects for the Neighborhood Discovery Protocol
draft-ietf-manet-nhdp-mib-15 draft-ietf-manet-nhdp-mib-16
Abstract Abstract
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 Neighborhood Discovery Protocol (NHDP) process on a parameters of the Neighborhood Discovery Protocol (NHDP) process on a
router. The MIB module defined in this document, denoted NHDP-MIB, router. The MIB module defined in this document, denoted NHDP-MIB,
also reports state, performance information and notifications about also reports state, performance information and notifications about
NHDP. This additional state and performance information is useful to NHDP. This additional state and performance information is useful to
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 15, 2013. This Internet-Draft will expire on March 1, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 19 skipping to change at page 2, line 19
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
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 4 5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 4
5.1.1. Introduction . . . . . . . . . . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . 6 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 6
5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 6 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 6
5.4. The Performance Group . . . . . . . . . . . . . . . . . . 7 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 7
5.5. Tables and Indexing . . . . . . . . . . . . . . . . . . . 7 5.5. Tables and Indexing . . . . . . . . . . . . . . . . . . . 7
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9
6.2. Relationship to Routing Protocol MIB Modules Relying 6.2. Relationship to Routing Protocol MIB Modules Relying
on the NHDP-MIB Module . . . . . . . . . . . . . . . . . . 9 on the NHDP-MIB Module . . . . . . . . . . . . . . . . . . 9
6.3. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10 6.3. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 61 8. Security Considerations . . . . . . . . . . . . . . . . . . . 61
9. Applicability Statement . . . . . . . . . . . . . . . . . . . 63 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 63
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 64 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 64
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65
12.1. Normative References . . . . . . . . . . . . . . . . . . . 64 12.1. Normative References . . . . . . . . . . . . . . . . . . . 65
12.2. Informative References . . . . . . . . . . . . . . . . . . 65 12.2. Informative References . . . . . . . . . . . . . . . . . . 65
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 67
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 Neighborhood Discovery Protocol (NHDP) [RFC6130] parameters of the Neighborhood Discovery Protocol (NHDP) [RFC6130]
process on a router. The MIB module defined in this document, process on a router. The MIB module defined in this document,
denoted NHDP-MIB, also reports state, performance information and denoted NHDP-MIB, also reports state, performance information and
notifications about NHDP. This additional state and performance notifications about NHDP. This additional state and performance
skipping to change at page 4, line 17 skipping to change at page 4, line 17
interface defined by this MIB module. interface defined by this MIB module.
o State Objects - automatically generated values which define the o State Objects - automatically generated values which 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 which help an o Performance Objects - automatically generated values which help an
administrator or automated tool to assess the performance of the administrator or automated tool to assess the performance of the
NHDP instance on the router and the overall discovery performance NHDP instance on the router and the overall discovery performance
within the MANET. within the MANET.
4.2. Notation
The same notations as defined in [RFC6130] are used throughout this
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:
o nhdpNotifications - objects defining NHDP-MIB notifications. o nhdpNotifications - objects defining NHDP-MIB notifications.
o nhdpObjects - defining objects within this MIB module. The o nhdpObjects - defining objects within this MIB module. The
objects are arranged into the following groups: objects are arranged into the following groups:
skipping to change at page 5, line 33 skipping to change at page 5, line 41
The majority of critical events occur when NHDP is first enabled on a The majority of critical events occur when NHDP is first enabled on a
router, at which time the symmetric neighbors and two-hop neighbors router, at which time the symmetric neighbors and two-hop neighbors
of the router are discovered. During this initial period, a of the router are discovered. During this initial period, a
potential flood of notifications is unnecessary since the events are potential flood of notifications is unnecessary since the events are
expected. To avoid unnecessary notifications, a router SHOULD NOT expected. To avoid unnecessary notifications, a router SHOULD NOT
originate expected notifications until a certain time interval has originate expected notifications until a certain time interval has
elapsed, which is to be predefined by the network manager. It is elapsed, which is to be predefined by the network manager. It is
RECOMMENDED that this time interval is at least 3 x RECOMMENDED that this time interval is at least 3 x
'nhdpHelloInterval', so that symmetric neighbors are discovered. The 'nhdpHelloInterval', so that symmetric neighbors are discovered. The
suppression window for notifications is started when the suppression window for notifications is started when the
'nhdpIfStatus' transitions from its default value of 'false' to 'nhdpIfStatus' transitions from its default value of 'false(2)' to
'true' '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 amount of transmitted notifications per time is [RFC4750] (i.e. the amount of transmitted notifications per time is
bounded). bounded).
Appropriate values for the window time and upper bound are to be Appropriate values for the window time and upper bound are to be
selected by the network manager and depend on the deployment of the selected by the network manager and depend on the deployment of the
MANET. If NHDP is deployed on a lossy, wireless medium, sending too MANET. If NHDP is deployed on a lossy, wireless medium, sending too
skipping to change at page 7, line 49 skipping to change at page 8, line 11
o interfaces on other routers which are 1-hop removed from the local o interfaces on other routers which are 1-hop removed from the local
router, and router, and
o other routers which are 2-hop removed from the local router. o other routers which are 2-hop 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 - which is the IfIndex of the local router on which o nhdpIfIndex - which is the IfIndex of the local router on which
NHDP is enabled. NHDP is 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.
o nhdpDiscRouterIndex - a locally managed index representing an ID o nhdpDiscRouterIndex - a locally managed index representing an ID
of a known neighboring router. of a known neighboring router.
These tables and their indexing are: These tables and their indexing are:
o nhdpInterfaceTable - describes the configuration of the interfaces o nhdpInterfaceTable - describes the configuration of the interfaces
skipping to change at page 8, line 34 skipping to change at page 8, line 42
o nhdpInterfaceStateTable - records state information related to o nhdpInterfaceStateTable - records state information related to
specific interfaces of this router. This table has 'INDEX { specific interfaces of this router. This table has 'INDEX {
nhdpIfIndex }'. nhdpIfIndex }'.
o nhdpDiscIfSetTable - include the nhdpDiscRouterIndex of the o nhdpDiscIfSetTable - include the nhdpDiscRouterIndex of the
discovered router, the nhdpDiscIfIndex of the discovered interface discovered router, the nhdpDiscIfIndex of the discovered interface
and the current set of addresses associated with this neighbor and the current set of addresses associated with this neighbor
interface. This table has 'INDEX { nhdpDiscIfSetIndex }'. interface. This table has 'INDEX { nhdpDiscIfSetIndex }'.
o nhdpIibLinkSetTable - foreach local interface, this table records o nhdpIibLinkSetTable - for-each local interface, this table records
all links belonging to other routers which are, or recently were, all links belonging to other routers which are, or recently were,
1-hop neighbors to this router. This table has 'INDEX { 1-hop neighbors to this router. This table has 'INDEX {
nhdpIfIndex, nhdpDiscIfIndex }'. nhdpIfIndex, nhdpDiscIfIndex }'.
o nhdpIib2HopSetTable - foreach local interface, this table records o nhdpIib2HopSetTable - for-each local interface, this table records
network addresses (one at a time) of symmetric 2-hop neighbors, network addresses (one at a time) of symmetric 2-hop neighbors,
and the symmetric links to symmetric 1-hop neighbors of this and the symmetric links to symmetric 1-hop neighbors of this
router through which these symmetric 2-hop neighbors can be router through which these symmetric 2-hop neighbors can be
reached. This table has 'INDEX { nhdpIfIndex, nhdpDiscIfIndex, reached. This table has 'INDEX { nhdpIfIndex, nhdpDiscIfIndex,
nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddress }'. nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddress }'.
o nhdpNibNeighborSetTable - records all network addresses of each o nhdpNibNeighborSetTable - records all network addresses of each
1-hop neighbor to this router. This table has 'INDEX { 1-hop neighbor to this router. This table has 'INDEX {
nhdpDiscRouterIndex }'. nhdpDiscRouterIndex }'.
o nhdpNibLostNeighborSetTable - records network addresses of other o nhdpNibLostNeighborSetTable - records network addresses of other
routers which recently were symmetric 1-hop neighbors to this routers which recently were symmetric 1-hop neighbors to this
router, but which are now advertised as lost. This table has router, but which are now advertised as lost. This table has
'INDEX { nhdpDiscRouterIndex }'. 'INDEX { nhdpDiscRouterIndex }'.
o nhdpInterfacePerfTable - records performance objects that are o nhdpInterfacePerfTable - records performance objects that are
measured foreach local NHDP interface on this router. This table measured for-each local NHDP interface on this router. This table
has 'INDEX { nhdpIfIndex }'. has 'INDEX { nhdpIfIndex }'.
o nhdpDiscIfSetPerfTable - records performance objects that are o nhdpDiscIfSetPerfTable - records performance objects that are
measured foreach discovered interface of a neighbor of this measured for-each discovered interface of a neighbor of this
router. This table has 'INDEX { nhdpDiscIfIndex }'. router. This table has 'INDEX { nhdpDiscIfIndex }'.
o nhdpDiscNeighborSetPerfTable - records performance objects that o nhdpDiscNeighborSetPerfTable - records performance objects that
are measured for discovered neighbors of this router. This table are measured for discovered neighbors of this router. This table
has 'INDEX { nhdpDiscRouterIndex }'. has 'INDEX { nhdpDiscRouterIndex }'.
o nhdpIib2HopSetPerfTable - records performance objects that are o nhdpIib2HopSetPerfTable - records performance objects that are
measured for discovered 2-hop neighbors of this router. This measured for discovered 2-hop neighbors of this router. This
table has 'INDEX { nhdpDiscRouterIndex }'. table has 'INDEX { nhdpDiscRouterIndex }'.
skipping to change at page 11, line 6 skipping to change at page 11, line 13
FROM INET-ADDRESS-MIB -- RFC 4001 FROM INET-ADDRESS-MIB -- RFC 4001
InterfaceIndex InterfaceIndex
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
Float32TC Float32TC
FROM FLOAT-TC-MIB -- RFC 6340 FROM FLOAT-TC-MIB -- RFC 6340
; ;
nhdpMIB MODULE-IDENTITY nhdpMIB MODULE-IDENTITY
LAST-UPDATED "201207141000Z" -- July 14, 2012 LAST-UPDATED "201208281000Z" -- August 28, 2012
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG Chairs: sratliff@cisco.com WG Chairs: sratliff@cisco.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Ulrich Herberg Editors: Ulrich Herberg
Ecole Polytechnique Ecole Polytechnique
LIX LIX
skipping to change at page 11, line 51 skipping to change at page 12, line 10
DESCRIPTION DESCRIPTION
"This NHDP-MIB module is applicable to routers "This NHDP-MIB module is applicable to routers
implementing the Neighborhood Discovery Protocol implementing the Neighborhood Discovery Protocol
defined in RFC 6130. defined in RFC 6130.
Copyright (C) The IETF Trust (2012). This version Copyright (C) The IETF Trust (2012). This version
of this MIB module is part of RFC xxxx; see the RFC of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices." itself for full legal notices."
-- revision -- revision
REVISION "201207141000Z" -- July 14, 2012 REVISION "201208281000Z" -- August 28, 2012
DESCRIPTION DESCRIPTION
"The first version of this MIB module, "The first version of this MIB module,
published as RFC xxxx. published as RFC xxxx.
" "
-- RFC-Editor assigns xxxx -- RFC-Editor assigns xxxx
::= { mib-2 xxxx } -- to be assigned by IANA ::= { mib-2 xxxx } -- to be assigned by IANA
-- --
-- Top-Level Components of this MIB Module -- Top-Level Components of this MIB Module
-- --
skipping to change at page 15, line 7 skipping to change at page 15, line 13
-- which determine the overall performance and operation of the -- which determine the overall performance and operation of the
-- discovery protocol. -- discovery protocol.
nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 } nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 }
nhdpInterfaceTable OBJECT-TYPE nhdpInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpInterfaceEntry SYNTAX SEQUENCE OF NhdpInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpInterfaceTable describes the "The nhdpInterfaceTable describes the
configuration of the interfaces of this router configuration of the interfaces of this router
which are intended to use MANET control protocols. which are intended to use MANET control protocols.
The ifIndex is from the interfaces group As such, this table 'sparse augments' the ifTable
defined in the Interfaces Group MIB module. Only specifically when NHDP is to be configured to
for interfaces listed as ifType of 'manet' operate over this interface. The interface is
within the Interfaces Group MIB module, there is identified by the ifIndex from the interfaces
a corresponding entry to be contained within group defined in the Interfaces Group MIB module.
the nhdpInterfaceTable.
If the corresponding entry with ifIndex value A conceptual row in this table exists if and only
is deleted from the Interface Table, then the entry if either a manager has explicitly created the row
in this table is automatically deleted and or there is an interface on the managed device
NHDP is disabled on this interface, that supports and runs NHDP.
and all configuration and state information
related to this interface is to be removed The manager can create a row by setting
from memory." rowStatus to 'createAndGo' or 'createAndWait'.
Row objects having associated DEFVAL clauses are
automatically defined by the agent with these
values during row creation, unless the manager
explicitly defines these object values during the
row creation.
If the corresponding entry with ifIndex value
is deleted from the Interface Table, then the entry
in this table is automatically deleted and
NHDP is disabled on this interface,
and all configuration 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
"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 non-volatile 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."
skipping to change at page 16, line 33 skipping to change at page 17, line 4
nhdpInitialQuality nhdpInitialQuality
Float32TC, Float32TC,
nhdpInitialPending nhdpInitialPending
TruthValue, TruthValue,
nhdpHpMaxJitter nhdpHpMaxJitter
Unsigned32, Unsigned32,
nhdpHtMaxJitter nhdpHtMaxJitter
Unsigned32, Unsigned32,
nhdpIfRowStatus nhdpIfRowStatus
RowStatus RowStatus
} }
nhdpIfIndex OBJECT-TYPE nhdpIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex for this interface." "This value MUST correspond to an ifIndex referring
to a valid entry in The Interfaces Table."
REFERENCE
"RFC 2863 - The Interfaces Group MIB, McCloghrie, K.,
and F. Kastenholtz, June 2000"
::= { nhdpInterfaceEntry 1 } ::= { nhdpInterfaceEntry 1 }
nhdpIfName OBJECT-TYPE nhdpIfName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual name of the interface. The value of this "The textual name of the interface. The value of this
object SHOULD be the name of the interface as assigned by object SHOULD be the name of the interface as assigned by
the local device. This can be a textname, such as `le0' the local device. This can be a text-name, such as `le0'
or a simple port number, such as `1', or a simple port number, such as `1',
depending on the interface naming syntax of the device. depending on the interface naming syntax of the device.
If there is no local name, or this object is otherwise not If there is no local name, or this object is otherwise not
applicable, then this object contains a zero-length string." applicable, then this object contains a zero-length string."
::= { nhdpInterfaceEntry 2 } ::= { nhdpInterfaceEntry 2 }
nhdpIfStatus OBJECT-TYPE nhdpIfStatus OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpIfStatus indicates whether this interface is "nhdpIfStatus indicates whether this interface is
currently running NHDP. A value of true(1) indicates currently running NHDP. A value of true(1) indicates
that NHDP is running on this interface. that NHDP is running on this interface.
A value of false(2) indicates that NHDP is not A value of false(2) indicates that NHDP is not
currently running on this interface. This corresponds currently running on this interface. This corresponds
to the I_manet parameter in the Local Interface Set to the I_manet parameter in the Local Interface Set
of NHDP. of NHDP."
"
DEFVAL { false } DEFVAL { false }
::= { nhdpInterfaceEntry 3 } ::= { nhdpInterfaceEntry 3 }
-- --
-- Interface Parameters - Message Intervals -- Interface Parameters - Message Intervals
-- --
nhdpHelloInterval OBJECT-TYPE nhdpHelloInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpHelloInterval corresponds to "nhdpHelloInterval corresponds to
HELLO_INTERVAL of NHDP and represents the HELLO_INTERVAL of NHDP and represents the
maximum time between the transmission of two maximum time between the transmission of two
successive HELLO messages on this MANET interface. successive HELLO messages on this MANET interface.
skipping to change at page 20, line 7 skipping to change at page 20, line 31
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.
The following constraints apply to this The following constraints apply to this
parameter: parameter:
o nhdpHHoldTime >= nhdpRefreshInterval o nhdpHHoldTime >= nhdpRefreshInterval
o nhdpHHoldTime SHOULD be significantly greater o nhdpHHoldTime SHOULD be significantly greater
than nhdpRefreshInterval than nhdpRefreshInterval
o nhdpHHoldTime MUST be representable as o nhdpHHoldTime MUST be representable as
described in RFC5497" described in RFC 5497"
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 }
::= { nhdpInterfaceEntry 8 } ::= { nhdpInterfaceEntry 8 }
-- --
-- Interface Parameters - Link Quality -- Interface Parameters - Link Quality
skipping to change at page 21, line 43 skipping to change at page 22, line 20
Clausen, T., Dearlove, C. and J. Dean, April 2011" Clausen, T., Dearlove, C. and J. Dean, April 2011"
DEFVAL { "1.0" } DEFVAL { "1.0" }
::= { 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 true, then a INITIAL_PENDING of NHDP. If true(1), then a
newly identified link is considered pending, and newly identified link is considered pending, and
is not usable until the link quality has reached is not usable until the link quality has reached
or exceeded the nhdpHystAcceptQuality threshold. or exceeded the nhdpHystAcceptQuality threshold.
The following constraints apply to this The following constraints apply to this
parameter: parameter:
o If nhdpInitialQuality >= nhdpHystAcceptQuality, o If nhdpInitialQuality >= nhdpHystAcceptQuality,
then nhdpInitialPending := false. then nhdpInitialPending := false(2).
o If nhdpInitialQuality < nhdpHystRejectQuality, o If nhdpInitialQuality < nhdpHystRejectQuality,
then nhdpInitialPending := true." then nhdpInitialPending := true(1)."
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 { false } DEFVAL { false }
::= { nhdpInterfaceEntry 12 } ::= { nhdpInterfaceEntry 12 }
-- --
-- Interface Parameters - Jitter -- Interface Parameters - Jitter
skipping to change at page 25, line 28 skipping to change at page 26, line 5
-- --
-- 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
network addresses which are defined as local network addresses which are defined as local
MANET interface network addresses. The local MANET interface network addresses.
interface is defined by the nhdpIfIndex. As such, this table 'sparse augments' the
nhdpInterfaceTable when network addresses are
being defined for the interfaces existing within
the nhdpInterfaceTable. The local interface
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).
Further guidance on the addition or removal of A conceptual row in this table exists if and only
local addresses and network addresses is found if a manager has explicitly created the row. The
in Section 9 of RFC 6130." manager can create a row by setting rowStatus
to 'createAndGo' or 'createAndWait'.
Further guidance on the addition or removal of
local addresses and network addresses is found
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
skipping to change at page 28, line 8 skipping to change at page 28, 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"
::= { nhdpLibLocalIfSetEntry 4 } ::= { nhdpLibLocalIfSetEntry 4 }
nhdpLibLocalIfSetIpAddrPrefixLen OBJECT-TYPE nhdpLibLocalIfSetIpAddrPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of leading one bits that "Indicates the number of leading one bits that
form the mask. The mask is logically-ANDed form the mask. The mask is logically-AND-ed
to the nhdpLibLocalIfSetIpAddr to determine to the nhdpLibLocalIfSetIpAddr to determine
the address prefix. A row match is true the address prefix. A row match is true
if the address used as an index falls within if the address used as an index falls within
the network address range defined by the the network address range defined by the
address prefix." address prefix."
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"
::= { nhdpLibLocalIfSetEntry 5 } ::= { nhdpLibLocalIfSetEntry 5 }
skipping to change at page 31, line 18 skipping to change at page 32, line 5
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 3 } ::= { nhdpLibRemovedIfAddrSetEntry 3 }
nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of leading one bits that "Indicates the number of leading one bits that
form the mask. The mask is logically-ANDed form the mask. The mask is logically-AND-ed
to the nhdpLibRemovedIfAddrSetIpAddr to determine to the nhdpLibRemovedIfAddrSetIpAddr to determine
the address prefix. A row match is true the address prefix. A row match is true
if the address used as an index falls within if the address used as an index falls within
the network address range defined by the the network address range defined by the
address prefix." address prefix."
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 4 } ::= { nhdpLibRemovedIfAddrSetEntry 4 }
skipping to change at page 36, line 16 skipping to change at page 37, line 4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpDiscIfSetIpAddr is a "The nhdpDiscIfSetIpAddr is a
recently used address of a neighbor recently used address of a neighbor
of this router." of this router."
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"
::= { nhdpDiscIfSetEntry 5 } ::= { nhdpDiscIfSetEntry 5 }
nhdpDiscIfSetIpAddrPrefixLen OBJECT-TYPE nhdpDiscIfSetIpAddrPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of leading one bits that "Indicates the number of leading one bits that
form the mask. The mask is logically-ANDed form the mask. The mask is logically-AND-ed
to the nhdpDiscIfSetIpAddr to determine to the nhdpDiscIfSetIpAddr to determine
the address prefix. A row match is true the address prefix. A row match is true
if the address used as an index falls within if the address used as an index falls within
the network address range defined by the the network address range defined by the
address prefix." address prefix."
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"
::= { nhdpDiscIfSetEntry 6 } ::= { nhdpDiscIfSetEntry 6 }
skipping to change at page 41, line 48 skipping to change at page 42, line 36
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 2 } ::= { nhdpIib2HopSetEntry 2 }
nhdpIib2HopSetIpAddrPrefixLen OBJECT-TYPE nhdpIib2HopSetIpAddrPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of leading one bits that "Indicates the number of leading one bits that
form the mask. The mask is logically-ANDed form the mask. The mask is logically-AND-ed
to the nhdpIib2HopSetIpAddress to determine to the nhdpIib2HopSetIpAddress to determine
the address prefix. A row match is true the address prefix. A row match is true
if the address used as an index falls within if the address used as an index falls within
the network address range defined by the the network address range defined by the
address prefix." address prefix."
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 3 } ::= { nhdpIib2HopSetEntry 3 }
skipping to change at page 63, line 12 skipping to change at page 63, line 45
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. Applicability Statement 9. Applicability Statement
This document describes objects for configuring parameters of the This document describes objects for configuring parameters of the
Neighborhood Discovery Protocol [RFC6130] process on a router. This Neighborhood Discovery Protocol [RFC6130] process on a router. This
MIB module, denoted NHDP-MIB, also reports state, performance MIB module, denoted NHDP-MIB, also reports state, performance
information and notifications. This sections provides some examples information and notifications. This sections provides some examples
of how this MIB module can be used in MANET network deployments. A of how this MIB module can be used in MANET network deployments. A
complete discussion of MANET network management use cases and fuller discussion of MANET network management use cases and
operational challenges is out of scope of this document, but will be challenges will be provided elsewhere.
integrated into a future document.
NHDP is designed to allow routers to automatically discover and track NHDP is designed to allow routers to automatically discover and track
routers one hop remote (denoted "neighbors"), and routers two hops routers one hop remote (denoted "neighbors"), and routers two hops
remote (denoted "two-hop neighbors). This information is used by remote (denoted "two-hop neighbors). This information is used by
other MANET protocols in operation on the router to perform routing, other MANET protocols in operation on the router to perform routing,
multicast forwarding and other functions with ad-hoc and mobile multicast forwarding and other functions with ad-hoc and mobile
networks. In the following, three scenarios are listed where this networks. In the following, three scenarios are listed where this
MIB module is useful: MIB module is useful, i.e.,
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 Operation 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
 End of changes. 39 change blocks. 
62 lines changed or deleted 92 lines changed or added

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