draft-ietf-pce-pcep-mib-07.txt   draft-ietf-pce-pcep-mib-08.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: August 10, 2014 France Telecom Expires: October 4, 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
February 6, 2014 April 2, 2014
Path Computation Element Protocol (PCEP) Management Information Base Path Computation Element Protocol (PCEP) Management Information Base
draft-ietf-pce-pcep-mib-07 draft-ietf-pce-pcep-mib-08
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 August 10, 2014. This Internet-Draft will expire on October 4, 2014.
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
skipping to change at page 2, line 18 skipping to change at page 2, line 18
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. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . . 4
5. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . . 4 4.1. pcePcepEntityTable . . . . . . . . . . . . . . . . . . . . 4
5.1. pcePcepEntityTable . . . . . . . . . . . . . . . . . . . . 4 4.2. pcePcepPeerTable . . . . . . . . . . . . . . . . . . . . . 4
5.2. pcePcepPeerTable . . . . . . . . . . . . . . . . . . . . . 4 4.3. pcePcepSessTable . . . . . . . . . . . . . . . . . . . . . 4
5.3. pcePcepSessTable . . . . . . . . . . . . . . . . . . . . . 4 4.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . . 5
5.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . . 5 4.5. Relationship to other MIB modules . . . . . . . . . . . . 5
5.5. Relationship to other MIB modules . . . . . . . . . . . . 5 5. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 5
6. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 6 5.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 45
7. Security Considerations . . . . . . . . . . . . . . . . . . . 45 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 46
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 46 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46 9.1. Normative References . . . . . . . . . . . . . . . . . . . 46
10.1. Normative References . . . . . . . . . . . . . . . . . . . 46 9.2. Normative References . . . . . . . . . . . . . . . . . . . 46
10.2. Normative 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 26 skipping to change at page 3, line 26
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 monitor 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.
This document uses the terminology defined in [RFC4655] and
[RFC5440].
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
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
skipping to change at page 3, line 48 skipping to change at page 4, line 5
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", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
4. Terminology 4. PCEP MIB Module Architecture
The terminology used in this document is built on notions introduced
and discussed in PCE WG documents. The reader should be familiar
with these documents.
Domain: any collection of network elements within a common sphere of
address management or path computational responsibility.
IGP Area: OSPF Area or ISIS level/area.
This document also uses the terminology defined in [RFC4655] and
[RFC5440].
5. 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).
d. Notifications to indicate PCEP session changes. d. Notifications to indicate PCEP session changes.
5.1. pcePcepEntityTable 4.1. pcePcepEntityTable
The pcePcepEntityTable contains one row for each PCEP-speaking entity The pcePcepEntityTable contains one row for each PCEP-speaking entity
(PCC or PCE). Each row is read-only and contains current status (PCC or PCE). Each row is read-only and contains current status
information plus the running configuration of the PCEP-speaking information plus the running configuration of the PCEP-speaking
entity. entity.
5.2. pcePcepPeerTable 4.2. pcePcepPeerTable
The pcePcepPeerTable contains one row for each PCEP peer that the The pcePcepPeerTable contains one row for each PCEP peer that the
PCEP entity (PCE or PCC) knows about. Each row is read-only and PCEP entity (PCE or PCC) knows about. Each row is read-only and
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 pcePcepPeerTable
if and only if no PCEP session exists to the corresponding peer. if and only if no PCEP session exists to the corresponding peer.
5.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 pcePcepSessTable
may contain two rows for a given peer, one representing a session 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 local PCEP speaker and one representing a session
initiated by the remote PCEP speaker. If either of these sessions initiated by the remote PCEP speaker. If either of these sessions
reaches active state, then the other is discarded. reaches active state, then the other is discarded.
5.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
PCNtf on this session. PCNtf on this session.
d. pcePcepSessLocalOverloadClear: Local PCEP entity has sent an d. pcePcepSessLocalOverloadClear: Local PCEP entity has sent an
overload-cleared PCNtf on this session. overload-cleared PCNtf on this session.
e. pcePcepSessPeerOverload: Remote PCEP entity has sent an overload e. pcePcepSessPeerOverload: Remote PCEP entity has sent an overload
PCNtf on this session. PCNtf on this session.
f. pcePcepSessPeerOverloadClear: Remote PCEP entity has sent an f. pcePcepSessPeerOverloadClear: Remote PCEP entity has sent an
overload-cleared PCNtf on this session. overload-cleared PCNtf on this session.
5.5. Relationship to other MIB modules 4.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
considers that the monitoring of underlying protocols is out of scope considers that the monitoring of underlying protocols is out of scope
of the PCEP MIB module. of the PCEP MIB module.
6. Object Definitions 5. Object Definitions
6.1. PCE-PCEP-MIB 5.1. PCE-PCEP-MIB
PCE-PCEP-MIB DEFINITIONS ::= BEGIN PCE-PCEP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
mib-2, mib-2,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
Unsigned32, Unsigned32,
Counter32 Counter32
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
TruthValue, TruthValue,
TimeStamp TimeStamp
skipping to change at page 6, line 33 skipping to change at page 6, line 25
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
"201402051200Z" -- 5 February 2014 "201404021200Z" -- 2 April 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
"201402051200Z" -- 5 February 2014 "201404021200Z" -- 2 April 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 45, line 4 skipping to change at page 44, line 42
::= { pcePcepGroups 1 } ::= { pcePcepGroups 1 }
pcePcepNotificationsGroup NOTIFICATION-GROUP pcePcepNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { pcePcepSessUp, NOTIFICATIONS { pcePcepSessUp,
pcePcepSessDown, pcePcepSessDown,
pcePcepSessLocalOverload, pcePcepSessLocalOverload,
pcePcepSessLocalOverloadClear, pcePcepSessLocalOverloadClear,
pcePcepSessPeerOverload, pcePcepSessPeerOverload,
pcePcepSessPeerOverloadClear pcePcepSessPeerOverloadClear
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notifications for a PCEP MIB implementation." "The notifications for a PCEP MIB implementation."
::= { pcePcepGroups 2 } ::= { pcePcepGroups 2 }
END END
7. Security Considerations 6. Security Considerations
The readable objects in the PCE-PCEP-MIB module (i.e., those with The readable objects in the PCE-PCEP-MIB module (i.e., those with
MAX-ACCESS other than not-accessible) may be considered sensitive in MAX-ACCESS other than not-accessible) may be considered sensitive in
some environments since, collectively, they provide information about some environments since, collectively, they provide information about
the amount and frequency of path computation requests and responses the amount and frequency of path computation requests and responses
within the network and can reveal some aspects of their within the network and can reveal some aspects of their
configuration. 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
skipping to change at page 45, line 44 skipping to change at page 45, line 37
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 7. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
pcePcepMIB { mib-2 XXX } pcePcepMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note. this note.
9. Contributors 8. Contributors
Thanks to Dhruv Dhody for his contribution and detailed review. Thanks to Dhruv Dhody for his contribution and detailed review.
10. References 9. References
10.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",
skipping to change at page 46, line 46 skipping to change at page 46, line 39
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 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, August 2006. 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 2009. March 2009.
10.2. Normative References 9.2. Normative 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.
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.
 End of changes. 26 change blocks. 
57 lines changed or deleted 43 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/