draft-ietf-forces-mib-10.txt   rfc5813.txt 
Forwarding and Control Element R. Haas Internet Engineering Task Force (IETF) R. Haas
Separation (forces) IBM Request for Comments: 5813 IBM
Internet-Draft September 10, 2008 Category: Standards Track March 2010
Intended status: Standards Track ISSN: 2070-1721
Expires: March 14, 2009
ForCES MIB Forwarding and Control Element Separation (ForCES) MIB
draft-ietf-forces-mib-10
Status of this Memo Abstract
By submitting this Internet-Draft, each author represents that any This memo defines a Management Information Base (MIB) module for use
applicable patent or other IPR claims of which he or she is aware with network management protocols in the Internet community. In
have been or will be disclosed, and any of which he or she becomes particular, it defines managed objects for the Forwarding and Control
aware will be disclosed, in accordance with Section 6 of BCP 79. Element Separation (ForCES) Network Element (NE).
Internet-Drafts are working documents of the Internet Engineering Status of This Memo
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months This is an Internet Standards Track document.
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/ietf/1id-abstracts.txt. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
The list of Internet-Draft Shadow Directories can be accessed at Information about the current status of this document, any errata,
http://www.ietf.org/shadow.html. and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc5813.
This Internet-Draft will expire on March 14, 2009. Copyright Notice
Abstract Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This memo defines a Management Information Base (MIB) module for use This document is subject to BCP 78 and the IETF Trust's Legal
with network management protocols in the Internet community. In Provisions Relating to IETF Documents
particular, it defines managed objects for the Forwarding and Control (http://trustee.ietf.org/license-info) in effect on the date of
Element Separation (ForCES) Network Element (NE). publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. The Internet-Standard Management Framework ......................2
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. Introduction ....................................................2
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Requirements Notation ...........................................3
4. ForCES MIB Overview . . . . . . . . . . . . . . . . . . . . . 3 4. ForCES MIB Overview .............................................3
5. ForCES MIB Definition . . . . . . . . . . . . . . . . . . . . 5 5. ForCES MIB Definition ...........................................4
6. Associations kept in the MIB . . . . . . . . . . . . . . . . . 13 6. Associations Kept in the MIB ...................................13
7. Support for multiple CEs and FEs . . . . . . . . . . . . . . . 13 7. Support for Multiple CEs and FEs ...............................14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14 8. Security Considerations ........................................14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 9. IANA Considerations ............................................15
10. Changes from Previous Draft Revisions . . . . . . . . . . . . 15 10. References ....................................................15
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 10.1. Normative References .....................................15
11.1. Normative References . . . . . . . . . . . . . . . . . . 18 10.2. Informative References ...................................16
11.2. Informative References . . . . . . . . . . . . . . . . . 18 Appendix A. Acknowledgments ......................................17
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . . . 20
1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
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 2. Introduction
The ForCES MIB module is a read-only MIB module that captures The ForCES MIB module is a read-only MIB module that captures
information related to the ForCES protocol ([RFC3654], [RFC3746], information related to the ForCES protocol ([RFC3654], [RFC3746],
[forces-applicability-draft] and [forces-protocol-draft]). [FORCES-APP], and [RFC5810]).
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 (between Control Elements and Forwarding Elements) to associations (between Control Elements and Forwarding Elements)
that are in the UP state includes: that are in the UP state 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. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
4. ForCES MIB Overview 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 Control Element (CE) (forcesLatestProtocolVersionSupported). by the Control Element (CE) (forcesLatestProtocolVersionSupported).
Note that the CE must also allow interaction with Forwarding Elements Note that the CE must also allow interaction with Forwarding Elements
(FEs) supporting earlier versions. (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
skipping to change at page 5, line 25 skipping to change at page 4, line 36
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
ZeroBasedCounter32 ZeroBasedCounter32
FROM RMON2-MIB; FROM RMON2-MIB;
forcesMib MODULE-IDENTITY forcesMib MODULE-IDENTITY
LAST-UPDATED "200809101200Z" -- Sep 10, 2008 LAST-UPDATED "201003100000Z" -- March 10, 2010
ORGANIZATION "IETF Forwarding and Control Element ORGANIZATION "IETF Forwarding and Control Element
Separation (ForCES) Working Group" Separation (ForCES) Working Group"
CONTACT-INFO CONTACT-INFO
"WG Charter: "WG Charter:
http://www.ietf.org/html.charters/forces-charter.html http://www.ietf.org/html.charters/forces-charter.html
Mailing lists: Mailing lists:
General Discussion: forces@peach.ease.lsoft.com General Discussion: forces@ietf.org
To Subscribe: listserv@peach.ease.lsoft.com To Subscribe:
In Body: subscribe forces https://www.ietf.org/mailman/listinfo/forces
Chairs: Patrick Droz Chairs: Patrick Droz
Email: dro@zurich.ibm.com Email: dro@zurich.ibm.com
Jamal Hadi Salim Jamal Hadi Salim
Email: hadi@znyx.com Email: hadi@mojatatu.com
Editor: Robert Haas Editor: Robert Haas
IBM IBM
Email: rha@zurich.ibm.com" 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.
Copyright (C) The Internet Trust (2008). This
version of this MIB module is part of RFC yyyy; see Copyright (c) 2010 IETF Trust and the persons identified
the RFC itself for full legal notices." as authors of the code. All rights reserved.
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200809101200Z" -- Sep 10, 2008 Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and
subject to the license terms contained in, the
Simplified BSD License set forth in Section 4.c of the
IETF Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this MIB module is part of RFC 5813;
see the RFC itself for full legal notices."
REVISION "201003100000Z" -- March 10, 2010
DESCRIPTION DESCRIPTION
"Initial version, published as RFC yyyy." "Initial version, published as RFC 5813."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note ::= { mib-2 187 }
::= { mib-2 XXX }
-- 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 }
forcesMibConformance OBJECT IDENTIFIER ::= { forcesMib 2 } forcesMibConformance OBJECT IDENTIFIER ::= { forcesMib 2 }
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 4-octet quantity."
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
ForcesProtocolVersion ::= TEXTUAL-CONVENTION ForcesProtocolVersion ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
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, RFC 5810."
-- RFC Ed.: replace zzzz with actual RFC number of ForCES protocol
-- & remove this note
SYNTAX Integer32 (1..255) SYNTAX Integer32 (1..255)
-- Notifications -- Notifications
forcesAssociationEntryUp NOTIFICATION-TYPE forcesAssociationEntryUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
forcesAssociationRunningProtocolVersion forcesAssociationRunningProtocolVersion
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 9, line 24 skipping to change at page 9, line 10
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ForCES ID of the FE." "The ForCES ID of the FE."
::= { forcesAssociationEntry 2 } ::= { 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
association. this 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
skipping to change at page 10, line 10 skipping to change at page 9, line 43
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 ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
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 been sent by the CE on this association
since the association entered the UP state. since the association entered the UP state.
Discontinuities in the value of this counter Discontinuities in the value of this counter
can occur at re-initialization of the management can occur at reinitialization of the management
system, and at other times as indicated by the system, and at other times as indicated by the
value of forcesAssociationCounterDiscontinuityTime." value of forcesAssociationCounterDiscontinuityTime."
::= { forcesAssociationEntry 6 } ::= { forcesAssociationEntry 6 }
forcesAssociationHBMsgReceived OBJECT-TYPE forcesAssociationHBMsgReceived OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
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 the association entered the UP state. since the association entered the UP state.
Discontinuities in the value of this counter Discontinuities in the value of this counter
can occur at re-initialization of the management can occur at reinitialization of the management
system, and at other times as indicated by the system, and at other times as indicated by the
value of forcesAssociationCounterDiscontinuityTime." value of forcesAssociationCounterDiscontinuityTime."
::= { forcesAssociationEntry 7 } ::= { forcesAssociationEntry 7 }
forcesAssociationOperMsgSent OBJECT-TYPE forcesAssociationOperMsgSent OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
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 the association entered the UP state. since the association entered the UP state.
Discontinuities in the value of this counter Discontinuities in the value of this counter
can occur at re-initialization of the management can occur at reinitialization of the management
system, and at other times as indicated by the system, and at other times as indicated by the
value of forcesAssociationCounterDiscontinuityTime." value of forcesAssociationCounterDiscontinuityTime."
::= { forcesAssociationEntry 8 } ::= { forcesAssociationEntry 8 }
forcesAssociationOperMsgReceived OBJECT-TYPE forcesAssociationOperMsgReceived OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
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 the association entered the UP state. since the association entered the UP state.
Discontinuities in the value of this counter Discontinuities in the value of this counter
can occur at re-initialization of the management can occur at reinitialization of the management
system, and at other times as indicated by the system, and at other times as indicated by the
value of forcesAssociationCounterDiscontinuityTime." value of forcesAssociationCounterDiscontinuityTime."
::= { forcesAssociationEntry 9 } ::= { forcesAssociationEntry 9 }
forcesAssociationCounterDiscontinuityTime OBJECT-TYPE forcesAssociationCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion "The value of sysUpTime on the most recent occasion
at which any one or more of this association's at which any one or more of this association's
counters suffered a discontinuity. The relevant counters suffered a discontinuity. The relevant
counters are the specific instances associated with counters are the specific instances associated with
this association of any ZeroBasedCounter32 object this association of any ZeroBasedCounter32 object
contained in the forcesAssociationTable. If no contained in the forcesAssociationTable. If no
such discontinuities have occured since the last such discontinuities have occurred since the last
reinitialization of the local management subsystem, reinitialization of the local management subsystem,
then this object contains a zero value." then this object contains a zero value."
::= { forcesAssociationEntry 10 } ::= { forcesAssociationEntry 10 }
-- 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
implementing the ForCES MIB." ForCES and implementing the ForCES MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { forcesMibGroup, forcesNotificationGroup } MANDATORY-GROUPS { forcesMibGroup, forcesNotificationGroup }
GROUP forcesNotificationStatsGroup GROUP forcesNotificationStatsGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is recommended." "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,
forcesAssociationEntryDown forcesAssociationEntryDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications for signaling
"A collection of notifications for signaling important important ForCES events."
ForCES events."
::= { forcesMibGroups 1 } ::= { forcesMibGroups 1 }
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
routers." of ForCES routers."
::= { forcesMibGroups 2 } ::= { forcesMibGroups 2 }
forcesNotificationStatsGroup NOTIFICATION-GROUP forcesNotificationStatsGroup NOTIFICATION-GROUP
NOTIFICATIONS { forcesAssociationEntryUpStats, NOTIFICATIONS { forcesAssociationEntryUpStats,
forcesAssociationEntryDownStats forcesAssociationEntryDownStats
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional notifications for
"A collection of optional notifications for signaling signaling important ForCES events including
important ForCES events including statistics." statistics."
::= { forcesMibGroups 3 } ::= { forcesMibGroups 3 }
forcesStatsGroup OBJECT-GROUP forcesStatsGroup OBJECT-GROUP
OBJECTS { forcesAssociationTimeUp, OBJECTS { forcesAssociationTimeUp,
forcesAssociationTimeDown, forcesAssociationTimeDown,
forcesAssociationHBMsgSent, forcesAssociationHBMsgSent,
forcesAssociationHBMsgReceived, forcesAssociationHBMsgReceived,
forcesAssociationOperMsgSent, forcesAssociationOperMsgSent,
forcesAssociationOperMsgReceived, forcesAssociationOperMsgReceived,
forcesAssociationCounterDiscontinuityTime forcesAssociationCounterDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects to provide extra "A collection of optional objects to provide
information about the associations. There is no protocol extra information about the associations.
reason to keep such information, but these objects can There is no protocol reason to keep such
be very useful in debugging connectivity problems." information, but these objects can be very
useful in debugging connectivity problems."
::= { forcesMibGroups 4} ::= { forcesMibGroups 4}
END END
6. Associations kept in the MIB 6. Associations Kept in the MIB
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. Only associations that are UP are Association Setup Result. Only associations that are UP are
reflected in this MIB module. reflected in this MIB module.
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.
Statistics counters are initialized to zero when the association is Statistics counters are initialized to zero when the association is
created. If the same association goes down and comes back up, the created. If the same association goes down and comes back up, the
counters will reset and the discontinuity can be discovered by counters will reset and the discontinuity can be discovered by
checking the discontinuity timestamp. In addition, the time-up checking the discontinuity timestamp. In addition, the time-up
timestamp in the association allows to distinguish new associations timestamp in the association allows to distinguish new associations
from past ones with the same index. Note that the optional down from past ones with the same index. Note that the optional down
notification contains the statistics with the final values of the notification contains the statistics with the final values of the
statistics counters. statistics counters.
7. Support for multiple CEs and FEs 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.
skipping to change at page 15, line 9 skipping to change at page 15, line 17
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. 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 187 }
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.
10. 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-09: Moved the DISPLAY-HINT clause
in the ForcesProtocolVersion MIB object before the STATUS clause to
be conformant with RFC2579 (comment from Bert).
Changes from draft-ietf-forces-mib-08:
o Changed the MIB objects forcesAssociationOtherMsgSent and
forcesAssociationOtherMsgReceived to forcesAssociationOperMsgSent
and forcesAssociationOperMsgReceived as they are not all other
messages besides HB (comment from the General Area Review Team).
o Changed MIB counter objects forcesAssociationHBMsgSent,
forcesAssociationHBMsgReceived, forcesAssociationOperMsgSent, and
forcesAssociationOperMsgReceived from Counter32 to
ZeroBasedCounter32 (comment from Bert Wijnen). Adapted the
paragraph about statistics counters in section "Associations kept
in the MIB"
o Introduced a MIB object forcesAssociationCounterDiscontinuityTime,
and added it to the forcesAssociationEntry as well as to the
forcesAssociationEntryDownStats notification and the
forcesStatsGroup compliance group. Added text on discontinuity
for all counter objects.
o Removed MIB counters from the forcesAssociationEntryUpStats
notification, as passing now zero values is useless.
Changes from draft-ietf-forces-mib-07: They are editorial changes
made as suggested by the General Area Review Team.
Changes from draft-ietf-forces-mib-06:
o Informational RFCs 3654 and 3746 moved to Informative References
section.
o Updated chairs' names in the MIB description.
o Update references to protocol and applicability drafts.
o Reversed the order of the two first sentences in section
"Associations kept in the MIB"
Changes from draft-ietf-forces-mib-05: Copyright statement in the MIB
description corrected to IETF Trust.
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
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
MIB module:
o Changed forcesAssociationCEID and forcesAssociationFEID from read-
only to not-accessible to conform with Section 7.7 in [RFC2578].
o Removed forcesAssociationCEID and forcesAssociationFEID from the
notifications. This information is conveyed in the OID anyway.
o Added MIB conformance information.
Changes from draft-ietf-forces-mib-01. The changes are in response
to the Working Group Last Call:
o Addition of two traps/notifications to signal the associations
that enter or leave the UP state.
o Suppression of the DOWN and ESTABLISHING states. Only
associations in the UP state are kept in the table.
o Split of the Message counters into Heartbeat and other messages.
o Addition of the current running version of ForCES protocol for
each association in the UP state.
o Addition of the latest version of the ForCES protocol supported by
the CE.
11. References 10. References
11.1. Normative References 10.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.
[forces-protocol-draft] [RFC5810] Doria, A., Ed., Hadi Salim, J., Ed., Haas, R., Ed.,
Doria, A., Haas, R., Hadi Salim, J., Khosravi, H., and W. Khosravi, H., Ed., Wang, W., Ed., Dong, L., Gopal, R., and
Wang, "ForCES Protocol Specification", ID Document: J. Halpern, "Forwarding and Control Element Separation
draft-ietf-forces-protocol-15.txt, August 2008. (ForCES) Protocol Specification", RFC 5810, March 2010.
11.2. Informative References 10.2. Informative References
[FORCES-APP]
Crouch, A., Khosravi, H., Doria, A., Wang, X., and K.
Ogawa, "ForCES Applicability Statement", Work in Progress,
February 2010.
[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
Standard Management Framework", RFC 3410, December 2002. Internet-Standard Management Framework", RFC 3410,
December 2002.
[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-applicability-draft]
Crouch, A., Khosravi, H., Handley, M., and A. Doria,
"ForCES Applicability Statement", ID Document:
draft-ietf-forces-applicability-05.txt, July 2006.
Appendix A. Acknowledgments Appendix A. Acknowledgments
The author gratefully acknowledges the contributions of: Jinrong The author gratefully acknowledges the contributions of Spencer
Fenggen, John Flick, Xiaoyi Guo, Joel Halpern, Tom Petch, and Jamal Dawkins, Jinrong Fenggen, John Flick, Xiaoyi Guo, Joel Halpern, Tom
Hadi Salim. Petch, Jamal Hadi Salim, and Bert Wijnen.
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
Copyright (C) The IETF Trust (2008).
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, THE IETF TRUST 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
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 52 change blocks. 
281 lines changed or deleted 129 lines changed or added

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