draft-ietf-manet-smf-mib-01.txt   draft-ietf-manet-smf-mib-02.txt 
Internet Engineering Task Force R. Cole Internet Engineering Task Force R. Cole
Internet-Draft Johns Hopkins University Internet-Draft US Army CERDEC
Intended status: Standards Track J. Macker Intended status: Standards Track J. Macker
Expires: April 29, 2010 B. Adamson Expires: July 20, 2011 B. Adamson
Naval Research Laboratory Naval Research Laboratory
S. Harnedy S. Harnedy
Booz Allen Hamilton Booz Allen Hamilton
October 26, 2009 January 16, 2011
Definition of Managed Objects for the Manet Simplified Multicast Definition of Managed Objects for the Manet Simplified Multicast
Framework Relay Set Process Framework Relay Set Process
draft-ietf-manet-smf-mib-01 draft-ietf-manet-smf-mib-02
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
Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc
Networks (MANETs). The SMF-MIB also reports state information,
performance metrics, and notifications. In addition to
configuration, the additional state and performance information is
useful to operators troubleshooting multicast forwarding problems.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on July 20, 2011.
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 April 29, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2011 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This memo defines a portion of the Management Information Base (MIB) described in the Simplified BSD License.
for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the
Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc
Networks (MANETs). The SMF-MIB also reports state information,
performance metrics, and notifications. In addition to
configuration, this additional state and performance information is
useful to operators troubleshooting multicast forwarding problems.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4
4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6
5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6 5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6
5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7
5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7
5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7
5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8
6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 8
6.3. Relationship to the Future RSSA-MIBs . . . . . . . . . . . 9 6.3. Relationship to the Future RSSA-MIBs . . . . . . . . . . . 8
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Security Considerations . . . . . . . . . . . . . . . . . . . 40 8. Security Considerations . . . . . . . . . . . . . . . . . . . 48
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 42 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 50
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 43 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 50
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
12.1. Normative References . . . . . . . . . . . . . . . . . . . 43 12.1. Normative References . . . . . . . . . . . . . . . . . . . 50
12.2. Informative References . . . . . . . . . . . . . . . . . . 43 12.2. Informative References . . . . . . . . . . . . . . . . . . 51
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 44 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 51
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 44 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 52
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 53
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of a In particular, it describes objects for configuring aspects of a
process implementing Simplified Multicast Forwarding (SMF) process implementing Simplified Multicast Forwarding (SMF)
[I-D.ietf-manet-smf] for Mobile Ad-Hoc Networks (MANETs). SMF [I-D.ietf-manet-smf] for Mobile Ad-Hoc Networks (MANETs). SMF
provides multicast Duplicate Packet Detection (DPD) and supports provides multicast Duplicate Packet Detection (DPD) and supports
algorithms for constructing an estimate of a MANET Minimum Connected algorithms for constructing an estimate of a MANET Minimum Connected
skipping to change at page 4, line 13 skipping to change at page 4, line 13
multicast mechanism for MANETs. multicast mechanism for MANETs.
Various algorithms for the construction of estimates of the MCDS Various algorithms for the construction of estimates of the MCDS
exist. The Simplified Multicast Framework [I-D.ietf-manet-smf] exist. The Simplified Multicast Framework [I-D.ietf-manet-smf]
describes some of these. It further defines various operational describes some of these. It further defines various operational
modes for a node which is participating in the collective creation of modes for a node which is participating in the collective creation of
the MCDS estimates. These modes depend upon the set of related MANET the MCDS estimates. These modes depend upon the set of related MANET
routing and discovery protocols and mechanisms in operation in the routing and discovery protocols and mechanisms in operation in the
specific MANET node. specific MANET node.
A SMF routers' MIB contains SMF process configuration parameters A SMF router's MIB contains SMF process configuration parameters
(e.g. specific CDS algorithm), state information (e.g., current (e.g. specific CDS algorithm), state information (e.g., current
membership in the CDS), performance counters (e.g., packet counters), membership in the CDS), performance counters (e.g., packet counters),
and notifications. and notifications.
4.1. SMF Management Model 4.1. SMF Management Model
This section describes the management model for the SMF node process. This section describes the management model for the SMF node process.
Figure 1 (reproduced from Figure 4 of [I-D.ietf-manet-smf]) shows the Figure 1 (reproduced from Figure 4 of [I-D.ietf-manet-smf]) shows the
relationship between the SMF Relay Set selection algorithm and the relationship between the SMF Relay Set selection algorithm and the
related algorithms, processes and protocols running in the MANET related algorithms, processes and protocols running in the MANET
nodes. The Relay Set Selection Algorithm (RSSA) can rely upon nodes. The Relay Set Selection Algorithm (RSSA) can rely upon
topology information gotten from the MANET Neighborhood Discovery topology information gotten from the MANET Neighborhood Discovery
Protocol (NHDP), from the specific MANET routing protocol running on Protocol (NHDP), from the specific MANET routing protocol running on
the node, or from Layer 2 information passed up to the higher layer the node, or from Layer 2 information passed up to the higher layer
protocol processes. protocol processes.
Possible L2 Trigger/Information RGC Note: update this figure from the latest SMF draft.
|
|
______________ ______|_____ __________________
| MANET | | | | |
| Neighborhood | | Relay Set | | Other Heuristics |
| Discovery |------------| Selection |-------| (Preference,etc) |
| Protocol | neighbor | Algorithm | | |
|______________| info |____________| |__________________|
\ /
\ /
neighbor\ / Dynamic Relay
info* \ ____________ / Set Status
\ | SMF | / (State, {neighbor info})
`---| Relay Set |---'
| State |
---|____________|
/
/
______________
| Coexistent |
| MANET |
| Unicast |
| Process |
|______________|
Figure 1: SMF Relay Set Control Options ______________ ____________
| | | |
| Neighborhood | | Relay Set |
| Discovery |------------->| Selection |
| Protocol | neighbor | Algorithm |
|______________| info |____________|
\ /
\ /
neighbor\ / forwarding
info* \ _____________ / status
\ | | /
`-->| Forwarding |<--'
| Process |
----------------->|_____________|----------------->
incoming packet, forwarded packets
interface id*, and
previous hop*
Figure 1: SMF Node Architecture
4.2. Terms 4.2. Terms
The following definitions apply throughout this document: The following definitions apply throughout this document:
o Configuration Objects - switches, tables, objects which are o Configuration Objects - switches, tables, objects which are
initialized to default settings or set through the management initialized to default settings or set through the management
interface defined by this MIB. interface defined by this MIB.
o Tunable Configuration Objects - objects whose values affect timing o Tunable Configuration Objects - objects whose values affect timing
skipping to change at page 6, line 39 skipping to change at page 6, line 31
* Performance Group - Contains objects which help to characterize * Performance Group - Contains objects which help to characterize
the performance of the SMF RSSA process, typically statistics the performance of the SMF RSSA process, typically statistics
counters. counters.
o smfMIBConformance - defines minimal and full conformance of o smfMIBConformance - defines minimal and full conformance of
implementations to this SMF-MIB. implementations to this SMF-MIB.
5.1. Textual Conventions 5.1. Textual Conventions
The textual conventions defined within the SMF-MIB are as follows. The textual conventions defined within the SMF-MIB are as follows:
The SmfStatus is defined within the SMF-MIB. This contains the
current operational status of the SMF process on the interface. The o The SmfStatus is defined within the SMF-MIB. This contains the
SmfOpModeID represents an index that identifies a specific SMF current operational status of the SMF process on an interface.
operational mode. The SmfRssaID represents an index that identifies
through reference a specific RSSA avaliable for operation on the o The SmfOpModeID represents an index that identifies a specific SMF
device. operational mode.
o The SmfRssaID represents an index that identifies, through
reference, a specific RSSA available for operation on the device.
5.2. The Capabilities Group 5.2. The Capabilities Group
The SMF device supports a set of capabilities. The list of The SMF device supports a set of capabilities. The list of
capabilities which the device can advertise are: capabilities which the device can advertise are:
o Operational Mode - topology information from NHDP, CDS-aware o Operational Mode - topology information from NHDP, CDS-aware
unicast routing or Cross-layer from Layer 2. unicast routing or Cross-layer from Layer 2.
o SMF RSSA - the specific RSSA operational on the device. Note that o SMF RSSA - the specific RSSA operational on the device. Note that
configuration, state and performance objects related to aspecific configuration, state and performance objects related to a specific
RSSA must be defined within another speperate MIB. RSSA must be defined within another separate MIB.
5.3. The Configuration Group 5.3. The Configuration Group
The SMF device is configured with a set of controls. The list of The SMF device is configured with a set of controls. Some of the
configuration controls for the SMF device follow. prominent configuration controls for the SMF device follow:
o Operational Mode - topology information from NHDP, CDS-aware o Operational Mode - topology information from NHDP, CDS-aware
unicast routing or Cross-layer from Layer 2. unicast routing or Cross-layer from Layer 2.
o SMF RSSA - the specific RSSA operational on the device. o SMF RSSA - the specific RSSA operational on the device.
o Duplicate Packet detection for IPv4 - Identification-based or o Duplicate Packet detection for IPv4 - Identification-based or
Hash-based DPD. Hash-based DPD.
o Duplicate Packet detection for IPv6 - Identification-based or o Duplicate Packet detection for IPv6 - Identification-based or
Hash-based DPD. Hash-based DPD.
o NHDP RSSA Message TLV - if NHDP mode is selected, then is the RSSA o SMF Type Message TLV - if NHDP mode is selected, then is the SMF
Message TLV included in the NHDP exchanges. [Note: Is this and Type Message TLV may be included in the NHDP exchanges.
the following two TLVs optional and are they included as a group
or independently of one another?].
o NHDP RSSA Address Block TLV - if NHDP mode is selected, then is
the RSSA Address Block TLV included in the NHDP exchanges.
o Router Priority TLV - if NHDP mode is selected, then is the Router o SMF Address Block TLV - if NHDP mode is selected, then is the SMF
Priority TLV included in the NHDP exchanges. Address Block TLV included in the NHDP exchanges. (Note: is this
correct?)
5.4. The State Group 5.4. The State Group
The State Subtree reports current state information. The State Subtree reports current state information, e.g.,
o Node RSS State - is the node currently in or out of the Relay Set. o Node RSS State - is the node currently in or out of the Relay Set.
o Neighbors Table - a table containing current neighbors and their o Neighbors Table - a table containing current neighbors and their
operational RSSA. operational RSSA.
5.5. The Performance Group 5.5. The Performance Group
The Performance subtree reports primarily counters that relate to SMF The Performance subtree reports primarily counters that relate to SMF
RSSA performance. The SMF performance counters consists of per node RSSA performance. The SMF performance counters consists of per node
skipping to change at page 8, line 25 skipping to change at page 8, line 14
* Multicast packets received. * Multicast packets received.
* Multicast packets forwarded. * Multicast packets forwarded.
* Duplicate multicast packets detected. * Duplicate multicast packets detected.
5.6. The Notifications Group 5.6. The Notifications Group
The Notifications Subtree contains the list of notifications The Notifications Subtree contains the list of notifications
supported within the SMF-MIB and their intended purpose or utility. supported within the SMF-MIB and their intended purpose or utility.
[Note: This group is currently empty.]
6. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
[TODO]: The text of this section specifies the relationship of the [TODO]: The text of this section specifies the relationship of the
MIB modules contained in this document to other standards, MIB modules contained in this document to other standards,
particularly to standards containing other MIB modules. Definitions particularly to standards containing other MIB modules. Definitions
imported from other MIB modules and other MIB modules that SHOULD be imported from other MIB modules and other MIB modules that SHOULD be
implemented in conjunction with the MIB module contained within this implemented in conjunction with the MIB module contained within this
document are identified in this section. document are identified in this section.
skipping to change at page 8, line 47 skipping to change at page 8, line 35
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 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 mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The SMF-MIB does not entity and certain other system-wide data. The SMF-MIB does not
duplicate those objects. duplicate those objects.
6.2. MIB modules required for IMPORTS 6.2. MIB modules required for IMPORTS
The textual conventions imported for use in the SMF-MIB are as The textual conventions imported for use in the SMF-MIB are as
follows. The MOUDULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, Integer32 and mib-2 textual conventions are Counter32, Unsigned32, Integer32 and mib-2 textual conventions are
imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus
and TruthValue textual conventions are imported from RFC 2579 and TruthValue textual conventions are imported from RFC 2579
[RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION-
GROUP textual conventions are imported from RFC 2580 [RFC2580]. The GROUP textual conventions are imported from RFC 2580 [RFC2580]. The
InterfaceIndexOrZero textual convention is imported from RFC 2863 InterfaceIndexOrZero textual convention is imported from RFC 2863
[RFC2863]. The SnmpAdminString textual convention is imported from [RFC2863]. The SnmpAdminString textual convention is imported from
RFC 3411 [RFC3411]. The InetAddress, InetAddressType and RFC 3411 [RFC3411]. The InetAddress, InetAddressType and
InetAddressPrefixLength textual conventions are imported from RFC InetAddressPrefixLength textual conventions are imported from RFC
4001 [RFC4001]. 4001 [RFC4001].
6.3. Relationship to the Future RSSA-MIBs 6.3. Relationship to the Future RSSA-MIBs
In a sense, the SMF-MIB is a general front-end to a set of, yet to be In a sense, the SMF-MIB is a general front-end to a set of, yet to be
developed, RSSA-specific MIBs. These RSSA-specific MIBs will define developed, RSSA-specific MIBs. These RSSA-specific MIBs will define
the objects for the configuration, state, performance and the objects for the configuration, state, performance and
notification objects required for the operation of these specific notification objects required for the operation of these specific
RSSAs. RSSAs. The SMF-MIB Capabilities Group allows the remote management
station the ability to query the router to discover the set of
supported RSSAs.
7. Definitions 7. Definitions
MANET-SMF-MIB DEFINITIONS ::= BEGIN MANET-SMF-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, Integer32, mib-2 Counter32, Unsigned32, Integer32, TimeTicks, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, RowStatus, TruthValue TEXTUAL-CONVENTION, RowStatus, TruthValue
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
InterfaceIndexOrZero InterfaceIndexOrZero
skipping to change at page 9, line 47 skipping to change at page 9, line 38
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411] FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
InetAddress, InetAddressType, InetAddress, InetAddressType,
InetAddressPrefixLength InetAddressPrefixLength
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- [RFC4001]
; ;
manetSmfMIB MODULE-IDENTITY manetSmfMIB MODULE-IDENTITY
LAST-UPDATED "200910261300Z" -- October 26, 2009 LAST-UPDATED "201101161300Z" -- January 16, 2011
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: ian.chakeres@gmail.com WG Chairs: ian.chakeres@gmail.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Robert G. Cole Editors: Robert G. Cole
Johns Hopkins University US Army CERDEC
Applied Physics Lab and Space and Terrestrial Communications
Department of Computer Science 328 Hopkins Road
11000 Johns Hopkins Road Bldg 245, Room 16
Room 02-257 Aberdeen Proving Ground, MD 21005
Laurel, MD 22014
USA USA
+1 443 778-6951 +1 410 278-6779
robert.cole@jhuapl.edu robert.g.cole@us.army.mil
http://www.cs.jhu.edu/~rgcole/
Joseph Macker Joseph Macker
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
USA USA
macker@itd.nrl.navy.mil macker@itd.nrl.navy.mil
Brian Adamson Brian Adamson
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
skipping to change at page 10, line 42 skipping to change at page 10, line 34
Sean Harnedy Sean Harnedy
Booz Allen Hamilton Booz Allen Hamilton
333 City Boulevard West 333 City Boulevard West
Orange, CA 92868 Orange, CA 92868
USA USA
+1 714 938-3898 +1 714 938-3898
harnedy_sean@bah.com" harnedy_sean@bah.com"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions for "This MIB module contains managed object definitions for
the Manet SMF RSSA process defined in: Macker, J.(ed.), the Manet SMF RSSA process defined in:
Simplified Multicast Forwarding draft-ietf-manet-smf-09,
July 13, 2009. [SMF] Macker, J.(ed.),
Simplified Multicast Forwarding draft-ietf-manet-smf-10,
March 06, 2010.
Copyright (C) The IETF Trust (2008). This version Copyright (C) The IETF Trust (2008). 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 History -- Revision History
REVISION "201101161300Z" -- January 16, 2011
DESCRIPTION
"Updated 5th revision of the
draft of this MIB module published as
draft-ietf-manet-smf-mib-02.txt. The changes
made in this revision include:
- Added the Notification Group and cleaned
up the Conformance section
- Completed the TEXTUAL CONVENTION for the
smfOpMode.
- Completed the Description clauses of
several objects within the MIB.
- Removed the routerPriority object.
- Added the definition of a smfRouterID
object and associated smfRouterIDAddrType
object.
"
REVISION "200910261300Z" -- October 26, 2009 REVISION "200910261300Z" -- October 26, 2009
DESCRIPTION DESCRIPTION
"Updated draft of this MIB module published as "Updated draft of this MIB module published as
draft-ietf-manet-smf-mib-01.txt. A few changes draft-ietf-manet-smf-mib-01.txt. A few changes
were made in the development of this draft. were made in the development of this draft.
Specifically, the following changes were made: Specifically, the following changes were made:
- Updated the textual material, included - Updated the textual material, included
section on IMPORTS, relationship to other section on IMPORTS, relationship to other
MIBs, etc. MIBs, etc.
" "
skipping to change at page 12, line 38 skipping to change at page 12, line 48
function or feature. For example, the status function or feature. For example, the status
of an interface: 'enabled' indicates that of an interface: 'enabled' indicates that
it is performing SMF functions, it is performing SMF functions,
and 'disabled' indicates that it is not." and 'disabled' indicates that it is not."
SYNTAX INTEGER { SYNTAX INTEGER {
enabled (1), enabled (1),
disabled (2) disabled (2)
} }
SmfOpModeID ::= TEXTUAL-CONVENTION SmfOpModeID ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that identifies through reference to a specific "An index that identifies through reference to a specific
SMF operations mode ... SMF operations mode. There are basically three styles
of SMF operation with reduced relay sets:
Independent operation - SMF performs its own relay
set selection using information from an associated
MANET NHDP process.
CDS-aware unicast routing operation - a coexistent
unicast routing protocol provides dynamic relay
set state based upon its own control plane
CDS or neighborhood discovery information.
Cross-layer operation - SMF operates using
neighborhood status and triggers from a
cross-layer information base for dynamic relay
set selection and maintenance
" "
SYNTAX Unsigned32 (1..2147483647) SYNTAX INTEGER {
independent (1),
routing (2),
crossLayer (3)
-- future (4-255)
}
SmfRssaID ::= TEXTUAL-CONVENTION SmfRssaID ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that identifies through reference to a specific "An index that identifies through reference to a specific
RSSA algorithms ... RSSA algorithms. Several are currently defined
in the appendix of
" "
SYNTAX INTEGER { SYNTAX INTEGER {
cF(1), cF(1),
sMPR(2), sMPR(2),
eCDS(3), eCDS(3),
mprCDS(4) mprCDS(4)
-- future(5-127) -- future(5-127)
-- noStdAction(128-239) -- noStdAction(128-239)
-- experimental(240-255) -- experimental(240-255)
} }
skipping to change at page 14, line 5 skipping to change at page 14, line 33
-- --
-- SMF Operational Mode Capabilities Table -- SMF Operational Mode Capabilities Table
-- --
smfOpModeCapabilitiesTable OBJECT-TYPE smfOpModeCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfOpModeCapabilitiesEntry SYNTAX SEQUENCE OF SmfOpModeCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smfOpModeCapabilitiesTable contains ... "The smfOpModeCapabilitiesTable identifies the
resident set of SMF Operational Modes on this
router.
" "
::= { smfCapabilitiesGroup 1 } ::= { smfCapabilitiesGroup 1 }
smfOpModeCapabilitiesEntry OBJECT-TYPE smfOpModeCapabilitiesEntry OBJECT-TYPE
SYNTAX SmfOpModeCapabilitiesEntry SYNTAX SmfOpModeCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular operational "Information about a particular operational
mode. mode.
skipping to change at page 14, line 42 skipping to change at page 15, line 27
the particular operational mode for this device. the particular operational mode for this device.
" "
::= { smfOpModeCapabilitiesEntry 1 } ::= { smfOpModeCapabilitiesEntry 1 }
smfOpModeCapabilitiesName OBJECT-TYPE smfOpModeCapabilitiesName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual name of this operational "The textual name of this operational
mode. mode. Current operational modes include:
Independent Mode, CDS-aware Routing Mode,
and Cross-layer Mode. Others may be defined
in future revisions of [SMF].
" "
::= { smfOpModeCapabilitiesEntry 2 } ::= { smfOpModeCapabilitiesEntry 2 }
smfOpModeCapabilitiesReference OBJECT-TYPE smfOpModeCapabilitiesReference OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a reference to the document that "This object contains a reference to the document that
defines this operational mode. defines this operational mode.
skipping to change at page 15, line 46 skipping to change at page 16, line 34
smfRssaCapabilitiesReference SnmpAdminString smfRssaCapabilitiesReference SnmpAdminString
} }
smfRssaCapabilitiesID OBJECT-TYPE smfRssaCapabilitiesID OBJECT-TYPE
SYNTAX SmfRssaID SYNTAX SmfRssaID
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this entry. This object identifies "The index for this entry. This object identifies
the particular RSSA algorithm in this MIB the particular RSSA algorithm in this MIB
module." module. Example RSSAs are found in the
appendix of [SMF]."
::= { smfRssaCapabilitiesEntry 1 } ::= { smfRssaCapabilitiesEntry 1 }
smfRssaCapabilitiesName OBJECT-TYPE smfRssaCapabilitiesName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual name of this RSSA algorithm. "The textual name of this RSSA algorithm.
Currently defined names are:
Classical Flooding - cF,
Source-based MultiPoint
Relay - sMPR,
Essential Connecting Dominating
Set - eCDS,
MultiPoint Relay Connected
Dominating Set - mprCDS.
" "
::= { smfRssaCapabilitiesEntry 2 } ::= { smfRssaCapabilitiesEntry 2 }
smfRssaCapabilitiesReference OBJECT-TYPE smfRssaCapabilitiesReference OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a published reference "This object contains a published reference
to the document that defines this algorithm. to the document that defines this algorithm.
skipping to change at page 17, line 4 skipping to change at page 17, line 45
on this device. Enabled(1) means that on this device. Enabled(1) means that
SMF is configured to run on this device. SMF is configured to run on this device.
Disabled(2) mean that the SMF process Disabled(2) mean that the SMF process
is configured off. is configured off.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
::= { smfConfigurationGroup 1 } ::= { smfConfigurationGroup 1 }
smfConfiguredOpMode OBJECT-TYPE
SYNTAX INTEGER { -- Note: need to better define the algorithm to
-- choose the smfRouterID.
smfRouterIDAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The address type of the address used for
SMF ID of this router as specified
in the 'smfRouterID' next.
This can be set by the management station, must
the smfRouterID must be a routable address
assigned to this router. If the management
station does not assign this value, then the
router should choose the highest IP address
assigned to this router.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 2 }
smfRouterID OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The IP address used as the SMF router ID.
this can be set by the management station.
If not explicitly set, then the device
should select a routable IP address
assigned to this router for use as
the 'smfRouterID'.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 3 }
smfConfiguredOpMode OBJECT-TYPE
SYNTAX INTEGER {
withNHDP(1), withNHDP(1),
cdsAwareRouting(2), cdsAwareRouting(2),
crossLayer(3), crossLayer(3),
other(4) other(4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF RSS node operational mode. "The SMF RSS node operational mode as defined
in the TEXTUAL CONVENTION for `SmfOpModeID'
and in [SMF]..
The value withNHDP(1) indicates ... The value withNHDP(1) indicates Independent
The value cdsAwareRouting(2) indicates ... Mode of operation.
The value crossLayer(3) indicates... .
The value cdsAwareRouting(2) indicates
CDS-aware Routing Mode of operation.
The value crossLayer(3) indicates
Cross-layer Mode of operation.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
::= { smfConfigurationGroup 2 } ::= { smfConfigurationGroup 4 }
smfConfiguredRssa OBJECT-TYPE smfConfiguredRssa OBJECT-TYPE
SYNTAX SmfRssaID SYNTAX SmfRssaID
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF RSS currently operational algorithm. "The SMF RSS currently operational algorithm
as defined in the TEXTUAL CONVENTION for
The value cf(1) indicates ... `SmfRssaID' and in [SMF].
The value experimental(240-255) indicates... .
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
::= { smfConfigurationGroup 3 } ::= { smfConfigurationGroup 5 }
smfRssaMember OBJECT-TYPE smfRssaMember OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
potential(1), potential(1),
always(2), always(2),
never(3) never(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 18, line 25 skipping to change at page 20, line 20
The value always(1) forces the selected The value always(1) forces the selected
RSSA include this agent in the RSS. RSSA include this agent in the RSS.
The value never(3) forces the selected The value never(3) forces the selected
RSSA to exclude this agent from the RSS. RSSA to exclude this agent from the RSS.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
::= { smfConfigurationGroup 4 } ::= { smfConfigurationGroup 6 }
smfIpv4Dpd OBJECT-TYPE smfIpv4Dpd OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
identificationBased(1), identificationBased(1),
hashBased(2) hashBased(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current method for IPv4 duplicate packet "The current method for IPv4 duplicate packet
skipping to change at page 18, line 37 skipping to change at page 20, line 32
smfIpv4Dpd OBJECT-TYPE smfIpv4Dpd OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
identificationBased(1), identificationBased(1),
hashBased(2) hashBased(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current method for IPv4 duplicate packet "The current method for IPv4 duplicate packet
detection. detection.
The value identificationBased(1) The value identificationBased(1)
indicates... indicates that the duplicate packet
detection relies upon header information
in the multicast packets to identify
previously received packets.
The value 'hashBased(2) indicates... . The value 'hashBased(2) indicates that the
routers duplicate packet detection is based
upon comparing a hash over the packet fields.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
::= { smfConfigurationGroup 5 } ::= { smfConfigurationGroup 7 }
smfIpv6Dpd OBJECT-TYPE smfIpv6Dpd OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
identificationBased(1), identificationBased(1),
hashBased(2) hashBased(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current method for IPv6 duplicate packet "The current method for IPv6 duplicate packet
detection. detection.
The value identificationBased(1)
indicates...
The value 'hashBased(2) indicates... . The values indicate the type of method used
for duplicate packet detection as described
the previous description for the object
`smfIpv4Dpd'.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
::= { smfConfigurationGroup 6 } ::= { smfConfigurationGroup 8 }
smfMaxPktLifetime OBJECT-TYPE smfMaxPktLifetime OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The estimate of the network packet "The estimate of the network packet
traversal time. traversal time.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
DEFVAL { 60 } DEFVAL { 60 }
::= { smfConfigurationGroup 7 } ::= { smfConfigurationGroup 9 }
smfDpdMaxMemorySize OBJECT-TYPE smfDpdMaxMemorySize OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
UNITS "Kilo-Bytes" UNITS "Kilo-Bytes"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The locally reserved memory for storage "The locally reserved memory for storage
of cached DPD records for both IPv4 and of cached DPD records for both IPv4 and
IPv6 methods. IPv6 methods.
skipping to change at page 19, line 50 skipping to change at page 22, line 4
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The locally reserved memory for storage "The locally reserved memory for storage
of cached DPD records for both IPv4 and of cached DPD records for both IPv4 and
IPv6 methods. IPv6 methods.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
DEFVAL { 1024 } DEFVAL { 1024 }
::= { smfConfigurationGroup 10 }
::= { smfConfigurationGroup 8 }
smfDpdEntryMaxLifetime OBJECT-TYPE smfDpdEntryMaxLifetime OBJECT-TYPE
SYNTAX Integer32 (0..65525) SYNTAX Integer32 (0..65525)
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum lifetime of a cached DPD "The maximum lifetime of a cached DPD
record in the local device storage. record in the local device storage.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
DEFVAL { 600 } DEFVAL { 600 }
::= { smfConfigurationGroup 9 } ::= { smfConfigurationGroup 11 }
-- --
-- Configuration of messages to be included in -- Configuration of messages to be included in
-- NHDP message exchanges in support of SMF -- NHDP message exchanges in support of SMF
-- operations. -- operations.
-- --
-- Note: need to clarify whether this is an option
-- or is required when the smfOpMode is set
-- to 'independent'.
smfNhdpRssaMesgTLVIncluded OBJECT-TYPE smfNhdpRssaMesgTLVIncluded OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the associated NHDP messages "Indicates whether the associated NHDP messages
include the RSSA Message TLV, or not. This include the RSSA Message TLV, or not. This
is an optional SMF operational setting. is an optional SMF operational setting.
The value true(1) indicates that this TLV is The value true(1) indicates that this TLV is
included; the value false(2) indicates that it included; the value false(2) indicates that it
is not included. is not included.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
::= { smfConfigurationGroup 10 } ::= { smfConfigurationGroup 12 }
smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the associated NHDP messages "Indicates whether the associated NHDP messages
include the RSSA Address Block TLV, or not. include the RSSA Address Block TLV, or not.
This is an optional SMF operational setting. This is an optional SMF operational setting.
The value true(1) indicates that this TLV is The value true(1) indicates that this TLV is
included; the value false(2) indicates that it included; the value false(2) indicates that it
is not included. is not included.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
::= { smfConfigurationGroup 11 } ::= { smfConfigurationGroup 13 }
smfNhdpRouterPriorityTLVIncluded OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the associated NHDP messages
include the RSSA Router Priority TLV, or not.
This is an optional SMF operational setting.
The value true(1) indicates that this TLV is
included; the value false(2) indicates that it
is not included.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfConfigurationGroup 12 }
-- --
-- Table identifying configured multicast addresses to be forwarded. -- Table identifying configured multicast addresses to be forwarded.
-- --
smfConfiguredAddrForwardingTable OBJECT-TYPE smfConfiguredAddrForwardingTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 22, line 14 skipping to change at page 23, line 48
these additional, dynamically discovered address for these additional, dynamically discovered address for
forwarding. forwarding.
Each row is associated with a range of multicast Each row is associated with a range of multicast
addresses, and ranges for different rows must be disjoint. addresses, and ranges for different rows must be disjoint.
The objects in this table are persistent and when written The objects in this table are persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage. non-volatile storage.
" "
::= { smfConfigurationGroup 13 } ::= { smfConfigurationGroup 15 }
smfConfiguredAddrForwardingEntry OBJECT-TYPE smfConfiguredAddrForwardingEntry OBJECT-TYPE
SYNTAX SmfConfiguredAddrForwardingEntry SYNTAX SmfConfiguredAddrForwardingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) containing the information on a "An entry (conceptual row) containing the information on a
particular multicast scope." particular multicast scope."
INDEX { smfConfiguredAddrForwardingAddrType, INDEX { smfConfiguredAddrForwardingAddrType,
smfConfiguredAddrForwardingFirstAddr } smfConfiguredAddrForwardingFirstAddr }
::= { smfConfiguredAddrForwardingTable 1 } ::= { smfConfiguredAddrForwardingTable 1 }
skipping to change at page 24, line 5 skipping to change at page 25, line 40
from the interfaces group defined in the from the interfaces group defined in the
Interfaces Group MIB. Interfaces Group MIB.
The objects in this table are persistent The objects in this table are persistent
and when written the entity SHOULD save and when written the entity SHOULD save
the change to non-volatile storage. the change to non-volatile storage.
" "
REFERENCE REFERENCE
"RFC 2863 - The Interfaces Group MIB, McCloghrie, "RFC 2863 - The Interfaces Group MIB, McCloghrie,
K., and F. Kastenholtz, June 2000." K., and F. Kastenholtz, June 2000."
::= { smfConfigurationGroup 14 } ::= { smfConfigurationGroup 16 }
smfInterfaceEntry OBJECT-TYPE smfInterfaceEntry OBJECT-TYPE
SYNTAX SmfInterfaceEntry SYNTAX SmfInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF interface entry describes one SMF "The SMF interface entry describes one SMF
interface as indexed by its ifIndex." interface as indexed by its ifIndex."
INDEX { smfIfIndex } INDEX { smfIfIndex }
::= { smfInterfaceTable 1 } ::= { smfInterfaceTable 1 }
skipping to change at page 24, line 16 skipping to change at page 26, line 4
smfInterfaceEntry OBJECT-TYPE smfInterfaceEntry OBJECT-TYPE
SYNTAX SmfInterfaceEntry SYNTAX SmfInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF interface entry describes one SMF "The SMF interface entry describes one SMF
interface as indexed by its ifIndex." interface as indexed by its ifIndex."
INDEX { smfIfIndex } INDEX { smfIfIndex }
::= { smfInterfaceTable 1 } ::= { smfInterfaceTable 1 }
SmfInterfaceEntry ::= SmfInterfaceEntry ::=
SEQUENCE { SEQUENCE {
smfIfIndex InterfaceIndexOrZero, smfIfIndex InterfaceIndexOrZero,
smfIfAdminStatus SmfStatus, smfIfAdminStatus SmfStatus,
smfIfRowStatus RowStatus smfIfRowStatus RowStatus
} }
smfIfIndex OBJECT-TYPE smfIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex for this SMF interface." "The ifIndex for this SMF interface."
::= { smfInterfaceEntry 1 } ::= { smfInterfaceEntry 1 }
smfIfAdminStatus OBJECT-TYPE smfIfAdminStatus OBJECT-TYPE
SYNTAX SmfStatus SYNTAX SmfStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 30, line 50 skipping to change at page 32, line 37
device due to TTL exceeded." device due to TTL exceeded."
::= { smfGlobalPerfGroup 4 } ::= { smfGlobalPerfGroup 4 }
smfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE smfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv4 packets "A counter of the total number of IPv4 packets
recieved which have a TTL larger than that recieved which have a TTL larger than that
of a previously recived identical packet. of a previously received identical packet.
" "
::= { smfGlobalPerfGroup 5 } ::= { smfGlobalPerfGroup 5 }
-- --
-- IPv6 packet counters -- IPv6 packet counters
-- --
smfIpv6MultiPktsRecvTotal OBJECT-TYPE smfIpv6MultiPktsRecvTotal OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 37, line 14 skipping to change at page 39, line 4
smfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE smfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of the total number of IPv6 packets "A counter of the total number of IPv6 packets
recieved which the device inserted the recieved which the device inserted the
DPD header option. DPD header option.
" "
::= { smfIpv6InterfacePerfEntry 8 } ::= { smfIpv6InterfacePerfEntry 8 }
-- --
-- Notifications -- Notifications
-- --
-- Note: What notifications do we want for this MIB? smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 }
smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 2 }
smfMIBNotifStates OBJECT IDENTIFIER ::= { smfMIBNotifications 3 }
-- smfMIBNotifControl
smfSetNotification OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(4))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A 4-octet string serving as a bit map for
the notification events defined by the SMF MIB
notifications. This object is used to enable
and disable specific SMF MIB notifications where
a 1 in the bit field represents enabled. The
right-most bit (least significant) represents
notification 0.
This object is persistent and when written
the entity SHOULD save the change to
non-volatile storage.
"
::= { smfMIBNotifControl 1 }
smfDpdMemoryOverflowThreshold OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A threshold value for the
`smfDpdmemoryOverflowEvents' object.
If the number of occurences exceeds
this threshold within the previous
number of seconds
'smfDpdMemoryOverflowWindow',
then the `smfDpdMemoryOverflowEvent'
notification is sent.
"
::= { smfMIBNotifControl 2 }
smfDpdMemoryOverflowWindow OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A time window value for the
`smfDpdmemoryOverflowEvents' object.
If the number of occurences exceeds
the `smfDpdMemoryOverflowThreshold'
within the previous number of seconds
'smfDpdMemoryOverflowWindow',
then the `smfDpdMemoryOverflowEvent'
notification is sent.
"
::= { smfMIBNotifControl 3 }
smfIpv4DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A threshold value for the
`smfIpv4DuplMultiPktsDetectedTotal'
object. If the number of occurences
exceeds this threshold within the
previous number of seconds
`smfIpv4DuplMultiPktsDetectedTotalWindow',
then the
`smfIpv4DuplMultiPktsDetectedTotalEvent'
notification is sent.
"
::= { smfMIBNotifControl 4 }
smfIpv4DuplMultiPktsDetectedTotalWindow OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A time window value for the
`smfIpv4DuplMultiPktsDetectedTotalEvents'
object. If the number of occurences
exceeds the
`smfIpv4DuplMultiPktsDetectedTotalThreshold'
within the previous number of seconds
'smfIpv4DuplMultiPktsDetectedTotalWindow',
then the
`smfIpv4DuplMultiPktsDetectedTotalEvent'
notification is sent.
"
::= { smfMIBNotifControl 5 }
smfIpv6DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A threshold value for the
`smfIpv6DuplMultiPktsDetectedTotal'
object. If the number of occurences
exceeds this threshold within the
previous number of seconds
`smfIpv6DuplMultiPktsDetectedTotalWindow',
then the
`smfIpv6DuplMultiPktsDetectedTotalEvent'
notification is sent.
"
::= { smfMIBNotifControl 6 }
smfIpv6DuplMultiPktsDetectedTotalWindow OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A time window value for the
`smfIpv6DuplMultiPktsDetectedTotalEvents'
object. If the number of occurences
exceeds the
`smfIpv6DuplMultiPktsDetectedTotalThreshold'
within the previous number of seconds
'smfIpv6DuplMultiPktsDetectedTotalWindow',
then the
`smfIpv6DuplMultiPktsDetectedTotalEvent'
notification is sent.
"
::= { smfMIBNotifControl 7 }
-- smfMIBNotifObjects
smfAdminStatusChange NOTIFICATION-TYPE
OBJECTS { smfRouterIDAddrType, -- The originator of
-- the notification.
smfRouterID, -- The originator of
-- the notification.
smfAdminStatus -- The new status of the
-- SMF process.
}
STATUS current
DESCRIPTION
"smfAdminStatusChange is a notification sent when a
the 'smfAdminStatus' object changes.
"
::= { smfMIBNotifObjects 1 }
smfConfiguredOpModeChange NOTIFICATION-TYPE
OBJECTS { smfRouterIDAddrType, -- The originator of
-- the notification.
smfRouterID, -- The originator of
-- the notification.
smfConfiguredOpMode -- The new Operations
-- Mode of the SMF
-- process.
}
STATUS current
DESCRIPTION
"smfConfiguredOpModeChange is a notification
sent when a the 'smfConfiguredOpMode' object
changes.
"
::= { smfMIBNotifObjects 2 }
smfConfiguredRssaChange NOTIFICATION-TYPE
OBJECTS { smfRouterIDAddrType, -- The originator of
-- the notification.
smfRouterID, -- The originator of
-- the notification.
smfConfiguredRssa -- The new RSSA for
-- the SMF process.
}
STATUS current
DESCRIPTION
"smfAdminStatusChange is a notification sent when a
the 'smfConfiguredRssa' object changes.
"
::= { smfMIBNotifObjects 3 }
smfIfAdminStatusChange NOTIFICATION-TYPE
OBJECTS { smfRouterIDAddrType, -- The originator of
-- the notification.
smfRouterID, -- The originator of
-- the notification.
smfIfIndex, -- The interface whose
-- status has changed.
smfIfAdminStatus -- The new status of the
-- SMF interface.
}
STATUS current
DESCRIPTION
"smfIfAdminStatusChange is a notification sent when a
the 'smfIfAdminStatus' object changes.
"
::= { smfMIBNotifObjects 4 }
smfDpdMemoryOverflowEvent NOTIFICATION-TYPE
OBJECTS { smfRouterIDAddrType, -- The originator of
-- the notification.
smfRouterID, -- The originator of
-- the notification.
smfDpdMemoryOverflow -- The counter of
-- the overflows.
}
STATUS current
DESCRIPTION
"smfDpdMemoryOverflowEvents is sent when the
number of memory overflow events exceeds the
the 'smfDpdMemoryOverflowThreshold' within the
previous number of seconds defined by the
'smfDpdMemoryOverflowWindow'.
"
::= { smfMIBNotifObjects 5 }
smfIpv4DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE
OBJECTS { smfRouterIDAddrType, -- The originator of
-- the notification.
smfRouterID, -- The originator of
-- the notification.
smfIpv4DuplMultiPktsDetectedTotal -- The
-- counter of detected
-- duplicates.
}
STATUS current
DESCRIPTION
"smfIpv4DuplMultiPktsDetectedTotal is a
notification sent when the number of
IPv4 duplicate packets detected exceeds the
'smfIpv4DuplMultiPktsDetectedTotalThreshold'
during the previous number of seconds
'smfIpv4DuplPktsDetectedTotalWindow'.
"
::= { smfMIBNotifObjects 6 }
smfIpv6DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE
OBJECTS { smfRouterIDAddrType, -- The originator of
-- the notification.
smfRouterID, -- The originator of
-- the notification.
smfIpv6DuplMultiPktsDetectedTotal -- The
-- counter of detected
-- duplicates.
}
STATUS current
DESCRIPTION
"smfIpv6DuplMultiPktsDetectedTotal is a
notification sent when the number of
IPv6 duplicate packets detected exceeds the
'smfIpv6DuplMultiPktsDetectedTotalThreshold'
during the previous number of seconds
'smfIpv6DuplPktsDetectedTotalWindow'.
"
::= { smfMIBNotifObjects 7 }
-- smfMIBNotifStates
-- is empty.
-- --
-- Compliance Statements -- Compliance Statements
-- --
-- Note: need to update the Compliance section once the mib
-- objects stablize.
smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 }
smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 }
smfBasicCompliance MODULE-COMPLIANCE smfBasicCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The basic implementation requirements for DESCRIPTION "The basic implementation requirements for
managed network entities that implement managed network entities that implement
the SMF RSSA process." the SMF RSSA process."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { smfCapabObjectsGroup, MANDATORY-GROUPS { smfCapabObjectsGroup,
skipping to change at page 37, line 46 skipping to change at page 45, line 4
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { smfCapabObjectsGroup, MANDATORY-GROUPS { smfCapabObjectsGroup,
smfConfigObjectsGroup } smfConfigObjectsGroup }
::= { smfCompliances 1 } ::= { smfCompliances 1 }
smfFullCompliance MODULE-COMPLIANCE smfFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The full implementation requirements for DESCRIPTION "The full implementation requirements for
managed network entities that implement managed network entities that implement
the SMF RSSA process." the SMF RSSA process."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { smfCapabObjectsGroup, MANDATORY-GROUPS { smfCapabObjectsGroup,
smfConfigObjectsGroup, smfConfigObjectsGroup,
smfStateObjectsGroup, smfStateObjectsGroup,
smfPerfObjectsGroup smfPerfObjectsGroup,
smfNotifObjectsGroup,
smfNotificationsGroup
} }
::= { smfCompliances 2 } ::= { smfCompliances 2 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
smfCapabObjectsGroup OBJECT-GROUP smfCapabObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
smfOpModeCapabilitiesName, smfOpModeCapabilitiesName,
skipping to change at page 38, line 30 skipping to change at page 45, line 36
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of SMF configuration objects implemented "Set of SMF configuration objects implemented
in this module." in this module."
::= { smfMIBGroups 1 } ::= { smfMIBGroups 1 }
smfConfigObjectsGroup OBJECT-GROUP smfConfigObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
smfAdminStatus, smfAdminStatus,
smfRouterIDAddrType,
smfRouterID,
smfIfIndex,
smfConfiguredOpMode, smfConfiguredOpMode,
smfConfiguredRssa, smfConfiguredRssa,
smfRssaMember, smfRssaMember,
smfIpv4Dpd, smfIpv4Dpd,
smfIpv6Dpd, smfIpv6Dpd,
smfMaxPktLifetime, smfMaxPktLifetime,
smfDpdMaxMemorySize, smfDpdMaxMemorySize,
smfDpdEntryMaxLifetime, smfDpdEntryMaxLifetime,
smfNhdpRssaMesgTLVIncluded, smfNhdpRssaMesgTLVIncluded,
smfNhdpRssaAddrBlockTLVIncluded, smfNhdpRssaAddrBlockTLVIncluded,
smfNhdpRouterPriorityTLVIncluded,
smfConfiguredAddrForwardingLastAddr, smfConfiguredAddrForwardingLastAddr,
smfConfiguredAddrForwardingStatus, smfConfiguredAddrForwardingStatus,
smfIfAdminStatus, smfIfAdminStatus,
smfIfRowStatus smfIfRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of SMF configuration objects implemented "Set of SMF configuration objects implemented
in this module." in this module."
::= { smfMIBGroups 2 } ::= { smfMIBGroups 2 }
smfStateObjectsGroup OBJECT-GROUP smfStateObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
smfNodeRsStatusIncluded, smfNodeRsStatusIncluded,
smfDpdMemoryOverflow, smfDpdMemoryOverflow,
smfDiscoveredAddrForwardingLastAddr, smfDiscoveredAddrForwardingLastAddr,
smfDiscoveredAddrForwardingStatus, smfDiscoveredAddrForwardingStatus,
skipping to change at page 39, line 45 skipping to change at page 47, line 4
smfIpv6DroppedMultiPktsTTLExceededTotal, smfIpv6DroppedMultiPktsTTLExceededTotal,
smfIpv6TTLLargerThanPreviousTotal, smfIpv6TTLLargerThanPreviousTotal,
smfIpv6HAVAssistsReqdTotal, smfIpv6HAVAssistsReqdTotal,
smfIpv6DpdHeaderInsertionsTotal, smfIpv6DpdHeaderInsertionsTotal,
smfIpv4MultiPktsRecvPerIf, smfIpv4MultiPktsRecvPerIf,
smfIpv4MultiPktsForwardedPerIf, smfIpv4MultiPktsForwardedPerIf,
smfIpv4DuplMultiPktsDetectedPerIf, smfIpv4DuplMultiPktsDetectedPerIf,
smfIpv4DroppedMultiPktsTTLExceededPerIf, smfIpv4DroppedMultiPktsTTLExceededPerIf,
smfIpv4TTLLargerThanPreviousPerIf, smfIpv4TTLLargerThanPreviousPerIf,
smfIpv6MultiPktsRecvPerIf, smfIpv6MultiPktsRecvPerIf,
smfIpv6MultiPktsForwardedPerIf, smfIpv6MultiPktsForwardedPerIf,
smfIpv6DuplMultiPktsDetectedPerIf, smfIpv6DuplMultiPktsDetectedPerIf,
smfIpv6DroppedMultiPktsTTLExceededPerIf, smfIpv6DroppedMultiPktsTTLExceededPerIf,
smfIpv6TTLLargerThanPreviousPerIf, smfIpv6TTLLargerThanPreviousPerIf,
smfIpv6HAVAssistsReqdPerIf, smfIpv6HAVAssistsReqdPerIf,
smfIpv6DpdHeaderInsertionsPerIf smfIpv6DpdHeaderInsertionsPerIf
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of SMF performance objects implemented "Set of SMF performance objects implemented
in this module by total and per interface." in this module by total and per interface."
::= { smfMIBGroups 4 } ::= { smfMIBGroups 4 }
smfNotifObjectsGroup OBJECT-GROUP
OBJECTS {
smfSetNotification,
smfDpdMemoryOverflowThreshold,
smfDpdMemoryOverflowWindow,
smfIpv4DuplMultiPktsDetectedTotalThreshold,
smfIpv4DuplMultiPktsDetectedTotalWindow,
smfIpv6DuplMultiPktsDetectedTotalThreshold,
smfIpv6DuplMultiPktsDetectedTotalWindow
}
STATUS current
DESCRIPTION
"Set of SMF notification control
objects implemented in this module."
::= { smfMIBGroups 5 }
smfNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
smfAdminStatusChange,
smfConfiguredOpModeChange,
smfConfiguredRssaChange,
smfIfAdminStatusChange,
smfDpdMemoryOverflowEvent,
smfIpv4DuplMultiPktsDetectedTotalEvents,
smfIpv6DuplMultiPktsDetectedTotalEvents
}
STATUS current
DESCRIPTION
"Set of SMF notifications implemented
in this module."
::= { smfMIBGroups 6 }
END END
8. Security Considerations 8. Security Considerations
[TODO] Each specification that defines one or more MIB modules MUST [TODO] Each specification that defines one or more MIB modules MUST
contain a section that discusses security considerations relevant to contain a section that discusses security considerations relevant to
those modules. This section MUST be patterned after the latest those modules. This section MUST be patterned after the latest
approved template (available at approved template (available at
http://www.ops.ietf.org/mib-security.html). Remember that the http://www.ops.ietf.org/mib-security.html). Remember that the
objective is not to blindly copy text from the template, but rather objective is not to blindly copy text from the template, but rather
skipping to change at page 43, line 46 skipping to change at page 51, line 34
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for Schoenwaelder, Ed., "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2580] McCloghrie, K., Perkins, D., and J.
Schoenwaelder, "Conformance Statements for Schoenwaelder, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[I-D.ietf-manet-smf] Macker, J. and S. Team, "Simplified Multicast [I-D.ietf-manet-smf] Macker, J. and S. Team, "Simplified Multicast
Forwarding", draft-ietf-manet-smf-09 (work in Forwarding", draft-ietf-manet-smf-10 (work in
progress), July 2009. progress), March 2010.
12.2. Informative References 12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. [RFC3410] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction and Applicability Stewart, "Introduction and Applicability
Statements for Internet-Standard Management Statements for Internet-Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
Appendix A. Change Log Appendix A. Change Log
This section tracks the revision history in the development of this This section tracks the revision history in the development of this
SMF-MIB. It will be removed from the final version of this document. SMF-MIB. It will be removed from the final version of this document.
These changes were made from draft-ietf-manet-dymo-mib-00 to These changes were made from draft-ietf-manet-smf-mib-01 to
draft-ietf-manet-dymo-mib-01. draft-ietf-manet-smf-mib-02.
1. Added the NotificationGroup to the MIB and updated the
ConformanceGroup.
2. Added the definition of an smfRouterID to the MIB. This is later
used in the Notifications to indicate the origin of the event to
the management station.
3. Removed the Router Priority object as this was used only in the
eCDS algorithm and hence should be contained within the future
eCDS-MIB.
4. Cleaned up the TEXTUAL CONVENTION for the `SmfOpMode'.
5. Filled in some of the missing text in various object
descriptions.
These changes were made from draft-ietf-manet-smf-mib-00 to
draft-ietf-manet-dsmf-mib-01.
1. Editorial changes to the textual material. These included the 1. Editorial changes to the textual material. These included the
addition of the paragraphs on TEXTUAL-CONVENTIONS defined and addition of the paragraphs on TEXTUAL-CONVENTIONS defined and
imported into this MIB and relationships to other MIBs. imported into this MIB and relationships to other MIBs.
2. Identified those objects in the SMF-MIB requiring non-volatile 2. Identified those objects in the SMF-MIB requiring non-volatile
storage. storage.
3. Changed the name of the TEXTUAL-CONVENTION 'Status', defined 3. Changed the name of the TEXTUAL-CONVENTION 'Status', defined
within this MIB to 'SmfStatus'. within this MIB to 'SmfStatus'.
Appendix B. Open Issues Appendix B. Open Issues
This section contains the set of open issues related to the This section contains the set of open issues related to the
development and design of the SMF-MIB. This section will not be development and design of the SMF-MIB. This section will not be
present in the final version of the MIB and will be removed once all present in the final version of the MIB and will be removed once all
the open issues have been resolved. the open issues have been resolved.
1. The text states 'NHDP RSSA Message TLV - if NHDP mode is 1. The SMF draft states that use of the SMF Type Message TLV is
selected, then is the RSSA Message TLV included in the NHDP optional and is used when the router runs NHDP. But the draft
exchanges.' Is this and the following two TLVs optional and are does not clearly state if the use of the SMF Address Block TLV is
they included as a group or independently of one another?]. also optional.
2. Is it useful to track the effectiveness of the coverage of the 2. Is it useful to track the effectiveness of the coverage of the
current RSSA? Is it possible to track this? current RSSA? Is it possible to track this?
3. Complete notification group. 3. Complete the security analysis and section.
4. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB.
5. Update the text of the document to reflect the final state of the
MIB.
6. Incorporate parameter relationship conditions into their
DESCRIPTION clauses.
7. Complete the security analysis and section.
8. Cleanup all the [TODOs] from the MIB template. 4. Cleanup all the [TODOs] from the MIB template.
Appendix C. Appendix C.
*************************************************************** ***************************************************************
* Note to the RFC Editor (to be removed prior to publication) * * Note to the RFC Editor (to be removed prior to publication) *
* * * *
* 1) The reference to RFCXXXX within the DESCRIPTION clauses * * 1) The reference to RFCXXXX within the DESCRIPTION clauses *
* of the MIB module point to this draft and are to be * * of the MIB module point to this draft and are to be *
* assigned by the RFC Editor. * * assigned by the RFC Editor. *
* * * *
* 2) The reference to RFCXXX2 throughout this document point * * 2) The reference to RFCXXX2 throughout this document point *
* to the current draft-ietf-manet-smf-xx.txt. This * * to the current draft-ietf-manet-smf-xx.txt. This *
* need to be replaced with the XXX RFC number. * * need to be replaced with the XXX RFC number. *
* * * *
*************************************************************** ***************************************************************
Authors' Addresses Authors' Addresses
Robert G. Cole Robert G. Cole
Johns Hopkins University US Army CERDEC
11100 Johns Hopkins Road, Room 257 328 Hopkins Road, Bldg 245
Laurel, Maryland 21073 Aberdeen Proving Ground, Maryland 21005
USA USA
Phone: +1 443 778 6951 Phone: +1 410 278 6779
EMail: robert.cole@jhuapl.edu EMail: robert.g.cole@us.army.mil
URI: http://www.cs.jhu.edu/~rgcole/ URI: http://www.cs.jhu.edu/~rgcole/
Joseph Macker Joseph Macker
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
USA USA
EMail: macker@itd.nrl.navy.mil EMail: macker@itd.nrl.navy.mil
Brian Adamson Brian Adamson
 End of changes. 84 change blocks. 
204 lines changed or deleted 575 lines changed or added

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