Internet Engineering Task Force R. Cole, Ed.
Internet-Draft Johns Hopkins University
Intended status: Standards Track I. Chakeres, Ed.
Expires: November 13, 2008 Motorola
May 12, 2008
Definition of Managed Objects for the Neighborhood Discovery Protocol
draft-cole-manet-nhdp-mib-00
Status of This Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 13, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the
Neighborhood Discovery Protocol (NHDP) process on a router. The NHDP
MIB also reports state information, performance information and
notifications. This additional state and performance information is
useful to management stations troubleshooting neighbor discovery
Cole & Chakeres Expires November 13, 2008 [Page 1]
Internet-Draft The NHDP MIB May 2008
problems.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.2. Organization . . . . . . . . . . . . . . . . . . . . . . . 4
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4
5.2. The General Information Group . . . . . . . . . . . . . . 5
5.3. The Configuration Group . . . . . . . . . . . . . . . . . 5
5.3.1. Interface Parameters . . . . . . . . . . . . . . . . . 5
5.3.2. Node Parameters . . . . . . . . . . . . . . . . . . . 8
5.3.3. Parameter Change Constraints . . . . . . . . . . . . . 9
5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 9
5.5. The Performance Group . . . . . . . . . . . . . . . . . . 10
5.6. The Notifications . . . . . . . . . . . . . . . . . . . . 10
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 10
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 11
6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 11
6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 11
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 17
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
12.1. Normative References . . . . . . . . . . . . . . . . . . . 20
12.2. Informative References . . . . . . . . . . . . . . . . . . 20
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 20
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 21
Cole & Chakeres Expires November 13, 2008 [Page 2]
Internet-Draft The NHDP MIB May 2008
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the
Neighborhood Discovery Protocol (NHDP) [I-D:ietf-manet-nhdp] process
on a router. The NHDP MIB also reports state information,
performance information and notifications. This additional state and
performance information is useful to management stations
troubleshooting neighbor discovery problems.
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
4. Overview
The NHDP protocol allows routers in a Mobile Ad-Hoc network (MANET)
setting to discover and track one-hop and two-hop neighbor sets.
This information is useful for routers running various routing and
multicast flooding protocols developed within the IETF MANET Working
Group.
4.1. Terms
The following definitions apply throughout this document:
o Configuration Objects - switches, tables, objects which are
initialized to default settings or set through the management
interface defined by this MIB.
Cole & Chakeres Expires November 13, 2008 [Page 3]
Internet-Draft The NHDP MIB May 2008
o Tunable Configuration Objects - objects whose values affect timing
or attempt bounds on the NHDP protocol.
o State Objects - automatically generated values which define the
current operating state of the NHDP protocol process in the
router.
o Performance Objects - automatically generated values which help an
administrator or automated tool to assess the performance of the
NHDP protocol process on the router and the overall discovery
performance within the NHDP domain.
4.2. Organization
This document is organized as ...
5. Structure of the MIB Module
This section presents the structure of the NHDP MIB module. The MIB
is arranged into the following structure:
o nhdpNotifications - objects defining NHDP MIB notifications.
o nhdpObjects - defining objects within this MIB. The objects are
arranged into the following groups:
* General Information Group - defining objects of a general
nature, e.g., version numbers.
* Configuration Group - defining objects related to the
configuration of the NHDP instance on the device.
* State Group - defining objects which reflect the current state
of the NHDP running on the device.
* Performance Group - defining objects which are useful to a
management station when characterizing the performance of the
NHDP on the device and in the MANET.
o nhdpConformance - defining the minimal and maximal conformance
requirements for implementations of this MIB.
5.1. Textual Conventions
This section is TBD.
Cole & Chakeres Expires November 13, 2008 [Page 4]
Internet-Draft The NHDP MIB May 2008
5.2. The General Information Group
This section provides general information about the capabilities of
the device running the NHDP. This group is currently empty and will
be removed in future drafts if no objects are identified.
5.3. The Configuration Group
The device is configured with a set of controls. These will serve as
the object descriptions once they are discussed and refined. The
list of configuration controls for the NHDP-MIB (found in [ietf-
manet-nhdp]), are discussed in the following subsections.
5.3.1. Interface Parameters
The Interface Parameters include:
5.3.1.1. Message Intervals
o HELLO_INTERVAL - is the maximum time between the transmission of
two successive HELLO messages on this MANET interface. If using
periodic transmission of HELLO messages, these SHOULD be at a
separation of HELLO_INTERVAL, possibly modified by jitter as
specified in [XXX].
o HELLO_MIN_INTERVAL - is the minimum interval between transmission
of two successive HELLO messages, on this MANET interface. (This
minimum interval MAY be modified by jitter, as defined in [XXX].)
o REFRESH_INTERVAL - is the maximum interval between advertisements
in a HELLO message of each 1-hop neighbor address and its status.
In all intervals of length REFRESH_INTERVAL, a node MUST include
all 1-hop neighbor information which it is specified as sending in
at least one HELLO message on this MANET interface.
The following constraints apply to these interface parameters:
o HELLO_INTERVAL > 0
o HELLO_MIN_INTERVAL >= 0
o HELLO_INTERVAL >= HELLO_MIN_INTERVAL
o REFRESH_INTERVAL >= HELLO_INTERVAL
o If INTERVAL_TIME message TLVs as defined in [XXX] are included in
HELLO messages, then HELLO_INTERVAL MUST be representable as
described in [XXX].
Cole & Chakeres Expires November 13, 2008 [Page 5]
Internet-Draft The NHDP MIB May 2008
o If REFRESH_INTERVAL > HELLO_INTERVAL, then a node may distribute
its neighbor advertisements between HELLO messages in any manner,
subject to the constraints above.
o For a node to employ this protocol in a purely responsive manner
on a MANET interface, REFRESH_INTERVAL and HELLO_INTERVAL SHOULD
both be set to a value such that a responsive HELLO message is
always expected in a shorter period than this.
The following default values are recommended:
o HELLO_INTERVAL = 2 seconds
o HELLO_MIN_INTERVAL = HELLO_INTERVAL/4
o REFRESH_INTERVAL = HELLO_INTERVAL
5.3.1.2. Information Validity Times
Parameters related to the Information Validity Times include:
o L_HOLD_TIME - is the period of advertisement, on this MANET
interface, of former 1-hop neighbor addresses as lost in HELLO
messages, allowing recipients of these HELLO messages to
accelerate removal of information from their Link Sets.
L_HOLD_TIME can be set to zero if accelerated information removal
is not required.
o H_HOLD_TIME - is used as the value in the VALIDITY_TIME message
TLV included in all HELLO messages on this MANET interface.
The following constraints apply to these interface parameters:
o L_HOLD_TIME >= 0
o H_HOLD_TIME >= REFRESH_INTERVAL
o If HELLO messages can be lost then both SHOULD be significantly
greater than REFRESH_INTERVAL.
o H_HOLD_TIME MUST be representable as described in [XXX].
o H_HOLD_TIME = 3 x REFRESH_INTERVAL
o L_HOLD_TIME = H_HOLD_TIME
o N_HOLD_TIME = L_HOLD_TIME
Cole & Chakeres Expires November 13, 2008 [Page 6]
Internet-Draft The NHDP MIB May 2008
o I_HOLD_TIME = N_HOLD_TIME
5.3.1.3. Link Quality
Parameters related to the Link Quality include:
o HYST_ACCEPT - is the link quality threshold at or above which a
link becomes usable, if it was not already so.
o HYST_REJECT - is the link quality threshold below which a link
becomes unusable, if it was not already so.
o INITIAL_QUALITY - is the initial quality of a newly identified
link.
o INITIAL_PENDING - if true, then a newly identified link is
considered pending, and is not usable until the link quality has
reached or exceeded the HYST_ACCEPT threshold.
The following constraints apply to these interface parameters:
o 0 < = HYST_REJECT < = HYST_ACCEPT < = 1
o 0 < = INITIAL_QUALITY < = 1.
o If link quality is not updated, then INITIAL_QUALITY >=
HYST_ACCEPT.
o If INITIAL_QUALITY => HYST_ACCEPT, then INITIAL_PENDING == false.
o If INITIAL_QUALITY < HYST_REJECT, then INITIAL_PENDING == true.
Link quality is a mechanism whereby a node MAY take considerations
other than message exchange into account for determining when a link
is and is not a candidate for being considered as HEARD or SYMMETRIC.
Link quality is used only locally by a node, and nodes may fully
inter-operate whether they are using the same, different or no link
quality methods.
NHDP can be operated when the local node does not implement Link
Quality. In order for a node to not employ link quality, the node
MUST define:
o INITIAL_PENDING = false
o INITIAL_QUALITY >= HYST_REJECT (there is no reason not to define
INITIAL_QUALITY = 1).
Cole & Chakeres Expires November 13, 2008 [Page 7]
Internet-Draft The NHDP MIB May 2008
If link quality is changed, then parameter values will depend on the
link quality process. If link quality is not changed, then:
o HYST_ACCEPT = 1
o HYST_REJECT = 0
o INITIAL_QUALITY = 1
o INITIAL_PENDING = false
5.3.1.4. Jitter
If jitter, as defined in [XXX], is used then these parameters are as
follows:
o HP_MAXJITTER - represents the value of MAXJITTER used in [XXX] for
periodically generated HELLO messages on this MANET interface.
o HT_MAXJITTER - represents the value of MAXJITTER used in [XXX] for
externally triggered HELLO messages on this MANET interface.
For constraints on these interface parameters see [XXX].
The following default values are recommended:
o HP_MAXJITTER = HELLO_INTERVAL/4
o HT_MAXJITTER = HP_MAXJITTER
o C = 1/1024 second
5.3.2. Node Parameters
The following Node Parameters apply:
5.3.2.1. Information Validity Time
o N_HOLD_TIME - is used as the period during which former 1-hop
neighbor addresses are advertised as lost in HELLO messages,
allowing recipients of these HELLO messages to accelerate removal
of information from their 2-Hop Sets. N_HOLD_TIME can be set to
zero if accelerated information removal is not required.
o I_HOLD_TIME - is the period for which a recently used local
interface address is recorded.
The following constraints applies to these node parameters:
Cole & Chakeres Expires November 13, 2008 [Page 8]
Internet-Draft The NHDP MIB May 2008
o N_HOLD_TIME >= 0
o I_HOLD_TIME >= 0
5.3.3. Parameter Change Constraints
These parameters may be made dynamic:
o HELLO_INTERVAL
o REFRESH_INTERVAL
o HYST_ACCEPT and HYST_REJECT
o L_HOLD_TIME
o N_HOLD_TIME
o HP_MAXJITTER
o HT_MAXJITTER
5.4. The State Group
The State Subtree reports current state information, including
neighbor tables. These are separately discussed below.
(Note: these will serve as the object descriptions once they are
discussed and refined.)
The Local Information Base (LIB), contains the addresses of the
interfaces (MANET and non-MANET) of this node. The contents of this
Information Base are not changed by signaling. The LIB contains two
tables:
o The "Local Interface Set", which consists of Local Interface
Tuples, each of which records the addresses of an interface (MANET
or non- MANET) of the node.
o The "Removed Interface Address Set", which consists of Removed
Interface Address Tuples, each of which records a recently used
address of an interface (MANET or non-MANET) of the node. A
node's Removed Interface Address Set records addresses which were
recently local interface addresses. If a node's interface
addresses are immutable then this set is always empty and MAY be
omitted.
The Interface Information Based (IIB), recording information
Cole & Chakeres Expires November 13, 2008 [Page 9]
Internet-Draft The NHDP MIB May 2008
regarding links to this MANET interface and symmetric 2-hop neighbors
which can be reached through such links. The IIB contains two
tables:
o A "Link Set", which records information about current and recently
lost links between this interface and MANET interfaces of 1-hop
neighbors. The Link Set consists of Link Tuples, each of which
contains information about a single link. Recently lost links are
recorded so that they can be advertised in HELLO messages,
accelerating their removal from relevant 1-hop neighbors' Link
Sets. Link quality information, if used and available, is
recorded in Link Tuples and may indicate that links are treated as
lost.
o A "Two-Hop Set", which records the existence of bidirectional
links between symmetric 1-hop neighbors of this MANET interface
and other nodes (symmetric 2-hop neighbors). The 2-Hop Set
consists of 2-Hop Tuples, each of which records an interface
address of a symmetric 2-hop neighbor, and all interface addresses
of the corresponding symmetric 1-hop neighbor. The 2-Hop Set is
updated by the signaling of this protocol, but is not itself
reported in that signaling.
The Node Information Base (NIB), records information regarding
current and recently lost 1-hop neighbors of this node. The NIB
contains two tables:
o The "Neighbor Set", and
o The "Lost Neighbor Set".
5.5. The Performance Group
Reports values relevant to system performance. These will serve as
the object descriptions once they are discussed and refined.
5.6. The Notifications
The Notifications Subtree contains the list of notifications
supported within the NHDP MIB and their intended purpose or utility.
This group is currently empty, pending further discussion.
6. Relationship to Other MIB Modules
[TODO]: The text of this section specifies the relationship of the
MIB modules contained in this document to other standards,
particularly to standards containing other MIB modules. Definitions
imported from other MIB modules and other MIB modules that SHOULD be
Cole & Chakeres Expires November 13, 2008 [Page 10]
Internet-Draft The NHDP MIB May 2008
implemented in conjunction with the MIB module contained within this
document are identified in this section.
6.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The NHDP-MIB does not
duplicate those objects.
6.2. Relationship to the IF-MIB
[TODO] This section is included as an example; If the MIB module is
not an adjunct of the Interface MIB, then this section should be
removed.
6.3. MIB modules required for IMPORTS
[TODO]: Citations are not permitted within a MIB module, but any
module mentioned in an IMPORTS clause or document mentioned in a
REFERENCE clause is a Normative reference, and must be cited
someplace within the narrative sections. If there are imported items
in the MIB module, such as Textual Conventions, that are not already
cited, they can be cited in text here. Since relationships to other
MIB modules should be described in the narrative text, this section
is typically used to cite modules from which Textual Conventions are
imported.
The following NHDP MIB module IMPORTS objects from SNMPv2-SMI
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB
[RFC2863]
7. Definitions
NHDP-MIB DEFINITIONS ::= BEGIN
-- This MIB is currently in a very initial stage.
-- Not all proposed objects have been identified yet
-- in the current draft. The MIB have not been
-- formally checked by any MIB checkers yet.
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32,
Gauge32, Integer32, Unsigned32
FROM SNMPv2-SMI --[RFC2578]
TEXTUAL-CONVENTION, StorageType, TimeStamp,
Cole & Chakeres Expires November 13, 2008 [Page 11]
Internet-Draft The NHDP MIB May 2008
TruthValue, RowStatus
FROM SNMPv2-TC --[RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF --[STD58]
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB --[RFC3291]
InterfaceIndexOrZero
FROM IF-MIB --[RFC2863]
nhdpMIB MODULE-IDENTITY
LAST-UPDATED "200802151500Z" -- April 25, 2008
ORGANIZATION "IETF MANET working group"
CONTACT-INFO
"WG E-Mail: manet@ietf.org
WG Chairs: ian.chakeres@gmail.com
jmacker@nrl.navy.mil
Editors: Robert G. Cole
Johns Hopkins University
Applied Physics Lab and
Department of Computer Science
11000 Johns Hopkins Road
Room 02-257
Laurel, MD 22014
USA
+1 443 778-6951
robert.cole@jhuapl.edu
Ian D Chakeres
Motorola
Bagmane Tech Park
66/1, Plot 5, CV Raman Nagar
Bangalore, Karnataka 560093
India
ian.chakeres@gmail.com"
DESCRIPTION
"This NHDP MIB module is applicable to devices
implementing the Neighborhood Discovery Protocol
defined in [XXX].
Copyright (C) The IETF Trust (2008). This version
of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices."
Cole & Chakeres Expires November 13, 2008 [Page 12]
Internet-Draft The NHDP MIB May 2008
-- revision
REVISION "200804251500Z" -- April 25, 2008
DESCRIPTION
"The original version of this MIB module,
published as RFCXXXX."
-- RFC-Editor assigns XXXX
::= { manet XX } -- to be assigned by IANA
--
-- Top-Level Components of this MIB
--
nhdpNotifications OBJECT IDENTIFIER ::= { nhdpMIB 0 }
nhdpObjects OBJECT IDENTIFIER ::= { nhdpMIB 1 }
nhdpConformance OBJECT IDENTIFIER ::= { nhdpMIB 2 }
--
-- Textual Conventions
--
-- (are these necessary to or used in NHDP?)
InstanceID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An identifier for the instance of the NHDP
protocol running on the device. Multiple instances
of the NHDP protocol may run concurrently on the same
device."
SYNTAX InetAddress
RouterID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A NHDP Router Identifier.
Note that the Router ID, in NHDP, has the same format
as an IP address, but identifies the router independent
of its IP address."
SYNTAX InetAddress
--
-- nhdpObjects
--
-- General Objects Group - ...
-- Configuration Objects Group - ...
-- State Objects Group - ...
-- Performance Objects Group - ...
Cole & Chakeres Expires November 13, 2008 [Page 13]
Internet-Draft The NHDP MIB May 2008
--
-- nhdpGeneralObjGrp
--
-- Note: These objects apply globally to the router's
-- NHDP process.
nhdpGeneralObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 }
--(proposed object list here.)
--
-- nhdpConfigurationObjGrp
--
-- Contains the NHDP objects which configure specific options
-- which determine the overall performance and operation of the
-- discovery protocol.
nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 2 }
-- The proposed list of objects are:
-- Interface Parameters - Message Intervals
-- HELLO_INTERVAL (default: 2 seconds)
-- HELLO_MIN_INTERVAL (default: HELLO_INTERVAL)
-- REFRESH_INTERVAL (default: HELLO_INTERVAL)
-- Interface Parameters - Information Validity times
-- L_HOLD_TIME (default: TBD)
-- H_HOLD_TIME (default: TBD)
-- Interface Parameters - Link Quality
-- (is optional and settings define operation)
-- HYST_ACCEPT (default: TBD)
-- HYST_REJECT (default: TBD)
-- INITIAL_QUALITY (default: TBD)
-- INITIAL_PENDING (default: TBD)
-- Interface Parameters - Jitter
-- HP_MAXJITTER (default: HELLO_INTERVAL/4)
-- HT_MAXJITTER (default: HP_MAXJITTER)
Cole & Chakeres Expires November 13, 2008 [Page 14]
Internet-Draft The NHDP MIB May 2008
-- Node Parameters - Information Validity Time
-- N_HOLD_TIME (default: 2 seconds)
-- I_HOLD_TIME (default: HELLO_INTERVAL)
--
-- nhdpStateObjGrp
--
-- Contains information describing the current state of the NHDP
-- process.
nhdpStateObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 3 }
--(Proposed list of objects are:)
-- LIB (foreach node)
-- Local IF Set Table
-- Entry (foreach IF): (IfAddrList,
-- PrefixMask,
-- Manet_indication)
-- Removed Addr Set Table
-- Entry (foreach Addr): (IfAddrRemoved,
-- ExpirationTime)
-- IIB (foreach IF)
-- Link Set
-- Entry (foreach 1-H neighbor): (NeighborAddrList,
-- HeardTime,
-- SymTime,
-- Quality,
-- Pending,
-- Lost,
-- ExpireTime)
--
-- Two-Hop Set
-- Entry (foreach IF on a 2-H neighbor): (1NeighIfAddrList,
-- 2NeighIfAddr,
-- ExpireTime)
-- NIB (foreach node)
-- Neighbor Set
-- Entry (foreach 1-H Neighbor): (AllIfAddrListOfIhNeighbor,
Cole & Chakeres Expires November 13, 2008 [Page 15]
Internet-Draft The NHDP MIB May 2008
-- SymmetricIndicator)
-- Lost Neighbor Set
-- Entry ( foreach IF foreach 1-H Neighbor): (IfAddr,
-- ExpireTime)
--
-- nhdpPerformanceObjGrp
--
-- Contains objects which help to characterize the performance of
-- the NHDP process, typically counters.
nhdpPerformanceObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 4 }
--(insert proposed objects here.)
--
-- nhdpNotifications
--
--What are the valuable notification information for the
--NHDP-MIB?
--
-- nhdpConformance information
--
-- To be determined.
nhdpCompliances OBJECT IDENTIFIER ::= { nhdpConformance 1 }
nhdpGroups OBJECT IDENTIFIER ::= { nhdpConformance 2 }
-- Compliance Statements
nhdpGeneralCompliance MODULE-COMPLIANCE
STATUS current
Cole & Chakeres Expires November 13, 2008 [Page 16]
Internet-Draft The NHDP MIB May 2008
DESCRIPTION
"A general compliance which allows ...."
MODULE -- this module
MANDATORY-GROUPS { nhdpGeneralGroup }
::= { nhdpCompliances 1 }
--
-- NHDP MIB Group Compliance
--
--
-- Groups
--
END
8. Security Considerations
[TODO] Each specification that defines one or more MIB modules MUST
contain a section that discusses security considerations relevant to
those modules. This section MUST be patterned after the latest
approved template (available at
http://www.ops.ietf.org/mib-security.html). Remember that the
objective is not to blindly copy text from the template, but rather
to think and evaluate the risks/vulnerabilities and then state/
document the result of this evaluation.
[TODO] if you have any read-write and/or read-create objects, please
include the following boilerplate paragraph.
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
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
o [TODO] writable MIB objects that could be especially disruptive if
abused MUST be explicitly listed by name and the associated
security risks MUST be spelled out; RFC 2669 has a very good
example.
o [TODO] list the writable tables and objects and state why they are
sensitive.
Cole & Chakeres Expires November 13, 2008 [Page 17]
Internet-Draft The NHDP MIB May 2008
[TODO] else if there are no read-write objects in your MIB module,
use the following boilerplate paragraph.
There are no management objects defined in this MIB module that have
a MAX-ACCESS clause of read-write and/or read-create. So, if this
MIB module is implemented correctly, then there is no risk that an
intruder can alter or create any management objects of this MIB
module via direct SNMP SET operations.
[TODO] if you have any sensitive readable objects, please include the
following boilerplate paragraph.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
o [TODO] you must explicitly list by name any readable objects that
are sensitive or vulnerable and the associated security risks MUST
be spelled out (for instance, if they might reveal customer
information or violate personal privacy laws such as those of the
European Union if exposed to unauthorized parties)
o [TODO] list the tables and objects and state why they are
sensitive.
[TODO] discuss what security the protocol used to carry the
information should have. The following three boilerplate paragraphs
should not be changed without very good reason. Changes will almost
certainly require justification during IESG review.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
Cole & Chakeres Expires November 13, 2008 [Page 18]
Internet-Draft The NHDP MIB May 2008
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
9. IANA Considerations
[TODO] In order to comply with IESG policy as set forth in
http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is
submitted to the IESG for publication MUST contain an IANA
Considerations section. The requirements for this section vary
depending what actions are required of the IANA. see RFC4181 section
3.5 for more information on writing an IANA clause for a MIB module
document.
[TODO] select an option and provide the necessary details.
Option #1:
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
sampleMIB { mib-2 XXX }
Option #2:
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.
Note well: prior to official assignment by the IANA, a draft document
MUST use placeholders (such as "XXX" above) rather than actual
numbers. See RFC4181 Section 4.5 for an example of how this is done
in a draft MIB module.
Option #3:
This memo includes no request to IANA.
Cole & Chakeres Expires November 13, 2008 [Page 19]
Internet-Draft The NHDP MIB May 2008
10. Contributors
This MIB document uses the template authored by D. Harrington which
is based on contributions from the MIB Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn.
11. Acknowledgements
[TODO]This acknowledgement can be removed from your MIB module
document.
12. References
12.1. Normative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
Appendix A. Change Log
The following changes have been made from
draft-cole-manet-nhdp-mib-00 .
Cole & Chakeres Expires November 13, 2008 [Page 20]
Internet-Draft The NHDP MIB May 2008
Not applicable to draft 00
1.
Appendix B. Open Issues
This section contains the set of open issues related to the
development and design of the NHDP-MIB. This section will not be
present in the final version of the MIB and will be removed once all
the open issues have been resolved.
1. How to handle dynamic parameters within NHDP? Should we expose
setting, min and max values?
2. Need to address how to handle Link Quality settings and
parameters for a) optional operation and b) changing nature of
link quality.
3. What performance objects are of interest and utility?
4. What notifications are of interest and utility?
5. Work on the Security Section. This MIB does have settable
objects, but not sensitive objects (true?).
6. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB.
7. Cleanup all the [TODOs] from the MIB template.
***************************************************************
* Note to the RFC Editor (to be removed prior to publication) *
* *
* 1) The reference to RFCXXXX within the DESCRIPTION clauses *
* of the MIB module point to this draft and are to be *
* assigned by the RFC Editor. *
* *
* 2) The reference to RFCXXX2 throughout this document point *
* to the current draft-cole-manet-nhdp-xx.txt. This *
* need to be replaced with the XXX RFC number. *
* *
***************************************************************
Cole & Chakeres Expires November 13, 2008 [Page 21]
Internet-Draft The NHDP MIB May 2008
Authors' Addresses
Robert G. Cole (editor)
Johns Hopkins University
11100 Johns Hopkins Road, Room 257
Laurel, Maryland 21073
USA
Phone: +1 443 778 6951
EMail: robert.cole@jhuapl.edu
URI: http://www.cs.jhu.edu/~rgcole/
Ian D Chakeres (editor)
Motorola
Bagmane Tech Park
66/1, Plot 5, CV Raman Nagar
Bangalore, Karnataka 560093
India
EMail: ian.chakeres@gmail.com
URI: http://www.ianchak.com/
Cole & Chakeres Expires November 13, 2008 [Page 22]
Internet-Draft The NHDP MIB May 2008
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Cole & Chakeres Expires November 13, 2008 [Page 23]