draft-ietf-manet-smf-mib-05.txt   draft-ietf-manet-smf-mib-06.txt 
Internet Engineering Task Force R. Cole Internet Engineering Task Force R. Cole
Internet-Draft US Army CERDEC Internet-Draft US Army CERDEC
Intended status: Experimental J. Macker Intended status: Experimental J. Macker
Expires: May 4, 2013 B. Adamson Expires: June 4, 2013 B. Adamson
Naval Research Laboratory Naval Research Laboratory
November 05, 2012 December 1, 2012
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-05 draft-ietf-manet-smf-mib-06
Abstract Abstract
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 the In particular, it describes objects for configuring aspects of the
Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc
Networks (MANETs). The SMF-MIB also reports state information, Networks (MANETs). The SMF-MIB also reports state information,
performance metrics, and notifications. In addition to performance metrics, and notifications. In addition to
configuration, the additional state and performance information is configuration, the additional state and performance information is
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 4, 2013. This Internet-Draft will expire on June 4, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 35 skipping to change at page 2, line 35
5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8
5.7. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 5.7. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9
6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 10
6.3. Relationship to the Future RSSA-MIBs . . . . . . . . . . . 10 6.3. Relationship to the Future RSSA-MIBs . . . . . . . . . . . 10
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 52 8. Security Considerations . . . . . . . . . . . . . . . . . . . 52
9. Applicability Statement . . . . . . . . . . . . . . . . . . . 55 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 55
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 56 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 57
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 56 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 57
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57
13.1. Normative References . . . . . . . . . . . . . . . . . . . 56 13.1. Normative References . . . . . . . . . . . . . . . . . . . 57
13.2. Informative References . . . . . . . . . . . . . . . . . . 57 13.2. Informative References . . . . . . . . . . . . . . . . . . 58
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 58 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 58
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 59 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 60
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 60
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) [RFC6621] process implementing Simplified Multicast Forwarding (SMF) [RFC6621]
for Mobile Ad-Hoc Networks (MANETs). SMF provides multicast for Mobile Ad-Hoc Networks (MANETs). SMF provides multicast
Duplicate Packet Detection (DPD) and supports algorithms for Duplicate Packet Detection (DPD) and supports algorithms for
skipping to change at page 6, line 9 skipping to change at page 6, line 9
This section presents the structure of the SMF-MIB module. The This section presents the structure of the SMF-MIB module. The
objects are arranged into the following groups: objects are arranged into the following groups:
o smfMIBNotifications - defines the notifications associated with o smfMIBNotifications - defines the notifications associated with
the SMF-MIB. the SMF-MIB.
o smfMIBObjects - defines the objects forming the basis for the SMF- o smfMIBObjects - defines the objects forming the basis for the SMF-
MIB. These objects are divided up by function into the following MIB. These objects are divided up by function into the following
groups: groups:
o
* Capabilities Group - This group contains the SMF objects that * Capabilities Group - This group contains the SMF objects that
the device uses to advertise its local capabilities with the device uses to advertise its local capabilities with
respect to, e.g., the supported RSSAs. respect to, e.g., the supported RSSAs.
* Configuration Group - This group contains the SMF objects that * Configuration Group - This group contains the SMF objects that
configure specific options that determine the overall operation configure specific options that determine the overall operation
of the SMF RSSA and the resulting multicast performance. of the SMF RSSA and the resulting multicast performance.
* State Group - Contains information describing the current state * State Group - Contains information describing the current state
of the SMF RSSA process such as the Neighbor Table. of the SMF RSSA process such as the Neighbor Table.
skipping to change at page 7, line 51 skipping to change at page 7, line 51
node and per interface objects: node and per interface objects:
o Total multicast packets received. o Total multicast packets received.
o Total multicast packets forwarded. o Total multicast packets forwarded.
o Total duplicate multicast packets detected. o Total duplicate multicast packets detected.
o Per interface statistics table with the following entries: o Per interface statistics table with the following entries:
o
* 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 Sub-tree contains the list of notifications The Notifications Sub-tree 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.
skipping to change at page 11, line 14 skipping to change at page 11, line 14
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]
; ;
smfMIB MODULE-IDENTITY smfMIB MODULE-IDENTITY
LAST-UPDATED "201211051300Z" -- November 05, 2012 LAST-UPDATED "201212011300Z" -- December 01, 2012
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG Chairs: sratliff@cisco.com WG Chairs: sratliff@cisco.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Robert G. Cole Editors: Robert G. Cole
US Army CERDEC US Army CERDEC
Space and Terrestrial Communications Space and Terrestrial Communications
skipping to change at page 12, line 10 skipping to change at page 12, line 10
[SMF] Macker, J.(ed.), [SMF] Macker, J.(ed.),
Simplified Multicast Forwarding, RFC XXXX, Simplified Multicast Forwarding, RFC XXXX,
July 2012. July 2012.
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 "201212011300Z" -- December 01, 2012
DESCRIPTION
"Updated 9th revision of the
draft of this MIB module published as
draft-ietf-manet-smf-mib-06.txt. The changes
made in this revision to the SMF-MIB include:
- None. Only changes to the surrounding
textual material associated with this
MIB module."
REVISION "201211051300Z" -- November 05, 2012 REVISION "201211051300Z" -- November 05, 2012
DESCRIPTION DESCRIPTION
"Updated 8th revision of the "Updated 8th revision of the
draft of this MIB module published as draft of this MIB module published as
draft-ietf-manet-smf-mib-05.txt. The changes draft-ietf-manet-smf-mib-05.txt. The changes
made in this revision include: made in this revision include:
- Updated the smfInterfaceTable to reflect a - Updated the smfInterfaceTable to reflect a
sparse augmentation of the ifTable. sparse augmentation of the ifTable.
- Added text discussing the tables and their - Added text discussing the tables and their
indexing. indexing.
skipping to change at page 52, line 45 skipping to change at page 53, line 15
o 'smfAdminStatus' - this writable configuration object controls the o 'smfAdminStatus' - this writable configuration object controls the
operational status of the SMF process. If this setting is operational status of the SMF process. If this setting is
configured inconsistently across the MANET multicast domain, then configured inconsistently across the MANET multicast domain, then
delivery of multicast data may be inconsistent across the domain; delivery of multicast data may be inconsistent across the domain;
some nodes may not receive multicast data intended for them. some nodes may not receive multicast data intended for them.
o 'smfRouterIDAddrType' and 'smfRouterID' - these writable o 'smfRouterIDAddrType' and 'smfRouterID' - these writable
configuration objects define the ID of the SMF process. These configuration objects define the ID of the SMF process. These
objects should be configured with a routable address defined on objects should be configured with a routable address defined on
the local SMF device. The smfRouterID is a logical identification the local SMF device. The smfRouterID is a logical identification
that MUST be consistent across interoperating SMF neighborhoods that MUST be consistent across inter-operating SMF neighborhoods
and it is RECOMMENDED to be chosen as the numerically largest and it is RECOMMENDED to be chosen as the numerically largest
address contained in a node's 'Neighbor Address List' as defined address contained in a node's 'Neighbor Address List' as defined
in NHDP. A smfRouterID MUST be unique within the scope of the in NHDP. A smfRouterID MUST be unique within the scope of the
operating MANET network regardless of the method used for operating MANET network regardless of the method used for
selecting it. selecting it.
o 'smfConfiguredOpMode' - this writable configuration objects define o 'smfConfiguredOpMode' - this writable configuration objects define
the operational mode of the SMF process. The operational mode the operational mode of the SMF process. The operational mode
defines how the SMF process develops its local estimate of the defines how the SMF process develops its local estimate of the
CDS. CDS.
skipping to change at page 56, line 45 skipping to change at page 57, line 15
11. Contributors 11. Contributors
This MIB document uses the template authored by D. Harrington which This MIB document uses the template authored by D. Harrington which
is based on contributions from the MIB Doctors, especially Juergen is based on contributions from the MIB Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn.
12. Acknowledgements 12. Acknowledgements
The authors would like to acknowledge the valuable comments from Sean The authors would like to acknowledge the valuable comments from Sean
Harnedy in the early phases of the development of this MIB-module. Harnedy in the early phases of the development of this MIB-module.
The authors would like to thank James Nguyen for his careful review
and comments on this MIB-module and his work on the definitions of
the follow on MIB-modules to configure specific RSSA algorithms
related to SMF. Further, the authors would like to acknowledge to
work of James Nguyen, Brian Little and Ryan Morgan on their software
development of the SMF-MIB.
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
skipping to change at page 58, line 18 skipping to change at page 58, line 43
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
RFC 6353, July 2011. RFC 6353, July 2011.
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-smf-mib-05 to
draft-ietf-manet-smf-mib-06.
1. Only minor editorial and formatting changes were made to this
document revision. No substantive changes were made to the SMF-
MIB module itself.
These changes were made from draft-ietf-manet-smf-mib-04 to These changes were made from draft-ietf-manet-smf-mib-04 to
draft-ietf-manet-smf-mib-05. draft-ietf-manet-smf-mib-05.
1. Updated the smfInterfaceTable to reflect that fact that we want 1. Updated the smfInterfaceTable to reflect that fact that we want
it to 'sparsely augment' the ifTable. it to 'sparsely augment' the ifTable.
2. Added a section to the text discussing the SMF Tables and their 2. Added a section to the text discussing the SMF Tables and their
indexing. indexing.
3. Added the section on 'Applicability Statement'. 3. Added the section on 'Applicability Statement'.
skipping to change at page 59, line 4 skipping to change at page 59, line 37
These changes were made from draft-ietf-manet-smf-mib-02 to These changes were made from draft-ietf-manet-smf-mib-02 to
draft-ietf-manet-smf-mib-03. draft-ietf-manet-smf-mib-03.
1. Clarified and added discussion of default values for several of 1. Clarified and added discussion of default values for several of
the configuration objects within the MIB. the configuration objects within the MIB.
2. Added the security section. 2. Added the security section.
These changes were made from draft-ietf-manet-smf-mib-01 to These changes were made from draft-ietf-manet-smf-mib-01 to
draft-ietf-manet-smf-mib-02.
1. Added the NotificationGroup to the MIB and updated the 1. Added the NotificationGroup to the MIB and updated the
ConformanceGroup. ConformanceGroup.
2. Added the definition of an smfRouterID to the MIB. This is later 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 used in the Notifications to indicate the origin of the event to
the management station. the management station.
3. Removed the Router Priority object as this was used only in the 3. Removed the Router Priority object as this was used only in the
eCDS algorithm and hence should be contained within the future eCDS algorithm and hence should be contained within the future
eCDS-MIB. eCDS-MIB.
 End of changes. 14 change blocks. 
15 lines changed or deleted 36 lines changed or added

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