draft-ietf-forces-mib-07.txt   draft-ietf-forces-mib-08.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: February 26, 2009 Expires: March 7, 2009
ForCES MIB ForCES MIB
draft-ietf-forces-mib-07 draft-ietf-forces-mib-08
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 February 26, 2009. This Internet-Draft will expire on March 7, 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 . . . . . . . . . . . . . . . . . 12 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 . . . . . . . . . . . . . . . . . . . 13
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10. Changes from Previous Draft Revisions . . . . . . . . . . . . 14 10. Changes from Previous Draft Revisions . . . . . . . . . . . . 14
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
11.1. Normative References . . . . . . . . . . . . . . . . . . 17 11.1. Normative References . . . . . . . . . . . . . . . . . . 17
11.2. Informative References . . . . . . . . . . . . . . . . . 17 11.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 18 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 18 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . . . . 19
1. Requirements notation 1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
skipping to change at page 3, line 35 skipping to change at page 3, line 35
3. Introduction 3. 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-applicability-draft] and [forces-protocol-draft]).
The ForCES MIB module does not include information that is specified The ForCES MIB module does not include information that is specified
in other MIB modules, such as packet counters for interfaces, etc. in other MIB modules, such as packet counters for interfaces, etc.
More specifically, the information in the ForCES MIB module relative More specifically, the information in the ForCES MIB module relative
to associations that are up includes: to associations (between Control Elements and Forwarding Elements)
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.
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 CE (forcesLatestProtocolVersionSupported). Note that the CE by the Control Element (CE) (forcesLatestProtocolVersionSupported).
must also allow interaction with FEs supporting earlier versions. Note that the CE must also allow interaction with Forwarding Elements
(FEs) supporting earlier versions.
For each association identified by the pair CE ID and FE ID, the For each association identified by the pair CE ID and FE ID, the
following associated information is provided by the MIB module as an following associated information is provided by the MIB module as an
entry (forcesAssociationEntry) in the association table entry (forcesAssociationEntry) in the association table
(forcesAssociationTable): (forcesAssociationTable):
o Version number of the ForCES protocol running in this association o Version number of the ForCES protocol running in this association
(forcesAssociationRunningProtocolVersion). (forcesAssociationRunningProtocolVersion).
o Time when the association entered the UP state o Time when the association entered the UP state
skipping to change at page 4, line 35 skipping to change at page 4, line 37
(forcesAssociationOtherMsgSent) and received by the CE (forcesAssociationOtherMsgSent) and received by the CE
(forcesAssociationOtherMsgReceived) since the association entered (forcesAssociationOtherMsgReceived) 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. Note that as CE ID and FE ID are ForCES protocol running. CE ID and FE ID are concatenated to form
indexes, they appear in the OID of the ForCES-protocol running- the table index, hence they appear in the OID of the ForCES-
version object. Optionally, a notification protocol running-version object. Optionally, a notification
(forcesAssociationEntryUpStats) can instead be issued with all (forcesAssociationEntryUpStats) can instead be issued with all
associated information for this association, except associated information for this association, except
forcesAssociationTimeDown. forcesAssociationTimeDown.
o Whenever an association leaves the UP state, a notification o Whenever an association leaves the UP state, a notification
(forcesAssociationEntryDown) is issued containing the version of (forcesAssociationEntryDown) is issued containing the version of
the ForCES protocol running. Optionally, a notification the ForCES protocol running. Optionally, a notification
(forcesAssociationEntryDownStats) can instead be issued with all (forcesAssociationEntryDownStats) can instead be issued with all
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
skipping to change at page 5, line 19 skipping to change at page 5, line 22
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 "200808251200Z" -- Aug 25, 2008 LAST-UPDATED "200809031200Z" -- Sep 3, 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 46 skipping to change at page 5, line 49
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 "200808251200Z" -- Aug 25, 2008 REVISION "200809031200Z" -- Sep 3, 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 14, line 46 skipping to change at page 15, line 7
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-07: They are editorial changes
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.
o Update references to protocol and applicability drafts. o Update references to protocol and applicability drafts.
o Reversed the order of the two first sentences in section o Reversed the order of the two first sentences in section
 End of changes. 11 change blocks. 
13 lines changed or deleted 18 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/