draft-ietf-manet-smf-mib-10.txt   draft-ietf-manet-smf-mib-11.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 9, 2014 B. Adamson Expires: September 24, 2014 B. Adamson
Naval Research Laboratory Naval Research Laboratory
March 8, 2014 March 23, 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-10 draft-ietf-manet-smf-mib-11
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 9, 2014. This Internet-Draft will expire on September 24, 2014.
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 32 skipping to change at page 2, line 32
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. MIB modules required for IMPORTS . . . . . . . . . . . . . 9
6.3. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10 6.3. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10
7. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 10 7. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 10
8. IANAsmfOpModeID-MIB Definitions . . . . . . . . . . . . . . . 50 8. IANA-SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . 51
9. IANAsmfRssaID-MIB Definitions . . . . . . . . . . . . . . . . 52 9. Security Considerations . . . . . . . . . . . . . . . . . . . 55
10. Security Considerations . . . . . . . . . . . . . . . . . . . 55 10. Applicability Statement . . . . . . . . . . . . . . . . . . . 58
11. Applicability Statement . . . . . . . . . . . . . . . . . . . 58 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 62
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 61 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 62
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 61 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 61 14.1. Normative References . . . . . . . . . . . . . . . . . . . 62
15.1. Normative References . . . . . . . . . . . . . . . . . . . 61 14.2. Informative References . . . . . . . . . . . . . . . . . . 63
15.2. Informative References . . . . . . . . . . . . . . . . . . 62 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 63
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 6, line 39 skipping to change at page 6, line 39
The textual conventions defined within the SMF-MIB module are: The textual conventions defined within the SMF-MIB module are:
o The SmfStatus is defined within the SMF-MIB module. This contains o The SmfStatus is defined within the SMF-MIB module. This contains
the current operational status of the SMF process on an interface. the current operational status of the SMF process on an interface.
The textual conventions defined for the SMF-MIB module and maintained The textual conventions defined for the SMF-MIB module and maintained
by IANA are: by IANA are:
o The IANAsmfOpModeIdTC represents an index that identifies a o The IANAsmfOpModeIdTC represents an index that identifies a
specific SMF operational mode. This textual convention is specific SMF operational mode. This textual convention is
maintained by IANA in the IANAsmfOpModeID-MIB. maintained by IANA in the IANA-SMF-MIB.
o The IANAsmfRssaIdTC represents an index that identifies, through o The IANAsmfRssaIdTC represents an index that identifies, through
reference, a specific RSSA available for operation on the device. reference, a specific RSSA available for operation on the device.
This textual convention is maintained by IANA in the This textual convention is maintained by IANA also in the IANA-
IANAsmfRssaID-MIB. SMF-MIB.
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
skipping to change at page 10, line 48 skipping to change at page 10, line 48
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 IANAsmfOpModeID-MIB FROM IANA-SMF-MIB
IANAsmfRssaIdTC IANAsmfRssaIdTC
FROM IANAsmfRssaID-MIB FROM IANA-SMF-MIB
; ;
smfMIB MODULE-IDENTITY smfMIB MODULE-IDENTITY
LAST-UPDATED "201403081300Z" -- March 8, 2014 LAST-UPDATED "201403231300Z" -- March 23, 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 50 skipping to change at page 11, line 50
[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 (2012). This version
of this MIB module is part of RFC xxxx; see the RFC of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices." itself for full legal notices."
-- Revision History -- Revision History
REVISION "201403081300Z" -- March 8, 2014 REVISION "201403231300Z" -- March 23, 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 26, line 14 skipping to change at page 26, line 14
SMF packet forwarding process. The ifIndex is SMF packet forwarding process. The ifIndex is
from the interfaces group defined in the from the interfaces group defined in the
Interfaces Group MIB module (RFC 2863). As such, Interfaces Group MIB module (RFC 2863). As such,
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 supports and runs SMF. that automatically supports and runs SMF as part
of the device's initialization process.
The manager can create a row by setting 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
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.
If the corresponding entry with ifIndex value The value of the smfCfgIfAdminStatus is independent
is deleted from the Interface Table, then the entry of the value of the associated ifAdminStatus.
in this table is automatically deleted and The value of the smfCfgIfAdminStatus can be
SMF is disabled on this interface, 'enabled' or 'disabled' when the value of the
and all configuration and state information smfCfgAdminStatus is 'enabled'. However, if the
related to this interface is to be removed value of the smfCfgAdminStatus is 'disabled',
from memory. then all rows in the smfCfgInterfaceTable
MUST be removed.
If the value of the smfCfgAdminStatus object is changed If the value of smfCfgIfAdminStatus is 'disabled',
from 'enabled' to 'disabled', then all rows in this then the value of the corresponding
table are to be deleted and all smfCfgIfRowStatus MUST be set to 'notInService'.
configuration and state information While the value of smfCfgIfRowStatus MAY be
related to this interface is to be removed 'active' or 'notInService' when smfCfgIfAdminStatus
from memory." is set to 'enabled', depending on the state of
the other objects in the corresponding row."
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 28, line 18 skipping to change at page 28, line 33
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
'enabled' or 'disabled' when the value of the
smfCfgAdminStatus object is 'enabled'. When the
value of the smfCfgAdminStatus is 'disabled', then
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 3 }
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(1) state." the 'active' state."
::= { smfCfgInterfaceEntry 4 } ::= { smfCfgInterfaceEntry 4 }
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 the 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(1) 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 this object in order
for the row to transit to the active(1) 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 this object 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 this object prior to this row
transitioning to the active(1) state. transitioning to the 'active' state.
When this object transitions to active(1), all objects 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
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(1) 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(1), 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 5 }
-- --
-- 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.
-- --
skipping to change at page 50, line 18 skipping to change at page 51, line 5
smfNotifDpdMemoryOverflowEvent smfNotifDpdMemoryOverflowEvent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of SMF notifications implemented "Set of SMF notifications implemented
in this module." in this module."
::= { smfMIBGroups 6 } ::= { smfMIBGroups 6 }
END END
8. IANAsmfOpModeID-MIB Definitions 8. IANA-SMF-MIB Definitions
This section contains the IANAsmfOpModeID-MIB module. This MIB This section contains the IANA-SMF-MIB module. This MIB module
module defines the single textual convention for which IANA SHOULD defines two textual conventions for which IANA SHOULD maintain and
maintain and keep synchronized with the registry identified below keep synchronized with the registry identified below within the
within the IANAsmfOpModeIdTC TEXTUAL-CONVENTION. IANAsmfOpModeIdTC and the IANAsmfRssaIdTC TEXTUAL-CONVENTIONs.
The IANAsmfOpModeIdTC defines an index that identifies through The IANAsmfOpModeIdTC defines an index that identifies through
reference to a specific SMF operations mode. The index is an integer reference to a specific SMF operations mode. The index is an integer
valued named-number enumeration consisting of an integer and label. valued named-number enumeration consisting of an integer and label.
IANA is to create and maintain this textual convention. Future IANA is to create and maintain this textual convention. Future
assignments are made to anyone on a first come, first served basis. assignments are made to anyone on a first come, first served basis.
There is no substantive review of the request, other than to ensure There is no substantive review of the request, other than to ensure
that it is well-formed and does not duplicate an existing assignment. that it is well-formed and does not duplicate an existing assignment.
However, requests must include a minimal amount of clerical However, requests must include a minimal amount of clerical
information, such as a point of contact (including an email address) information, such as a point of contact (including an email address)
and a brief description of the method being identified as a new SMF and a brief description of the method being identified as a new SMF
operations mode. operations mode.
IANAsmfOpModeID-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
ianasmfOpModeID MODULE-IDENTITY
LAST-UPDATED "201403081300Z" -- March 8, 2014
ORGANIZATION "IANA"
CONTACT-INFO "Internet Assigned Numbers Authority
Postal: ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1 310 823 9358
E-Mail: iana@iana.org"
DESCRIPTION "This MIB module defines the
IANAsmfOpModeIdTC Textual
Convention, and thus the enumerated values of
the smfCapabilitiesOpModeID object defined in
the SMF-MIB."
REVISION "201403081300Z" -- March 8, 2014
DESCRIPTION "Initial version of this MIB as published in
RFC KKKK."
::= { mib-2 kkkk }
IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An index that identifies through reference to a specific
SMF operations mode. There are basically three styles
of SMF operation with reduced relay sets currently
identified:
Independent operation 'independent(1)' -
SMF performs its own relay
set selection using information from an associated
MANET NHDP process.
CDS-aware unicast routing operation 'routing(2)'-
a coexistent unicast routing
protocol provides dynamic relay
set state based upon its own control plane
CDS or neighborhood discovery information.
Cross-layer operation 'crossLayer(3)' -
SMF operates using neighborhood
status and triggers from a
cross-layer information base for dynamic relay
set selection and maintenance.
IANA MUST update this textual convention accordingly.
The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values SHOULD be made to IANA via
email (iana@iana.org)."
REFERENCE
"See Section 7.2. 'Reduced Relay Set Forwarding',
and the Appendices A, B and C in
RFC 6621 - Simplified Multicast Forwarding
(SMF), Macker, J., May 2012."
SYNTAX INTEGER {
independent (1),
routing (2),
crossLayer (3)
-- future (4-255)
}
END
9. IANAsmfRssaID-MIB Definitions
This section contains the IANAsmfRssaID-MIB module. This MIB module
defines the single textual convention for which IANA SHOULD maintain
and keep synchronized with the registry identified below within the
IANAsmfRssadTC TEXTUAL-CONVENTION.
The IANAsmfRssaIdTC defines an index that identifies through The IANAsmfRssaIdTC defines an index that identifies through
reference to a specific Reduced Set Selection Algorithm (RSSA). The reference to a specific Reduced Set Selection Algorithm (RSSA). The
index is an integer valued named-number enumeration consisting of an index is an integer valued named-number enumeration consisting of an
integer and label. IANA is to create and maintain this textual integer and label. IANA is to create and maintain this textual
convention. convention.
Future assignments for the index range 5-127 require an RFC Future assignments to the IANAsmfRssaIdTC for the index range 5-127
publication (either as an IETF submission or as an RFC Editor require an RFC publication (either as an IETF submission or as an RFC
Independent submission [RFC3932]). The type of RFC MUST be Standards Editor Independent submission [RFC3932]). The type of RFC MUST be
Track. The specific RSSA algorithms MUST be documented in sufficient Standards Track. The specific RSSA algorithms MUST be documented in
detail so that interoperability between independent implementations sufficient detail so that interoperability between independent
is possible. implementations is possible.
Future assignments for the index range 128-239 are private or local Future assignments to the IANAsmfRssaIdTC for the index range 128-239
use only, with the type and purpose defined by the local site. No are private or local use only, with the type and purpose defined by
attempt is made to prevent multiple sites from using the same value the local site. No attempt is made to prevent multiple sites from
in different (and incompatible) ways. There is no need for IANA to using the same value in different (and incompatible) ways. There is
review such assignments (since IANA will not record these) and no need for IANA to review such assignments (since IANA will not
assignments are not generally useful for broad interoperability. It record these) and assignments are not generally useful for broad
is the responsibility of the sites making use of the Private Use interoperability. It is the responsibility of the sites making use
range to ensure that no conflicts occur (within the intended scope of of the Private Use range to ensure that no conflicts occur (within
use). the intended scope of use).
Future assignments for the index range 240-255 are to facilitate Future assignments to the IANAsmfRssaIdTC for the index range 240-255
experimentation. These require an RFC publication (either as an IETF are to facilitate experimentation. These require an RFC publication
submission or as an RFC Editor Independent submission [RFC3932]). (either as an IETF submission or as an RFC Editor Independent
The type of RFC MUST be Experimental. The RSSA algorithms MUST be submission [RFC3932]). The type of RFC MUST be Experimental. The
documented in sufficient detail so that interoperability between RSSA algorithms MUST be documented in sufficient detail so that
independent implementations is possible. interoperability between independent implementations is possible.
IANAsmfRssaID-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;
ianasmfRssaID MODULE-IDENTITY ianaSmfMIB MODULE-IDENTITY
LAST-UPDATED "201403081300Z" -- March 8, 2014 LAST-UPDATED "201403231300Z" -- March 23, 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
IANAsmfRssaIdTC Textual IANAsmfOpModeIdTC and IANAsmfRssaIdTC
Convention, and thus the enumerated values of Textual Conventions, and thus the
the smfCapabilitiesRssaID object defined in enumerated values of the
the SMF-MIB." smfCapabilitiesOpModeID and
REVISION "201403081300Z" -- March 8, 2014 smfCapabilitiesRssaID objects defined
in the SMF-MIB."
REVISION "201403231300Z" -- March 23, 2014
DESCRIPTION "Initial version of this MIB as published in DESCRIPTION "Initial version of this MIB as published in
RFC LLLL." RFC KKKK."
::= { mib-2 kkkk }
::= { mib-2 llll } IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An index that identifies through reference to a specific
SMF operations mode. There are basically three styles
of SMF operation with reduced relay sets currently
identified:
Independent operation 'independent(1)' -
SMF performs its own relay
set selection using information from an associated
MANET NHDP process.
CDS-aware unicast routing operation 'routing(2)'-
a coexistent unicast routing
protocol provides dynamic relay
set state based upon its own control plane
CDS or neighborhood discovery information.
Cross-layer operation 'crossLayer(3)' -
SMF operates using neighborhood
status and triggers from a
cross-layer information base for dynamic relay
set selection and maintenance.
IANA MUST update this textual convention accordingly.
The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values SHOULD be made to IANA via
email (iana@iana.org)."
REFERENCE
"See Section 7.2. 'Reduced Relay Set Forwarding',
and the Appendices A, B and C in
RFC 6621 - Simplified Multicast Forwarding
(SMF), Macker, J., May 2012."
SYNTAX INTEGER {
independent (1),
routing (2),
crossLayer (3)
-- future (4-255)
}
IANAsmfRssaIdTC ::= TEXTUAL-CONVENTION IANAsmfRssaIdTC ::= 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. Several are currently defined RSSA algorithms. Several are currently defined
in the Appendix A, B and C of RFC 6621. in the Appendix A, B and C of RFC 6621.
Examples of RSSA algorithms already identified within Examples of RSSA algorithms already identified within
this TC are: this TC are:
skipping to change at page 55, line 19 skipping to change at page 55, line 15
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)
} }
END END
10. Security Considerations 9. Security Considerations
This section discusses security implications of the choices made in This section discusses security implications of the choices made in
this SMF-MIB module. this SMF-MIB module.
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
skipping to change at page 58, line 48 skipping to change at page 58, line 45
[RFC5592] or TLS/DTLS [RFC6353]. [RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
11. Applicability Statement 10. Applicability Statement
This document describes objects for configuring parameters of the This document describes objects for configuring parameters of the
Simplified Multicast Forwarding [RFC6621] process on a Mobile Ad-Hoc Simplified Multicast Forwarding [RFC6621] process on a Mobile Ad-Hoc
Network (MANET) router. This MIB module, denoted SMF-MIB, also Network (MANET) router. This MIB module, denoted SMF-MIB, also
reports state and performance information and notifications. This reports state and performance information and notifications. This
section provides some examples of how this MIB module can be used in section provides some examples of how this MIB module can be used in
MANET network deployments. A fuller discussion of MANET network MANET network deployments. A fuller discussion of MANET network
management use cases and challenges will be provided elsewhere. management use cases and challenges will be provided elsewhere.
SMF is designed to allow MANET routers to forward IPv4 and IPv6 SMF is designed to allow MANET routers to forward IPv4 and IPv6
skipping to change at page 60, line 10 skipping to change at page 60, line 7
This discussion only identifies the configuration necessary through This discussion only identifies the configuration necessary through
the SMF-MIB module and assumes that other configuration has occurred. the SMF-MIB module and assumes that other configuration has occurred.
Assume that the MANET is to support only IPv4 addressing and that the Assume that the MANET is to support only IPv4 addressing and that the
MANET nodes are to be configured in the context of the Parking Lot MANET nodes are to be configured in the context of the Parking Lot
Initialization case above. Then the SMF-MIB module defines ten Initialization case above. Then the SMF-MIB module defines ten
configuration OIDs and two configuration tables, i.e., the configuration OIDs and two configuration tables, i.e., the
smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten
OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL
clauses which allow for a functional configuration of the SMF process clauses which allow for a functional configuration of the SMF process
within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the
smfCfgRouterID can be set as, e.g.,: smfCfgRouterID can be set as, e.g. (assuming the use of the Net-SNMP
toolkit),:
snmpset [options] <smfCfgRouterID_OID>.0 a 192.168.1.100 snmpset [options] <smfCfgRouterID_OID>.0 a 192.168.1.100
If the smfCfgAddrForwardingTable is left empty, then the SMF local If the smfCfgAddrForwardingTable is left empty, then the SMF local
forwarder will forward all multicast addresses. So this table does forwarder will forward all multicast addresses. So this table does
not require configuration if you want to have the MANET forward all not require configuration if you want to have the MANET forward all
multicast addresses. multicast addresses.
All that remains is to configure at least one row in the All that remains is to configure at least one row in the
smfCfgInterfaceTable. Assume that the node has a wireless interface smfCfgInterfaceTable. Assume that the node has a wireless interface
with an <ifName>='wlan0' and an <ifIndex>='1'. All of the objects in with an <ifName>='wlan0' and an <ifIndex>='1'. All of the objects in
the rows of the smfCfgInterfaceTable have a DEFVAL clause, hence only the rows of the smfCfgInterfaceTable have a DEFVAL clause, hence only
the RowStatus object needs to be set. So the SMF process will be the RowStatus object needs to be set. So the SMF process will be
activated on the 'wlan0' interface by the following network manager activated on the 'wlan0' interface by the following network manager
snmpset command: snmpset command:
snmpset [options] <smfCfgIfRowStatus>.1 i active(1) snmpset [options] <smfCfgIfRowStatus>.1 i active(1)
At this point, the configured forwarder will begin a Classical At this point, the configured forwarder will begin a Classical
Flooding algorithm to forward all multicast addresses IPv4 packets it Flooding algorithm to forward all multicast addresses IPv4 packets it
receives. If the receives.
To provide a more efficient multicast forwarding within the MANET, To provide a more efficient multicast forwarding within the MANET,
the network manager could walk the smfCapabilitiesTable to identify the network manager could walk the smfCapabilitiesTable to identify
other SMF operational modes, e.g.,: other SMF operational modes, e.g.,:
snmpwalk -c public -v 2c router <smfCapabilitiesTable> snmpwalk [options] <smfCapabilitiesTable>
SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1 SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1
SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2 SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2
SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1) SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1)
SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2) SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2)
SMF-MIB::smfCapabilitiesRssaID.1 = INTEGER: cF(1) SMF-MIB::smfCapabilitiesRssaID.1 = INTEGER: cF(1)
skipping to change at page 61, line 13 skipping to change at page 61, line 11
In this example, the forwarding device also supports the Extended In this example, the forwarding device also supports the Extended
Connected Dominating Set (eCDS) RSSA with the forwarder in the Connected Dominating Set (eCDS) RSSA with the forwarder in the
'independent(2)' operational mode. If the network manager were to 'independent(2)' operational mode. If the network manager were to
then issue an snmpset, e.g.,: then issue an snmpset, e.g.,:
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.
12. IANA Considerations 11. IANA Considerations
The MIB module in this document uses the following IANA-assigned This document defines two MIB modules:
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value o SMF-MIB is defined in Section 7 and is an experimental MIB module
---------- -----------------------
SMF-MIB { experimental XXXX }
IANAsmfOpModeID-MIB { experimental KKKK }
IANAsmfRssaID-MIB { experimental LLLL }
IANA EDITOR NOTE: please assign XXXX, KKKK and LLLL and o IANA-SMF-MIB is defined in Section 8 and is an IANA MIB module
remove this note. that IANA is requested to maintain
13. Contributors Thus, there are three actions requested of IANA:
1. IANA is requested to allocate an OBJECT IDENTIFIER value and
record it in the SMI Numbers registry in the sub-registry called "SMI
Experimental Codes" under the experimental branch (1.3.6.1.3).
Decimal | Name | Description | Reference
--------+---------+---------------+------------
xxxx | smfMib | SMF-MIB | [This.I-D]
[RFC Editor Note: Please replace the tag "xxxx" in
this document with the value assigned by IANA and
remove this note.]
2. IANA is requested to allocate an OBJECT IDENTIFIER value and
record it in the SMI Numbers registry in the sub-registry called "SMI
Network Management MGMT Codes Internet-standard MIB" under the mib-2
branch (1.3.6.1.2.1).
Decimal | Name | Description | Reference
--------+---------------+-----------------+------------
kkkk | ianaSmfMIB | IANA-SMF-MIB | [This.I-D]
[RFC Editor Note: Please replace the tag "kkkk" in
this document with the value assigned by IANA and
remove this note.]
3. IANA is requested to maintain a MIB module called ianaSmfMIB and
populate it with the initial MIB module defined in Section 8 of this
document by creating a new entry in the registry "IANA Maintained
MIBs" called "IANA-SMF-MIB".
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.
14. 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 and
from Dan Romascanu in the final reviews of this MIB module. The from Dan Romascanu in the final reviews of this MIB module. The
authors would like to thank James Nguyen for his careful review and 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 comments on this MIB module and his work on the definitions of the
follow-on MIB modules to configure specific RSSA algorithms related follow-on MIB modules to configure specific RSSA algorithms related
to SMF. Further, the authors would like to acknowledge to work of to SMF. Further, the authors would like to acknowledge to work of
James Nguyen, Brian Little, Ryan Morgan and Justin Dean on their James Nguyen, Brian Little, Ryan Morgan and Justin Dean on their
software development of the SMF-MIB. software development of the SMF-MIB.
15. References 14. References
15.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.
[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
skipping to change at page 62, line 36 skipping to change at page 63, line 12
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[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.
15.2. Informative References 14.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. 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
skipping to change at page 63, line 18 skipping to change at page 64, line 10
[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. 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. *
* * * *
* 2) This document also contains the IANAsmfOpModeID-MIB * * 2) This document also contains the IANA-SMF-MIB module *
* module which is defined by this specification above. * * which is defined by this specification above. IANA should *
* IANA should take over the IANAsmfOpModeID-MIB and keep it * * take over the IANA-SMF-MIB and keep it synchronized with *
* synchronized with the registry identified within the * * the registries identified within the contained *
* contained IANAsmfOpModeIdTC TEXTUAL-CONVENTION. * * IANAsmfOpModeIdTC and IANAsmfRssaIdTC TEXTUAL-CONVENTIONs. *
* *
* 3) This document contains the IANAsmfRssaID-MIB *
* module which is defined by this specification above. *
* IANA should take over the IANAsmfRssaID-MIB and keep it *
* synchronized with the registry identified within the *
* contained IANAsmfRssaID TEXTUAL-CONVENTION. *
* * * *
*************************************************************** ***************************************************************
Authors' Addresses Authors' Addresses
Robert G. Cole Robert G. Cole
US Army CERDEC US Army CERDEC
6010 Frankford Road 6010 Frankford Road
Aberdeen Proving Ground, Maryland 21005 Aberdeen Proving Ground, Maryland 21005
USA USA
 End of changes. 51 change blocks. 
199 lines changed or deleted 216 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/