draft-ietf-pce-of-01.txt   draft-ietf-pce-of-02.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
Expires: May 2008 J.P. Vasseur Expires: August 2008 J.P. Vasseur
Cisco System Inc. Cisco System Inc.
Y. Lee Y. Lee
Huawei Huawei
November 2007
Encoding of Objective Functions in Path Computation Element Encoding of Objective Functions in Path Computation Element
communication Protocol (PCEP) communication Protocol (PCEP)
draft-ietf-pce-of-01.txt draft-ietf-pce-of-02.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 39 skipping to change at page 2, line 39
document are to be interpreted as described in RFC-2119. document are to be interpreted as described in RFC-2119.
Table of Contents Table of Contents
1. Terminology.................................................3 1. Terminology.................................................3
2. Introduction................................................3 2. Introduction................................................3
3. Discovery of PCE Objective Functions........................5 3. Discovery of PCE Objective Functions........................5
3.1. OF-List TLV.................................................5 3.1. OF-List TLV.................................................5
3.2. Elements of procedure.......................................6 3.2. Elements of procedure.......................................6
4. Objective Function in PCEP Path Computation request and 4. Objective Function in PCEP Path Computation request and
reply messages..............................................6 reply messages............................................6
4.1. OF Object...................................................6 4.1. OF Object...................................................6
4.1.1. Elements of Procedure.......................................7 4.1.1. Elements of Procedure.......................................7
4.2. Carrying the OF object in a PCEP message....................8 4.2. Carrying the OF object in a PCEP message....................8
4.3. New RP object flag.........................................10 4.3. New RP object flag.........................................10
4.3.1. Elements of procedure......................................10 4.3.1. Elements of procedure......................................10
5. Objective Functions definition.............................10 5. Objective Functions definition.............................10
6. IANA Considerations........................................12 6. IANA Considerations........................................12
6.1. PCE Objective Function registry............................12 6.1. PCE Objective Function registry............................12
6.2. PCEP code points...........................................13 6.2. PCEP code points...........................................13
6.2.1. OF Object..................................................13 6.2.1. OF Object..................................................13
skipping to change at page 4, line 38 skipping to change at page 4, line 38
optional function parameters. optional function parameters.
For these purposes, this document extends the PCE communication For these purposes, this document extends the PCE communication
Protocol (PCEP). It defines PCEP extensions allowing a PCE Protocol (PCEP). It defines PCEP extensions allowing a PCE
advertising a list of supported objective functions, as well as advertising a list of supported objective functions, as well as
extensions so as to carry the objective function in PCEP request and extensions so as to carry the objective function in PCEP request and
reply messages. It thus complements the PCEP base specification reply messages. It thus complements the PCEP base specification
[PCEP]. [PCEP].
Note that IS-IS and OSPF based PCE Discovery mechanisms are defined Note that IS-IS and OSPF based PCE Discovery mechanisms are defined
in ([ISIS-PCED], [OSPF-PCED]). These mechanisms are dedicated to the in ([RFC5089], [RFC5088]). These mechanisms are dedicated to the
discovery of a few generic parameters while more detailed PCE discovery of a few generic parameters while more detailed PCE
parameters should rather be discovered using the PCE communication parameters should rather be discovered using the PCE communication
Protocol. Objective functions pertain to this second category; thus Protocol. Objective functions pertain to this second category; thus
the Objective Function discovery procedure is handled by PCEP. the Objective Function discovery procedure is handled by PCEP.
A new PCEP TLV, named the OF-List TLV is defined in section 3. The A new PCEP TLV, named the OF-List TLV is defined in section 3. The
OF-List TLV is carried in the PCEP OPEN object and allows a PCE OF-List TLV is carried in the PCEP OPEN object and allows a PCE
advertising to a PCEP peer, during PCEP session setup phase, the list advertising to a PCEP peer, during PCEP session setup phase, the list
of objective functions that it supports. of objective functions that it supports.
skipping to change at page 10, line 4 skipping to change at page 9, line 53
[<path-list>] [<path-list>]
<path-list>::=<path>[<path-list>] <path-list>::=<path>[<path-list>]
<path>::= <ERO> <path>::= <ERO>
[<OF>] [<OF>]
[<LSPA>] [<LSPA>]
[<BANDWIDTH>] [<BANDWIDTH>]
[<metric-list>] [<metric-list>]
[<IRO>] [<IRO>]
where: where:
<metric-list>::=<METRIC>[<metric-list>] <metric-list>::=<METRIC>[<metric-list>]
Note: The OF object MUST NOT be associated to a negative reply, i.e.
a reply with a NO-PATH object.
4.3. New RP object flag 4.3. New RP object flag
In some cases, where no objective function is specified in the In some cases, where no objective function is specified in the
request, or an optional objective function is desired (P flag cleared request, or an optional objective function is desired (P flag cleared
in the OF object common header) but the PCE does not follow the in the OF object common header) but the PCE does not follow the
recommendation, the PCC may desire to know the objective function recommendation, the PCC may desire to know the objective function
that was used by the PCE during path computation. To that end, a new that was used by the PCE during path computation. To that end, a new
flag is defined in the RP object, named the OF flag, allowing a PCC flag is defined in the RP object, named the OF flag, allowing a PCC
to request for the inclusion in the path computation reply of the to request for the inclusion in the path computation reply of the
objective function that was used by the PCE during path computation. objective function that was used by the PCE during path computation.
skipping to change at page 14, line 20 skipping to change at page 14, line 20
document. The IANA is requested to make the following allocation document. The IANA is requested to make the following allocation
(suggested value): (suggested value):
Bit Hex Name Reference Bit Hex Name Reference
Number Number
16 0x200 OF (this document) 16 0x200 OF (this document)
7. Security Considerations 7. Security Considerations
Mechanisms discussed in [PCEP] to secure a PCEP session can be used Mechanisms discussed in [PCEP] to secure a PCEP session can be used to
to secure the PCEP OF object and OF list TLV as well. secure the PCEP OF object and OF list TLV as well.
8. Manageability Considerations 8. Manageability Considerations
8.1. Control of Function and Policy 8.1. Control of Function and Policy
It MUST be possible to configure the activation/deactivation of It MUST be possible to configure the activation/deactivation of
Objective Function Discovery in PCEP. Objective Function Discovery in PCEP.
In addition to the parameters already listed in section 8.1 of [PCEP], In addition to the parameters already listed in section 8.1 of [PCEP],
a PCEP implementation SHOULD allow configuring on a PCE a list of a PCEP implementation SHOULD allow configuring on a PCE a list of
skipping to change at page 15, line 29 skipping to change at page 15, line 29
Mechanisms defined in this document do not imply any requirements on Mechanisms defined in this document do not imply any requirements on
other protocols in addition to those already listed in [PCEP]. other protocols in addition to those already listed in [PCEP].
8.6. Impact on network operations 8.6. Impact on network operations
Mechanisms defined in this document do not have any impact on network Mechanisms defined in this document do not have any impact on network
operations in addition to those already listed in [PCEP]. operations in addition to those already listed in [PCEP].
9. Acknowledgments 9. Acknowledgments
The authors would like to thank Jerry Ash for his useful comments. The authors would like to thank Jerry Ash and Fabien Verhaeghe for
their useful comments.
10. References 10. References
10.1. Normative references 10.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.
[RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", [RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6",
RFC 2740, December 1999. RFC 2740, December 1999.
skipping to change at page 16, line 13 skipping to change at page 16, line 13
progress. progress.
10.2. Informative references 10.2. Informative references
[RFC4657] Ash, J., Le Roux, J.L., " PCE Communication Protocol [RFC4657] Ash, J., Le Roux, J.L., " PCE Communication Protocol
Generic Requirements", RFC4657, September 2006. Generic Requirements", RFC4657, September 2006.
[RFC4674] Le Roux, J.L., et al. "Requirements for PCE discovery", [RFC4674] Le Roux, J.L., et al. "Requirements for PCE discovery",
RFC4674, October 2006. RFC4674, October 2006.
[ISIS-PCED] Le Roux, Vasseur, et al. "IS-IS protocol extensions for [RFC5089] Le Roux, Vasseur, et al. "IS-IS protocol extensions for
Path Computation Element (PCE) Discovery", draft-ietf-pce-disco- Path Computation Element (PCE) Discovery", RFC5089,
proto-isis, work in progress. January 2008.
[OSPF-PCED] Le Roux, Vasseur, et al. "OSPF protocol extensions for [RFC5088] Le Roux, Vasseur, et al. "OSPF protocol extensions for
Path Computation Element (PCE) Discovery", draft-ietf-pce-disco- Path Computation Element (PCE) Discovery", RFC5088,
proto-ospf, work in progress. January 2008.
[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) Requirements and Computation Element Communication Protocol (PCECP) Requirements and
Protocol Extensions In Support of Global Concurrent Optimization", Protocol Extensions In Support of Global Concurrent Optimization",
draft-ietf-pce-global-concurrent-optimization-01.txt, work in draft-ietf-pce-global-concurrent-optimization, work in
progress progress
11. Author's Addresses: 11. Author's 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
skipping to change at page 17, line 41 skipping to change at page 17, line 41
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The IETF Trust (2007). This document is subject to the Copyright (C) The IETF Trust (2008). This document is subject to the
rights, licenses and restrictions contained in BCP 78, and except as rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights. set forth therein, the authors retain all their rights.
 End of changes. 14 change blocks. 
18 lines changed or deleted 21 lines changed or added

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