draft-ietf-forces-mib-08.txt   draft-ietf-forces-mib-09.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: March 7, 2009 Expires: March 13, 2009
ForCES MIB ForCES MIB
draft-ietf-forces-mib-08 draft-ietf-forces-mib-09
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 March 7, 2009. This Internet-Draft will expire on March 13, 2009.
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). Element Separation (ForCES) Network Element (NE).
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. ForCES MIB Overview . . . . . . . . . . . . . . . . . . . . . 3 4. ForCES MIB Overview . . . . . . . . . . . . . . . . . . . . . 3
5. ForCES MIB Definition . . . . . . . . . . . . . . . . . . . . 5 5. ForCES MIB Definition . . . . . . . . . . . . . . . . . . . . 5
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 . . . . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10. Changes from Previous Draft Revisions . . . . . . . . . . . . 14 10. Changes from Previous Draft Revisions . . . . . . . . . . . . 15
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
11.1. Normative References . . . . . . . . . . . . . . . . . . 17 11.1. Normative References . . . . . . . . . . . . . . . . . . 18
11.2. Informative References . . . . . . . . . . . . . . . . . 18 11.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 18 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 18 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . . . . 20
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. The Internet-Standard Management Framework 2. 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
skipping to change at page 4, line 26 skipping to change at page 4, line 26
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 entered the (forcesAssociationHBMsgReceived) since the association entered the
UP state. UP state.
o Number of other ForCES messages sent from the CE o Number of operational ForCES messages sent from the CE
(forcesAssociationOtherMsgSent) and received by the CE (forcesAssociationOperMsgSent) and received by the CE
(forcesAssociationOtherMsgReceived) since the association entered (forcesAssociationOperMsgReceived) since the association entered
the UP state. Only messages other than Heartbeat, Association the UP state. Only messages other than Heartbeat, Association
Setup, Association Setup Response, and Association Teardown are Setup, Association Setup Response, and Association Teardown are
counted. 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. CE ID and FE ID are concatenated to form ForCES protocol running. CE ID and FE ID are concatenated to form
the table index, hence they appear in the OID of the ForCES- the table index, hence they appear in the OID of the ForCES-
skipping to change at page 5, line 11 skipping to change at page 5, line 11
associated information for this association. The reason is that associated information for this association. The reason is that
the association and all its associated information will be removed 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 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
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
ZeroBasedCounter32
FROM RMON2-MIB;
forcesMib MODULE-IDENTITY forcesMib MODULE-IDENTITY
LAST-UPDATED "200809031200Z" -- Sep 3, 2008 LAST-UPDATED "200809091200Z" -- Sep 9, 2008
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@peach.ease.lsoft.com
To Subscribe: listserv@peach.ease.lsoft.com To Subscribe: listserv@peach.ease.lsoft.com
In Body: subscribe forces In Body: subscribe forces
skipping to change at page 5, line 49 skipping to change at page 6, line 4
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 Copyright (C) The Internet Trust (2008). This
version of this MIB module is part of RFC yyyy; see version of this MIB module is part of RFC yyyy; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200809031200Z" -- Sep 3, 2008 REVISION "200809091200Z" -- Sep 9, 2008
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 7, line 18 skipping to change at page 7, line 20
"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.
Note that these notifications are not Note that these notifications are not
throttled as the CE itself should throttled as the CE itself should
throttle the setup of associations." throttle the setup of associations."
::= { forcesMibNotifications 2 } ::= { forcesMibNotifications 2 }
forcesAssociationEntryUpStats NOTIFICATION-TYPE forcesAssociationEntryUpStats NOTIFICATION-TYPE
OBJECTS { OBJECTS {
forcesAssociationRunningProtocolVersion, forcesAssociationRunningProtocolVersion,
forcesAssociationTimeUp, forcesAssociationTimeUp
forcesAssociationHBMsgSent,
forcesAssociationHBMsgReceived,
forcesAssociationOtherMsgSent,
forcesAssociationOtherMsgReceived
} }
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 Note that these notifications are not
throttled as the CE itself should throttled as the CE itself should
throttle the setup of associations." throttle the setup of associations."
::= { forcesMibNotifications 3 } ::= { forcesMibNotifications 3 }
forcesAssociationEntryDownStats NOTIFICATION-TYPE forcesAssociationEntryDownStats NOTIFICATION-TYPE
OBJECTS { OBJECTS {
forcesAssociationRunningProtocolVersion, forcesAssociationRunningProtocolVersion,
forcesAssociationTimeUp, forcesAssociationTimeUp,
forcesAssociationTimeDown, forcesAssociationTimeDown,
forcesAssociationHBMsgSent, forcesAssociationHBMsgSent,
forcesAssociationHBMsgReceived, forcesAssociationHBMsgReceived,
forcesAssociationOtherMsgSent, forcesAssociationOperMsgSent,
forcesAssociationOtherMsgReceived forcesAssociationOperMsgReceived,
forcesAssociationCounterDiscontinuityTime
} }
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.
Note that these notifications are not Note that these notifications are not
throttled as the CE itself should throttled as the CE itself should
throttle the setup of associations." throttle the setup of associations."
::= { forcesMibNotifications 4 } ::= { forcesMibNotifications 4 }
skipping to change at page 8, line 47 skipping to change at page 8, line 44
ForcesAssociationEntry ::= SEQUENCE { ForcesAssociationEntry ::= SEQUENCE {
forcesAssociationCEID ForcesID, forcesAssociationCEID ForcesID,
forcesAssociationFEID ForcesID, forcesAssociationFEID ForcesID,
forcesAssociationRunningProtocolVersion forcesAssociationRunningProtocolVersion
ForcesProtocolVersion, ForcesProtocolVersion,
forcesAssociationTimeUp TimeStamp, forcesAssociationTimeUp TimeStamp,
forcesAssociationTimeDown TimeStamp, forcesAssociationTimeDown TimeStamp,
forcesAssociationHBMsgSent Counter32, forcesAssociationHBMsgSent ZeroBasedCounter32,
forcesAssociationHBMsgReceived Counter32, forcesAssociationHBMsgReceived ZeroBasedCounter32,
forcesAssociationOtherMsgSent Counter32, forcesAssociationOperMsgSent ZeroBasedCounter32,
forcesAssociationOtherMsgReceived Counter32 } forcesAssociationOperMsgReceived ZeroBasedCounter32,
forcesAssociationCounterDiscontinuityTime TimeStamp
}
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 1 } ::= { forcesAssociationEntry 1 }
forcesAssociationFEID OBJECT-TYPE forcesAssociationFEID OBJECT-TYPE
skipping to change at page 10, line 5 skipping to change at page 10, line 5
forcesAssociationTimeDown OBJECT-TYPE forcesAssociationTimeDown OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS accessible-for-notify 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 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 have been sent by the CE on this association
since the association entered the UP state. since the association entered the UP state.
If this association started prior to the last Discontinuities in the value of this counter
initialization of the network subsystem, then can occur at re-initialization of the management
this object contains the value since the system, and at other times as indicated by the
initialization." value of forcesAssociationCounterDiscontinuityTime."
::= { forcesAssociationEntry 6 } ::= { forcesAssociationEntry 6 }
forcesAssociationHBMsgReceived OBJECT-TYPE forcesAssociationHBMsgReceived OBJECT-TYPE
SYNTAX Counter32 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.
If this association started prior to the last Discontinuities in the value of this counter
initialization of the network subsystem, then can occur at re-initialization of the management
this object contains the value since the system, and at other times as indicated by the
initialization." value of forcesAssociationCounterDiscontinuityTime."
::= { forcesAssociationEntry 7 } ::= { forcesAssociationEntry 7 }
forcesAssociationOtherMsgSent OBJECT-TYPE forcesAssociationOperMsgSent OBJECT-TYPE
SYNTAX Counter32 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.
If this association started prior to the last Discontinuities in the value of this counter
initialization of the network subsystem, then can occur at re-initialization of the management
this object contains the value since the system, and at other times as indicated by the
initialization." value of forcesAssociationCounterDiscontinuityTime."
::= { forcesAssociationEntry 8 } ::= { forcesAssociationEntry 8 }
forcesAssociationOtherMsgReceived OBJECT-TYPE forcesAssociationOperMsgReceived OBJECT-TYPE
SYNTAX Counter32 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.
If this association started prior to the last Discontinuities in the value of this counter
initialization of the network subsystem, then can occur at re-initialization of the management
this object contains the value since the system, and at other times as indicated by the
initialization." value of forcesAssociationCounterDiscontinuityTime."
::= { forcesAssociationEntry 9 } ::= { forcesAssociationEntry 9 }
forcesAssociationCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion
at which any one or more of this association's
counters suffered a discontinuity. The relevant
counters are the specific instances associated with
this association of any ZeroBasedCounter32 object
contained in the forcesAssociationTable. If no
such discontinuities have occured since the last
reinitialization of the local management subsystem,
then this object contains a zero value."
::= { 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
skipping to change at page 12, line 34 skipping to change at page 13, line 5
"A collection of optional notifications for signaling "A collection of optional notifications for signaling
important ForCES events including statistics." important ForCES events including statistics."
::= { forcesMibGroups 3 } ::= { forcesMibGroups 3 }
forcesStatsGroup OBJECT-GROUP forcesStatsGroup OBJECT-GROUP
OBJECTS { forcesAssociationTimeUp, OBJECTS { forcesAssociationTimeUp,
forcesAssociationTimeDown, forcesAssociationTimeDown,
forcesAssociationHBMsgSent, forcesAssociationHBMsgSent,
forcesAssociationHBMsgReceived, forcesAssociationHBMsgReceived,
forcesAssociationOtherMsgSent, forcesAssociationOperMsgSent,
forcesAssociationOtherMsgReceived forcesAssociationOperMsgReceived,
forcesAssociationCounterDiscontinuityTime
} }
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 4} ::= { forcesMibGroups 4}
END END
skipping to change at page 13, line 17 skipping to change at page 13, line 31
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 not initialized to zero when the association Statistics counters are initialized to zero when the association is
is created. Instead, a delta value must be calculated from two created. If the same association goes down and comes back up, the
successive readings. Note that the optional up and down counters will reset and the discontinuity can be discovered by
notifications contain the statistics with the initial and final value checking the discontinuity timestamp. In addition, the time-up
of the statistics. timestamp in the association allows to distinguish new associations
from past ones with the same index. Note that the optional down
notification contains the statistics with the final values of the
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
skipping to change at page 15, line 7 skipping to change at page 15, line 24
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.
10. 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-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 Changes from draft-ietf-forces-mib-07: They are editorial changes
made as suggested by the General Area Review Team. made as suggested by the General Area Review Team.
Changes from draft-ietf-forces-mib-06: Changes from draft-ietf-forces-mib-06:
o Informational RFCs 3654 and 3746 moved to Informative References o Informational RFCs 3654 and 3746 moved to Informative References
section. section.
o Updated chairs' names in the MIB description. o Updated chairs' names in the MIB description.
 End of changes. 26 change blocks. 
57 lines changed or deleted 102 lines changed or added

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