draft-ietf-pce-pcep-16.txt   draft-ietf-pce-pcep-17.txt 
Networking Working Group JP. Vasseur, Ed. Networking Working Group JP. Vasseur, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track JL. Le Roux, Ed. Intended status: Standards Track JL. Le Roux, Ed.
Expires: April 17, 2009 France Telecom Expires: May 6, 2009 France Telecom
October 14, 2008 November 2, 2008
Path Computation Element (PCE) Communication Protocol (PCEP) Path Computation Element (PCE) Communication Protocol (PCEP)
draft-ietf-pce-pcep-16.txt draft-ietf-pce-pcep-17.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 17, 2009. This Internet-Draft will expire on May 6, 2009.
Abstract Abstract
This document specifies the Path Computation Element Communication This document specifies the Path Computation Element Communication
Protocol (PCEP) for communications between a Path Computation Client Protocol (PCEP) for communications between a Path Computation Client
(PCC) and a Path Computation Element (PCE), or between two PCEs. (PCC) and a Path Computation Element (PCE), or between two PCEs.
Such interactions include path computation requests and path Such interactions include path computation requests and path
computation replies as well as notifications of specific states computation replies as well as notifications of specific states
related to the use of a PCE in the context of Multiprotocol Label related to the use of a PCE in the context of Multiprotocol Label
Switching (MPLS) and Generalized (GMPLS) Traffic Engineering. PCEP Switching (MPLS) and Generalized (GMPLS) Traffic Engineering. PCEP
skipping to change at page 34, line 47 skipping to change at page 34, line 47
TYPE: To be assigned by IANA (suggested value=1) TYPE: To be assigned by IANA (suggested value=1)
LENGTH: 4 LENGTH: 4
VALUE: 32-bit flags field VALUE: 32-bit flags field
IANA is requested to manage the space of flags carried in the NO- IANA is requested to manage the space of flags carried in the NO-
PATH-VECTOR TLV (see Section 9). PATH-VECTOR TLV (see Section 9).
The following flags are currently defined: The following flags are currently defined:
o Bit number: 1 - PCE currently unavailable o Bit number: 0 - PCE currently unavailable
o Bit number: 2 - Unknown destination o Bit number: 1 - Unknown destination
o Bit number: 3 - Unknown source o Bit number: 2 - Unknown source
7.6. END-POINT Object 7.6. END-POINT Object
The END-POINTS object is used in a PCReq message to specify the The END-POINTS object is used in a PCReq message to specify the
source IP address and the destination IP address of the path for source IP address and the destination IP address of the path for
which a path computation is requested. The P flag of the END-POINT which a path computation is requested. The P flag of the END-POINT
object MUST be set. If the END-POINT objet is received with the P object MUST be set. If the END-POINT objet is received with the P
flag cleared, the receiving peer MUST send a PCErr message with flag cleared, the receiving peer MUST send a PCErr message with
Error-type=10 and Error-value=1. The corresponding path computation Error-type=10 and Error-value=1. The corresponding path computation
request MUST be cancelled by the PCE without further notification. request MUST be cancelled by the PCE without further notification.
skipping to change at page 62, line 14 skipping to change at page 62, line 14
o Capability Description o Capability Description
o Defining RFC o Defining RFC
Several bits are defined in this document. The following values have Several bits are defined in this document. The following values have
been assigned: been assigned:
Codespace of the Flag field (Metric Object) Codespace of the Flag field (Metric Object)
Bit Description Reference Bit Description Reference
1-3 Priority This document 0-2 Priority This document
4 Reoptimization This document 3 Reoptimization This document
5 Bi-directional This document 4 Bi-directional This document
6 Strict/Loose This document 5 Strict/Loose This document
9.5. Notification Object 9.5. Notification Object
IANA is requested to create a registry for the Notification-type and IANA is requested to create a registry for the Notification-type and
Notification-value of the Notification Object and manage the code Notification-value of the Notification Object and manage the code
space. space.
Notification-type Name Reference Notification-type Name Reference
1 Pending Request cancelled This document 1 Pending Request cancelled This document
Notification-value Notification-value
skipping to change at page 65, line 8 skipping to change at page 65, line 8
o Capability Description o Capability Description
o Defining RFC o Defining RFC
Several bits are defined in this document. The following values have Several bits are defined in this document. The following values have
been assigned: been assigned:
Codespace of the Flag field (Metric Object) Codespace of the Flag field (Metric Object)
Bit Description Reference Bit Description Reference
1 Bound This document 0 Bound This document
2 Computed metric This document 1 Computed metric This document
9.10. PCEP TLV Type Indicators 9.10. PCEP TLV Type Indicators
IANA is requested to create a registry for the PCEP TLVs. IANA is requested to create a registry for the PCEP TLVs.
Value Meaning Reference Value Meaning Reference
1 NO-PATH-VECTOR TLV This document 1 NO-PATH-VECTOR TLV This document
2 OVERLOAD-DURATION TLV This document 2 OVERLOAD-DURATION TLV This document
3 REQ-MISSING TLV This document 3 REQ-MISSING TLV This document
skipping to change at page 65, line 33 skipping to change at page 65, line 33
IANA is requested to manage the space of flags carried in the NO- IANA is requested to manage the space of flags carried in the NO-
PATH-VECTOR TLV defined in this document, numbering them from 1 as PATH-VECTOR TLV defined in this document, numbering them from 1 as
the most significant bit. the most significant bit.
New bit numbers may be allocated only by an IETF Consensus action. New bit numbers may be allocated only by an IETF Consensus action.
Each bit should be tracked with the following qualities: - Bit number Each bit should be tracked with the following qualities: - Bit number
- Name flag - Reference - Name flag - Reference
Bit Number Name Reference Bit Number Name Reference
1 PCE currently Unavailable This document 0 PCE currently Unavailable This document
2 Unknown Destination This document 1 Unknown Destination This document
3 Unknown Source This document 2 Unknown Source This document
10. Security Considerations 10. Security Considerations
10.1. Vulnerability 10.1. Vulnerability
Attacks on PCEP may result in damage to active networks. If path Attacks on PCEP may result in damage to active networks. If path
computation responses are changed, the PCC may be encouraged to set computation responses are changed, the PCC may be encouraged to set
up inappropriate LSPs. Such LSPs might deviate to parts of the up inappropriate LSPs. Such LSPs might deviate to parts of the
network susceptible to snooping, or might transit congested or network susceptible to snooping, or might transit congested or
teserved links. Path computation responses may be attacked by teserved links. Path computation responses may be attacked by
skipping to change at page 73, line 39 skipping to change at page 73, line 39
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
13.2. Informative References 13.2. Informative References
[I-D.farrel-rtg-common-bnf] [I-D.farrel-rtg-common-bnf]
Farrel, A., "Reduced Backus-Naur Form (RBNF) A Syntax Used Farrel, A., "Reduced Backus-Naur Form (RBNF) A Syntax Used
in Various Protocol Specifications", in Various Protocol Specifications",
draft-farrel-rtg-common-bnf-05 (work in progress), draft-farrel-rtg-common-bnf-07 (work in progress),
September 2008. November 2008.
[I-D.ietf-mpls-mpls-and-gmpls-security-framework] [I-D.ietf-mpls-mpls-and-gmpls-security-framework]
Fang, L. and M. Behringer, "Security Framework for MPLS Fang, L. and M. Behringer, "Security Framework for MPLS
and GMPLS Networks", and GMPLS Networks",
draft-ietf-mpls-mpls-and-gmpls-security-framework-03 (work draft-ietf-mpls-mpls-and-gmpls-security-framework-03 (work
in progress), July 2008. in progress), July 2008.
[I-D.ietf-pce-inter-layer-req] [I-D.ietf-pce-inter-layer-req]
Oki, E., "PCC-PCE Communication and PCE Discovery Oki, E., Roux, J., Kumaki, K., Farrel, A., and T. Takeda,
Requirements for Inter-Layer Traffic Engineering", "PCC-PCE Communication and PCE Discovery Requirements for
draft-ietf-pce-inter-layer-req-07 (work in progress), Inter-Layer Traffic Engineering",
April 2008. draft-ietf-pce-inter-layer-req-08 (work in progress),
October 2008.
[I-D.ietf-pce-interas-pcecp-reqs] [I-D.ietf-pce-interas-pcecp-reqs]
Bitar, N., Kumaki, K., and R. Zhang, "Inter-AS Bitar, N., Kumaki, K., and R. Zhang, "Inter-AS
Requirements for the Path Computation Element Requirements for the Path Computation Element
Communication Protocol (PCEP)", Communication Protocol (PCEP)",
draft-ietf-pce-interas-pcecp-reqs-06 (work in progress), draft-ietf-pce-interas-pcecp-reqs-06 (work in progress),
May 2008. May 2008.
[I-D.ietf-pce-manageability-requirements] [I-D.ietf-pce-manageability-requirements]
Farrel, A., "Inclusion of Manageability Sections in PCE Farrel, A., "Inclusion of Manageability Sections in PCE
Working Group Drafts", Working Group Drafts",
draft-ietf-pce-manageability-requirements-04 (work in draft-ietf-pce-manageability-requirements-05 (work in
progress), June 2008. progress), October 2008.
[I-D.ietf-pce-monitoring] [I-D.ietf-pce-monitoring]
Vasseur, J., Roux, J., and Y. Ikejiri, "A set of Vasseur, J., Roux, J., and Y. Ikejiri, "A set of
monitoring tools for Path Computation Element based monitoring tools for Path Computation Element based
Architecture", draft-ietf-pce-monitoring-02 (work in Architecture", draft-ietf-pce-monitoring-02 (work in
progress), September 2008. progress), September 2008.
[I-D.ietf-rpsec-bgpsecrec] [I-D.ietf-rpsec-bgpsecrec]
Christian, B. and T. Tauber, "BGP Security Requirements", Christian, B. and T. Tauber, "BGP Security Requirements",
draft-ietf-rpsec-bgpsecrec-09 (work in progress), draft-ietf-rpsec-bgpsecrec-09 (work in progress),
 End of changes. 12 change blocks. 
24 lines changed or deleted 25 lines changed or added

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