draft-ietf-pce-pcep-mib-05.txt   draft-ietf-pce-pcep-mib-06.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 S. Emile Intended status: Standards Track S. Emile
Expires: January 16, 2014 France Telecom Expires: July 13, 2014 France Telecom
Q. Zhao Q. Zhao
Huawei Technology Huawei Technology
D. King D. King
Old Dog Consulting Old Dog Consulting
J. Hardwick J. Hardwick
Metaswitch Metaswitch
July 15, 2013 January 9, 2014
PCE communication protocol (PCEP) Management Information Base PCE communication protocol (PCEP) Management Information Base
draft-ietf-pce-pcep-mib-05 draft-ietf-pce-pcep-mib-06
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base for use with network management protocols in the Information Base for use with network management protocols in the
Internet community. In particular, it describes managed objects for Internet community. In particular, it describes managed objects for
modeling of Path Computation Element communication Protocol (PCEP) modeling of Path Computation Element communication Protocol (PCEP)
for communications between a Path Computation Client (PCC) and a Path for communications between a Path Computation Client (PCC) and a Path
Computation Element (PCE), or between two PCEs. Computation 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 January 16, 2014. This Internet-Draft will expire on July 13, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . . 4 5. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . . 4
5.1. Relations to other MIB modules . . . . . . . . . . . . . . 4 5.1. pcePcepEntityTable . . . . . . . . . . . . . . . . . . . . 4
6. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 4 5.2. pcePcepPeerTable . . . . . . . . . . . . . . . . . . . . . 4
6.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . . 4 5.3. pcePcepSessTable . . . . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 43 5.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 5.5. Relationship to other MIB modules . . . . . . . . . . . . 5
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 44 6. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 6
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 44 6.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . . 6
10.1. Normative References . . . . . . . . . . . . . . . . . . . 44 7. Security Considerations . . . . . . . . . . . . . . . . . . . 45
10.2. Normative References . . . . . . . . . . . . . . . . . . . 45 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45
Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . . 45 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 46
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.1. Normative References . . . . . . . . . . . . . . . . . . . 46
10.2. Normative References . . . . . . . . . . . . . . . . . . . 46
Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . . 46
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
between a PCC and PCE for point-to-point (P2P) path computations and between a PCC and PCE for point-to-point (P2P) path computations and
is defined in [RFC5440]. Such PCEP communication interactions is defined in [RFC5440]. Such PCEP communication interactions
include path computation requests and path computation replies as include path computation requests and path computation replies as
well as notifications of specific states related to the use of a PCE well as notifications of specific states related to the use of a PCE
in the context of Multiprotocol Label Switching (MPLS) and in the context of Multiprotocol Label Switching (MPLS) and
Generalized MPLS (GMPLS) Traffic Engineering. Generalized MPLS (GMPLS) Traffic Engineering.
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines a MIB module that can be used to manage In particular, it defines a MIB module that can be used to monitor
PCEP communications between a PCC and a PCE, or between two PCEs. PCEP communications between a PCC and a PCE, or between two PCEs.
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
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [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
skipping to change at page 4, line 17 skipping to change at page 4, line 17
IGP Area: OSPF Area or ISIS level/area. IGP Area: OSPF Area or ISIS level/area.
This document also uses the terminology defined in [RFC4655] and This document also uses the terminology defined in [RFC4655] and
[RFC5440]. [RFC5440].
5. PCEP MIB Module Architecture 5. PCEP MIB Module Architecture
The PCEP MIB contains the following information: The PCEP MIB contains the following information:
a. PCEP entity status. a. PCE and PCC entity status (see pcePcepEntityTable).
b. PCEP peer information. b. PCEP peer information (see pcePcepPeerTable).
c. PCEP session information. c. PCEP session information (see pcePcepSessTable).
d. Notifications to indicate PCEP session changes. d. Notifications to indicate PCEP session changes.
5.1. Relations to other MIB modules 5.1. pcePcepEntityTable
The pcePcepEntityTable contains one row for each PCEP-speaking entity
(PCC or PCE). Each row is read-only and contains current status
information plus the running configuration of the PCEP-speaking
entity.
5.2. pcePcepPeerTable
The pcePcepPeerTable contains one row for each PCEP peer that the
PCEP entity (PCE or PCC) knows about. Each row is read-only and
contains information to identify the peer, the running configuration
relating to that peer and statistics that track the messages
exchanged with that peer and its response times.
Since PCEP sessions can be ephemeral, the pcePcepPeerTable tracks a
peer even when no PCEP session currently exists to that peer. The
statistics contained in pcePcepPeerTable are an aggregate of the
statistics for all successive sessions to that peer.
To limit the quantity of information that is stored, an
implementation MAY choose to discard a row from the pcePcepPeerTable
if and only if no PCEP session exists to the corresponding peer.
5.3. pcePcepSessTable
The pcePcepSessTable contains one row for each PCEP session that the
PCEP entity (PCE or PCC) is currently participating in. Each row is
read-only and contains the running configuration that is applied to
the session, plus identifiers and statistics for the session.
The statistics in pcePcepSessTable are semantically different from
those in pcePcepPeerTable since the former apply to the current
session only, whereas the latter are the aggregate for all sessions
that have existed to that peer.
Although [RFC5440] forbids there from being more than one active PCEP
session between a given pair of PCEP entities at any one time, there
is a window during session establishment where the pcePcepSessTable
may contain two rows for a given peer, one representing a session
initiated by the local PCEP speaker and one representing a session
initiated by the remote PCEP speaker. If either of these sessions
reaches active state, then the other is discarded.
5.4. PCEP Notifications
The PCEP MIB contains notifications for the following conditions.
a. pcePcepSessUp: PCEP Session has gone up.
b. pcePcepSessDown: PCEP Session has gone down.
c. pcePcepSessLocalOverload: Local PCEP entity has sent an overload
PCNtf on this session.
d. pcePcepSessLocalOverloadClear: Local PCEP entity has sent an
overload-cleared PCNtf on this session.
e. pcePcepSessPeerOverload: Remote PCEP entity has sent an overload
PCNtf on this session.
f. pcePcepSessPeerOverloadClear: Remote PCEP entity has sent an
overload-cleared PCNtf on this session.
5.5. Relationship to other MIB modules
The PCEP MIB imports the following textual conventions from the INET- The PCEP MIB imports the following textual conventions from the INET-
ADDRESS-MIB defined in RFC 4001 [RFC4001]: ADDRESS-MIB defined in RFC 4001 [RFC4001]:
o InetAddressType o InetAddressType
o InetAddress o InetAddress
PCEP relies on existing protocols which have specialized MIB objects PCEP relies on existing protocols which have specialized MIB objects
to monitor their own activities. Consequently this document to monitor their own activities. Consequently this document
 End of changes. 11 change blocks. 
20 lines changed or deleted 88 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/