draft-ietf-manet-rfc6779bis-03.txt   draft-ietf-manet-rfc6779bis-04.txt 
Network Working Group U. Herberg Network Working Group U. Herberg
Internet-Draft Internet-Draft
Obsoletes: 6779 (if approved) R. Cole Obsoletes: 6779 (if approved) R. Cole
Intended status: Standards Track US Army CERDEC Intended status: Standards Track US Army CERDEC
Expires: September 4, 2015 I. Chakeres Expires: August 23, 2016 I. Chakeres
Delvin Delvin
T. Clausen T. Clausen
LIX, Ecole Polytechnique LIX, Ecole Polytechnique
March 3, 2015 February 20, 2016
Definition of Managed Objects for the Neighborhood Discovery Protocol Definition of Managed Objects for the Neighborhood Discovery Protocol
draft-ietf-manet-rfc6779bis-03 draft-ietf-manet-rfc6779bis-04
Abstract Abstract
This document revises, extends, and replaces RFC 6779. It defines a This document revises, extends, and replaces RFC 6779. It defines a
portion of the Management Information Base (MIB) for use with network portion of the Management Information Base (MIB) for use with network
management protocols in the Internet community. In particular, it management protocols in the Internet community. In particular, it
describes objects for configuring parameters of the Neighborhood describes objects for configuring parameters of the Neighborhood
Discovery Protocol (NHDP) process on a router. The MIB module Discovery Protocol (NHDP) process on a router. The MIB module
defined in this document, denoted NHDP-MIB, also reports state, defined in this document, denoted NHDP-MIB, also reports state,
performance information, and notifications about NHDP. This performance information, and notifications about NHDP. This
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 September 4, 2015. This Internet-Draft will expire on August 23, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
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
skipping to change at page 2, line 39 skipping to change at page 2, line 39
5.2. The Configuration Group . . . . . . . . . . . . . . . . . 6 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 6
5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . . . . . . . 10 on the NHDP-MIB Module . . . . . . . . . . . . . . . . . . 10
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 . . . . . . . . . . . . . . . . . . . 64 8. Security Considerations . . . . . . . . . . . . . . . . . . . 65
9. Applicability Statement . . . . . . . . . . . . . . . . . . . 66 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 67
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 68
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 67 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 68
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 68 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 68
12.1. Normative References . . . . . . . . . . . . . . . . . . . 68 12.1. Normative References . . . . . . . . . . . . . . . . . . . 68
12.2. Informative References . . . . . . . . . . . . . . . . . . 69 12.2. Informative References . . . . . . . . . . . . . . . . . . 69
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 Mobile Ad Hoc Network (MANET) Neighborhood
process on a router. The MIB module defined in this document, Discovery Protocol (NHDP) [RFC6130] process on a router. The MIB
denoted NHDP-MIB, also reports state, performance information, and module defined in this document, denoted NHDP-MIB, also reports
notifications about NHDP. This additional state and performance state, performance information, and notifications about NHDP. This
information is useful to troubleshoot problems and performance issues additional state and performance information is useful to
during neighbor discovery. troubleshoot problems and performance issues during neighbor
discovery.
1.1. Difference from RFC 6779 1.1. Difference from RFC 6779
This document obsoletes [RFC6779], replacing that document as the This document obsoletes [RFC6779], replacing that document as the
specification of the MIB module for [RFC6130]. specification of the MIB module for [RFC6130].
Specifically, the MIB module for [RFC6130], specified in this Specifically, the MIB module for [RFC6130], specified in this
document, captures the new information and states for each symmetric document, captures the new information and states for each symmetric
2-hop neighbor, recorded in the Neighbor Information Base of a router 2-hop neighbor, recorded in the Neighbor Information Base of a router
and to be reflected in the appropriate tables, introduced by and to be reflected in the appropriate tables, introduced by
[draft-ietf-manet-nhdp-optimization]. [RFC7466].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 10, line 39 skipping to change at page 10, line 39
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB
[RFC2863], INET-ADDRESS-MIB [RFC4001], and FLOAT-TC-MIB [RFC6340]. [RFC2863], INET-ADDRESS-MIB [RFC4001], and FLOAT-TC-MIB [RFC6340].
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)
-- Neighborhood Discovery Protocol (NHDP),
-- Clausen, T., Dearlove, C., and J. Dean, January 2011. -- Clausen, T., Dearlove, C., and J. Dean, January 2011.
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Counter64, Integer32, Unsigned32, mib-2, Counter32, Counter64, Integer32, Unsigned32, mib-2,
TimeTicks TimeTicks
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, TruthValue, TimeStamp, TEXTUAL-CONVENTION, TruthValue, TimeStamp,
skipping to change at page 11, line 23 skipping to change at page 11, line 24
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 "201503031100Z" -- 3 March 2015 LAST-UPDATED "201602201100Z" -- 20 February 2016
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG web page: https://datatracker.ietf.org/wg/manet WG web page: https://datatracker.ietf.org/wg/manet
Editors: Ulrich Herberg Editors: Ulrich Herberg
USA USA
ulrich@herberg.name ulrich@herberg.name
http://www.herberg.name/ http://www.herberg.name/
skipping to change at page 12, line 14 skipping to change at page 12, line 16
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 Neighborhood Discovery Protocol implementing the Mobile Ad Hoc Network (MANET)
Neighborhood Discovery Protocol (NHDP)
defined in RFC 6130. defined in RFC 6130.
Copyright (c) 2014 IETF Trust and the persons Copyright (c) 2014 IETF Trust and the persons
identified as authors of the code. All rights reserved. identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this MIB module is part of RFC 6779; see This version of this MIB module is part of RFC 6779; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- revision -- revision
REVISION "201503031100Z" -- 3 March 2015 REVISION "201602201100Z" -- 20 Feburary 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
draft-ietf-manet-nhdp-optimization, RFC 7466, published as RFC xxxx."
published as RFC xxxx."
REVISION "201210221000Z" -- 22 October 2012 REVISION "201210221000Z" -- 22 October 2012
DESCRIPTION DESCRIPTION
"Initial version of this MIB module, "Initial version of this MIB module,
published as RFC 6779." published as RFC 6779."
::= { mib-2 213 } ::= { mib-2 213 }
-- --
-- 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 13, line 34 skipping to change at page 13, line 35
-- at this point in time. As more topology information -- at this point in time. As more topology information
-- is gathered by the local router, it may associate -- is gathered by the local router, it may associate
-- virtual interfaces or routers and collapse these -- virtual interfaces or routers and collapse these
-- indexes appropriately. -- indexes appropriately.
-- Multiple addresses can be associated with a -- Multiple addresses can be associated with a
-- given NeighborIfIndex. Each NeighborIfIndex is -- given NeighborIfIndex. Each NeighborIfIndex is
-- associated with a NeighborRouterIndex. Throughout -- associated with a NeighborRouterIndex. Throughout
-- the nhdpStateObjGroup, the -- the nhdpStateObjGroup, the
-- NeighborIfIndex and the NeighborRouterIndex are used -- NeighborIfIndex and the NeighborRouterIndex are used
-- to define the set of IpAddrs related to a virtual -- to define the set of IP Addresses related to a virtual
-- neighbor interface or virtual neighbor under discussion. -- neighbor interface or virtual neighbor under discussion.
NeighborIfIndex ::= TEXTUAL-CONVENTION NeighborIfIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
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
skipping to change at page 21, line 46 skipping to change at page 21, line 47
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 mechanisms for of the OCTET STRING type, the SMI's mechanism 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 9 } ::= { nhdpInterfaceEntry 9 }
nhdpHystRejectQuality OBJECT-TYPE nhdpHystRejectQuality OBJECT-TYPE
skipping to change at page 22, line 34 skipping to change at page 22, line 34
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 mechanisms for of the OCTET STRING type, the SMI's mechanism 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 17 skipping to change at page 23, line 18
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 mechanisms for of the OCTET STRING type, the SMI's mechanism 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 28, line 17 skipping to change at page 28, line 20
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 Configured Interface Address 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 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 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
skipping to change at page 31, line 48 skipping to change at page 32, line 4
nhdpLibRemovedIfAddrSetEntry OBJECT-TYPE nhdpLibRemovedIfAddrSetEntry OBJECT-TYPE
SYNTAX NhdpLibRemovedIfAddrSetEntry SYNTAX NhdpLibRemovedIfAddrSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
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 the Standard MIB II's router's Interface is found in RFC 4293 (ipAddressTable)"
IP address table (RFC 1213)."
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 { nhdpLibRemovedIfAddrSetIndex } INDEX { nhdpLibRemovedIfAddrSetIndex }
::= { nhdpLibRemovedIfAddrSetTable 1 } ::= { nhdpLibRemovedIfAddrSetTable 1 }
NhdpLibRemovedIfAddrSetEntry ::= NhdpLibRemovedIfAddrSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpLibRemovedIfAddrSetIndex nhdpLibRemovedIfAddrSetIndex
skipping to change at page 43, line 7 skipping to change at page 43, line 8
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
draft-ietf-manet-nhdp-optimization-04 - RFC 7466 -
An Optimization for the MANET Neighborhood Discovery An Optimization for the Mobile Ad Hoc Network (MANET)
Protocol (NHDP), Dearlove, C., and T. Clausen, Neighborhood Discovery Protocol (NHDP),
January 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,
nhdpIib2HopSetN2Lost
TruthValue,
nhdpIib2HopSetN2Time nhdpIib2HopSetN2Time
TimeStamp TimeStamp,
nhdpIib2HopSetN2Lost
TruthValue
} }
nhdpIib2HopSetIpAddressType OBJECT-TYPE nhdpIib2HopSetIpAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the nhdpIib2HopSetIpAddress "The type of the nhdpIib2HopSetIpAddress
in the InetAddress MIB module (RFC 4001). in the InetAddress MIB module (RFC 4001).
skipping to change at page 44, line 50 skipping to change at page 45, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpIib2HopSet1HopIfIndex is "nhdpIib2HopSet1HopIfIndex is
nhdpDiscIfIndex of the 1-hop nhdpDiscIfIndex of the 1-hop
neighbor that communicated the ipAddress neighbor that communicated the ipAddress
of the 2-hop neighbor in this row entry." of the 2-hop neighbor in this row entry."
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 4 }
nhdpIib2HopSetN2Lost OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and
is a boolean flag, describing if for a 2-Hop Tuple, the
corresponding Link Tuple currently is considered lost
due to link quality."
REFERENCE ::= { nhdpIib2HopSetEntry 4 }
"draft-ietf-manet-nhdp-optimization-04 -
An Optimization for the MANET Neighborhood Discovery
Protocol (NHDP), Dearlove, C., and T. Clausen,
January 2015"
::= {nhdpIib2HopSetEntry 5}
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 6 } ::= { nhdpIib2HopSetEntry 5 }
nhdpIib2HopSetN2Lost OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and
is a boolean flag, describing if for a 2-Hop Tuple, the
corresponding Link Tuple currently is considered lost
due to link quality."
REFERENCE
"RFC 7466 -
An Optimization for the Mobile Ad Hoc Network (MANET)
Neighborhood Discovery Protocol (NHDP),
Dearlove, C., and T. Clausen,
March 2015"
::= {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.
-- --
-- Neighbor Set -- Neighbor Set
skipping to change at page 54, line 34 skipping to change at page 54, line 40
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
the neighbor becomes 'nbrup'. A neighbor is a new nhdpNibNeighborSetEntry
said to become 'nbrup' if a new nhdpNibNeighborSetEntry has been created for a particular
is created for a particular nhdpNibNeighborSetRouterIndex. nhdpNibNeighborSetRouterIndex."
It becomes 'nbrdown' if the entry for that neighbor
has been 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"
::= { 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 57, line 4 skipping to change at page 57, line 6
C., and J. Dean, April 2011" C., and J. Dean, April 2011"
::= { nhdpIib2HopSetPerfEntry 2 } ::= { nhdpIib2HopSetPerfEntry 2 }
-- --
-- nhdpNotifications -- nhdpNotifications
-- --
nhdpNotificationsObjects OBJECT IDENTIFIER ::= { nhdpNotifications 0 } nhdpNotificationsObjects OBJECT IDENTIFIER ::= { nhdpNotifications 0 }
nhdpNotificationsControl OBJECT IDENTIFIER ::= { nhdpNotifications 1 } nhdpNotificationsControl OBJECT IDENTIFIER ::= { nhdpNotifications 1 }
nhdpNotificationsStates OBJECT IDENTIFIER ::= { nhdpNotifications 2 } nhdpNotificationsStates OBJECT IDENTIFIER ::= { nhdpNotifications 2 }
-- nhdpNotificationsObjects -- nhdpNotificationsObjects
nhdpNbrStateChange NOTIFICATION-TYPE nhdpNbrStateChange NOTIFICATION-TYPE
OBJECTS { nhdpIfName, -- The originator of OBJECTS { nhdpIfName, -- The originator of the notification.
-- the notification.
nhdpNbrState -- The new state nhdpNbrState -- The new state
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpNbrStateChange is a notification sent when "nhdpNbrStateChange is a notification sent when
more than nhdpNbrStateChangeThreshold neighbors change more than nhdpNbrStateChangeThreshold neighbors change
their status (i.e., 'down(0)', 'asymmetric(1)', or their status (i.e., 'down(0)', 'asymmetric(1)', or
'symmetric(2)') within a time window of 'symmetric(2)') within a time window of
nhdpNbrStateChangeWindow." nhdpNbrStateChangeWindow."
::= { nhdpNotificationsObjects 1 } ::= { nhdpNotificationsObjects 1 }
skipping to change at page 64, line 44 skipping to change at page 65, line 4
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Set of NHDP state objects implemented "Set of NHDP state objects implemented
in this module. in this module.
For version-independence, this compliance statement For version-independence, this compliance statement
is deprecated in favor of nhdpStateGroup2." is deprecated in favor of nhdpStateGroup2."
::= { nhdpMIBGroups 3 } ::= { nhdpMIBGroups 3 }
END END
8. Security Considerations 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 Neighborhood Discovery Protocol [RFC6130]. and notification of the Mobile Ad Hoc Network (MANET) Neighborhood
NHDP allows routers to acquire topological information up to two hops Discovery Protocol (NHDP) [RFC6130]. NHDP allows routers to acquire
away by virtue of exchanging HELLO messages. The information topological information up to two hops away by virtue of exchanging
acquired by NHDP may be used by routing protocols. The neighborhood HELLO messages. The information acquired by NHDP may be used by
information, exchanged between routers using NHDP, serves these routing protocols. The neighborhood information, exchanged between
routing protocols as a baseline for calculating paths to all routers using NHDP, serves these routing protocols as a baseline for
destinations in the MANET, relay set selection for network-wide calculating paths to all destinations in the MANET, relay set
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
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o nhdpIfStatus - This writable object turns on or off the NHDP o nhdpIfStatus - This writable object turns on or off the NHDP
skipping to change at page 66, line 46 skipping to change at page 67, line 8
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
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 Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)
MIB module, denoted NHDP-MIB, also reports state, performance [RFC6130] process on a router. This MIB module, denoted NHDP-MIB,
information, and notifications. This section provides some examples also reports state, performance information, and notifications. This
of how this MIB module can be used in MANET network deployments. A section provides some examples of how this MIB module can be used in
fuller discussion of MANET network management use cases and MANET network deployments. A fuller discussion of MANET network
challenges will be provided elsewhere. management use cases and challenges will be provided elsewhere.
NHDP is designed to allow routers to automatically discover and track NHDP is designed to allow routers to automatically discover and track
routers one hop remote (denoted "neighbors") and routers two hops routers one hop remote (denoted "neighbors") and routers two hops
remote (denoted "two-hop neighbors"). This information is used by remote (denoted "two-hop neighbors"). This information is used by
other MANET protocols in operation on the router to perform routing, other MANET protocols in operation on the router to perform routing,
multicast forwarding, and other functions with ad hoc and mobile multicast forwarding, and other functions with ad hoc and mobile
networks. In the following, three example scenarios are listed where networks. In the following, three example scenarios are listed where
this MIB module is useful: this MIB module is useful:
o For a Parking Lot Initial Configuration Situation - It is common o For a Parking Lot Initial Configuration Situation - It is common
skipping to change at page 68, line 13 skipping to change at page 68, line 28
and insightful comments regarding RFC6779 and this document. and insightful comments regarding RFC6779 and this document.
This MIB document uses the template authored by D. Harrington, which This MIB document uses the template authored by D. Harrington, which
is based on contributions from the MIB Doctors, especially Juergen is based on contributions from the MIB Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn. Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn.
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2119] Bradner, S., "Key words for use [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
in RFCs to Indicate Requirement Requirement Levels", BCP 14, RFC 2119, March 1997.
Levels", BCP 14, RFC 2119,
March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
D., Ed., and J. Schoenwaelder, Schoenwaelder, Ed., "Structure of Management Information
Ed., "Structure of Management Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
D., Ed., and J. Schoenwaelder, Schoenwaelder, Ed., "Textual Conventions for SMIv2",
Ed., "Textual Conventions for STD 58, RFC 2579, April 1999.
SMIv2", STD 58, RFC 2579,
April 1999.
[RFC2580] McCloghrie, K., Perkins, D., [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580,
"Conformance Statements for April 1999.
SMIv2", STD 58, RFC 2580,
April 1999.
[RFC2863] McCloghrie, K. and F. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Kastenholz, "The Interfaces MIB", RFC 2863, June 2000.
Group MIB", RFC 2863,
June 2000.
[RFC3418] Presuhn, R., "Management [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62,
Simple Network Management RFC 3418, December 2002.
Protocol (SNMP)", STD 62,
RFC 3418, December 2002.
[RFC4001] Daniele, M., Haberman, B., [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network
Schoenwaelder, "Textual Addresses", RFC 4001, February 2005.
Conventions for Internet
Network Addresses", RFC 4001,
February 2005.
[RFC6130] Clausen, T., Dearlove, C., and [RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc
J. Dean, "Mobile Ad Hoc Network Network (MANET) Neighborhood Discovery Protocol (NHDP)",
(MANET) Neighborhood Discovery RFC 6130, April 2011.
Protocol (NHDP)", RFC 6130,
April 2011.
[RFC6340] Presuhn, R., "Textual [RFC6340] Presuhn, R., "Textual Conventions for the Representation
Conventions for the of Floating-Point Numbers", RFC 6340, August 2011.
Representation of Floating-
Point Numbers", RFC 6340,
August 2011.
[draft-ietf-manet-nhdp-optimization] Dearlove, C. and T. Clausen, [RFC7466] Dearlove, C. and T. Clausen, "An Optimization for the
"An Optimization for the MANET Mobile Ad Hoc Network (MANET) Neighborhood Discovery
Neighborhood Discovery Protocol Protocol (NHDP)", RFC 7466, March 2015.
(NHDP)", work in progress draft
-ietf-manet-nhdp-optimization-
04, January 2015.
12.2. Informative References 12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
D., and B. Stewart, "Introduction and Applicability Statements for Internet-
"Introduction and Applicability Standard Management Framework", RFC 3410, December 2002.
Statements for Internet-
Standard Management Framework",
RFC 3410, December 2002.
[RFC3414] Blumenthal, U. and B. Wijnen, [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
"User-based Security Model Architecture for Describing Simple Network Management
(USM) for version 3 of the Protocol (SNMP) Management Frameworks", RFC 3411,
Simple Network Management December 2002.
Protocol (SNMPv3)", STD 62,
RFC 3414, December 2002.
[RFC3826] Blumenthal, U., Maino, F., and [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
K. McCloghrie, "The Advanced (USM) for version 3 of the Simple Network Management
Encryption Standard (AES) Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
Cipher Algorithm in the SNMP
User-based Security Model",
RFC 3826, June 2004.
[RFC4750] Joyal, D., Galecki, P., [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Giacalone, S., Coltun, R., and Advanced Encryption Standard (AES) Cipher Algorithm in the
F. Baker, "OSPF Version 2 SNMP User-based Security Model", RFC 3826, June 2004.
Management Information Base",
RFC 4750, December 2006.
[RFC5148] Clausen, T., Dearlove, C., and [RFC4293] Routhier, S., "Management Information Base for the
B. Adamson, "Jitter Internet Protocol (IP)", RFC 4293, April 2006.
Considerations in Mobile Ad Hoc
Networks (MANETs)", RFC 5148,
February 2008.
[RFC5591] Harrington, D. and W. Hardaker, [RFC4750] Joyal, D., Galecki, P., Giacalone, S., Coltun, R., and F.
"Transport Security Model for Baker, "OSPF Version 2 Management Information Base",
the Simple Network Management RFC 4750, December 2006.
Protocol (SNMP)", RFC 5591,
June 2009.
[RFC5592] Harrington, D., Salowey, J., [RFC5148] Clausen, T., Dearlove, C., and B. Adamson, "Jitter
and W. Hardaker, "Secure Shell Considerations in Mobile Ad Hoc Networks (MANETs)",
Transport Model for the Simple RFC 5148, February 2008.
Network Management Protocol
(SNMP)", RFC 5592, June 2009.
[RFC6353] Hardaker, W., "Transport Layer [RFC5497] Clausen, T. and C. Dearlove, "Representing Multi-Value
Security (TLS) Transport Model Time in Mobile Ad Hoc Networks (MANETs)", RFC 5497,
for the Simple Network March 2009.
Management Protocol (SNMP)",
RFC 6353, July 2011.
[RFC6779] Herberg, U., Cole, R., and I. [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
Chakeres, "Definition of for the Simple Network Management Protocol (SNMP)",
Managed Objects for the RFC 5591, June 2009.
Neighborhood Discovery
Protocol", RFC 6779, [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
October 2012. Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, June 2009.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)",
RFC 6353, July 2011.
[RFC6779] Herberg, U., Cole, R., and I. Chakeres, "Definition of
Managed Objects for the Neighborhood Discovery Protocol",
RFC 6779, October 2012.
Authors' Addresses Authors' Addresses
Ulrich Herberg Ulrich Herberg
United States United States
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
Phone: +1 443 395-8744 Phone: +1 443 395-8744
EMail: robert.g.cole@us.army.mil EMail: robert.g.cole@us.army.mil
URI: http://www.cs.jhu.edu/~rgcole/ URI: http://www.cs.jhu.edu/~rgcole/
 End of changes. 53 change blocks. 
175 lines changed or deleted 144 lines changed or added

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