draft-ietf-pce-of-04.txt   draft-ietf-pce-of-05.txt 
Network Working Group J.L. Le Roux Network Working Group J.L. Le Roux
Internet Draft France Telecom Internet Draft France Telecom
Category: Standard Track Category: Standard Track
Created: August 5, 2008 J.P. Vasseur Created: September 6, 2008 J.P. Vasseur
Expires: February 5, 2009 Cisco System Inc. Expires: March 6, 2009 Cisco System Inc.
Y. Lee Y. Lee
Huawei Huawei
Encoding of Objective Functions in the Path Computation Element Encoding of Objective Functions in the Path Computation Element
Communication Protocol (PCEP) Communication Protocol (PCEP)
draft-ietf-pce-of-04.txt draft-ietf-pce-of-05.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 other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 2, line 16 skipping to change at page 2, line 16
(PCEP) to allow a PCE to indicate the set of objective functions it (PCEP) to allow a PCE to indicate the set of objective functions it
supports. Extensions are also defined so that a PCC can indicate in supports. Extensions are also defined so that a PCC can indicate in
a path computation request the required objective function, and so a path computation request the required objective function, and so
that a PCE can report in a path computation reply the objective that a PCE can report in a path computation reply the objective
function that was used for path computation. function that was used for path computation.
Table of Contents Table of Contents
1. Introduction................................................3 1. Introduction................................................3
1.1. Terminology.................................................4 1.1. Terminology.................................................4
1.2. Message Formats.............................................5
2. Discovery of PCE Objective Functions........................5 2. Discovery of PCE Objective Functions........................5
2.1. OF-List TLV.................................................5 2.1. OF-List TLV.................................................5
2.2. Elements of procedure.......................................6 2.2. Elements of procedure.......................................6
3. Objective Function in PCEP Path Computation Request and 3. Objective Function in PCEP Path Computation Request and
Reply Messages............................................6 Reply Messages............................................6
3.1. OF Object...................................................6 3.1. OF Object...................................................6
3.1.1. Elements of Procedure.......................................7 3.1.1. Elements of Procedure.......................................7
3.2. Carrying The OF Object In a PCEP Message....................8 3.2. Carrying The OF Object In a PCEP Message....................8
3.3. New RP Object Flag.........................................10 3.3. New RP Object Flag.........................................10
3.3.1. Elements Of Procedure......................................10 3.3.1. Elements Of Procedure......................................10
skipping to change at page 5, line 5 skipping to change at page 5, line 5
path computation to be performed by a Path Computation Element. path computation to be performed by a Path Computation Element.
PCE: Path Computation Element: An entity (component, application, or PCE: Path Computation Element: An entity (component, application, or
network node) that is capable of computing a network path or route network node) that is capable of computing a network path or route
based on a network graph, and applying computational constraints. based on a network graph, and applying computational constraints.
PCEP: Path Computation Element communication Protocol. PCEP: Path Computation Element communication Protocol.
TE LSP: Traffic Engineered Label Switched Path. TE LSP: Traffic Engineered Label Switched Path.
1.2. Message Formats
Message formats in this document are expressed using Reduced BNF as
used in [PCEP] and defined in [RBNF].
2. Discovery of PCE Objective Functions 2. Discovery of PCE Objective Functions
This section defines PCEP extensions (see [PCEP]) so as to support This section defines PCEP extensions (see [PCEP]) so as to support
the advertisement of the objective functions supported by a PCE. the advertisement of the objective functions supported by a PCE.
A new PCEP OF-List (Objective Function list) TLV is defined. The PCEP A new PCEP OF-List (Objective Function list) TLV is defined. The PCEP
OF-List TLV is carried within an OPEN object, in order for a PCE to OF-List TLV is carried within an OPEN object, in order for a PCE to
advertise to a PCEP peer the list of objective functions it supports, advertise to a PCEP peer the list of objective functions it supports,
during PCEP session setup phase. during PCEP session setup phase.
skipping to change at page 5, line 33 skipping to change at page 5, line 38
octets specifying the TLV length, and a value field. The Length field octets specifying the TLV length, and a value field. The Length field
defines the length of the value portion in octets. The TLV is padded defines the length of the value portion in octets. The TLV is padded
to four-octet alignment and padding is not included in the Length to four-octet alignment and padding is not included in the Length
field (e.g. a three octet value would have a length of three, but the field (e.g. a three octet value would have a length of three, but the
total size of the TLV would be eight octets). total size of the TLV would be eight octets).
The PCEP OF-List TLV has the following format: The PCEP OF-List TLV has the following format:
TYPE: To be assigned by IANA (suggested value = 4 ) TYPE: To be assigned by IANA (suggested value = 4 )
LENGTH: N * 2 (where N is the number of objective functions) LENGTH: N * 2 (where N is the number of objective functions)
VALUE: list of 2-bytes objective function code points, VALUE: list of 2-bytes objective function code points, identifying
identifying the objective functions supported by the the objective functions supported by the sender of the Open message.
sender of the Open message.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OF Code #1 | OF Code #2 | | OF Code #1 | OF Code #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// // // //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OF Code #N | padding | | OF Code #N | padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 17, line 19 skipping to change at page 17, line 19
[PCE-GCO] Y. Lee, J.L. Le Roux, D. King, and E. Oki, "Path [PCE-GCO] Y. Lee, J.L. Le Roux, D. King, and E. Oki, "Path
Computation Element Communication Protocol (PCECP) Computation Element Communication Protocol (PCECP)
Requirements and Protocol Extensions In Support of Global Requirements and Protocol Extensions In Support of Global
Concurrent Optimization", draft-ietf-pce-global-concurrent- Concurrent Optimization", draft-ietf-pce-global-concurrent-
optimization, work in progress. optimization, work in progress.
[PCEP-MIB] Koushik, K., and Stephan, E., "PCE communication protocol [PCEP-MIB] Koushik, K., and Stephan, E., "PCE communication protocol
(PCEP) Management Information Base", draft-kkoushik-pce- (PCEP) Management Information Base", draft-kkoushik-pce-
pcep-mib, work in progress. pcep-mib, work in progress.
[RBNF] A. Farrel, "Reduced Backus-Naur Form (RBNF) - A Syntax Used
in Various Protocol Specifications", draft-farrel-rtg-
common-bnf, work in progress.
11. Authors' Addresses 11. Authors' Addresses
Jean-Louis Le Roux Jean-Louis Le Roux
France Telecom France Telecom
2, avenue Pierre-Marzin 2, avenue Pierre-Marzin
22307 Lannion Cedex 22307 Lannion Cedex
FRANCE FRANCE
Email: jeanlouis.leroux@orange-ftgroup.com Email: jeanlouis.leroux@orange-ftgroup.com
Jean-Philippe Vasseur Jean-Philippe Vasseur
 End of changes. 6 change blocks. 
6 lines changed or deleted 15 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/