draft-ietf-forces-mib-06.txt   draft-ietf-forces-mib-07.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: September 12, 2008 Expires: February 26, 2009
ForCES MIB ForCES MIB
draft-ietf-forces-mib-06 draft-ietf-forces-mib-07
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 September 12, 2008. This Internet-Draft will expire on February 26, 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
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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 . . . . . . . . . . . . . . . . . 12
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 . . . . . . . . . . . . . . . . . 17
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 17 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].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
skipping to change at page 5, line 19 skipping to change at page 5, line 19
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 "200803111200Z" -- Mar 11, 2008 LAST-UPDATED "200808251200Z" -- Aug 25, 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
Chairs: Patrick Droz Chairs: Patrick Droz
Email: dro@zurich.ibm.com Email: dro@zurich.ibm.com
David Putzolu Jamal Hadi Salim
Email: David.Putzolu@intel.com Email: hadi@znyx.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 IETF 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 "200803111200Z" -- Mar 11, 2008 REVISION "200808251200Z" -- Aug 25, 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 12, line 45 skipping to change at page 12, line 45
"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
6. Associations kept in the MIB 6. 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 Associations enter the UP state as soon as the CE has sent to the FE
an Association Setup Response message containing a successful an Association Setup Response message containing a successful
Association Setup Result. Association Setup Result. Only associations that are UP are
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 not initialized to zero when the association
is created. Instead, a delta value must be calculated from two is created. Instead, a delta value must be calculated from two
successive readings. Note that the optional up and down successive readings. Note that the optional up and down
notifications contain the statistics with the initial and final value notifications contain the statistics with the initial and final value
skipping to change at page 14, line 46 skipping to change at page 14, line 46
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-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 Changes from draft-ietf-forces-mib-05: Copyright statement in the MIB
description corrected to IETF Trust. description corrected to IETF Trust.
Changes from draft-ietf-forces-mib-04. They are changes suggested by Changes from draft-ietf-forces-mib-04. They are changes suggested by
the MIB doctor review, according to the MIB Review Checklist in the MIB doctor review, according to the MIB Review Checklist in
Appendix A of RFC 4181: Appendix A of RFC 4181:
o Changed MIB descriptions with "since the association entered the o Changed MIB descriptions with "since the association entered the
UP state" instead of "since the association is up". UP state" instead of "since the association is up".
skipping to change at page 17, line 24 skipping to change at page 17, line 35
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.
[RFC3654] Khosravi, H. and T. Anderson, "Requirements for Separation
of IP Control and Forwarding", RFC 3654, November 2003.
[RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal,
"Forwarding and Control Element Separation (ForCES)
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-15.txt, August 2008.
11.2. Informative References 11.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC3654] Khosravi, H. and T. Anderson, "Requirements for Separation
of IP Control and Forwarding", RFC 3654, November 2003.
[RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal,
"Forwarding and Control Element Separation (ForCES)
Framework", RFC 3746, April 2004.
[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-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: Jinrong
Fenggen, John Flick, Xiaoyi Guo, Joel Halpern, Tom Petch, and Jamal Fenggen, John Flick, Xiaoyi Guo, Joel Halpern, Tom Petch, and Jamal
Hadi Salim. Hadi Salim.
Author's Address Author's Address
Robert Haas Robert Haas
 End of changes. 15 change blocks. 
20 lines changed or deleted 32 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/