draft-ietf-forces-mib-04.txt   draft-ietf-forces-mib-05.txt 
Forwarding and Control Element R. Haas Forwarding and Control Element R. Haas
Separation (forces) IBM Separation (forces) IBM
Intended status: Standards Track Intended status: Standards Track
Expires: January 28, 2007 Expires: September 2, 2007
ForCES MIB ForCES MIB
draft-ietf-forces-mib-04 draft-ietf-forces-mib-05
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 28, 2007. This Internet-Draft will expire on September 2, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This memo defines a Management Information Base (MIB) module for use This memo defines a Management Information Base (MIB) module for use
with network management protocols in the Internet community. In with network management protocols in the Internet community. In
particular, it defines managed objects for the Forwarding and Control particular, it defines managed objects for the Forwarding and Control
Element Separation (ForCES) Network Element (NE). The ForCES working Element Separation (ForCES) Network Element (NE).
group is defining a protocol to allow a Control Element (CE) to
control the behavior of a Forwarding Element (FE).
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. ForCES MIB Definition . . . . . . . . . . . . . . . . . . . . 3 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Associations kept in the MIB . . . . . . . . . . . . . . . . . 11 4. ForCES MIB Overview . . . . . . . . . . . . . . . . . . . . . 3
5. Support for multiple CEs and FEs . . . . . . . . . . . . . . . 11 5. ForCES MIB Definition . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 6. Associations kept in the MIB . . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. Support for multiple CEs and FEs . . . . . . . . . . . . . . . 13
8. Changes from Previous Draft Revisions . . . . . . . . . . . . 12 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 10. Changes from Previous Draft Revisions . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . . 14 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 14 11.1. Normative References . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 11.2. Informative References . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 16 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . . . 19
1. Requirements notation 1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. The Internet-Standard Management Framework
The ForCES MIB module is a read-only MIB module that captures
information related to the ForCES protocol ([RFC3654], [RFC3746],
[forces-applicability-draft] and [forces-protocol-draft]).
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
[RFC3410]. [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
[RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580].
3. Introduction
The ForCES MIB module is a read-only MIB module that captures
information related to the ForCES protocol ([RFC3654], [RFC3746],
[forces-applicability-draft] and [forces-protocol-draft]).
The ForCES MIB module does not include information that is specified The ForCES MIB module does not include information that is specified
in other MIB modules, such as packet counters for interfaces, etc. in other MIB modules, such as packet counters for interfaces, etc.
More specifically, the information in the ForCES MIB module relative More specifically, the information in the ForCES MIB module relative
to associations that are up includes: to associations that are up includes:
o identifiers of the elements in the association, o identifiers of the elements in the association,
o configuration parameters of the association, and o configuration parameters of the association, and
o statistics of the association. o statistics of the association.
3. ForCES MIB Definition 4. ForCES MIB Overview
The MIB module contains the latest ForCES protocol version supported The MIB module contains the latest ForCES protocol version supported
by the CE (forcesLatestProtocolVersionSupported). Note that the CE by the CE (forcesLatestProtocolVersionSupported). Note that the CE
must also allow interaction with FEs supporting earlier versions. must also allow interaction with FEs supporting earlier versions.
For each association identified by the pair CE ID and FE ID, the For each association identified by the pair CE ID and FE ID, the
following associated information is provided by the MIB module as an following associated information is provided by the MIB module as an
entry (forcesAssociationEntry) in the association table entry (forcesAssociationEntry) in the association table
(forcesAssociationTable): (forcesAssociationTable):
skipping to change at page 4, line 18 skipping to change at page 4, line 21
o Time when the association entered the UP state o Time when the association entered the UP state
(forcesAssociationTimeUp). (forcesAssociationTimeUp).
o Time when the association left the UP state o Time when the association left the UP state
(forcesAssociationTimeDown). Note that this is only used for (forcesAssociationTimeDown). Note that this is only used for
notification purposes as the association is removed from the MIB notification purposes as the association is removed from the MIB
immediately after it leaves the UP state. immediately after it leaves the UP state.
o Number of ForCES Heartbeat messages sent from the CE o Number of ForCES Heartbeat messages sent from the CE
(forcesAssociationHBMsgSent) and received by the CE (forcesAssociationHBMsgSent) and received by the CE
(forcesAssociationHBMsgReceived) since the association is UP. (forcesAssociationHBMsgReceived) since the association entered the
UP state.
o Number of other ForCES messages sent from the CE o Number of other ForCES messages sent from the CE
(forcesAssociationOtherMsgSent) and received by the CE (forcesAssociationOtherMsgSent) and received by the CE
(forcesAssociationOtherMsgReceived) since the association is UP. (forcesAssociationOtherMsgReceived) since the association entered
Only messages other than Heartbeat, Association Setup, Association the UP state. Only messages other than Heartbeat, Association
Setup Response, and Association Teardown are counted. Setup, Association Setup Response, and Association Teardown are
counted.
Finally, the MIB module defines the following notifications: Finally, the MIB module defines the following notifications:
o Whenever an association enters the UP state, a notification o Whenever an association enters the UP state, a notification
(forcesAssociationEntryUp) is issued containing the version of the (forcesAssociationEntryUp) is issued containing the version of the
ForCES protocol running. Note that as CE ID and FE ID are ForCES protocol running. Note that as CE ID and FE ID are
indexes, they appear in the OID of the ForCES-protocol running- indexes, they appear in the OID of the ForCES-protocol running-
version object. version object. Optionally, a notification
(forcesAssociationEntryUpStats) can instead be issued with all
associated information for this association, except
forcesAssociationTimeDown.
o Whenever an association leaves the UP state, a notification o Whenever an association leaves the UP state, a notification
(forcesAssociationEntryDown) is issued containing all associated (forcesAssociationEntryDown) is issued containing the version of
information for this association. The reason is that the the ForCES protocol running. Optionally, a notification
association and all its associated information will be removed (forcesAssociationEntryDownStats) can instead be issued with all
associated information for this association. The reason is that
the association and all its associated information will be removed
from the MIB immediately after this notification has been issued. from the MIB immediately after this notification has been issued.
5. ForCES MIB Definition
FORCES-MIB DEFINITIONS ::= BEGIN FORCES-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
mib-2, Integer32, Counter32 mib-2, Integer32, Counter32
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, TimeStamp TEXTUAL-CONVENTION, TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
forcesMib MODULE-IDENTITY forcesMib MODULE-IDENTITY
LAST-UPDATED "200607261200Z" -- Jul 26, 2006 LAST-UPDATED "200703011200Z" -- Mar 1, 2007
ORGANIZATION "Forwarding and Control Element Separation ORGANIZATION "IETF Forwarding and Control Element
(ForCES) Working Group" Separation (ForCES) Working Group"
CONTACT-INFO CONTACT-INFO
"Robert Haas (rha@zurich.ibm.com), IBM" "WG Charter:
http://www.ietf.org/html.charters/forces-charter.html
Mailing lists:
General Discussion: forces@peach.ease.lsoft.com
To Subscribe: listserv@peach.ease.lsoft.com
In Body: subscribe forces
Chairs: Patrick Droz
Email: dro@zurich.ibm.com
David Putzolu
Email: David.Putzolu@intel.com
Editor: Robert Haas
IBM
Email: rha@zurich.ibm.com"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions "This MIB module contains managed object definitions
for the ForCES Protocol." for the ForCES Protocol.
REVISION "200607261200Z" -- Jul 26, 2006 Copyright (C) The Internet Society (2007). This
version of this MIB module is part of RFC yyyy; see
the RFC itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200703011200Z" -- Mar 01, 2007
DESCRIPTION DESCRIPTION
"Initial version, published as RFC yyyy." "Initial version, published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note -- RFC Ed.: replace XXX with IANA-assigned number & remove this note
--**************************************************************** --****************************************************************
forcesMibNotifications OBJECT IDENTIFIER ::= { forcesMib 0 } forcesMibNotifications OBJECT IDENTIFIER ::= { forcesMib 0 }
forcesMibObjects OBJECT IDENTIFIER ::= { forcesMib 1 } forcesMibObjects OBJECT IDENTIFIER ::= { forcesMib 1 }
skipping to change at page 5, line 45 skipping to change at page 6, line 29
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ForCES protocol version number. "ForCES protocol version number.
The version numbers used are defined in the The version numbers used are defined in the
specifications of the respective protocol: specifications of the respective protocol:
1 - ForCESv1 [RFCzzzz]." 1 - ForCESv1 [RFCzzzz]."
-- RFC Ed.: replace zzzz with actual RFC number of ForCES protocol -- RFC Ed.: replace zzzz with actual RFC number of ForCES protocol
-- & remove this note -- & remove this note
SYNTAX Integer32 (1..255) SYNTAX Integer32 (1..255)
DISPLAY-HINT "d"
-- Notifications -- Notifications
forcesAssociationEntryUp NOTIFICATION-TYPE forcesAssociationEntryUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
forcesAssociationRunningProtocolVersion forcesAssociationRunningProtocolVersion
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated as soon "This notification is generated as soon
as an association enters the UP state." as an association enters the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations."
::= { forcesMibNotifications 1 } ::= { forcesMibNotifications 1 }
forcesAssociationEntryDown NOTIFICATION-TYPE forcesAssociationEntryDown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
forcesAssociationRunningProtocolVersion
}
STATUS current
DESCRIPTION
"This notification is generated as soon
as an association leaves the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations."
::= { forcesMibNotifications 2 }
forcesAssociationEntryUpStats NOTIFICATION-TYPE
OBJECTS {
forcesAssociationRunningProtocolVersion,
forcesAssociationTimeUp,
forcesAssociationHBMsgSent,
forcesAssociationHBMsgReceived,
forcesAssociationOtherMsgSent,
forcesAssociationOtherMsgReceived
}
STATUS current
DESCRIPTION
"This notification is generated as soon
as an association enters the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations."
::= { forcesMibNotifications 3 }
forcesAssociationEntryDownStats NOTIFICATION-TYPE
OBJECTS {
forcesAssociationRunningProtocolVersion, forcesAssociationRunningProtocolVersion,
forcesAssociationTimeUp, forcesAssociationTimeUp,
forcesAssociationTimeDown, forcesAssociationTimeDown,
forcesAssociationHBMsgSent, forcesAssociationHBMsgSent,
forcesAssociationHBMsgReceived, forcesAssociationHBMsgReceived,
forcesAssociationOtherMsgSent, forcesAssociationOtherMsgSent,
forcesAssociationOtherMsgReceived } forcesAssociationOtherMsgReceived
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated as soon "This notification is generated as soon
as an association leaves the UP state." as an association leaves the UP state.
::= { forcesMibNotifications 2 } Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations."
::= { forcesMibNotifications 4 }
-- Objects -- Objects
forcesLatestProtocolVersionSupported OBJECT-TYPE forcesLatestProtocolVersionSupported OBJECT-TYPE
SYNTAX ForcesProtocolVersion SYNTAX ForcesProtocolVersion
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ForCES protocol version supported by the CE. "The ForCES protocol version supported by the CE.
The current protocol version is 1. The current protocol version is 1.
skipping to change at page 8, line 4 skipping to change at page 9, line 25
forcesAssociationRunningProtocolVersion OBJECT-TYPE forcesAssociationRunningProtocolVersion OBJECT-TYPE
SYNTAX ForcesProtocolVersion SYNTAX ForcesProtocolVersion
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current ForCES protocol version used in this "The current ForCES protocol version used in this
association. association.
The current protocol version is 1." The current protocol version is 1."
::= { forcesAssociationEntry 3 } ::= { forcesAssociationEntry 3 }
forcesAssociationTimeUp OBJECT-TYPE forcesAssociationTimeUp OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this "The value of sysUpTime at the time this
association entered the UP state. association entered the UP state.
If this association started prior to the last If this association started prior to the last
initialization of the network subsystem, then initialization of the network subsystem, then
this object contains a zero value." this object contains a zero value.
This object allows to uniquely identify
associations with the same CE and FE IDs."
::= { forcesAssociationEntry 4 } ::= { forcesAssociationEntry 4 }
forcesAssociationTimeDown OBJECT-TYPE forcesAssociationTimeDown OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this "The value of sysUpTime at the time this
association left the UP state." association left the UP state."
::= { forcesAssociationEntry 5 } ::= { forcesAssociationEntry 5 }
forcesAssociationHBMsgSent OBJECT-TYPE forcesAssociationHBMsgSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of how many heartbeat messages have "A counter of how many heartbeat messages have
have been sent by the CE on this association have been sent by the CE on this association
since it is up. since the association entered the UP state.
If this association started prior to the last If this association started prior to the last
initialization of the network subsystem, then initialization of the network subsystem, then
this object contains the value since the this object contains the value since the
initialization." initialization."
::= { forcesAssociationEntry 6 } ::= { forcesAssociationEntry 6 }
forcesAssociationHBMsgReceived OBJECT-TYPE forcesAssociationHBMsgReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of how many heartbeat messages "A counter of how many heartbeat messages
have been received by the CE on this association have been received by the CE on this association
since it is up. since the association entered the UP state.
If this association started prior to the last If this association started prior to the last
initialization of the network subsystem, then initialization of the network subsystem, then
this object contains the value since the this object contains the value since the
initialization." initialization."
::= { forcesAssociationEntry 7 } ::= { forcesAssociationEntry 7 }
forcesAssociationOtherMsgSent OBJECT-TYPE forcesAssociationOtherMsgSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of how many messages other than "A counter of how many messages other than
heartbeat (i.e., config and query) heartbeat (i.e., config and query)
have been sent by the CE on this association have been sent by the CE on this association
since it is up. since the association entered the UP state.
If this association started prior to the last If this association started prior to the last
initialization of the network subsystem, then initialization of the network subsystem, then
this object contains the value since the this object contains the value since the
initialization." initialization."
::= { forcesAssociationEntry 8 } ::= { forcesAssociationEntry 8 }
forcesAssociationOtherMsgReceived OBJECT-TYPE forcesAssociationOtherMsgReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of how many messages other than "A counter of how many messages other than
heartbeat (i.e., config response, query response, heartbeat (i.e., config response, query response,
event notification, and packet redirect) event notification, and packet redirect)
have been received by the CE on this association have been received by the CE on this association
since it is up. since the association entered the UP state.
If this association started prior to the last If this association started prior to the last
initialization of the network subsystem, then initialization of the network subsystem, then
this object contains the value since the this object contains the value since the
initialization." initialization."
::= { forcesAssociationEntry 9 } ::= { forcesAssociationEntry 9 }
-- Conformance -- Conformance
forcesMibCompliances OBJECT IDENTIFIER forcesMibCompliances OBJECT IDENTIFIER
::= { forcesMibConformance 1 } ::= { forcesMibConformance 1 }
skipping to change at page 10, line 4 skipping to change at page 11, line 28
-- Compliance statements -- Compliance statements
forcesMibCompliance MODULE-COMPLIANCE forcesMibCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for routers running ForCES and "The compliance statement for routers running ForCES and
implementing the ForCES MIB." implementing the ForCES MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { forcesMibGroup, forcesNotificationGroup } MANDATORY-GROUPS { forcesMibGroup, forcesNotificationGroup }
GROUP forcesNotificationStatsGroup
DESCRIPTION
"Implementation of this group is recommended."
GROUP forcesStatsGroup GROUP forcesStatsGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is recommended." "Implementation of this group is recommended."
::= { forcesMibCompliances 1 } ::= { forcesMibCompliances 1 }
-- Units of conformance -- Units of conformance
forcesNotificationGroup NOTIFICATION-GROUP forcesNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { forcesAssociationEntryUp, NOTIFICATIONS { forcesAssociationEntryUp,
skipping to change at page 10, line 33 skipping to change at page 12, line 14
forcesMibGroup OBJECT-GROUP forcesMibGroup OBJECT-GROUP
OBJECTS { forcesLatestProtocolVersionSupported, OBJECTS { forcesLatestProtocolVersionSupported,
forcesAssociationRunningProtocolVersion forcesAssociationRunningProtocolVersion
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support management of ForCES "A collection of objects to support management of ForCES
routers." routers."
::= { forcesMibGroups 2 } ::= { forcesMibGroups 2 }
forcesNotificationStatsGroup NOTIFICATION-GROUP
NOTIFICATIONS { forcesAssociationEntryUpStats,
forcesAssociationEntryDownStats
}
STATUS current
DESCRIPTION
"A collection of optional notifications for signaling
important ForCES events including statistics."
::= { forcesMibGroups 3 }
forcesStatsGroup OBJECT-GROUP forcesStatsGroup OBJECT-GROUP
OBJECTS { forcesAssociationTimeUp, OBJECTS { forcesAssociationTimeUp,
forcesAssociationTimeDown, forcesAssociationTimeDown,
forcesAssociationHBMsgSent, forcesAssociationHBMsgSent,
forcesAssociationHBMsgReceived, forcesAssociationHBMsgReceived,
forcesAssociationOtherMsgSent, forcesAssociationOtherMsgSent,
forcesAssociationOtherMsgReceived forcesAssociationOtherMsgReceived
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects to provide extra "A collection of optional objects to provide extra
information about the associations. There is no protocol information about the associations. There is no protocol
reason to keep such information, but these objects can reason to keep such information, but these objects can
be very useful in debugging connectivity problems." be very useful in debugging connectivity problems."
::= { forcesMibGroups 3 } ::= { forcesMibGroups 4}
END END
4. Associations kept in the MIB 6. Associations kept in the MIB
Only associations that are UP are reflected in this MIB module. Only associations that are UP are reflected in this MIB module.
Associations enter the UP state as soon as the CE has sent to the FE Associations enter the UP state as soon as the CE has sent to the FE
an Association Setup Response message containing a successful an Association Setup Response message containing a successful
Association Setup Result. Association Setup Result.
Associations are removed from the MIB module as soon as they leave Associations are removed from the MIB module as soon as they leave
the UP state, i.e., if the CE has not received any message (Heartbeat the UP state, i.e., if the CE has not received any message (Heartbeat
or other protocol message) from the FE within a given time period or or other protocol message) from the FE within a given time period or
if an Association Teardown message has been sent by the CE. if an Association Teardown message has been sent by the CE.
5. Support for multiple CEs and FEs Statistics counters are not initialized to zero when the association
is created. Instead, a delta value must be calculated from two
successive readings. Note that the optional up and down
notifications contain the statistics with the initial and final value
of the statistics.
7. Support for multiple CEs and FEs
An NE consists of one or more FEs and one or more CEs. Where there An NE consists of one or more FEs and one or more CEs. Where there
is a single CE, that CE will have knowledge of all the associations is a single CE, that CE will have knowledge of all the associations
in the NE and so can provide the information necessary to support the in the NE and so can provide the information necessary to support the
managed objects defined in this MIB module. Where there is more than managed objects defined in this MIB module. Where there is more than
one CE, information about the associations may be distributed among one CE, information about the associations may be distributed among
the CEs. Whether each CE implements the managed objects for the the CEs. Whether each CE implements the managed objects for the
associations of which it is aware or whether the CEs cooperate to associations of which it is aware or whether the CEs cooperate to
present the appearance of a single set of managed objects for all the present the appearance of a single set of managed objects for all the
associations in the NE is outside the scope of this document. associations in the NE is outside the scope of this document.
6. Security Considerations 8. Security Considerations
Some of the readable objects in this MIB module may be considered There are no management objects defined in this MIB module that have
sensitive or vulnerable in some network environment. a MAX-ACCESS clause of read-write and/or read-create. So, if this
MIB module is implemented correctly, then there is no risk that an
intruder can alter or create any management objects of this MIB
module via direct SNMP SET operations.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
o Objects in the forcesMibGroup are protocol versions. They are
neither sensitive nor vulnerable.
o Objects in the forcesStatsGroup are statistics. They are neither
sensitive nor vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
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.
7. IANA Considerations 9. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
forcesMIB { mib-2 XXX } forcesMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note. this note.
8. Changes from Previous Draft Revisions 10. Changes from Previous Draft Revisions
Editor's Note (to be removed prior to publication): Prior to RFC Editor's Note (to be removed prior to publication): Prior to RFC
publication of this document, the RFC Editor is asked to remove this publication of this document, the RFC Editor is asked to remove this
entire section titled "Changes from Previous Draft Versions". entire section titled "Changes from Previous Draft Versions".
Changes from draft-ietf-forces-mib-04. They are changes suggested by
the MIB doctor review, according to the MIB Review Checklist in
Appendix A of RFC 4181:
o Changed MIB descriptions with "since the association entered the
UP state" instead of "since the association is up".
o Updated the I-D boilerplate copyright statement.
o Removed last sentence of abstract.
o Moved the MIB boilerplate into a section of its own.
o Moved the MIB definition into a section of its own.
o Updated the Security Considerations section according to the
boilerplate at http://www.ops.ietf.org/mib-security.html.
o Updated the MIB description with the copyright statement.
o Added DISPLAY-HINT to the ForCESProtocolVersion. Note that the
smilint tool doesn't like it.
o Added IETF to the MODULE-IDENTITY ORGANIZATION.
o Updated CONTACT-INFO to indicate how to reach the group.
o Changed forcesAssocationTimeDown MAX-ACCESS to accessible-for-
notify.
o Added text to DESCRIPTION of forcesAssociationTimeUp to indicate
that it allows to uniquely identify associations with the same FE
and CE IDs.
o Added two optional notifications that carry stats and added
corresponding text in the last paragraph of section titled
"Associations kept in the MIB". The reason is that optional
objects such as stats in a mandatory notification are not
supported.
Changes from draft-ietf-forces-mib-03. They are small fixes to the Changes from draft-ietf-forces-mib-03. They are small fixes to the
text and the MIB module: text and the MIB module:
o Added MIB boilerplate according to o Added MIB boilerplate according to
http://www.ops.ietf.org/mib-boilerplate.html http://www.ops.ietf.org/mib-boilerplate.html
o Clarified terminology with respect to MIB module and MIB managed o Clarified terminology with respect to MIB module and MIB managed
objects. objects.
o Added RFC Editor note to indicate RFC number for version 1 of o Added RFC Editor note to indicate RFC number for version 1 of
skipping to change at page 13, line 44 skipping to change at page 16, line 51
associations in the UP state are kept in the table. associations in the UP state are kept in the table.
o Split of the Message counters into Heartbeat and other messages. o Split of the Message counters into Heartbeat and other messages.
o Addition of the current running version of ForCES protocol for o Addition of the current running version of ForCES protocol for
each association in the UP state. each association in the UP state.
o Addition of the latest version of the ForCES protocol supported by o Addition of the latest version of the ForCES protocol supported by
the CE. the CE.
9. References 11. References
9.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
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.
skipping to change at page 14, line 28 skipping to change at page 17, line 34
[RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal, [RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal,
"Forwarding and Control Element Separation (ForCES) "Forwarding and Control Element Separation (ForCES)
Framework", RFC 3746, April 2004. Framework", RFC 3746, April 2004.
[forces-protocol-draft] [forces-protocol-draft]
Doria, A., Haas, R., Hadi Salim, J., Khosravi, H., and W. Doria, A., Haas, R., Hadi Salim, J., Khosravi, H., and W.
Wang, "ForCES Protocol Specification", ID Document: Wang, "ForCES Protocol Specification", ID Document:
draft-ietf-forces-protocol-08.txt, March 2006. draft-ietf-forces-protocol-08.txt, March 2006.
9.2. Informative References 11.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.
[forces-applicability-draft] [forces-applicability-draft]
Crouch, A., Khosravi, H., Handley, M., and A. Doria, Crouch, A., Khosravi, H., Handley, M., and A. Doria,
"ForCES Applicability Statement", ID Document: "ForCES Applicability Statement", ID Document:
draft-ietf-forces-applicability-04.txt, February 2006. draft-ietf-forces-applicability-04.txt, February 2006.
Appendix A. Acknowledgments Appendix A. Acknowledgments
The author gratefully acknowledges the contributions of: Jinrong The author gratefully acknowledges the contributions of: Jinrong
Fenggen, Xiaoyi Guo, Joel Halpern, Tom Petch, and Jamal Hadi Salim. Fenggen, John Flick, Xiaoyi Guo, Joel Halpern, Tom Petch, and Jamal
Hadi Salim.
Author's Address Author's Address
Robert Haas Robert Haas
IBM IBM
Saeumerstrasse 4 Saeumerstrasse 4
Rueschlikon 8803 Rueschlikon 8803
CH CH
Email: rha@zurich.ibm.com Email: rha@zurich.ibm.com
URI: http://www.zurich.ibm.com/~rha URI: http://www.zurich.ibm.com/~rha
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 48 change blocks. 
69 lines changed or deleted 221 lines changed or added

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