draft-ietf-pce-pcep-mib-08.txt   draft-ietf-pce-pcep-mib-09.txt 
PCE Working Group A. Koushik PCE Working Group A. Koushik
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track E. Stephan Intended status: Standards Track E. Stephan
Expires: October 4, 2014 France Telecom Expires: January 26, 2015 Orange
Q. Zhao Q. Zhao
Huawei Technology Huawei Technology
D. King D. King
Old Dog Consulting Old Dog Consulting
J. Hardwick J. Hardwick
Metaswitch Metaswitch
April 2, 2014 July 25, 2014
Path Computation Element Protocol (PCEP) Management Information Base Path Computation Element Protocol (PCEP) Management Information Base
draft-ietf-pce-pcep-mib-08 draft-ietf-pce-pcep-mib-09
Abstract Abstract
This memo defines a portion of the Management Information Base for This memo defines a portion of the Management Information Base for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes managed objects for modeling of Path particular, it describes managed objects for modeling of Path
Computation Element communication Protocol (PCEP) for communications Computation Element communication Protocol (PCEP) for communications
between a Path Computation Client (PCC) and a Path Computation between a Path Computation Client (PCC) and a Path Computation
Element (PCE), or between two PCEs. Element (PCE), or between two PCEs.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on October 4, 2014. This Internet-Draft will expire on January 26, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . 3
3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
4. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . . 4 4. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . 3
4.1. pcePcepEntityTable . . . . . . . . . . . . . . . . . . . . 4 4.1. pcePcepEntityTable . . . . . . . . . . . . . . . . . . . 3
4.2. pcePcepPeerTable . . . . . . . . . . . . . . . . . . . . . 4 4.2. pcePcepPeerTable . . . . . . . . . . . . . . . . . . . . 4
4.3. pcePcepSessTable . . . . . . . . . . . . . . . . . . . . . 4 4.3. pcePcepSessTable . . . . . . . . . . . . . . . . . . . . 4
4.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . . 5 4.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . 4
4.5. Relationship to other MIB modules . . . . . . . . . . . . 5 4.5. Relationship to other MIB modules . . . . . . . . . . . . 5
5. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 5 5. Object Definitions . . . . . . . . . . . . . . . . . . . . . 5
5.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . . 5 5.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 45 6. Security Considerations . . . . . . . . . . . . . . . . . . . 44
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 46 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 45
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.1. Normative References . . . . . . . . . . . . . . . . . . . 46 9.1. Normative References . . . . . . . . . . . . . . . . . . 45
9.2. Normative References . . . . . . . . . . . . . . . . . . . 46 9.2. Informative References . . . . . . . . . . . . . . . . . 46
Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . . 46 Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . 47
1. Introduction 1. Introduction
The Path Computation Element (PCE) defined in [RFC4655] is an entity The Path Computation Element (PCE) defined in [RFC4655] is an entity
that is capable of computing a network path or route based on a that is capable of computing a network path or route based on a
network graph, and applying computational constraints. A Path network graph, and applying computational constraints. A Path
Computation Client (PCC) may make requests to a PCE for paths to be Computation Client (PCC) may make requests to a PCE for paths to be
computed. computed.
The PCE communication protocol (PCEP) is the communication protocol The PCE communication protocol (PCEP) is the communication protocol
skipping to change at page 3, line 47 skipping to change at page 3, line 31
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,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Requirements Language 3. Requirements Language
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", "NOT RECOMMENDED", "MAY" and
document are to be interpreted as described in BCP 14, RFC 2119 "OPTIONAL" in this document are to be interpreted as described in BCP
[RFC2119]. 14, RFC 2119 [RFC2119].
4. PCEP MIB Module Architecture 4. PCEP MIB Module Architecture
The PCEP MIB contains the following information: The PCEP MIB contains the following information:
a. PCE and PCC entity status (see pcePcepEntityTable). a. PCE and PCC entity status (see pcePcepEntityTable).
b. PCEP peer information (see pcePcepPeerTable). b. PCEP peer information (see pcePcepPeerTable).
c. PCEP session information (see pcePcepSessTable). c. PCEP session information (see pcePcepSessTable).
skipping to change at page 4, line 38 skipping to change at page 4, line 19
contains information to identify the peer, the running configuration contains information to identify the peer, the running configuration
relating to that peer and statistics that track the messages relating to that peer and statistics that track the messages
exchanged with that peer and its response times. exchanged with that peer and its response times.
Since PCEP sessions can be ephemeral, the pcePcepPeerTable tracks a Since PCEP sessions can be ephemeral, the pcePcepPeerTable tracks a
peer even when no PCEP session currently exists to that peer. The peer even when no PCEP session currently exists to that peer. The
statistics contained in pcePcepPeerTable are an aggregate of the statistics contained in pcePcepPeerTable are an aggregate of the
statistics for all successive sessions to that peer. statistics for all successive sessions to that peer.
To limit the quantity of information that is stored, an To limit the quantity of information that is stored, an
implementation MAY choose to discard a row from the pcePcepPeerTable implementation MAY choose to discard a row from the
if and only if no PCEP session exists to the corresponding peer. pcePcepPeerTable if and only if no PCEP session exists to the
corresponding peer.
4.3. pcePcepSessTable 4.3. pcePcepSessTable
The pcePcepSessTable contains one row for each PCEP session that the The pcePcepSessTable contains one row for each PCEP session that the
PCEP entity (PCE or PCC) is currently participating in. Each row is PCEP entity (PCE or PCC) is currently participating in. Each row is
read-only and contains the running configuration that is applied to read-only and contains the running configuration that is applied to
the session, plus identifiers and statistics for the session. the session, plus identifiers and statistics for the session.
The statistics in pcePcepSessTable are semantically different from The statistics in pcePcepSessTable are semantically different from
those in pcePcepPeerTable since the former apply to the current those in pcePcepPeerTable since the former apply to the current
session only, whereas the latter are the aggregate for all sessions session only, whereas the latter are the aggregate for all sessions
that have existed to that peer. that have existed to that peer.
Although [RFC5440] forbids there from being more than one active PCEP Although [RFC5440] forbids there from being more than one active PCEP
session between a given pair of PCEP entities at any one time, there session between a given pair of PCEP entities at any one time, there
is a window during session establishment where the pcePcepSessTable is a window during session establishment where the
may contain two rows for a given peer, one representing a session pcePcepSessTable may contain two rows for a given peer, one
initiated by the local PCEP speaker and one representing a session representing a session initiated by the local PCEP speaker and one
initiated by the remote PCEP speaker. If either of these sessions representing a session initiated by the remote PCEP speaker. If
reaches active state, then the other is discarded. either of these sessions reaches active state, then the other is
discarded.
4.4. PCEP Notifications 4.4. PCEP Notifications
The PCEP MIB contains notifications for the following conditions. The PCEP MIB contains notifications for the following conditions.
a. pcePcepSessUp: PCEP Session has gone up. a. pcePcepSessUp: PCEP Session has gone up.
b. pcePcepSessDown: PCEP Session has gone down. b. pcePcepSessDown: PCEP Session has gone down.
c. pcePcepSessLocalOverload: Local PCEP entity has sent an overload c. pcePcepSessLocalOverload: Local PCEP entity has sent an overload
skipping to change at page 6, line 25 skipping to change at page 6, line 9
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; -- RFC 4001 FROM INET-ADDRESS-MIB; -- RFC 4001
pcePcepMIB MODULE-IDENTITY pcePcepMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201404021200Z" -- 2 April 2014 "201407251200Z" -- 25 July 2014
ORGANIZATION ORGANIZATION
"IETF Path Computation Element (PCE) Working Group" "IETF Path Computation Element (PCE) Working Group"
CONTACT-INFO CONTACT-INFO
"Email: pce@ietf.org "Email: pce@ietf.org
WG charter: WG charter:
http://www.ietf.org/html.charters/pce-charter.html" http://www.ietf.org/html.charters/pce-charter.html"
DESCRIPTION DESCRIPTION
"This MIB module defines a collection of objects for managing "This MIB module defines a collection of objects for managing
PCE communication protocol (PCEP). PCE communication protocol (PCEP).
Copyright (C) The IETF Trust (2014). This version of this Copyright (C) The IETF Trust (2014). This version of this
MIB module is part of RFC YYYY; see the RFC itself for full MIB module is part of RFC YYYY; see the RFC itself for full
legal notices." 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 REVISION
"201404021200Z" -- 2 April 2014 "201407251200Z" -- 25 July 2014
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
pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepMIB 0 } pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepMIB 0 }
pcePcepObjects OBJECT IDENTIFIER ::= { pcePcepMIB 1 } pcePcepObjects OBJECT IDENTIFIER ::= { pcePcepMIB 1 }
pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepMIB 2 } pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepMIB 2 }
pcePcepEntityObjects OBJECT IDENTIFIER ::= { pcePcepObjects 1 } pcePcepEntityObjects OBJECT IDENTIFIER ::= { pcePcepObjects 1 }
skipping to change at page 46, line 21 skipping to change at page 46, line 6
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[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
STD 58, RFC 2579, April 1999. 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.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, August 2006.
[RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element
(PCE) Communication Protocol (PCEP)", RFC 5440, (PCE) Communication Protocol (PCEP)", RFC 5440, March
March 2009. 2009.
9.2. Normative References 9.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.
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, August 2006.
Appendix A. Acknowledgement Appendix A. Acknowledgement
The authors would like to thank Santanu Mazumder and Meral The authors would like to thank Santanu Mazumder and Meral
Shirazipour for their valuable input. Shirazipour for their valuable input.
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
Authors' Addresses Authors' Addresses
A S Kiran Koushik A S Kiran Koushik
Cisco Systems, Inc. Cisco Systems, Inc.
EMail: kkoushik@cisco.com EMail: kkoushik@cisco.com
Emile Stephan Emile Stephan
France Telecom Orange
2 avenue Pierre Marzin 2 avenue Pierre Marzin
Lannion F-22307 Lannion F-22307
France France
EMail: emile.stephan@orange.com EMail: emile.stephan@orange.com
Quintin Zhao Quintin Zhao
Huawei Technology Huawei Technology
125 Nagog Technology Park 125 Nagog Technology Park
Acton, MA 01719 Acton, MA 01719
US US
EMail: qzhao@huawei.com EMail: qzhao@huawei.com
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
UK
EMail: daniel@olddog.co.uk EMail: daniel@olddog.co.uk
Jonathan Hardwick Jonathan Hardwick
Metaswitch Metaswitch
100 Church Street 100 Church Street
Enfield EN2 6BQ Enfield EN2 6BQ
UK UK
EMail: jonathan.hardwick@metaswitch.com EMail: jonathan.hardwick@metaswitch.com
 End of changes. 17 change blocks. 
44 lines changed or deleted 45 lines changed or added

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