draft-ietf-pce-pcep-17.txt   draft-ietf-pce-pcep-18.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: May 6, 2009 France Telecom Expires: May 6, 2009 France Telecom
November 2, 2008 November 2, 2008
Path Computation Element (PCE) Communication Protocol (PCEP) Path Computation Element (PCE) Communication Protocol (PCEP)
draft-ietf-pce-pcep-17.txt draft-ietf-pce-pcep-18.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 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: 0 - PCE currently unavailable o Bit number: 31 - PCE currently unavailable
o Bit number: 1 - Unknown destination o Bit number: 30 - Unknown destination
o Bit number: 2 - Unknown source o Bit number: 29 - 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 11 skipping to change at page 62, line 11
Each bit should be tracked with the following qualities: Each bit should be tracked with the following qualities:
o Bit number o Bit number
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 (RP Object)
Bit Description Reference Bit Description Reference
0-2 Priority This document 0-2 Priority This document
3 Reoptimization This document 3 Reoptimization This document
4 Bi-directional This document 4 Bi-directional This document
5 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
skipping to change at page 65, line 24 skipping to change at page 65, line 24
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
9.11. NO-PATH-VECTOR TLV 9.11. NO-PATH-VECTOR TLV
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 0 as
the most significant bit. the least 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
0 PCE currently Unavailable This document 31 PCE currently Unavailable This document
1 Unknown Destination This document 30 Unknown Destination This document
2 Unknown Source This document 29 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
 End of changes. 7 change blocks. 
10 lines changed or deleted 10 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/