draft-ietf-manet-nhdp-mib-17.txt   draft-ietf-manet-nhdp-mib-18.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: March 1, 2013 US Army CERDEC Expires: March 13, 2013 US Army CERDEC
I. Chakeres I. Chakeres
CenGen CenGen
August 28, 2012 September 9, 2012
Definition of Managed Objects for the Neighborhood Discovery Protocol Definition of Managed Objects for the Neighborhood Discovery Protocol
draft-ietf-manet-nhdp-mib-17 draft-ietf-manet-nhdp-mib-18
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 March 1, 2013. This Internet-Draft will expire on March 13, 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 41 skipping to change at page 2, line 41
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 . . . . . . . . . . . . . . . . . . . . . . . . . . 65 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65
12.1. Normative References . . . . . . . . . . . . . . . . . . . 65 12.1. Normative References . . . . . . . . . . . . . . . . . . . 65
12.2. Informative References . . . . . . . . . . . . . . . . . . 66 12.2. Informative References . . . . . . . . . . . . . . . . . . 65
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 67 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
skipping to change at page 11, line 13 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 "201208281000Z" -- August 28, 2012 LAST-UPDATED "201210091000Z" -- September 09, 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 12, line 10 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 "201208281000Z" -- August 28, 2012 REVISION "201210091000Z" -- September 09, 2012
DESCRIPTION DESCRIPTION
"The first version of this MIB module, "Initial version of this MIB module,
published as RFC xxxx. published as RFC XXXX.
" "
-- RFC-Editor assigns xxxx -- NOTE: 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
-- --
nhdpNotifications OBJECT IDENTIFIER ::= { nhdpMIB 0 } nhdpNotifications OBJECT IDENTIFIER ::= { nhdpMIB 0 }
nhdpObjects OBJECT IDENTIFIER ::= { nhdpMIB 1 } nhdpObjects OBJECT IDENTIFIER ::= { nhdpMIB 1 }
nhdpConformance OBJECT IDENTIFIER ::= { nhdpMIB 2 } nhdpConformance OBJECT IDENTIFIER ::= { nhdpMIB 2 }
-- --
-- Textual Conventions -- Textual Conventions
skipping to change at page 18, line 15 skipping to change at page 18, line 15
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.
Guidance for setting this object may be found The following constraint applies to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that:
o nhdpHelloInterval >= nhdpHelloMinInterval" o nhdpHelloInterval >= nhdpHelloMinInterval"
REFERENCE REFERENCE
"Section 5 on Protocol Parameters and "Section 5 on Protocol Parameters and
Constraints of RFC 6130 - Mobile Ad Hoc Constraints of RFC 6130 - Mobile Ad Hoc
Network (MANET) Neighborhood Discovery Network (MANET) Neighborhood Discovery
Protocol (NHDP), Clausen, T., Dearlove, Protocol (NHDP), Clausen, T., Dearlove,
C. and J. Dean, April 2011" C. and J. Dean, April 2011"
DEFVAL { 2000 } DEFVAL { 2000 }
::= { nhdpInterfaceEntry 4 } ::= { nhdpInterfaceEntry 4 }
skipping to change at page 18, line 40 skipping to change at page 18, line 39
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpHelloMinInterval corresponds to "nhdpHelloMinInterval corresponds to
HELLO_MIN_INTERVAL of NHDP and represents HELLO_MIN_INTERVAL of NHDP and represents
the minimum interval between transmission the minimum interval between transmission
of two successive HELLO messages on this of two successive HELLO messages on this
MANET interface. MANET interface.
Guidance for setting this object may be found The following constraint applies to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that:
o nhdpHelloInterval >= nhdpHelloMinInterval" o nhdpHelloInterval >= nhdpHelloMinInterval"
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 { 500 } DEFVAL { 500 }
::= { nhdpInterfaceEntry 5 } ::= { nhdpInterfaceEntry 5 }
nhdpRefreshInterval OBJECT-TYPE nhdpRefreshInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
skipping to change at page 19, line 17 skipping to change at page 19, line 17
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpRefreshInterval corresponds to "nhdpRefreshInterval corresponds to
REFRESH_INTERVAL of NHDP and represents the REFRESH_INTERVAL of NHDP and represents the
maximum interval between advertisements, in maximum interval between advertisements, in
a HELLO message on this MANET interface, of a HELLO message on this MANET interface, of
each 1-hop neighbor network address and its each 1-hop neighbor network address and its
status. status.
Guidance for setting this object may be found The following constraint applies to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that:
o nhdpRefreshInterval >= nhdpHelloInterval" o nhdpRefreshInterval >= nhdpHelloInterval"
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 { 2000 } DEFVAL { 2000 }
::= { nhdpInterfaceEntry 6 } ::= { nhdpInterfaceEntry 6 }
-- --
skipping to change at page 19, line 47 skipping to change at page 19, line 46
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpLHoldTime corresponds to "nhdpLHoldTime corresponds to
L_HOLD_TIME of NHDP and represents the period L_HOLD_TIME of NHDP and represents the period
of advertisement, on this MANET interface, of of advertisement, on this MANET interface, of
former 1-hop neighbor network addresses as lost former 1-hop neighbor network addresses as lost
in HELLO messages, allowing recipients of these in HELLO messages, allowing recipients of these
HELLO messages to accelerate removal of this HELLO messages to accelerate removal of this
information from their Link Sets. information from their Link Sets.
Guidance for setting this object may be found The following constraint applies to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that it should be assigned a o nhdpLHoldTime SHOULD be significantly greater
value significantly greater than the refresh than nhdpRefreshInterval"
interval held by nhdpRefreshInterval."
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 7 } ::= { nhdpInterfaceEntry 7 }
nhdpHHoldTime OBJECT-TYPE nhdpHHoldTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
skipping to change at page 20, line 28 skipping to change at page 20, line 25
DESCRIPTION DESCRIPTION
"nhdpHHoldTime corresponds to "nhdpHHoldTime corresponds to
H_HOLD_TIME of NHDP and is used as the Value H_HOLD_TIME of NHDP and is used as the Value
in the VALIDITY_TIME Message TLV included in all in the VALIDITY_TIME Message TLV included in all
HELLO messages on this MANET interface. It is then HELLO messages on this MANET interface. It is then
used by each router receiving such a HELLO message used by each router receiving such a HELLO message
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 The following constraints MUST apply to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that it should be assigned a o nhdpHHoldTime >= nhdpRefreshInterval
value significantly greather than the refresh interval o nhdpHHoldTime SHOULD be significantly greater
held by nhdpRefreshInterval and must be representable than nhdpRefreshInterval
as described in RFC 5497." o nhdpHHoldTime MUST be representable as
described in RFC5497"
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 7 skipping to change at page 21, line 6
nhdpHystAcceptQuality OBJECT-TYPE nhdpHystAcceptQuality OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpHystAcceptQuality corresponds to "nhdpHystAcceptQuality corresponds to
HYST_ACCEPT of NHDP and represents the link HYST_ACCEPT of NHDP and represents the link
quality threshold at or above which a link becomes quality threshold at or above which a link becomes
usable, if it was not already so. usable, if it was not already so.
Guidance for setting this object may be found The following constraint applies to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that:
o 0 <= nhdpHystRejectQuality o 0 <= nhdpHystRejectQuality
<= nhdpHystAcceptQuality <= 1.0" <= nhdpHystAcceptQuality <= 1.0"
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" } DEFVAL { "1.0" }
::= { nhdpInterfaceEntry 9 } ::= { nhdpInterfaceEntry 9 }
skipping to change at page 21, line 31 skipping to change at page 21, line 29
SYNTAX Float32TC SYNTAX Float32TC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpHystRejectQuality corresponds to "nhdpHystRejectQuality corresponds to
HYST_REJECT of NHDP and represents the HYST_REJECT of NHDP and represents the
link quality threshold below which a link quality threshold below which a
link becomes unusable, if it was not link becomes unusable, if it was not
already so. already so.
Guidance for setting this object may be found The following constraint applies to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that:
o 0 <= nhdpHystRejectQuality o 0 <= nhdpHystRejectQuality
<= nhdpHystAcceptQuality <= 1.0" <= nhdpHystAcceptQuality <= 1.0"
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 { "0.0" } DEFVAL { "0.0" }
::= { nhdpInterfaceEntry 10 } ::= { nhdpInterfaceEntry 10 }
nhdpInitialQuality OBJECT-TYPE nhdpInitialQuality OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpInitialQuality corresponds to "nhdpInitialQuality corresponds to
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 The following constraint applies to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that:
o 0 <= nhdpInitialQuality <= 1.0" o 0 <= nhdpInitialQuality <= 1.0"
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" } 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(1), 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.
Guidance for setting this object may be found The following constraints MUST apply to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that:
o If nhdpInitialQuality >= nhdpHystAcceptQuality, o If nhdpInitialQuality >= nhdpHystAcceptQuality,
then nhdpInitialPending := false(2). then nhdpInitialPending := false(2).
o If nhdpInitialQuality < nhdpHystRejectQuality, o If nhdpInitialQuality < nhdpHystRejectQuality,
then nhdpInitialPending := true(1)." 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 }
skipping to change at page 23, line 9 skipping to change at page 23, line 5
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpHpMaxJitter corresponds to "nhdpHpMaxJitter corresponds to
HP_MAXJITTER of NHDP and represents the HP_MAXJITTER of NHDP and represents the
value of MAXJITTER used in RFC5148 for value of MAXJITTER used in RFC5148 for
periodically generated HELLO messages on periodically generated HELLO messages on
this MANET interface. this MANET interface.
Guidance for setting this object may be found The following constraints MUST apply to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that:
o nhdpHpMaxJitter <= nhdpHelloInterval / 2 o nhdpHpMaxJitter <= nhdpHelloInterval / 2
o If nhdpHelloInterval > 0, then o If nhdpHelloInterval > 0, then
nhdpHpMaxJitter <= nhdpHelloMinInterval nhdpHpMaxJitter <= nhdpHelloMinInterval
" "
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 { 500 } DEFVAL { 500 }
skipping to change at page 23, line 36 skipping to change at page 23, line 31
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpHtMaxJitter corresponds to "nhdpHtMaxJitter corresponds to
HT_MAXJITTER of NHDP and represents the HT_MAXJITTER of NHDP and represents the
value of MAXJITTER used in RFC5148 for value of MAXJITTER used in RFC5148 for
externally triggered HELLO messages on this externally triggered HELLO messages on this
MANET interface. MANET interface.
Guidance for setting this object may be found The following constraints MUST apply to this
in Section 5 of the NHDP specification (RFC 6130) parameter:
where it indicates that:
o nhdpHtMaxJitter <= nhdpHelloInterval / 2 o nhdpHtMaxJitter <= nhdpHelloInterval / 2
o If nhdpHelloInterval > 0, then o If nhdpHelloInterval > 0, then
nhdpHtMaxJitter <= nhdpHelloMinInterval" nhdpHtMaxJitter <= nhdpHelloMinInterval"
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 { 500 } DEFVAL { 500 }
::= { nhdpInterfaceEntry 14 } ::= { nhdpInterfaceEntry 14 }
skipping to change at page 64, line 39 skipping to change at page 64, line 36
o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for
larger vehicles, a hierarchical network management arrangement is larger vehicles, a hierarchical network management arrangement is
useful. Centralized network management is performed from a fixed useful. Centralized network management is performed from a fixed
NOC while local management is performed locally from within the NOC while local management is performed locally from within the
vehicles. Standards-based methods for configuration, monitoring vehicles. Standards-based methods for configuration, monitoring
and fault management are necessary for this deployment option. and fault management are necessary for this deployment option.
10. IANA Considerations 10. IANA Considerations
IANA is requested to assign a "manet" ifType from the IANA ifType- The MIB module in this document uses the following IANA-assigned
MIB. OBJECT IDENTIFIER value recorded in the SMI Numbers registry:
IANA is requested to assign a value for "xxxx" under the 'mib-2' Descriptor OBJECT IDENTIFIER value
subtree and to record the assignment in the SMI Numbers registry. ---------- -----------------------
When the assignment has been made, the RFC Editor is asked to replace NHDP-MIB { mib-2 XXXX }
"xxxx" (here and in the MIB module) with the assigned value and to IANA EDITOR NOTE: please assign XXXX
remove this note.
11. Acknowledgements 11. Acknowledgements
The authors wish to thank Benoit Claise, Thomas Clausen, Justin Dean, The authors wish to thank Benoit Claise, Thomas Clausen, Justin Dean,
Adrian Farrel, Joel Halpern, Al Morton, and Thomas Nadeau for their Adrian Farrel, Joel Halpern, Al Morton, and Thomas Nadeau for their
detailed reviews and insightful comments to this document. detailed reviews and insightful comments to 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.
 End of changes. 22 change blocks. 
57 lines changed or deleted 47 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/