draft-ietf-manet-smf-mib-11.txt   draft-ietf-manet-smf-mib-12.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: September 24, 2014 B. Adamson Expires: January 31, 2015 B. Adamson
Naval Research Laboratory Naval Research Laboratory
March 23, 2014 July 30, 2014
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-11 draft-ietf-manet-smf-mib-12
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 module also reports state Networks (MANETs). The SMF-MIB module also reports state
information, performance information, and notifications. In addition information, performance information, and notifications. In addition
to configuration, the additional state and performance information is to 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 September 24, 2014. This Internet-Draft will expire on January 31, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 29 skipping to change at page 2, line 29
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 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
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 . . . . . . . . . . . . . 9 6.2. Relationship to the IP-MIB . . . . . . . . . . . . . . . . 9
6.3. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10 6.3. Relationship to the IPMCAST-MIB . . . . . . . . . . . . . 10
7. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 10 6.4. MIB modules required for IMPORTS . . . . . . . . . . . . . 10
8. IANA-SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . 51 6.5. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10
9. Security Considerations . . . . . . . . . . . . . . . . . . . 55 7. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 11
10. Applicability Statement . . . . . . . . . . . . . . . . . . . 58 8. IANA-SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . 52
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 9. Security Considerations . . . . . . . . . . . . . . . . . . . 56
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 62 10. Applicability Statement . . . . . . . . . . . . . . . . . . . 59
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 62 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 63
14.1. Normative References . . . . . . . . . . . . . . . . . . . 62 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 63
14.2. Informative References . . . . . . . . . . . . . . . . . . 63 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 64 14.1. Normative References . . . . . . . . . . . . . . . . . . . 63
14.2. Informative References . . . . . . . . . . . . . . . . . . 64
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 65
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
constructing an estimate of a MANET Minimum Connected Dominating Set constructing an estimate of a MANET Minimum Connected Dominating Set
skipping to change at page 9, line 43 skipping to change at page 9, line 43
6. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
6.1. Relationship to the SNMPv2-MIB 6.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB module [RFC3418] is defined as The 'system' group in the SNMPv2-MIB module [RFC3418] is defined as
being mandatory for all systems, and the objects apply to the entity being mandatory for all systems, and the objects apply to the entity
as a whole. The 'system' group provides identification of the as a whole. The 'system' group provides identification of the
management entity and certain other system-wide data. The SMF-MIB management entity and certain other system-wide data. The SMF-MIB
module does not duplicate those objects. module does not duplicate those objects.
6.2. MIB modules required for IMPORTS 6.2. Relationship to the IP-MIB
It is an expectation that SMF devices will implement the standard IP-
MIB module [RFC4293]. Exactly how to integrate SMF packet handling
and management into the standard IP-MIB module management are part of
the experiment.
The SMF-MIB module counters within the smfPerformanceGroup count
packets handled by the system and interface local SMF process (as
discussed above). Not all IP (unicast and multicast) packets on a
device interface are handled by the SMF process. So the counters are
tracking different packet streams in the IP-MIB and SMF-MIB modules.
6.3. Relationship to the IPMCAST-MIB
The smfCfgAddrForwardingTable is essentially a filter table (if
populated) that identifies addresses/packets to be forwarded via the
local SMF flooding process. The RFC 5132 IP Multicast MIB module
[RFC5132] manages objects related to standard IP multicast, which
could be running in parallel to SMF on the device.
RFC 5132 manages traditional IP-based multicast (based upon multicast
routing mechanisms). The SMF-MIB module provides management for a
MANET subnet-based flooding mechanism which, may be used for
multicast transport (through SMF broadcast) depending upon the MANET
dynamics and other factors regarding the MANET subnet. Further, they
may co-exist in certain MANET deployments using the
smfCfgAddrForwardingTable to hand certain IP multicast addresses to
the SMF process and other IP multicast packets to be forwarded by
other IP routed-based multicast mechanisms. SMF and the associated
SMF-MIB module are experimental and these are some of the experiments
to be had with SMF and the SMF-MIB module.
6.4. MIB modules required for IMPORTS
The textual conventions imported for use in the SMF-MIB module are as The textual conventions imported for use in the SMF-MIB module are as
follows. The MODULE-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-MIB Moduless 6.5. Relationship to the Future RSSA-MIB Moduless
In a sense, the SMF-MIB module is a general front-end to a set of, In a sense, the SMF-MIB module is a general front-end to a set of,
yet to be developed, RSSA-specific MIB modules. These RSSA-specific yet to be developed, RSSA-specific MIB modules. These RSSA-specific
MIB modules will define the objects for the configuration, state, MIB modules will define the objects for the configuration, state,
performance and notification required for the operation of these performance and notification required for the operation of these
specific RSSAs. The SMF-MIB module Capabilities Group allows the specific RSSAs. The SMF-MIB module Capabilities Group allows the
remote management station the ability to query the router to discover remote management station the ability to query the router to discover
the set of supported RSSAs. the set of supported RSSAs.
7. SMF-MIB Definitions 7. SMF-MIB Definitions
skipping to change at page 10, line 37 skipping to change at page 11, line 22
Counter32, Integer32, TimeTicks, experimental Counter32, Integer32, TimeTicks, experimental
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, ifName
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
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]
IANAsmfOpModeIdTC IANAsmfOpModeIdTC
FROM IANA-SMF-MIB FROM IANA-SMF-MIB
IANAsmfRssaIdTC IANAsmfRssaIdTC
FROM IANA-SMF-MIB FROM IANA-SMF-MIB
; ;
smfMIB MODULE-IDENTITY smfMIB MODULE-IDENTITY
LAST-UPDATED "201403231300Z" -- March 23, 2014 LAST-UPDATED "201407301300Z" -- July 30, 2014
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 11, line 45 skipping to change at page 12, line 31
adamson@itd.nrl.navy.mil" adamson@itd.nrl.navy.mil"
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: the Manet SMF RSSA process defined in:
[SMF] Macker, J.(ed.), [SMF] Macker, J.(ed.),
Simplified Multicast Forwarding, RFC 6621, Simplified Multicast Forwarding, RFC 6621,
May 2012. May 2012.
Copyright (C) The IETF Trust (2012). This version Copyright (C) The IETF Trust (2014). 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 "201403231300Z" -- March 23, 2014 REVISION "201407301300Z" -- July 30, 2014
DESCRIPTION DESCRIPTION
"The first version of this MIB module, "The first version of this MIB module,
published as RFC xxxx. published as RFC xxxx.
" "
-- RFC-Editor assigns xxxx -- RFC-Editor assigns xxxx
::= { experimental xxxx } -- to be assigned by IANA ::= { experimental xxxx } -- to be assigned by IANA
-- --
-- TEXTUAL CONVENTIONs -- TEXTUAL CONVENTIONs
-- --
skipping to change at page 15, line 34 skipping to change at page 16, line 20
SYNTAX SmfStatus SYNTAX SmfStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configured status of the SMF process "The configured status of the SMF process
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.
Prior to SNM functions being performed over Prior to SMF functions being performed over
specific interfaces, this object must first specific interfaces, this object must first
be 'enabled'. If this object is 'disabled', be 'enabled'. If this object is 'disabled',
then no SMF functions are being performed on then no SMF functions are being performed on
the device and all smfIfAdminStatus objects the device and all smfCfgIfAdminStatus objects
MUST also be set to 'disabled'. When this MUST also be set to 'disabled'. When this
object is changed from 'enabled' to 'disabled' object is changed from 'enabled' to 'disabled'
by the manager, then all smfIfAdminStatus by the manager, then all smfCfgIfAdminStatus
objects MUST also be automatically set to objects MUST also be automatically set to
'disabled' by the agent. 'disabled' by the agent.
The default value for this object SHOULD be The default value for this object SHOULD be
'enabled'. 'enabled'.
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 { enabled } DEFVAL { enabled }
::= { smfConfigurationGroup 1 } ::= { smfConfigurationGroup 1 }
smfCfgSmfSysUpTime OBJECT-TYPE smfCfgSmfSysUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time (in hundredths of a second) since the "The time (in hundredths of a second) since the
system SMF process was last re-initialized. system SMF process was last re-initialized.
skipping to change at page 22, line 32 skipping to change at page 23, line 18
-- --
-- Table identifying configured multicast addresses to be forwarded. -- Table identifying configured multicast addresses to be forwarded.
-- --
smfCfgAddrForwardingTable OBJECT-TYPE smfCfgAddrForwardingTable OBJECT-TYPE
SYNTAX SEQUENCE OF SmfCfgAddrForwardingEntry SYNTAX SEQUENCE OF SmfCfgAddrForwardingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table containing information on multicast "The smfCfgAddrForwardingTable is essentially a filter
table (if populated) that identifies addresses/packets
to be forwarded viaathe local SMF flooding process.
The RFC 5132 IP Multicast MIB module manages objects
related to standard IP multicast, which could be running
in parallel to SMF on the device.
RFC 5132 manages traditional IP-based multicast (based
upon multicast routing mechanisms). The SMF-MIB module
provides management for a MANET subnet-based flooding
mechanism which, may be used for multicast transport
(through SMF broadcast) depending upon the MANET dynamics
and other factors regarding the MANET subnet. Further,
they may co-exist in certain MANET deployments
using the smfCfgAddrForwardingTable to hand certain IP
multicast addresses to the SMF process and other IP
multicast packets to be forwarded by other IP
routed-based multicast mechanisms. SMF and the
associated SMF-MIB module are experimental and these
are some of the experiments to be had with SMF and
the SMF-MIB module.
This is the (conceptual) table containing information on
multicast addresses which are to be forwarded by the SMF multicast addresses which are to be forwarded by the SMF
process. This table represents an IP filters table for process. This table represents an IP filters table for
forwarding (or not) packets based upon their IP forwarding (or not) packets based upon their IP
multicast address. multicast address.
The SMF process can be configured to forward only those The SMF process can be configured to forward only those
multicast addresses found within the multicast addresses found within the
smfCfgAddrForwardingTable. As such, addresses which are smfCfgAddrForwardingTable. As such, addresses which are
to be forwarded by the SMF process MUST be found within to be forwarded by the SMF process MUST be found within
the address ranges configured within this table, unless the address ranges configured within this table, unless
skipping to change at page 26, line 17 skipping to change at page 27, line 24
this table 'sparse augments' the ifTable this table 'sparse augments' the ifTable
specifically when SMF is to be configured to specifically when SMF is to be configured to
operate over this interface. operate over this interface.
A conceptual row in this table exists if and only A conceptual row in this table exists if and only
if either a manager has explicitly created the row if either a manager has explicitly created the row
or there is an interface on the managed device or there is an interface on the managed device
that automatically supports and runs SMF as part that automatically supports and runs SMF as part
of the device's initialization process. of the device's initialization process.
The smfCfgIfRowStatus controls the creation
of the rows in the smfCfgInterfaceTable. As
this table only 'sparse augments' the ifTable,
rows in the smfCfgInterfaceTable MAY exist
only if a corresponding row exists in the ifTable.
Although the existance of a row in the ifTable
does not imply a corresponding row in the
smfCfgInterfaceTable. However, rows in the
smfCfgInterfaceTable MUST NOT exist if a
corresponding row in the ifTable is
non-existent.
The manager creates a row in this table by setting The manager creates a row in this table by setting
rowStatus to 'createAndGo' or 'createAndWait'. rowStatus to 'createAndGo' or 'createAndWait'.
Row objects having associated DEFVAL clauses are Row objects having associated DEFVAL clauses are
automatically defined by the agent with these automatically defined by the agent with these
values during row creation, unless the manager values during row creation, unless the manager
explicitly defines these object values during the explicitly defines these object values during the
row creation. row creation.
The value of the smfCfgIfAdminStatus is independent As the smfCfgInterfaceTable sparsely augments the
of the value of the associated ifAdminStatus. IfTable. Hence,
The value of the smfCfgIfAdminStatus can be
'enabled' or 'disabled' when the value of the
smfCfgAdminStatus is 'enabled'. However, if the
value of the smfCfgAdminStatus is 'disabled',
then all rows in the smfCfgInterfaceTable
MUST be removed.
If the value of smfCfgIfAdminStatus is 'disabled', + an entry cannot exist in smfCfgInterfaceTable
then the value of the corresponding without a corresponding entry in the ifTable.
smfCfgIfRowStatus MUST be set to 'notInService'.
While the value of smfCfgIfRowStatus MAY be + if an entry in the ifTable is removed, the
'active' or 'notInService' when smfCfgIfAdminStatus corresponding entry (if it exists) in the
is set to 'enabled', depending on the state of smfCfgInterfaceTable MUST be removed.
the other objects in the corresponding row."
+ the smfCfgIfStatus can have a value of
'enabled' or 'disabled' independent of the
current value of the ifAdminStatus of the
corresponding entry in the ifTable.
The values of the objects smfCfgAdminStatus and
smfCfgIfAdminStatus reflect the up-down status of
the SMF process running on the device and on the
specific interfaces respectively. Hence,
+ the value of the smfCfgAdminStatus can be
'enabled' or 'disabled' reflecting the current
running status of the SMF process on the device.
+ the value of the smfCfgIfAdminStatus can be
'enabled' or 'disabled' if the value of the
smfCfgAdminStatus is set to 'enabled'.
+ if the value of the smfCfgAdminStatus is
'disabled', then the corresponding
smfCfgIfAdminStatus objects MUST be set
to 'disabled' in the smfCfgInterfaceTable.
+ once the value of the smfCfgAdminStatus changes
from 'disabled' to 'enabled', it is up to the
management system to make the corresponding
changes to the smfCfgIfAdminStatus values
back to 'enabled'.
"
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 14 }
smfCfgInterfaceEntry OBJECT-TYPE smfCfgInterfaceEntry OBJECT-TYPE
SYNTAX SmfCfgInterfaceEntry SYNTAX SmfCfgInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 27, line 30 skipping to change at page 28, line 48
non-volatile storage. For further information non-volatile storage. For further information
on the storage behavior for these objects, refer on the storage behavior for these objects, refer
to the description for the smfCfgIfRowStatus to the description for the smfCfgIfRowStatus
object." object."
INDEX { smfCfgIfIndex } INDEX { smfCfgIfIndex }
::= { smfCfgInterfaceTable 1 } ::= { smfCfgInterfaceTable 1 }
SmfCfgInterfaceEntry ::= SmfCfgInterfaceEntry ::=
SEQUENCE { SEQUENCE {
smfCfgIfIndex InterfaceIndexOrZero, smfCfgIfIndex InterfaceIndexOrZero,
smfCfgIfName SnmpAdminString,
smfCfgIfAdminStatus SmfStatus, smfCfgIfAdminStatus SmfStatus,
smfCfgIfSmfUpTime TimeTicks, smfCfgIfSmfUpTime TimeTicks,
smfCfgIfRowStatus RowStatus smfCfgIfRowStatus RowStatus
} }
smfCfgIfIndex OBJECT-TYPE smfCfgIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 28, line 4 skipping to change at page 29, line 21
MUST correspond to an ifIndex referring MUST correspond to an ifIndex referring
to a valid entry in The Interfaces Table. to a valid entry in The Interfaces Table.
If the manager attempts to create a row If the manager attempts to create a row
for which the ifIndex does not exist on the for which the ifIndex does not exist on the
local device, then the agent SHOULD issue local device, then the agent SHOULD issue
a return value of 'inconsistentValue' and a return value of 'inconsistentValue' and
the operation SHOULD fail." the operation SHOULD fail."
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."
::= { smfCfgInterfaceEntry 1 } ::= { smfCfgInterfaceEntry 1 }
smfCfgIfName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The textual name of the interface. The value of this
object SHOULD be the name of the interface as assigned by
the local device. This can be a text-name, such as 'le0'
or a simple port number, such as '1',
depending on the interface-naming syntax of the device.
If there is no local name or this object is otherwise not
applicable, then this object contains a zero-length string."
::= { smfCfgInterfaceEntry 2 }
smfCfgIfAdminStatus OBJECT-TYPE smfCfgIfAdminStatus OBJECT-TYPE
SYNTAX SmfStatus SYNTAX SmfStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMF interface's administrative status. "The SMF interface's administrative status.
The value 'enabled' denotes that the interface The value 'enabled' denotes that the interface
is running the SMF forwarding process. is running the SMF forwarding process.
The value 'disabled' denotes that the interface is The value 'disabled' denotes that the interface is
currently external to the SMF forwarding process. currently external to the SMF forwarding process.
The value of the smfCfgIfAdminStatus MAY be either When the value of the smfCfgAdminStatus is
'enabled' or 'disabled' when the value of the 'disabled', then the corresponding smfCfgIfAdminStatus
smfCfgAdminStatus object is 'enabled'. When the objects MUST be set to 'disabled' in the
value of the smfCfgAdminStatus is 'disabled', then smfCfgInterfaceTable.
all rows in this table MUST be removed.
The default value for this object is 'enabled(1)'. The default value for this object is 'enabled(1)'.
This object SHOULD be persistent and when This object SHOULD be persistent and when
written the device SHOULD save the change to written the device SHOULD save the change to
non-volatile storage." non-volatile storage."
DEFVAL { enabled } DEFVAL { enabled }
::= { smfCfgInterfaceEntry 3 } ::= { smfCfgInterfaceEntry 2 }
smfCfgIfSmfUpTime OBJECT-TYPE smfCfgIfSmfUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time (in hundredths of a second) since "The time (in hundredths of a second) since
this interface SMF process was last this interface SMF process was last
re-initialized. The interface SMF process re-initialized. The interface SMF process
is re-initialized when the corresponding is re-initialized when the corresponding
'smfCfgIfRowStatus' object transits to 'smfCfgIfRowStatus' object transits to
the 'active' state." the 'active' state."
::= { smfCfgInterfaceEntry 4 } ::= { smfCfgInterfaceEntry 3 }
smfCfgIfRowStatus OBJECT-TYPE smfCfgIfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object permits management of this table "This object permits management of this table
by facilitating actions such as row creation, by facilitating actions such as row creation,
construction, and destruction. The value of construction, and destruction. The value of
this object has no effect on whether other this object has no effect on whether other
objects in this conceptual row can be objects in this conceptual row can be
modified. modified.
An entry may not exist in the 'active' state unless all An entry may not exist in the 'active' state unless all
objects in the entry have a defined appropriate value. For objects in the entry have a defined appropriate value. For
objects with DEFVAL clauses, the management station objects with DEFVAL clauses, the management station
does not need to specify the value of this object in order does not need to specify the value of these objects in order
for the row to transit to the 'active' state; the default for the row to transit to the 'active' state; the default
value for this object is used. For objects that do not value for these objects is used. For objects that do not
have DEFVAL clauses, then the network manager MUST have DEFVAL clauses, then the network manager MUST
specify the value of this object prior to this row specify the value of these objects prior to this row
transitioning to the 'active' state. transitioning to the 'active' state.
This object should be set to 'active' only if the
corresponding smfCfgIfAdminStatus is set to 'enabled'.
If the smfCfgIfAdminStatus is set to 'disabled', then the
value of the smfCfgIfRowStatus MAY be set to either
'notInService' or 'notReady' depending upon the values
of the other row objects.
Rows in this table SHOULD exist only if the value of
the smfCfgAdminStatus is 'enabled'. If this object
value changes to 'disabled', then all rows in this table
MUST be removed.
When this object transitions to 'active', all objects When this object transitions to 'active', all objects
in this row SHOULD be written to non-volatile (stable) in this row SHOULD be written to non-volatile (stable)
storage. Read-create objects in this row MAY be modified. storage. Read-create objects in this row MAY be modified.
When an object in a row with smfCfgIfRowStatus of 'active' When an object in a row with smfCfgIfRowStatus of 'active'
is changed, then the updated value MUST be reflected in SMF is changed, then the updated value MUST be reflected in SMF
and this new object value MUST be written to non-volatile and this new object value MUST be written to non-volatile
storage. storage.
If this object is not equal to 'active', all associated If this object is not equal to 'active', all associated
entries in the smfPerfIpv4InterfacePerfTable and the entries in the smfPerfIpv4InterfacePerfTable and the
smfPerfIpv6InterfacePerfTable MUST be deleted." smfPerfIpv6InterfacePerfTable MUST be deleted."
::= { smfCfgInterfaceEntry 5 } ::= { smfCfgInterfaceEntry 4 }
-- --
-- smfStateGroup -- smfStateGroup
-- --
-- Contains information describing the current state of the SMF -- Contains information describing the current state of the SMF
-- process such as the current inclusion in the RS or not. -- process such as the current inclusion in the RS or not.
-- --
smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 }
smfStateNodeRsStatusIncluded OBJECT-TYPE smfStateNodeRsStatusIncluded OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current status of the SMF node in the context of "The current status of the SMF node in the context of
skipping to change at page 33, line 19 skipping to change at page 34, line 8
::= { smfStateNeighborEntry 6 } ::= { smfStateNeighborEntry 6 }
-- --
-- SMF Performance Group -- SMF Performance Group
-- --
-- Contains objects which help to characterize the -- Contains objects which help to characterize the
-- performance of the SMF RSSA process, such as statistics -- performance of the SMF RSSA process, such as statistics
-- counters. There are two types of SMF RSSA statistics: -- counters. There are two types of SMF RSSA statistics:
-- global counters and per interface counters. -- global counters and per interface counters.
-- --
-- It is an expectation that SMF devices will
-- implement the standard IP-MIB module RFC4293.
-- Exactly how to integrate SMF packet handling and
-- management into the standard IP-MIB module management
-- are part of the experiment.
--
-- The SMF-MIB module counters within the
-- smfPerformanceGroup count packets handled by the
-- system and interface local SMF process (as discussed
-- above). Not all IP (unicast and multicast) packets
-- on a device interface are handled by the SMF process.
-- So the counters are tracking different packet streams
-- in the IP-MIB and SMF-MIB modules.
--
smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 }
smfPerfGobalGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } smfPerfGobalGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 }
-- --
-- IPv4 packet counters -- IPv4 packet counters
-- --
smfPerfIpv4MultiPktsRecvTotal OBJECT-TYPE smfPerfIpv4MultiPktsRecvTotal OBJECT-TYPE
skipping to change at page 46, line 15 skipping to change at page 47, line 18
"smfNotifConfiguredOpModeChange is a notification "smfNotifConfiguredOpModeChange is a notification
sent when the 'smfCfgOperationalMode' object sent when the 'smfCfgOperationalMode' object
changes." changes."
::= { smfMIBNotifObjects 2 } ::= { smfMIBNotifObjects 2 }
smfNotifIfAdminStatusChange NOTIFICATION-TYPE smfNotifIfAdminStatusChange NOTIFICATION-TYPE
OBJECTS { smfCfgRouterIDAddrType, -- The originator of OBJECTS { smfCfgRouterIDAddrType, -- The originator of
-- the notification. -- the notification.
smfCfgRouterID, -- The originator of smfCfgRouterID, -- The originator of
-- the notification. -- the notification.
smfCfgIfName, -- The interface whose ifName, -- The interface whose
-- status has changed. -- status has changed.
smfCfgIfAdminStatus -- The new status of the smfCfgIfAdminStatus -- The new status of the
-- SMF interface. -- SMF interface.
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"smfCfgIfAdminStatusChange is a notification sent when a "smfCfgIfAdminStatusChange is a notification sent when a
the 'smfCfgIfAdminStatus' object changes." the 'smfCfgIfAdminStatus' object changes."
::= { smfMIBNotifObjects 3 } ::= { smfMIBNotifObjects 3 }
skipping to change at page 49, line 4 skipping to change at page 50, line 6
smfCfgRouterIDAddrType, smfCfgRouterIDAddrType,
smfCfgRouterID, smfCfgRouterID,
smfCfgOperationalMode, smfCfgOperationalMode,
smfCfgRssaMember, smfCfgRssaMember,
smfCfgIpv4Dpd, smfCfgIpv4Dpd,
smfCfgIpv6Dpd, smfCfgIpv6Dpd,
smfCfgMaxPktLifetime, smfCfgMaxPktLifetime,
smfCfgDpdEntryMaxLifetime, smfCfgDpdEntryMaxLifetime,
smfCfgNhdpRssaMesgTLVIncluded, smfCfgNhdpRssaMesgTLVIncluded,
smfCfgNhdpRssaAddrBlockTLVIncluded, smfCfgNhdpRssaAddrBlockTLVIncluded,
smfCfgAddrForwardingGroupName, smfCfgAddrForwardingGroupName,
smfCfgAddrForwardingAddrType, smfCfgAddrForwardingAddrType,
smfCfgAddrForwardingAddress, smfCfgAddrForwardingAddress,
smfCfgAddrForwardingAddrPrefixLength, smfCfgAddrForwardingAddrPrefixLength,
smfCfgAddrForwardingStatus, smfCfgAddrForwardingStatus,
smfCfgIfName,
smfCfgIfAdminStatus, smfCfgIfAdminStatus,
smfCfgIfSmfUpTime, smfCfgIfSmfUpTime,
smfCfgIfRowStatus smfCfgIfRowStatus
} }
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 }
skipping to change at page 52, line 14 skipping to change at page 53, line 14
IANA-SMF-MIB DEFINITIONS ::= BEGIN IANA-SMF-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2 MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
ianaSmfMIB MODULE-IDENTITY ianaSmfMIB MODULE-IDENTITY
LAST-UPDATED "201403231300Z" -- March 23, 2014 LAST-UPDATED "201407301300Z" -- July 30, 2014
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO "Internet Assigned Numbers Authority CONTACT-INFO "Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292 Marina del Rey, CA 90292
Tel: +1 310 823 9358 Tel: +1 310 823 9358
E-Mail: iana@iana.org" E-Mail: iana@iana.org"
DESCRIPTION "This MIB module defines the DESCRIPTION "This MIB module defines the
IANAsmfOpModeIdTC and IANAsmfRssaIdTC IANAsmfOpModeIdTC and IANAsmfRssaIdTC
Textual Conventions, and thus the Textual Conventions, and thus the
enumerated values of the enumerated values of the
smfCapabilitiesOpModeID and smfCapabilitiesOpModeID and
smfCapabilitiesRssaID objects defined smfCapabilitiesRssaID objects defined
in the SMF-MIB." in the SMF-MIB."
REVISION "201403231300Z" -- March 23, 2014 REVISION "201407301300Z" -- July 30, 2014
DESCRIPTION "Initial version of this MIB as published in DESCRIPTION "Initial version of this MIB as published in
RFC KKKK." RFC KKKK."
::= { mib-2 kkkk } ::= { mib-2 kkkk }
IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION IANAsmfOpModeIdTC ::= 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
SMF operations mode. There are basically three styles SMF operations mode. There are basically three styles
of SMF operation with reduced relay sets currently of SMF operation with reduced relay sets currently
skipping to change at page 56, line 5 skipping to change at page 57, line 5
Address List' as defined in NHDP. A smfCfgRouterID MUST be unique Address List' as defined in NHDP. A smfCfgRouterID MUST be unique
within the scope of the operating MANET network regardless of the within the scope of the operating MANET network regardless of the
method used for selecting it. If these objects are mis-configured method used for selecting it. If these objects are mis-configured
or configured in-consistently across the MANET, then the ability or configured in-consistently across the MANET, then the ability
of various RSSA algorithms, e.g., ECDS, may be compromised. This of various RSSA algorithms, e.g., ECDS, may be compromised. This
would potentially result in some routers within the MANET not would potentially result in some routers within the MANET not
receiving multicast packets destine to them. Hence, intentionally receiving multicast packets destine to them. Hence, intentionally
mis-configuring these objects could pose a form of Denial-of- mis-configuring these objects could pose a form of Denial-of-
Service (DOS) attack against the MANET. Service (DOS) attack against the MANET.
o 'smfCfgOpMode' - this writable configuration objects define the o 'smfCfgOpMode' - this writable configuration object defines the
operational mode of the SMF process. The operational mode defines operational mode of the SMF process. The operational mode defines
how the SMF process receives its data to form its local estimate how the SMF process receives its data to form its local estimate
of the CDS. It is recommended that the value for this object be of the CDS. It is recommended that the value for this object be
set consistently across the MANET to ensure proper operation of set consistently across the MANET to ensure proper operation of
the multicast packet forwarding. If the value for this object is the multicast packet forwarding. If the value for this object is
set inconsistently across the MANET, the result may be that set inconsistently across the MANET, the result may be that
multicast packet delivery will be compromised within the MANET. multicast packet delivery will be compromised within the MANET.
Hence, intentionally mis-configuring this object could pose a form Hence, intentionally mis-configuring this object could pose a form
DOS attack against the MANET. DOS attack against the MANET.
skipping to change at page 57, line 16 skipping to change at page 58, line 16
sets the maximum lifetime (in seconds) for the cached DPD records sets the maximum lifetime (in seconds) for the cached DPD records
for the combined IPv4 and IPv6 methods. If the memory is running for the combined IPv4 and IPv6 methods. If the memory is running
low prior to the MaxLifetime being exceeded, the local SMF devices low prior to the MaxLifetime being exceeded, the local SMF devices
should purge the oldest records first. If this object value is should purge the oldest records first. If this object value is
set too small, then the effectiveness of the SMF DPD algorithms set too small, then the effectiveness of the SMF DPD algorithms
may become greatly diminished causing a higher than necessary may become greatly diminished causing a higher than necessary
packet load on the MANET. packet load on the MANET.
o 'smfCfgNhdpRssaMesgTLVIncluded' - this writable configuration o 'smfCfgNhdpRssaMesgTLVIncluded' - this writable configuration
object indicates whether the associated NHDP messages include the object indicates whether the associated NHDP messages include the
the RSSA Message TLV, or not. It is highly RECOMMENDED that this RSSA Message TLV, or not. It is highly RECOMMENDED that this
object be set to 'true(1)' when the SMF operation mode is set to object be set to 'true(1)' when the SMF operation mode is set to
independent as this information will inform the local forwarder of independent as this information will inform the local forwarder of
the RSSA algorithm implemented in neighboring forwarders and is the RSSA algorithm implemented in neighboring forwarders and is
used to ensure consistent forwarding across the MANET. While it used to ensure consistent forwarding across the MANET. While it
is possible that SMF neighbors MAY be configured differently with is possible that SMF neighbors MAY be configured differently with
respect to the RSSA algorithm and still operate cooperatively, but respect to the RSSA algorithm and still operate cooperatively, but
these cases will vary dependent upon the algorithm types these cases will vary dependent upon the algorithm types
designated and this situation SHOULD be avoided. designated and this situation SHOULD be avoided.
o 'smfCfgNhdpRssaAddrBlockTLVIncluded' - this writable configuration o 'smfCfgNhdpRssaAddrBlockTLVIncluded' - this writable configuration
skipping to change at page 61, line 15 skipping to change at page 62, line 15
snmpset [options] <smfCfgOperationalMode>.0 i 2 snmpset [options] <smfCfgOperationalMode>.0 i 2
then the local forwarder would switch if forwarding behavior from then the local forwarder would switch if forwarding behavior from
Classical Flooding to the more efficient eCDS flooding. Classical Flooding to the more efficient eCDS flooding.
11. IANA Considerations 11. IANA Considerations
This document defines two MIB modules: This document defines two MIB modules:
o SMF-MIB is defined in Section 7 and is an experimental MIB module o SMF-MIB is defined in Section 7 and is an experimental MIB module.
o IANA-SMF-MIB is defined in Section 8 and is an IANA MIB module o IANA-SMF-MIB is defined in Section 8 and is an IANA MIB module
that IANA is requested to maintain that IANA is requested to maintain.
Thus, there are three actions requested of IANA: Thus, there are three actions requested of IANA:
1. IANA is requested to allocate an OBJECT IDENTIFIER value and 1. IANA is requested to allocate an OBJECT IDENTIFIER value and
record it in the SMI Numbers registry in the sub-registry called "SMI record it in the SMI Numbers registry in the sub-registry called "SMI
Experimental Codes" under the experimental branch (1.3.6.1.3). Experimental Codes" under the experimental branch (1.3.6.1.3).
Decimal | Name | Description | Reference Decimal | Name | Description | Reference
--------+---------+---------------+------------ --------+---------+---------------+------------
xxxx | smfMib | SMF-MIB | [This.I-D] xxxx | smfMib | SMF-MIB | [This.I-D]
skipping to change at page 62, line 14 skipping to change at page 63, line 14
12. Contributors 12. 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.
13. Acknowledgements 13. 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 and Harnedy in the early phases of the development of this MIB module.
from Dan Romascanu in the final reviews of this MIB module. The The authors would like to thank Adrian Farrel, Dan Romascanu, Juergen
authors would like to thank James Nguyen for his careful review and Shoenwaelder, Stephen Hanna, and Brian Haberman for their careful
comments on this MIB module and his work on the definitions of the review of this documenti and their insightful comments. We also wish
follow-on MIB modules to configure specific RSSA algorithms related to thank the entire MANET WG for many reviews of this document.
to SMF. Further, the authors would like to acknowledge to work of Further the authors would like to thank James Nguyen for his careful
James Nguyen, Brian Little, Ryan Morgan and Justin Dean on their review and comments on this MIB module and his work on the
software development of the SMF-MIB. 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, Ryan Morgan and
Justin Dean on their software development of the SMF-MIB.
14. References 14. References
14.1. Normative References 14.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.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[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
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002. RFC 3418, December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
skipping to change at page 63, line 14 skipping to change at page 64, line 22
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621, [RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621,
May 2012. May 2012.
14.2. Informative References 14.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.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, June 2004. SNMP User-based Security Model", RFC 3826, June 2004.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", for the Simple Network Management Protocol (SNMP)",
RFC 5591, June 2009. STD 78, RFC 5591, June 2009.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, June 2009. Protocol (SNMP)", RFC 5592, June 2009.
[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. STD 78, RFC 6353, July 2011.
[RFC4293] Routhier, S., "Management Information Base for the
Internet Protocol (IP)", RFC 4293, April 2006.
[RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast
MIB", RFC 5132, December 2007.
Appendix A. Appendix A.
*************************************************************** ***************************************************************
* 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 throughout this document point * * 1) The reference to RFCXXXX throughout this document point *
* to the current draft-ietf-manet-smf-xx.txt. This needs * * to the current draft-ietf-manet-smf-xx.txt. This needs *
* to be replaced with the XXXX RFC number for the SMF * * to be replaced with the XXXX RFC number for the SMF *
* publication. * * publication. *
 End of changes. 47 change blocks. 
118 lines changed or deleted 177 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/