draft-ietf-pce-pcep-mib-02.txt   draft-ietf-pce-pcep-mib-03.txt 
Internet Engineering Task Force A S Kiran Koushik
Internet Draft Cisco Systems, Inc.
Intended Status: Standards Track E. Stephan
Expires: January 6, 2011 France Telecom
Quintin Zhao
Huawei Technology
Daniel King
Old Dog Consulting
July 6 2010
PCE communication protocol(PCEP) Management Information Base PCE Working Group A. Koushik
Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track S. Emile
Expires: January 11, 2013 France Telecom
Q. Zhao
Huawei Technology
D. King
Old Dog Consulting
J. Hardwick
Metaswitch
July 10, 2012
draft-ietf-pce-pcep-mib-02.txt PCE communication protocol (PCEP) Management Information Base
draft-ietf-pce-pcep-mib-03
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 Internet community. In particular, it describes managed objects for
for modeling of Path Computation Element communication modeling of Path Computation Element communication Protocol (PCEP)
Protocol (PCEP) for communications between a Path Computation Client for communications between a Path Computation Client (PCC) and a Path
(PCC) and a Path Computation Element (PCE), or between two PCEs. Computation Element (PCE), or between two PCEs.
Status of this Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on January 11, 2013.
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 6, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2012 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 carefully, as they describe your rights and restrictions with respect
respect to this document. Code Components extracted from this to this document. Code Components extracted from this document must
document must include Simplified BSD License text as described in include Simplified BSD License text as described in Section 4.e of
Section 4.e of the Trust Legal Provisions and are provided without the Trust Legal Provisions and are provided without warranty as
warranty as described in the Simplified BSD License. described in the Simplified BSD License.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in BCP 14,
RFC 2119 [RFC2119].
Table of Contents Table of Contents
Abstract......................................................... 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction.................................................. 2. The Internet-Standard Management Framework . . . . . . . . . . 3
2. Terminology................................................... 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework.................... 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. PCEP MIB modules Architecture................................. 5. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . . 4
4.1 Relations to other MIB modules............................. 5.1. Relations to other MIB modules . . . . . . . . . . . . . . 4
5. Example of the PCEP MIB modules usage ........................ 6. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 4
6. Object Definitions............................................ 6.1. PCE-PCEP-DRAFT-MIB . . . . . . . . . . . . . . . . . . . . 4
6.1 PCE-PCEP-DRAFT-MIB....................................... 7. Security Considerations . . . . . . . . . . . . . . . . . . . 23
7. Security Considerations....................................... 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
8. IANA Considerations........................................... 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
9. References.................................................... 9.1. Normative References . . . . . . . . . . . . . . . . . . . 24
9.1. Normative References..................................... 9.2. Normative References . . . . . . . . . . . . . . . . . . . 25
9.2. Informative References................................... Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . . 26
10. Acknowledgement .............................................
11. Author's Addresses...........................................
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 include is defined in [RFC5440]. Such PCEP communication interactions
path computation requests and path computation replies as well as include path computation requests and path computation replies as
notifications of specific states related to the use of a PCE in the well as notifications of specific states related to the use of a PCE
context of Multiprotocol Label Switching (MPLS) and Generalized MPLS in the context of Multiprotocol Label Switching (MPLS) and
(GMPLS) Traffic Engineering. Generalized MPLS (GMPLS) Traffic Engineering.
This memo defines a portion of the Management Information Base This memo defines a portion of the Management Information Base (MIB)
(MIB) for use with network management protocols in the Internet for use with network management protocols in the Internet community.
community. In particular, it defines a MIB module that can be In particular, it defines a MIB module that can be used to manage
used to manage PCEP communications between a PCC and a PCE, or PCEP communications between a PCC and a PCE, or between two PCEs.
between two PCEs.
2. Terminology 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
[RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58
[RFC2578] [RFC2579] [RFC2580].
3. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
4. Terminology
The terminology used in this document is built on notions introduced The terminology used in this document is built on notions introduced
and discussed in PCE WG documents. The reader should be familiar and discussed in PCE WG documents. The reader should be familiar
with these documents. with these documents.
Domain: Domain: any collection of network elements within a common sphere of
any collection of network elements within a common sphere of
address management or path computational responsibility. address management or path computational responsibility.
IGP Area: IGP Area: OSPF Area or ISIS level.
OSPF Area or ISIS level.
This document also uses the terminology defined in [RFC4655] This document also uses the terminology defined in [RFC4655] and
and [RFC5440]. [RFC5440].
3. The Internet-Standard Management Framework 5. PCEP MIB Module Architecture
For a detailed overview of the documents that describe the current The PCEP MIB will contain the following information:
Internet-Standard Management Framework, please refer to section 7
of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, a. PCEP entity configuration and status.
termed the Management Information Base or MIB. MIB objects are
generally accessed through the Simple Network Management Protocol
(SNMP). Objects in the MIB are defined using the mechanisms
defined in the Structure of Management Information (SMI). This
memo specifies a MIB 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 [RFC2580].
4. PCEP MIB Module Architecture b. PCEP peer configuration and information.
The PCEP MIB will contain the following information: c. PCEP session configuration and information.
a. PCEP client configuration and status. d. Notifications to indicate PCEP session changes.
b. PCEP peer configuration and information.
c. PCEP session configuration and information.
d. Notifications to indicate PCEP session changes.
4.1. Relations to other MIB modules 5.1. Relations to other MIB modules
PCEP relies on existing protocols which have specialized MIB PCEP relies on existing protocols which have specialized MIB objects
objects to monitor their own activities. Consequently this document to monitor their own activities. Consequently this document
considers that the monitoring underlying protocols are out of scope considers that the monitoring underlying protocols are out of scope
of the PCEP MIB module. of the PCEP MIB module.
5. Example of the PCEP MIB module usage
In this section we provide an example of using the MIB objects
described in Section 6. (Object definitions) to monitor. While
this example is not meant to illustrate every permutation of the
MIB, it is intended as an aid to understanding some of the key
concepts. It is meant to be read after going through the MIB
itself.
In the PCE-PCEP-DRAFT-MIB module:
{
pcePcepClientPcepId (1d.1d.1d.1d:1d:1d)
pcePcepClientIndex (10)
pcePcepClientAdminStatus enable(1),
pcePcepClientTcpPort (4189),
pcePcepClientKeepAliveTimer (10),
pcePcepClientStorageType permanent(4),
pcePcepClientDeadTimer (40),
pcePcepClientInitSession true (1),
pcePcepClientPoliciesAllowed independentSyncPathComp(2),
}
6. Object Definitions 6. Object Definitions
6.1 PCE-PCEP-DRAFT-MIB 6.1. PCE-PCEP-DRAFT-MIB
This MIB module makes references to the following documents. This MIB module makes references to the following documents:
[RFC2578], [RFC2579], [RFC2580], [RFC3411], [RFC2863], [RFC4001], [RFC2578]; [RFC2579]; [RFC2580]; [RFC2863]; [RFC3411]; [RFC3813];
[RFC4265] and [RFC3813]. [RFC4001]; and [RFC4265].
PCE-PCEP-DRAFT-MIB DEFINITIONS ::= BEGIN PCE-PCEP-DRAFT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY,
Unsigned32, OBJECT-TYPE,
experimental NOTIFICATION-TYPE,
FROM SNMPv2-SMI Unsigned32,
Integer32,
Counter32,
experimental
FROM SNMPv2-SMI
RowStatus,
TruthValue,
TimeStamp,
TimeInterval
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF
InetAddressType,
InetAddress,
InetPortNumber
FROM INET-ADDRESS-MIB;
PcePcepIdentifier, pcePcepDraftMIB MODULE-IDENTITY
FROM PCE-TC-STD-MIB LAST-UPDATED
"201207101200Z" -- July 10, 2012
ORGANIZATION
"IETF Path Computation Element (PCE) Working Group"
CONTACT-INFO
"Email: pce@ietf.org
WG charter:
http://www.ietf.org/html.charters/pce-charter.html"
DESCRIPTION
"This MIB module defines a collection of objects for managing
PCE communication protocol (PCEP)."
::= { experimental 9999 } --
RowStatus, TimeInterval, TruthValue, pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepDraftMIB 0 }
TimeStamp, StorageType,TEXTUAL-CONVENTION pcePcepMIBObjects OBJECT IDENTIFIER ::= { pcePcepDraftMIB 1 }
FROM SNMPv2-TC -- [RFC2579] pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepDraftMIB 2 }
pcePcepEntityObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 1 }
InetAddressType, --
InetAddress, -- PCE Entity Objects
InetPortNumber --
FROM INET-ADDRESS-MIB
MODULE-COMPLIANCE, pcePcepEntityLastChange OBJECT-TYPE
OBJECT-GROUP, SYNTAX TimeStamp
NOTIFICATION-GROUP MAX-ACCESS read-only
FROM SNMPv2-CONF; STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the most recent
addition or deletion of an entry to/from the
pcePcepEntityTable, or the most recent change in value of
any objects in the pcePcepEntityTable.
pcePcepDraftMIB MODULE-IDENTITY If no such changes have occurred since the last
LAST-UPDATED "201006181200Z" --July 6, 2010 re-initialization of the local management subsystem,
ORGANIZATION "Path Computation Element (PCE) Working Group" then this object contains a zero value."
CONTACT-INFO "
A S Kiran Koushik
Cisco Systems Inc.
Stephan Emile
France Telecom DR&D
Quintin Zhao
Huawei Technology
Daniel King
OldDog Consulting
Email: kkoushik@cisco.com ::= { pcePcepEntityObjects 1 }
Email: emile.stephan@orange-ft.com
Email: zhao@huawei.com
Email: daniel@oldog.co.uk
Email comments directly to the PCE WG Mailing List at pce@ietf.org
WG-URL: http://www.ietf.org/html.charters/pce-charter.html
"
DESCRIPTION pcePcepEntityIndexNext OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an appropriate value to be used for
pcePcepEntityIndex when creating entries in the
pcePcepEntityTable. The value 0 indicates that no unassigned
entries are available."
::= { pcePcepEntityObjects 2 }
"This MIB module defines a collection of objects for managing pcePcepEntityTable OBJECT-TYPE
PCE communication protocol(PCEP)." SYNTAX SEQUENCE OF PcePcepEntityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about the PCEP Entity."
::= { pcePcepEntityObjects 3 }
-- Revision history pcePcepEntityEntry OBJECT-TYPE
SYNTAX PcePcepEntityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents a PCEP entity.
An entry can be created by a network administrator
or by an SNMP agent as instructed by PCEP."
INDEX { pcePcepEntityIndex }
::= { pcePcepEntityTable 1 }
REVISION PcePcepEntityEntry ::= SEQUENCE {
"201006181200Z" -- 18 Jun 2010 12:00:00 EST pcePcepEntityIndex Integer32,
DESCRIPTION pcePcepEntityRowStatus RowStatus,
" pcePcepEntityAdminStatus INTEGER,
Changes from -01- ietf draft include support for the pcePcepEntityOperStatus INTEGER,
following in the MIB : pcePcepEntityAddrType InetAddressType,
o Cleanup all the compiling errors; pcePcepEntityAddr InetAddress,
o added text to Introduction, PCEP Module usage. " pcePcepEntityTcpPort InetPortNumber,
pcePcepEntityConnectTimer Unsigned32,
pcePcepEntityOpenWaitTimer Unsigned32,
pcePcepEntityKeepWaitTimer Unsigned32,
pcePcepEntityKeepAliveTimer Unsigned32,
pcePcepEntityDeadTimer Unsigned32,
pcePcepEntitySyncTimer Unsigned32,
pcePcepEntityRequestTimer Unsigned32,
pcePcepEntityInitBackoffTimer Unsigned32,
pcePcepEntityMaxBackoffTimer Unsigned32,
pcePcepEntityMaxSessions Unsigned32,
pcePcepEntityMaxReqPerSession Unsigned32,
pcePcepEntityMaxUnknownReqs Unsigned32,
pcePcepEntityMaxUnknownMsgs Unsigned32
}
REVISION pcePcepEntityIndex OBJECT-TYPE
"200811031200Z" -- Nov 03 2008 12:00:00 EST SYNTAX Integer32 (1..2147483647)
DESCRIPTION MAX-ACCESS not-accessible
" STATUS current
Changes from -01- ietf draft include support for the DESCRIPTION
following in the MIB : "This index is used to uniquely identify the PCEP entity."
o Text added describing the relations to other MIB modules, ::= { pcePcepEntityEntry 1 }
o Example of the PCEP MIB module usage added.
Changes from -00- ietf draft include support for the following pcePcepEntityRowStatus OBJECT-TYPE
in the MIB : SYNTAX RowStatus
o Whether the PCEP speaker should initiate the PCEP session MAX-ACCESS read-create
or wait for initiation by the peer, STATUS current
o A set of PCEP policies including the type of operations DESCRIPTION
allowed for the PCEP peer (e.g., diverse path computation, "The status of this conceptual row."
synchronization, etc.), ::= { pcePcepEntityEntry 2 }
o A scalar object restricting the set of PCEP peers
that can initiate a PCEP session with the PCEP speaker
(e.g., list of authorized PCEP peers, all PCEP peers in
the area, all PCEP peers in the AS).
Changes from -01- draft include support for the following pcePcepEntityAdminStatus OBJECT-TYPE
in the MIB : SYNTAX INTEGER {
o The SyncTimer, adminStatusUp(1),
o The maximum number of sessions that can be setup, adminStatusDown(2)
o Request timer: amount of time a PCC waits for a reply }
before resending its path computation requests MAX-ACCESS read-create
(potentially to an alternate PCE). STATUS current
o The MAX-UNKNOWN-REQUESTS DESCRIPTION
o The MAX-UNKNOWN-MESSAGES "The administrative status of this PCEP Entity. If this
o Response time (minimum, average and maximum), on a object is changed from 'up' to 'down' and this entity has
per PCE Peer basis, already attempted to establish contact with a Peer, then all
o PCEP Session failures, contact with that Peer is lost."
o Amount of time the session has been in active state,
o Number of corrupted messages,
o Number of failed computations,
Changes from -00- draft : DEFVAL { adminStatusDown }
1. Clarified the notion of PCEP Client. ::= { pcePcepEntityEntry 3 }
2. Added new objects to the PCEP client and session tables
to manage PCEP protocol as in section 8 of
draft-ietf-pce-pcep-08.txt
3. Did not add all the objects to manage the recommendations
in draft-ietf-pce-pcep-08.txt to control the complexity of
the MIB."
REVISION pcePcepEntityOperStatus OBJECT-TYPE
"200702201200Z" -- 20 Feb 2007 12:00:00 EST SYNTAX INTEGER {
DESCRIPTION operStatusUp(1), -- active
"draft-00 version" operStatusDown(2), -- inactive
::= { experimental 9999 } -- operStatusGoingUp(3), -- activating
operStatusGoingDown(4), -- deactivating
operStatusFailed(5), -- failed, will recover
-- when possible
operStatusFailedPerm(6) -- operator intervention
-- required
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of the PCEP entity."
-- Notifications -- ::= { pcePcepEntityEntry 4 }
pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepDraftMIB 0 } pcePcepEntityAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of the PCEP entity's Internet address. This object
specifies how the value of the pcePcepPeerAddr object should
be interpreted."
::= { pcePcepEntityEntry 5 }
pcePcepMIBObjects OBJECT IDENTIFIER ::= { pcePcepDraftMIB 1 } pcePcepEntityAddr OBJECT-TYPE
pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepDraftMIB 2 } SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Internet address of this PCEP entity. The type is given
by pcePcepEntityAddrType.
pcePcepClientObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 1 } If operating as a PCE server, the PCEP entity listens on
this address. If operating as a PCC, the PCEP entity binds
outgoing TCP connections to this address."
::= { pcePcepEntityEntry 6 }
-- pcePcepEntityTcpPort OBJECT-TYPE
-- PCE Client Objects SYNTAX InetPortNumber
-- MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The TCP Port for PCEP. The default value is the well-known
value of this port."
DEFVAL { 4189 }
::= { pcePcepEntityEntry 7 }
pcePcepClientLastChange OBJECT-TYPE pcePcepEntityConnectTimer OBJECT-TYPE
SYNTAX TimeStamp SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only UNITS "seconds"
STATUS current MAX-ACCESS read-create
DESCRIPTION STATUS current
"The value of sysUpTime at the time of the most DESCRIPTION
recent addition or deletion of an entry "The time that the PCEP entity will wait to establish a TCP
to/from the pcePcepClientTable/pcePcepClientStatsTable, or connection with a PCEP peer. If a TCP connection is not
the most recent change in value of any objects in the established within this time then PCEP aborts the session
pcePcepClientTable. setup attempt."
DEFVAL { 60 }
::= { pcePcepEntityEntry 8 }
If no such changes have occurred since the last pcePcepEntityOpenWaitTimer OBJECT-TYPE
re-initialization of the local management subsystem, SYNTAX Unsigned32 (1..65535)
then this object contains a zero value." UNITS "seconds"
::= { pcePcepClientObjects 1 } MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The time that the PCEP entity will wait to receive an Open
message from a PCEP peer. If no Open message is received
within this time then PCEP aborts the session setup attempt."
DEFVAL { 60 }
::= { pcePcepEntityEntry 9 }
pcePcepClientIndexNext OBJECT-TYPE pcePcepEntityKeepWaitTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only UNITS "seconds"
STATUS current MAX-ACCESS read-create
DESCRIPTION STATUS current
"This object contains an appropriate value to DESCRIPTION
be used for pcePcepClientIndex when creating "The time that the PCEP entity will wait to receive a
entries in the pcePcepClientTable. The value Keepalive or PCErr message from a PCEP peer during session
0 indicates that no unassigned entries are initialization. If no Keepalive or PCErr message is received
available." within this time then PCEP aborts the session setup attempt."
::= { pcePcepClientObjects 2 } DEFVAL { 60 }
::= { pcePcepEntityEntry 10 }
pcePcepClientSessionAuth OBJECT-TYPE pcePcepEntityKeepAliveTimer OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Unsigned32 (0..255)
allPcepPeersInArea(1), UNITS "seconds"
allPcepPeersInAS(2), MAX-ACCESS read-create
onlyAuthorizedPeers(3) STATUS current
} DESCRIPTION
MAX-ACCESS read-only "The keep alive transmission timer that this PCEP entity will
STATUS current propose in the initial OPEN message of each session it is
DESCRIPTION involved in. This is the maximum time between two
"This object indicates which peers can start consecutive messages sent to a PCEP peer. Zero means that
a PCEP session with the PCEP speaker. The value the PCEP entity prefers not to send Keepalives at all.
of this object is only applicable if this system
can be a PCEP speaker."
::= { pcePcepClientObjects 3 }
pcePcepClientTable OBJECT-TYPE Note that the actual Keepalive transmission intervals, in
SYNTAX SEQUENCE OF PcePcepClientEntry either direction of an active PCEP session, are determined
MAX-ACCESS not-accessible by negotiation between the PCEP peers as specified by RFC
STATUS current 5440, and so may differ from this configured value. For
DESCRIPTION the actually negotiated values (per-session), see
pcePcepSessionKeepaliveTimer and
pcePcepSessionPeerKeepaliveTimer."
DEFVAL { 30 }
::= { pcePcepEntityEntry 11 }
"This table contains information about the pcePcepEntityDeadTimer OBJECT-TYPE
PCEP Client." SYNTAX Unsigned32 (0..255)
::= { pcePcepClientObjects 4 } UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The dead timer that this PCEP entity will propose in the
initial OPEN message of each session it is involved in.
This is the time after which a PCEP peer should declare a
session down if it does not receive any PCEP messages.
pcePcepClientEntry OBJECT-TYPE pcePcepEntityDeadTimer is recommended to be 4 times the
SYNTAX PcePcepClientEntry pcePcepEntityKeepAliveTimer value. Zero means suggesting
MAX-ACCESS not-accessible that the peer does not run a dead timer at all; it is only
STATUS current allowed when pcePcepEntityKeepAliveTimer is also zero."
DESCRIPTION DEFVAL { 120 }
"An entry in this table represents a PCEP client. ::= { pcePcepEntityEntry 12 }
An entry can be created by a network administrator
or by an SNMP agent as instructed by PCEP."
INDEX { pcePcepClientPcepId, pcePcepClientIndex }
::= { pcePcepClientTable 1 }
PcePcepClientEntry ::= SEQUENCE { pcePcepEntitySyncTimer OBJECT-TYPE
pcePcepClientPcepId PcePcepIdentifier, SYNTAX Unsigned32 (1..65535)
pcePcepClientIndex Unsigned32, UNITS "seconds"
pcePcepClientAdminStatus INTEGER, MAX-ACCESS read-create
pcePcepClientOperStatus INTEGER, STATUS current
pcePcepClientTcpPort InetPortNumber, DESCRIPTION
pcePcepClientKeepAliveTimer Unsigned32, "The value of SYNC timer is used in the case of synchronized
pcePcepClientStorageType StorageType, path computation request using the SVEC object.
pcePcepClientRowStatus RowStatus,
pcePcepClientDeadTimer Unsigned32,
pcePcepClientInitSession TruthValue,
pcePcepClientPoliciesAllowed INTEGER
}
pcePcepClientPcepId OBJECT-TYPE Consider the case where a PCReq message is received by a PCE
SYNTAX PcePcepIdentifier that contains the SVEC object referring to M synchronized
MAX-ACCESS not-accessible path computation requests. If after the expiration of the
STATUS current SYNC timer all the M path computation requests have not been
DESCRIPTION received, a protocol error is triggered and the PCE MUST
"The PCEP client identifier." cancel the whole set of path computation requests.
::= { pcePcepClientEntry 1 }
pcePcepClientIndex OBJECT-TYPE The aim of the SyncTimer is to avoid the storage of unused
SYNTAX Unsigned32 synchronized request should one of them get lost for some
MAX-ACCESS not-accessible reasons (for example, a misbehaving PCC)."
STATUS current DEFVAL { 60 }
DESCRIPTION ::= { pcePcepEntityEntry 13 }
"This index is used to uniquely identify the PCEP client.
Before creating a row in this table,
the 'pcePcepClientIndexNext' object should be retrieved.
That value should be used for the value of this index
when creating a row in this table. NOTE: if a value
of zero (0) is retrieved, that indicates that no rows
can be created in this table at this time."
::= { pcePcepClientEntry 2 }
pcePcepClientAdminStatus OBJECT-TYPE pcePcepEntityRequestTimer OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Unsigned32 (1..65535)
enable(1), UNITS "seconds"
disable(2) MAX-ACCESS read-create
} STATUS current
MAX-ACCESS read-create DESCRIPTION
STATUS current "The maximum time that the PCEP entity will wait for a
DESCRIPTION response to a PCReq message."
"The administrative status of this PCEP Client. DEFVAL { 60 }
If this object is changed from 'enable' to 'disable' ::= { pcePcepEntityEntry 14 }
and this entity has already attempted to establish
contact with a Peer, then all contact with that
Peer is lost and all information from that Peer
needs to be removed from the MIB. (This implies
that the network management subsystem should clean
up any related entry in the pcePcepPeerTable. This
further implies that a 'tear-down' for that session
is issued and the session and all information related
to that session cease to exist).
At this point the operator is able to change values pcePcepEntityInitBackoffTimer OBJECT-TYPE
which are related to this entity. SYNTAX Unsigned32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The initial back-off time for retrying a failed session
setup attempt to a peer.
When the admin status is set back to 'enable', then The back-off time doubles for each failed session setup
this Entity will attempt to establish a new session attempt, until a maximum back-off time is reached. The
with the Peer." maximum back-off time is configured in
pcePcepEntityMaxBackoffTimer."
DEFVAL { 60 }
::= { pcePcepEntityEntry 15 }
DEFVAL { enable } pcePcepEntityMaxBackoffTimer OBJECT-TYPE
::= { pcePcepClientEntry 3 } SYNTAX Unsigned32 (1..604800)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum back-off time for retrying a failed session
setup attempt to a peer.
pcePcepClientOperStatus OBJECT-TYPE The back-off time doubles for each failed session setup
SYNTAX INTEGER { attempt, until this maximum value is reached. Session
unknown(1), setup attempts then repeat periodically without any
enabled(2), further increase in back-off time.
disabled(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of this PCEP client.
The value of unknown(1) indicates that the The value of pcePcepEntityMaxBackoffTimer must be greater
operational status cannot be determined at than or equal to pcePcepEntityInitBackoffTimer."
this time. The value of unknown should be DEFVAL { 600 }
a transient condition before changing ::= { pcePcepEntityEntry 16 }
to enabled(2) or disabled(3)."
::= { pcePcepClientEntry 4 } pcePcepEntityMaxSessions OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum number of sessions involving this PCEP entity
that can exist at any time."
DEFVAL { 100 }
::= { pcePcepEntityEntry 17 }
pcePcepClientTcpPort OBJECT-TYPE pcePcepEntityMaxReqPerSession OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TCP Port for "Maximum number of independent requests sent to a peer that
PCEP. The default value is the well-known can be outstanding at any time.
value of this port." -- To be assigned by IANA
::= { pcePcepClientEntry 5 }
pcePcepClientKeepAliveTimer OBJECT-TYPE Once a PCEP entity has this number of requests outstanding
SYNTAX Unsigned32 (1..65535) on a session, it MUST wait to receive responses before
UNITS "seconds" sending any further requests on the session."
MAX-ACCESS read-create DEFVAL { 100 }
STATUS current ::= { pcePcepEntityEntry 18 }
DESCRIPTION
"The integer value which is the proposed keep
alive timer for this PCEP client."
::= { pcePcepClientEntry 6 }
pcePcepClientStorageType OBJECT-TYPE pcePcepEntityMaxUnknownReqs OBJECT-TYPE
SYNTAX StorageType SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION
"The maximum number of unrecognized requests and replies that
any session on this PCEP entity is willing to accept per
minute.
DESCRIPTION A PCRep message contains an unrecognized reply if it
"The storage type for this conceptual row. contains an RP object whose request ID does not correspond
Conceptual rows having the value 'permanent(4)' to any in-progress request sent by this PCEP entity.
need not allow write-access to any columnar
objects in the row."
DEFVAL{ nonVolatile }
::= { pcePcepClientEntry 7 }
pcePcepClientRowStatus OBJECT-TYPE A PCReq message contains an unrecognized request if it
SYNTAX RowStatus containd an RP object whose request ID is zero."
MAX-ACCESS read-create DEFVAL { 5 }
STATUS current ::= { pcePcepEntityEntry 19 }
DESCRIPTION
"The status of this conceptual row. All writable
objects in this row may be modified at any
time, however, as described in detail in
the section entitled, 'Changing Values After
Session Establishment', and again described
in the DESCRIPTION clause of the
pcePcepClientAdminStatus object, if a session
has been initiated with a Peer, changing objects
in this table will wreak havoc with the session
and interrupt traffic. To repeat again:
the recommended procedure is to
set the pcePcepClientAdminStatus to down, thereby
explicitly causing a session to be torn down. Then,
change objects in this entry, then set
the pcePcepClientAdminStatus to enable,
which enables a new session to be initiated."
::= { pcePcepClientEntry 8 }
pcePcepClientDeadTimer OBJECT-TYPE pcePcepEntityMaxUnknownMsgs OBJECT-TYPE
SYNTAX Unsigned32 (4..262140) SYNTAX Unsigned32
UNITS "seconds" MAX-ACCESS read-create
MAX-ACCESS read-create STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The maximum number of unknown messages that any session
"The value which indicates a period of on this PCEP entity is willing to accept per minute."
time after the expiration of which a PCEP peer DEFVAL { 5 }
declares the session down if no PCEP message ::= { pcePcepEntityEntry 20 }
has been received. The Deadtimer value is recommended to
be 4 times the Keepalive value."
::= { pcePcepClientEntry 9 }
pcePcepClientInitSession OBJECT-TYPE --
SYNTAX TruthValue -- The PCEP Peer Table
MAX-ACCESS read-create --
STATUS current
DESCRIPTION
"The value indicates if the PCEP client should initiate
PCEP session or wait for initiation by the peer.
If the value is true(1) then this client will initiate
the session. If the value is false(2) the it has to
wait for the peer to initiate a session."
DEFVAL{ false }
::= { pcePcepClientEntry 10 }
pcePcepClientPoliciesAllowed OBJECT-TYPE pcePcepPeerObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 2 }
SYNTAX INTEGER {
independentNonSyncPathComp(1),
independentSyncPathComp(2),
dependentSyncPathComp(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value indicates the set of operation types allowed
for this client. Need to explain these three values.
Are the mutually incombaitble. Is it a set (bits - 1 2 4)
or choice (integer)"
::= { pcePcepClientEntry 11 }
-- The PCEP Client Statistics Table pcePcepPeerTable OBJECT-TYPE
-- The PCEP Peer Table SYNTAX SEQUENCE OF PcePcepPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about PCEP peers known by Entities in the
pcePcepEntityTable.
pcePcepSessionObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 3 } This MIB table gives PCEP peer information that spans PCEP
pcePcepPeerLastChange OBJECT-TYPE sessions. Information about current PCEP sessions can be
SYNTAX TimeStamp found in the pcePcepSessionTable MIB table."
MAX-ACCESS read-only ::= { pcePcepPeerObjects 1 }
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the most
recent addition or deletion to/from the
pcePcepPeerTable/pcePcepSessionTable."
::= { pcePcepSessionObjects 1 }
pcePcepPeerTable OBJECT-TYPE pcePcepPeerEntry OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepPeerEntry SYNTAX PcePcepPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about PCEP peers known by Entities in "Information about a single PCEP Peer which spans all PCEP
the pcePcepClientTable. The information in this table sessions to that peer. The information contained in a row
is based on information from the Client-Peer interaction is read-only."
during session initialization but is not appropriate INDEX { pcePcepEntityIndex,
for the pcePcepSessionTable, because objects in this pcePcepPeerAddrType,
table may or may not be used in session establishment." pcePcepPeerAddr }
::= { pcePcepSessionObjects 2 } ::= { pcePcepPeerTable 1 }
pcePcepPeerEntry OBJECT-TYPE PcePcepPeerEntry ::= SEQUENCE {
SYNTAX PcePcepPeerEntry pcePcepPeerAddrType InetAddressType,
MAX-ACCESS not-accessible pcePcepPeerAddr InetAddress,
STATUS current pcePcepPeerSessionExists TruthValue,
DESCRIPTION pcePcepPeerNumSessSetupOK Counter32,
"Information about a single Peer which is related pcePcepPeerNumSessSetupFail Counter32,
to a Session. This table is augmented by pcePcepPeerSessionUpTime TimeStamp,
the pcePcepSessionTable." pcePcepPeerSessionFailTime TimeStamp,
INDEX { pcePcepClientPcepId, pcePcepPeerResponseTime Unsigned32
pcePcepClientIndex, }
pcePcepPeerPcepId }
::= { pcePcepPeerTable 1 }
PcePcepPeerEntry ::= SEQUENCE { pcePcepPeerAddrType OBJECT-TYPE
pcePcepPeerPcepId PcePcepIdentifier, SYNTAX InetAddressType
pcePcepPeerTransportAddrType InetAddressType, MAX-ACCESS not-accessible
pcePcepPeerTransportAddr InetAddress, STATUS current
pcePcepPeerResponseTime Unsigned32 DESCRIPTION
} "The peer Internet address type (IPv4 or IPv6).
pcePcepPeerPcepId OBJECT-TYPE This specifies how the pcePcepPeerAddr value should be
SYNTAX PcePcepIdentifier interpreted."
MAX-ACCESS not-accessible ::= { pcePcepPeerEntry 2 }
STATUS current
DESCRIPTION
"The PCEP identifier of this PCE Peer."
::= { pcePcepPeerEntry 1 }
pcePcepPeerTransportAddrType OBJECT-TYPE pcePcepPeerAddr OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddress (SIZE (4..32))
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the Internet address for the "The Internet address of the peer.
pcePcepPeerTransportAddr object. The PCEP
specification describes this as being either
an IPv4 Transport Address or IPv6 Transport
This object specifies how the value of the
pcePcepPeerTransportAddr object should be
interpreted."
::= { pcePcepPeerEntry 2 }
pcePcepPeerTransportAddr OBJECT-TYPE The type of this address is specified by the
SYNTAX InetAddress pcePcepPeerAddrType value."
MAX-ACCESS read-only ::= { pcePcepPeerEntry 3 }
STATUS current
DESCRIPTION
"The Internet address advertised by the peer.
The type of this address is specified by the pcePcepPeerSessionExists OBJECT-TYPE
value of the pcePcepPeerTransportAddrType SYNTAX TruthValue
object." MAX-ACCESS read-only
::= { pcePcepPeerEntry 3 } STATUS current
DESCRIPTION
"Indicates whether a session with this peer currently
exists."
::= { pcePcepPeerEntry 4 }
pcePcepPeerResponseTime OBJECT-TYPE pcePcepPeerNumSessSetupOK OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Counter32
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The number of PCEP sessions successfully established with
"The Average response time for this PCEP peer." the peer, including any current session."
::= { pcePcepPeerEntry 4 } ::= { pcePcepPeerEntry 5 }
-- pcePcepPeerNumSessSetupFail OBJECT-TYPE
-- The PCEP Sessions Table SYNTAX Counter32
-- MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCEP sessions with the peer that failed before
reaching session state pceSessionUp."
::= { pcePcepPeerEntry 6 }
pcePcepSessionMax OBJECT-TYPE pcePcepPeerSessionUpTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of sessions that can be setup "The value of sysUpTime the last time a session with this
on this PCEP client." peer was successfully established.
::= { pcePcepSessionObjects 3 }
pcePcepSessionMaxUnknownRequests OBJECT-TYPE If pcePcepPeerSessionUpCount is zero, then this object
SYNTAX Unsigned32 contains zero."
MAX-ACCESS read-only ::= { pcePcepPeerEntry 7 }
STATUS current
DESCRIPTION
"The maximum number of unknown requests that any session
on this PCEP client is willing to accept."
::= { pcePcepSessionObjects 4 }
pcePcepSessionMaxUnknownMsgs OBJECT-TYPE pcePcepPeerSessionFailTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of unknown messages that any session "The value of sysUpTime the last time a session with this
on this PCEP client is willing to accept." peer failed to be established.
::= { pcePcepSessionObjects 5 }
pcePcepSessionFailures OBJECT-TYPE If pcePcepPeerSessionFailCount is zero, then this object
SYNTAX Unsigned32 contains zero."
MAX-ACCESS read-only ::= { pcePcepPeerEntry 8 }
STATUS current
DESCRIPTION
"The number of failed sessions on this client."
::= { pcePcepSessionObjects 6 }
pcePcepSessionTable OBJECT-TYPE pcePcepPeerResponseTime OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepSessionEntry SYNTAX Unsigned32 (1..65535)
MAX-ACCESS not-accessible UNITS "seconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"A table of Sessions between PCEP clients. DESCRIPTION
This table AUGMENTS the pcePcepPeerTable. "The average response time for this peer.
Each row in this table represents a single session."
::= { pcePcepSessionObjects 7 }
pcePcepSessionEntry OBJECT-TYPE If an average response time has not been calculated for this
SYNTAX PcePcepSessionEntry peer then this object has the value zero."
MAX-ACCESS not-accessible ::= { pcePcepPeerEntry 9 }
STATUS current
DESCRIPTION
"An entry in this table represents information on a
single session between two PCEP clients.
The information contained in a row is read-only."
AUGMENTS { pcePcepPeerEntry } --
::= { pcePcepSessionTable 1 } -- The PCEP Sessions Table
--
PcePcepSessionEntry ::= SEQUENCE { pcePcepSessionObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 3 }
pcePcepSessionStateLastChange TimeStamp,
pcePcepSessionState INTEGER,
pcePcepSessionKeepAliveHoldTimeRem TimeInterval,
pcePcepSessionKeepAliveTime Unsigned32,
pcePcepSessionDiscontinuityTime TimeStamp,
pcePcepSessionSpeakerRole INTEGER,
pcePcepSessionSyncTime Unsigned32,
pcePcepSessionRequestTime Unsigned32,
pcePcepSessionActiveTime Unsigned32,
pcePcepSessionCorruptedMsgs Unsigned32,
pcePcepSessionFailedComps Unsigned32
}
pcePcepSessionStateLastChange OBJECT-TYPE pcePcepSessionTable OBJECT-TYPE
SYNTAX TimeStamp SYNTAX SEQUENCE OF PcePcepSessionEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this "A table of Sessions on this PCEP entity. Each row in this
Session entered its current state as table represents a single session."
denoted by the pcePcepSessionState ::= { pcePcepSessionObjects 1 }
object."
::= { pcePcepSessionEntry 1 }
pcePcepSessionState OBJECT-TYPE pcePcepSessionEntry OBJECT-TYPE
SYNTAX INTEGER { SYNTAX PcePcepSessionEntry
sessionUp(1), MAX-ACCESS not-accessible
keepWait(2), STATUS current
openWait(3), DESCRIPTION
tcpPending(4), "An entry in this table represents information on a
idle(5) single session between two PCEP clients. The information
} contained in a row is read-only."
MAX-ACCESS read-only INDEX { pcePcepEntityIndex,
STATUS current pcePcepPeerAddrType,
DESCRIPTION pcePcepPeerAddr }
"The current state of the session, all of the ::= { pcePcepSessionTable 1 }
states 1 to 5 are based on the state machine
for session negotiation behavior."
::= { pcePcepSessionEntry 2 }
pcePcepSessionKeepAliveHoldTimeRem OBJECT-TYPE PcePcepSessionEntry ::= SEQUENCE {
SYNTAX TimeInterval pcePcepSessionStateLastChange TimeStamp,
MAX-ACCESS read-only pcePcepSessionState INTEGER,
STATUS current pcePcepSessionLocalID Integer32,
DESCRIPTION pcePcepSessionPeerID Integer32,
"The keep alive hold time remaining for pcePcepSessionKeepaliveTimer Unsigned32,
this session." pcePcepSessionPeerKeepaliveTimer Unsigned32,
::= { pcePcepSessionEntry 3 } pcePcepSessionDeadTimer Unsigned32,
pcePcepSessionPeerDeadTimer Unsigned32,
pcePcepSessionKAHoldTimeRem TimeInterval,
pcePcepSessionNumPCReqSent Counter32,
pcePcepSessionNumPCReqRcvd Counter32,
pcePcepSessionNumPCRepSent Counter32,
pcePcepSessionNumPCRepRcvd Counter32,
pcePcepSessionNumPCErrSent Counter32,
pcePcepSessionNumPCErrRcvd Counter32,
pcePcepSessionNumPCNtfSent Counter32,
pcePcepSessionNumPCNtfRcvd Counter32,
pcePcepSessionNumKeepaliveSent Counter32,
pcePcepSessionNumKeepaliveRcvd Counter32,
pcePcepSessionNumUnknownRcvd Counter32
}
pcePcepSessionKeepAliveTime OBJECT-TYPE pcePcepSessionStateLastChange OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX TimeStamp
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The value of sysUpTime at the time this session entered its
"The negotiated KeepAlive Time which current state as denoted by the pcePcepSessionState object."
represents the amount of seconds between ::= { pcePcepSessionEntry 1 }
keep alive messages. The
pcePcepClientKeepAliveHoldTimer
related to this Session is the
value that was proposed as the
KeepAlive Time for this session
This value is negotiated during pcePcepSessionState OBJECT-TYPE
session initialization between SYNTAX INTEGER {
the entity's proposed value idle(0),
(i.e., the value configured in tcpPending(1),
pcePcepClientKeepAliveHoldTimer) openWait(2),
and the peer's proposed keepWait(3),
KeepAlive Hold Timer value. sessionUp(4)
This value is the smaller }
of the two proposed values." MAX-ACCESS read-only
::= { pcePcepSessionEntry 4 } STATUS current
DESCRIPTION
"The current state of the session."
::= { pcePcepSessionEntry 2 }
pcePcepSessionDiscontinuityTime OBJECT-TYPE pcePcepSessionLocalID OBJECT-TYPE
SYNTAX TimeStamp SYNTAX Integer32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion "The value of the PCEP session ID used by the local PCEP
at which any one or more of this session's counters speaker in the Open message for this session."
suffered a discontinuity. The relevant counters are ::= { pcePcepSessionEntry 3 }
the specific instances associated with this session
of any Counter32 object contained in the
pcePcepSessionStatsTable.
The initial value of this object is the value of pcePcepSessionPeerID OBJECT-TYPE
sysUpTime when the entry was created in this table. SYNTAX Integer32 (0..255)
Also, a command generator can distinguish when a session MAX-ACCESS read-only
between a given Entity and Peer goes away and a new STATUS current
session is established. This value would change and DESCRIPTION
thus indicate to the command generator that this is a "The value of the PCEP session ID used by the peer in its
different session." Open message for this session."
::= { pcePcepSessionEntry 5 } ::= { pcePcepSessionEntry 4 }
pcePcepSessionSpeakerRole OBJECT-TYPE pcePcepSessionKeepaliveTimer OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Unsigned32
pcc(1), MAX-ACCESS read-only
pce(2), STATUS current
pccandpce(3) DESCRIPTION
} "The agreed maximum interval at which the local PCEP speaker
MAX-ACCESS read-only transmits PCEP messages on this PCEP session. Zero means
STATUS current that the local PCEP speaker never sends Keepalives on this
DESCRIPTION session."
"The value of this object indicates the PCEP ::= { pcePcepSessionEntry 5 }
speaker role in this session."
::= { pcePcepSessionEntry 6 }
pcePcepSessionSyncTime OBJECT-TYPE pcePcepSessionPeerKeepaliveTimer OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The agreed maximum interval at which the peer transmits PCEP
"The value of SYNC timer is used in the case messages on this PCEP session. Zero means that the peer
of synchronized path computation request using never sends Keepalives on this session."
the SVEC object. ::= { pcePcepSessionEntry 6 }
Consider the case where a PCReq message is received pcePcepSessionDeadTimer OBJECT-TYPE
by a PCE that contains the SVEC object referring to SYNTAX Unsigned32
M synchronized path computation requests. If after MAX-ACCESS read-only
the expiration of the SYNC timer all the M path STATUS current
computation requests have not been received, DESCRIPTION
a protocol error is triggered and the PCE MUST cancel "The local PCEP speaker's DeadTimer interval for this PCEP
the whole set of path computation requests. session."
::= { pcePcepSessionEntry 7 }
The aim of the SyncTimer is to avoid the storage pcePcepSessionPeerDeadTimer OBJECT-TYPE
of unused synchronized request should one of them get SYNTAX Unsigned32
lost for some reasons (e.g a misbehaving PCC)." MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The peer's DeadTimer interval for for this PCEP session."
::= { pcePcepSessionEntry 8 }
DEFVAL { 60 } pcePcepSessionKAHoldTimeRem OBJECT-TYPE
::= { pcePcepSessionEntry 7 } SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The keep alive hold time remaining for this session."
::= { pcePcepSessionEntry 9 }
pcePcepSessionRequestTime OBJECT-TYPE pcePcepSessionNumPCReqSent OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Counter32
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The number of PCReq messages sent on this session."
"The maximum amount of time a PCC waits for a ::= { pcePcepSessionEntry 10 }
reply before resending its path computation requests
(potentially to an alternate PCE)."
::= { pcePcepSessionEntry 8 }
pcePcepSessionActiveTime OBJECT-TYPE pcePcepSessionNumPCReqRcvd OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Counter32
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The number of PCReq messages received on this session."
"The amount of time this session has been active ::= { pcePcepSessionEntry 11 }
since creation or a discontinuity."
::= { pcePcepSessionEntry 9 }
pcePcepSessionCorruptedMsgs OBJECT-TYPE pcePcepSessionNumPCRepSent OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of corrupted messages received on this "The number of PCRep messages sent on this session."
session." ::= { pcePcepSessionEntry 12 }
::= { pcePcepSessionEntry 10 }
pcePcepSessionFailedComps OBJECT-TYPE pcePcepSessionNumPCRepRcvd OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests which had failed "The number of PCRep messages received on this session."
computations." ::= { pcePcepSessionEntry 13 }
::= { pcePcepSessionEntry 11 }
--- pcePcepSessionNumPCErrSent OBJECT-TYPE
--- Notifications SYNTAX Counter32
--- MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCErr messages sent on this session."
::= { pcePcepSessionEntry 14 }
pcePcepSessionUp NOTIFICATION-TYPE pcePcepSessionNumPCErrRcvd OBJECT-TYPE
OBJECTS { SYNTAX Counter32
pcePcepSessionState, MAX-ACCESS read-only
pcePcepSessionDiscontinuityTime STATUS current
} DESCRIPTION
STATUS current "The number of PCErr messages received on this session."
::= { pcePcepSessionEntry 15 }
DESCRIPTION pcePcepSessionNumPCNtfSent OBJECT-TYPE
"This notification is sent when the SYNTAX Counter32
value of 'pcePcepSessionState' enters MAX-ACCESS read-only
the 'sessionUp(1)' state." STATUS current
::= { pcePcepNotifications 1 } DESCRIPTION
"The number of PCNtf messages sent on this session."
::= { pcePcepSessionEntry 16 }
pcePcepSessionDown NOTIFICATION-TYPE pcePcepSessionNumPCNtfRcvd OBJECT-TYPE
OBJECTS { SYNTAX Counter32
pcePcepSessionState, MAX-ACCESS read-only
pcePcepSessionDiscontinuityTime STATUS current
DESCRIPTION
"The number of PCNtf messages received on this session."
::= { pcePcepSessionEntry 17 }
} pcePcepSessionNumKeepaliveSent OBJECT-TYPE
STATUS current SYNTAX Counter32
DESCRIPTION MAX-ACCESS read-only
"This notification is sent when the STATUS current
value of 'pcePcepSessionState' leaves DESCRIPTION
the 'sessionUp(1)' state." "The number of Keepalive messages sent on this session."
::= { pcePcepNotifications 2 } ::= { pcePcepSessionEntry 18 }
--**************************************************************** pcePcepSessionNumKeepaliveRcvd OBJECT-TYPE
-- Module Conformance Statement SYNTAX Counter32
--**************************************************************** MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Keepalive messages received on this session."
::= { pcePcepSessionEntry 19 }
pcePcepGroups pcePcepSessionNumUnknownRcvd OBJECT-TYPE
OBJECT IDENTIFIER ::= { pcePcepConformance 1 } SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of unknown messages received on this session."
::= { pcePcepSessionEntry 20 }
pcePcepCompliances ---
OBJECT IDENTIFIER ::= { pcePcepConformance 2 } --- Notifications
---
-- pcePcepSessionUp NOTIFICATION-TYPE
-- Full Compliance OBJECTS {
-- pcePcepSessionState,
pcePcepSessionStateLastChange
}
STATUS current
DESCRIPTION
"This notification is sent when the value of
'pcePcepSessionState' enters the 'sessionUp(4)' state."
::= { pcePcepNotifications 1 }
pcePcepModuleFullCompliance MODULE-COMPLIANCE pcePcepSessionDown NOTIFICATION-TYPE
STATUS current OBJECTS {
DESCRIPTION pcePcepSessionState,
"The Module is implemented with support pcePcepSessionStateLastChange
for read-create. In other }
words, both monitoring and configuration STATUS current
are available when using this MODULE-COMPLIANCE." DESCRIPTION
"This notification is sent when the value of
'pcePcepSessionState' leaves the 'sessionUp(4)' state."
::= { pcePcepNotifications 2 }
MODULE -- this module --
MANDATORY-GROUPS { pcePcepGeneralGroup, -- Module Conformance Statement
pcePcepNotificationsGroup --
}
::= { pcePcepCompliances 1 } pcePcepGroups
OBJECT IDENTIFIER ::= { pcePcepConformance 1 }
-- pcePcepCompliances
-- Read-Only Compliance OBJECT IDENTIFIER ::= { pcePcepConformance 2 }
--
pcePcepModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support
for read-only. In other words, only monitoring
is available by implementing this MODULE-COMPLIANCE."
MODULE -- this module --
MANDATORY-GROUPS { pcePcepGeneralGroup, -- Full Compliance
pcePcepNotificationsGroup --
}
::= { pcePcepCompliances 2 } pcePcepModuleFullCompliance MODULE-COMPLIANCE
-- units of conformance STATUS current
DESCRIPTION
"The Module is implemented with support for read-create. In
other words, both monitoring and configuration are available
when using this MODULE-COMPLIANCE."
pcePcepGeneralGroup OBJECT-GROUP MODULE -- this module
OBJECTS { MANDATORY-GROUPS { pcePcepGeneralGroup,
pcePcepClientLastChange, pcePcepNotificationsGroup
pcePcepClientIndexNext, }
pcePcepClientAdminStatus,
pcePcepClientOperStatus,
pcePcepClientTcpPort,
pcePcepClientKeepAliveTimer,
pcePcepClientStorageType,
pcePcepClientRowStatus,
pcePcepPeerLastChange,
pcePcepPeerTransportAddrType,
pcePcepPeerTransportAddr,
pcePcepSessionStateLastChange,
pcePcepSessionState,
pcePcepSessionKeepAliveHoldTimeRem,
pcePcepSessionKeepAliveTime,
pcePcepSessionDiscontinuityTime,
pcePcepClientDeadTimer,
pcePcepClientInitSession,
pcePcepClientPoliciesAllowed,
pcePcepSessionMax,
pcePcepSessionSpeakerRole,
pcePcepSessionSyncTime,
pcePcepSessionRequestTime,
pcePcepSessionMaxUnknownRequests,
pcePcepSessionMaxUnknownMsgs,
pcePcepSessionActiveTime,
pcePcepSessionCorruptedMsgs,
pcePcepClientSessionAuth,
pcePcepPeerResponseTime,
pcePcepSessionFailures,
pcePcepSessionSyncTime,
pcePcepSessionRequestTime,
pcePcepSessionFailedComps
}
STATUS current
DESCRIPTION
"Objects that apply to all PCEP MIB implementations."
::= { pcePcepGroups 1 } ::= { pcePcepCompliances 1 }
pcePcepNotificationsGroup NOTIFICATION-GROUP --
NOTIFICATIONS { pcePcepSessionUp, -- Read-Only Compliance
pcePcepSessionDown --
}
STATUS current
DESCRIPTION pcePcepModuleReadOnlyCompliance MODULE-COMPLIANCE
"The notifications for a PCEP MIB implementation." STATUS current
::= { pcePcepGroups 2 } DESCRIPTION
END "The Module is implemented with support for read-only. In
other words, only monitoring is available by implementing
this MODULE-COMPLIANCE."
7. Security Considerations MODULE -- this module
MANDATORY-GROUPS { pcePcepGeneralGroup,
pcePcepNotificationsGroup
}
This MIB module can be used for configuration of certain objects, ::= { pcePcepCompliances 2 }
and anything that can be configured can be incorrectly configured,
with potentially disastrous results.
There are a number of management objects defined in this MIB module -- units of conformance
with a MAX-ACCESS clause of read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
o pcePcepClientTcpPort: A PCC or PCE listening in on the wrong TCO pcePcepGeneralGroup OBJECT-GROUP
port would mean PCEP communications would fail. OBJECTS { pcePcepEntityLastChange,
pcePcepEntityIndexNext,
pcePcepEntityRowStatus,
pcePcepEntityAdminStatus,
pcePcepEntityOperStatus,
pcePcepEntityAddrType,
pcePcepEntityAddr,
pcePcepEntityTcpPort,
pcePcepEntityConnectTimer,
pcePcepEntityOpenWaitTimer,
pcePcepEntityKeepWaitTimer,
pcePcepEntityKeepAliveTimer,
pcePcepEntityDeadTimer,
pcePcepEntitySyncTimer,
pcePcepEntityRequestTimer,
pcePcepEntityInitBackoffTimer,
pcePcepEntityMaxBackoffTimer,
pcePcepEntityMaxSessions,
pcePcepEntityMaxReqPerSession,
pcePcepEntityMaxUnknownReqs,
pcePcepEntityMaxUnknownMsgs,
pcePcepPeerSessionExists,
pcePcepPeerNumSessSetupOK,
pcePcepPeerNumSessSetupFail,
pcePcepPeerSessionUpTime,
pcePcepPeerSessionFailTime,
pcePcepPeerResponseTime,
pcePcepSessionStateLastChange,
pcePcepSessionState,
pcePcepSessionLocalID,
pcePcepSessionPeerID,
pcePcepSessionKeepaliveTimer,
pcePcepSessionPeerKeepaliveTimer,
pcePcepSessionDeadTimer,
pcePcepSessionPeerDeadTimer,
pcePcepSessionKAHoldTimeRem,
pcePcepSessionNumPCReqSent,
pcePcepSessionNumPCReqRcvd,
pcePcepSessionNumPCRepSent,
pcePcepSessionNumPCRepRcvd,
pcePcepSessionNumPCErrSent,
pcePcepSessionNumPCErrRcvd,
pcePcepSessionNumPCNtfSent,
pcePcepSessionNumPCNtfRcvd,
pcePcepSessionNumKeepaliveSent,
pcePcepSessionNumKeepaliveRcvd,
pcePcepSessionNumUnknownRcvd
}
STATUS current
DESCRIPTION
"Objects that apply to all PCEP MIB implementations."
o pcePcepClientKeepAliveTimer: Changing the PCEP session keepalive ::= { pcePcepGroups 1 }
timer to a value lower than the default value, may force premature
PCEP communication time-outs.
o pcePcepClientStorageType: Changing this value may cause persitance pcePcepNotificationsGroup NOTIFICATION-GROUP
failure for the configuration. NOTIFICATIONS { pcePcepSessionUp,
pcePcepSessionDown
}
STATUS current
DESCRIPTION
"The notifications for a PCEP MIB implementation."
::= { pcePcepGroups 2 }
o pcePcepClientRowStatus: Setting row status incorrectly may turn END
off the PCEP client.
o pcePcepClientDeadTimer: Changing the PCEP session deadtimer timer 7. Security Considerations
to a value lower than the default value, may force premature PCEP
communication time-outs.
o pcepPcepClientInitSession: Setting this value incorrectly may cause This MIB module can be used for configuration of certain objects, and
the PCEP session not to come up. anything that can be configured can be incorrectly configured, with
potentially disastrous results.
o pcePcepClientPoliciesAllowed: Setting this value incorrectly may There are a number of management objects defined in this MIB module
cause specific PCE requests to fail. with a MAX-ACCESS clause of read-create. Such objects may be
considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. These
are the tables and objects and their sensitivity/vulnerability:
o pcePcepEnityTcpPort: A PCC or PCE listening in on the wrong TCP
port would mean PCEP communications would fail.
o pcePcepEntityKeepAliveTimer: Changing the PCEP session keepalive
timer to a value lower than the default value, may force premature
PCEP communication time-outs.
o pcePcepEntityRowStatus: Setting row status incorrectly may turn
off the PCEP client.
o pcePcepEntityDeadTimer: Changing the PCEP session deadtimer timer
to a value lower than the default value, may force premature PCEP
communication time-outs.
The user of the PCE-PCEP-DRAFT-MIB module must therefore be aware The user of the PCE-PCEP-DRAFT-MIB module must therefore be aware
that support for SET operations in a non-secure environment without that support for SET operations in a non-secure environment without
proper protection can have a negative effect on network operations. proper protection can have a negative effect on network operations.
The readable objects in the PCE-PCEP-DRAFT-MIB module (i.e., those The readable objects in the PCE-PCEP-DRAFT-MIB module (i.e., those
with MAX-ACCESS other than not-accessible) may be considered with MAX-ACCESS other than not-accessible) may be considered
sensitive in some environments since, collectively, they provide sensitive in some environments since, collectively, they provide
information about the amount and frequency of path computation information about the amount and frequency of path computation
requests and responses within the network and can reveal some requests and responses within the network and can reveal some aspects
aspects of their configuration. of their configuration.
In such environments it is important to control also GET and NOTIFY In such environments it is important to control also GET and NOTIFY
access to these objects and possibly even to encrypt their values access to these objects and possibly even to encrypt their values
when sending them over the network via SNMP. when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
skipping to change at page 23, line 45 skipping to change at page 24, line 28
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
8. IANA Considerations 8. IANA Considerations
IANA is requested to make a MIB OID assignment for pceStdMIB under IANA is requested to make a MIB OID assignment for pceStdMIB under
the mib-2 branch. The MIB module in this document uses the following the mib-2 branch. The MIB module in this document uses the following
IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry: registry:
Descriptor OBJECT IDENTIFIER value The MIB module in this document uses the following IANA-assigned
---------- ----------------------- OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
pceStdMIB { mib-2 XXX } Descriptor OBJECT IDENTIFIER value
---------- -----------------------
pceStdMIB { mib-2 XXX }
IANA is requested to root MIB objects in the MIB module contained in IANA is requested to root MIB objects in the MIB module contained in
this document under the mib-2 subtree. this document under the mib-2 subtree.
9. References 9. References
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., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, Schoenwaelder, Ed., "Structure of Management Information
J., Rose, M., and S. Waldbusser, "Textual Conventions Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
J., Rose, M., and S. Waldbusser, "Conformance Statements Schoenwaelder, Ed., "Textual Conventions for SMIv2",
for SMIv2", STD 58, RFC 2580, April 1999. STD 58, RFC 2579, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
MIB", RFC 2863, June 2000. "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Architecture for Describing Simple Network Management MIB", RFC 2863, June 2000.
Protocol (SNMP) Management Frameworks", STD 62, RFC
3411, December 2002.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "MPLS [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Multiprotocol Label Switching (MPLS) Label Switch Router Architecture for Describing Simple Network Management
Management Information Base ", RFC 3813, June 2004 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
Schoenwaelder, "Textual Conventions for Internet Network "Multiprotocol Label Switching (MPLS) Label Switching
Addresses", RFC 4001, February 2005. Router (LSR) Management Information Base (MIB)", RFC 3813,
[RFC4265] Schliesser, B. and T. Nadeau, "Definition of Textual June 2004.
Conventions for Virtual Private Network (VPN)
Management", RFC 4265, November 2005.
[RFC5440] Ayyangar, A., Farrel, A., Oki, E., Atlas, A., Dolganow [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
A. Ikejiri, Y., Kumaki, K., Vasseur, J., and J. Roux, Schoenwaelder, "Textual Conventions for Internet Network
"Path Computation Element (PCE) communication Protocol Addresses", RFC 4001, February 2005.
(PCEP)," RFC5440, March. 2009.
9.2. Informative References [RFC4265] Schliesser, B. and T. Nadeau, "Definition of Textual
Conventions for Virtual Private Network (VPN) Management",
RFC 4265, November 2005.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
"Introduction and Applicability Statements for Element (PCE)-Based Architecture", RFC 4655, August 2006.
Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element
Element (PCE)-Based Architecture", RFC 4655, August (PCE) Communication Protocol (PCEP)", RFC 5440,
2006. March 2009.
10. Acknowledgement 9.2. Normative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
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.
11. 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
Stephan Emile Stephan Emile
France Telecom France Telecom
2 avenue Pierre Marzin 2 avenue Pierre Marzin
Lannion, F-22307 Lannion F-22307
Email: emile.stephan@orange-ftgroup.com France
EMail: emile.stephan@orange-ftgroup.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 UK
Email: daniel@olddog.co.uk
EMail: daniel@olddog.co.uk
Jonathan Hardwick
Metaswitch
100 Church Street
Enfield EN2 6BQ
UK
EMail: jon.hardwick@metaswitch.com
 End of changes. 165 change blocks. 
927 lines changed or deleted 959 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/