draft-ietf-forces-mib-03.txt   draft-ietf-forces-mib-04.txt 
Forwarding and Control Element R. Haas Forwarding and Control Element R. Haas
Separation (forces) IBM Separation (forces) IBM
Expires: January 5, 2007 Intended status: Standards Track
Expires: January 28, 2007
ForCES MIB ForCES MIB
draft-ietf-forces-mib-03 draft-ietf-forces-mib-04
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 34 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 5, 2007. This Internet-Draft will expire on January 28, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a Management Information Base (MIB) for use with This memo defines a Management Information Base (MIB) module for use
network management protocols in the Internet community. In with network management protocols in the Internet community. In
particular, it defines a MIB for the Forwarding and Control Element particular, it defines managed objects for the Forwarding and Control
Separation (ForCES) Network Element (NE). The ForCES working group Element Separation (ForCES) Network Element (NE). The ForCES working
is defining a protocol to allow a Control Element (CE) to control the group is defining a protocol to allow a Control Element (CE) to
behavior of a Forwarding Element (FE). 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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Design of the ForCES MIB . . . . . . . . . . . . . . . . . . . 3 3. ForCES MIB Definition . . . . . . . . . . . . . . . . . . . . 3
4. Association State . . . . . . . . . . . . . . . . . . . . . . 3 4. Associations kept in the MIB . . . . . . . . . . . . . . . . . 11
5. ForCES MIB Definition . . . . . . . . . . . . . . . . . . . . 4 5. Support for multiple CEs and FEs . . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Changes from Previous Draft Revisions . . . . . . . . . . . . 11 8. Changes from Previous Draft Revisions . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . . 12 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . . 12 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 12 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 14
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 14 Intellectual Property and Copyright Statements . . . . . . . . . . 16
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. Introduction
The ForCES MIB is a primarily read-only MIB that captures information The ForCES MIB module is a read-only MIB module that captures
related to the ForCES protocol ([RFC3654], [RFC3746], [forces- information related to the ForCES protocol ([RFC3654], [RFC3746],
applicability-draft] and [forces-protocol-draft]). [forces-applicability-draft] and [forces-protocol-draft]).
The ForCES MIB does not include information that is specified in For a detailed overview of the documents that describe the current
other MIBs, such as packet counters for interfaces, etc. Internet-Standard Management Framework, please refer to section 7 of
[RFC3410].
More specifically, the information in the ForCES MIB relative to Managed objects are accessed via a virtual information store, termed
associations that are up includes: the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
[RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580].
The ForCES MIB module does not include information that is specified
in other MIB modules, such as packet counters for interfaces, etc.
More specifically, the information in the ForCES MIB module relative
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. Design of the ForCES MIB 3. ForCES MIB Definition
In an NE composed of one or more FEs and a single CE, the CE is
clearly aware of all associations and hence can provide this
information in a single ForCES MIB. In contrast, in an NE composed
of more than one CE, such association information is distributed and
hence more than one ForCES MIB may be necessary, unless this
information is aggregated into a single ForCES MIB by some means
beyond the scope of this document. Nevertheless, the ForCES MIB
design is compatible with both the single-CE and the multiple-CE
case.
4. Association State
Only associations that are UP are shown in the MIB. Associations
enter the UP state as soon as the CE has sent to the FE an
Association Setup Response message containing a successful
Association Setup Result.
Associations are removed from the MIB as soon as they leave 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 if
an Association Teardown message has been sent by the CE.
5. ForCES MIB Definition
The MIB contains the latest ForCES protocol version supported by the The MIB module contains the latest ForCES protocol version supported
CE. Note that the CE must also allow interaction with FEs supporting by the CE (forcesLatestProtocolVersionSupported). Note that the CE
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: following associated information is provided by the MIB module as an
entry (forcesAssociationEntry) in the association table
(forcesAssociationTable):
o Version number of the ForCES protocol running in this association. o Version number of the ForCES protocol running in this association
(forcesAssociationRunningProtocolVersion).
o Time when the association entered the UP state. o Time when the association entered the UP state
(forcesAssociationTimeUp).
o Time when the association left the UP state. Note that this is o Time when the association left the UP state
only used for notification purposes as the association is removed (forcesAssociationTimeDown). Note that this is only used for
from the MIB immediately after it leaves the UP state. notification purposes as the association is removed from the MIB
immediately after it leaves the UP state.
o Number of ForCES Heartbeat messages sent from the CE and received o Number of ForCES Heartbeat messages sent from the CE
by the CE since the association is UP. (forcesAssociationHBMsgSent) and received by the CE
(forcesAssociationHBMsgReceived) since the association is UP.
o Number of other ForCES messages sent from the CE and received by o Number of other ForCES messages sent from the CE
the CE since the association is UP. Only messages other than (forcesAssociationOtherMsgSent) and received by the CE
Heartbeat, Association Setup, Association Setup Response, and (forcesAssociationOtherMsgReceived) since the association is UP.
Association Teardown are counted. Only messages other than Heartbeat, Association Setup, Association
Setup Response, and Association Teardown are counted.
Finally, the MIB defines the following notifications: Finally, the MIB module defines the following notifications:
o Whenever an association enters the UP state, a notification is o Whenever an association enters the UP state, a notification
issued containing the version of the ForCES protocol running. (forcesAssociationEntryUp) is issued containing the version of the
Note that as CE ID and FE ID are indexes, they appear in the OID ForCES protocol running. Note that as CE ID and FE ID are
of the ForCES-protocol running-version object. indexes, they appear in the OID of the ForCES-protocol running-
version object.
o Whenever an association leaves the UP state, a notification is o Whenever an association leaves the UP state, a notification
issued containing all associated information for this association. (forcesAssociationEntryDown) is issued containing all associated
The reason is that the association and all its associated information for this association. The reason is that the
information will be removed from the MIB immediately after this association and all its associated information will be removed
notification has been issued. from the MIB immediately after this notification has been issued.
FORCES-MIB DEFINITIONS ::= BEGIN FORCES-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
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 "200607041200Z" -- Jul 4, 2006 LAST-UPDATED "200607261200Z" -- Jul 26, 2006
ORGANIZATION "Forwarding and Control Element Separation ORGANIZATION "Forwarding and Control Element Separation
(ForCES) Working Group" (ForCES) Working Group"
CONTACT-INFO CONTACT-INFO
"Robert Haas (rha@zurich.ibm.com), IBM" "Robert Haas (rha@zurich.ibm.com), IBM"
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for the "This MIB module contains managed object definitions
ForCES Protocol." for the ForCES Protocol."
REVISION "200607041200Z" -- Jul 4, 2006 REVISION "200607261200Z" -- Jul 26, 2006
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 44 skipping to change at page 5, line 37
ForcesID ::= TEXTUAL-CONVENTION ForcesID ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ForCES identifier is a four octet quantity." "The ForCES identifier is a four octet quantity."
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
ForcesProtocolVersion ::= TEXTUAL-CONVENTION ForcesProtocolVersion ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ForCES protocol version number." "ForCES protocol version number.
SYNTAX INTEGER (1..255) The version numbers used are defined in the
specifications of the respective protocol:
1 - ForCESv1 [RFCzzzz]."
-- RFC Ed.: replace zzzz with actual RFC number of ForCES protocol
-- & remove this note
SYNTAX Integer32 (1..255)
-- Notifications -- Notifications
forcesAssociationEntryUp NOTIFICATION-TYPE forcesAssociationEntryUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
forcesAssociationRunningProtocolVersion forcesAssociationRunningProtocolVersion
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a "This notification is generated as soon
forcesAssociationEntry object is created." as an association enters the UP state."
::= { forcesMibNotifications 1 } ::= { forcesMibNotifications 1 }
forcesAssociationEntryDown NOTIFICATION-TYPE forcesAssociationEntryDown NOTIFICATION-TYPE
OBJECTS { 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 when a "This notification is generated as soon
forcesAssociationEntry object is destroyed." as an association leaves the UP state."
::= { forcesMibNotifications 2 } ::= { forcesMibNotifications 2 }
-- 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.
skipping to change at page 7, line 33 skipping to change at page 7, line 32
forcesAssociationHBMsgReceived Counter32, forcesAssociationHBMsgReceived Counter32,
forcesAssociationOtherMsgSent Counter32, forcesAssociationOtherMsgSent Counter32,
forcesAssociationOtherMsgReceived Counter32 } forcesAssociationOtherMsgReceived Counter32 }
forcesAssociationCEID OBJECT-TYPE forcesAssociationCEID OBJECT-TYPE
SYNTAX ForcesID SYNTAX ForcesID
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ForCES ID of the CE." "The ForCES ID of the CE."
::= { forcesAssociationEntry 2 } ::= { forcesAssociationEntry 1 }
forcesAssociationFEID OBJECT-TYPE forcesAssociationFEID OBJECT-TYPE
SYNTAX ForcesID SYNTAX ForcesID
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ForCES ID of the FE." "The ForCES ID of the FE."
::= { forcesAssociationEntry 3 } ::= { forcesAssociationEntry 2 }
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 4 } ::= { 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."
::= { forcesAssociationEntry 5 } ::= { forcesAssociationEntry 4 }
forcesAssociationTimeDown OBJECT-TYPE forcesAssociationTimeDown 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 left the UP state." association left the UP state."
::= { forcesAssociationEntry 6 } ::= { 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 it is up.
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 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 it is up.
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 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 it is up.
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 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 it is up.
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 10} ::= { forcesAssociationEntry 9 }
-- Conformance -- Conformance
forcesMibCompliances OBJECT IDENTIFIER forcesMibCompliances OBJECT IDENTIFIER
::= { forcesMibConformance 1 } ::= { forcesMibConformance 1 }
forcesMibGroups OBJECT IDENTIFIER forcesMibGroups OBJECT IDENTIFIER
::= { forcesMibConformance 2 } ::= { forcesMibConformance 2 }
-- 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 forcesStatsGroup
DESCRIPTION
"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,
forcesAssociationEntryDown forcesAssociationEntryDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications for signaling important "A collection of notifications for signaling important
ForCES events." ForCES events."
::= { forcesMibGroups 1 } ::= { forcesMibGroups 1 }
forcesMibGroup OBJECT-GROUP forcesMibGroup OBJECT-GROUP
OBJECTS { forcesAssociationRunningProtocolVersion } OBJECTS { forcesLatestProtocolVersionSupported,
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 }
forcesStatsGroup OBJECT-GROUP forcesStatsGroup OBJECT-GROUP
OBJECTS { forcesAssociationTimeUp, OBJECTS { forcesAssociationTimeUp,
forcesAssociationTimeDown, forcesAssociationTimeDown,
forcesAssociationHBMsgSent, forcesAssociationHBMsgSent,
skipping to change at page 10, line 45 skipping to change at page 11, line 5
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 3 }
END END
4. Associations kept in the MIB
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
an Association Setup Response message containing a successful
Association Setup Result.
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
or other protocol message) from the FE within a given time period or
if an Association Teardown message has been sent by the CE.
5. Support for multiple CEs and FEs
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
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
one CE, information about the associations may be distributed among
the CEs. Whether each CE implements the managed objects for the
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
associations in the NE is outside the scope of this document.
6. Security Considerations 6. Security Considerations
Some of the readable objects in this MIB module may be considered Some of the readable objects in this MIB module may be considered
sensitive or vulnerable in some network environment. sensitive or vulnerable in some network environment.
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).
skipping to change at page 11, line 25 skipping to change at page 12, line 8
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 7. IANA Considerations
IANA will need to assign a number to this MIB. The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
forcesMIB { mib-2 XXX }
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
to record the assignment in the SMI Numbers registry. When the
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
this note.
8. Changes from Previous Draft Revisions 8. Changes from Previous Draft Revisions
Editor's Note (to be removed prior to publication): Prior to RFC
publication of this document, the RFC Editor is asked to remove this
entire section titled "Changes from Previous Draft Versions".
Changes from draft-ietf-forces-mib-03. They are small fixes to the
text and the MIB module:
o Added MIB boilerplate according to
http://www.ops.ietf.org/mib-boilerplate.html
o Clarified terminology with respect to MIB module and MIB managed
objects.
o Added RFC Editor note to indicate RFC number for version 1 of
ForCES protocol under ForcesProtocolVersion.
o Renumbered elements in forcesAssociationEntry starting with 1.
o Changed ForcesProtocolVersion from INTEGER to Integer32.
o Added forcesLatestProtocolVersionSupported into the mandatory
forcesMibGroups conformance group.
o Explicitely added the forcesStatsGroup to the forcesMibCompliance
compliance statement as optional.
o Moved the MIB Definition section to the front.
o Rephrased IANA Considerations section according to RFC 4181
Section 3.5.2.
o Added RFC Editor note to remove the "Changes from Previous Draft
Revisions" section prior to publication.
Changes from draft-ietf-forces-mib-02. They are refinements of the Changes from draft-ietf-forces-mib-02. They are refinements of the
MIB: MIB module:
o Changed forcesAssociationCEID and forcesAssociationFEID from read- o Changed forcesAssociationCEID and forcesAssociationFEID from read-
only to not-accessible to conform with Section 7.7 in [RFC2578]. only to not-accessible to conform with Section 7.7 in [RFC2578].
o Removed forcesAssociationCEID and forcesAssociationFEID from the o Removed forcesAssociationCEID and forcesAssociationFEID from the
notifications. This information is conveyed in the OID anyway. notifications. This information is conveyed in the OID anyway.
o Added MIB conformance information. o Added MIB conformance information.
Changes from draft-ietf-forces-mib-01. The changes are in response Changes from draft-ietf-forces-mib-01. The changes are in response
skipping to change at page 12, line 19 skipping to change at page 14, line 4
the CE. the CE.
9. References 9. References
9.1. Normative References 9.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.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Introduction and Applicability Statements for Internet- Schoenwaelder, Ed., "Textual Conventions for SMIv2",
Standard Management Framework", RFC 3410, December 2002. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC3654] Khosravi, H. and T. Anderson, "Requirements for Separation [RFC3654] Khosravi, H. and T. Anderson, "Requirements for Separation
of IP Control and Forwarding", RFC 3654, November 2003. of IP Control and Forwarding", RFC 3654, November 2003.
[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 9.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.
[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, Xiaoyi Guo, Joel Halpern, Tom Petch, and Jamal Hadi Salim.
skipping to change at page 14, line 5 skipping to change at page 16, line 5
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
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 14, line 29 skipping to change at page 16, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 47 change blocks. 
122 lines changed or deleted 210 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/