PCE Working Group Meeting IETF-64, November 2005, Vancouver

1. PCE Working Group MeetingIETF-64, November 2005, Vancouver Online Agenda and Slides at: http://www3.ietf.org/proceedings/05nov/agenda Co-chairs: JP Vasseur/Adrian Farrel ADs: Alex Zinin/Bill Fenner 64th IETF, Vancouver, November 2005

2. 1) Agenda/Admin (Chairs - 5mn) 1) Agenda/admin (Chairs-5mn) 2) PCE WG Milestone update (Chairs-10mn) 3) Path Computation Policy draft-bryskin-pce-policy-enabled-path-comp-00.txt (Igor - 20mn) 4) PCE Policy Architecture, draft-berger-pce-policy-architecture-00.txt (Lou - 10mn) 5) Discussion on the PCE Discovery protocol (Jean-Louis Le Roux - 15mn) draft-leroux-pce-disco-proto-igp-00.txt 6) PCECP discussion and next steps (Adrian - 20mn) 7) Inter-area PCECP requirement draft (Jean-Louis Le Roux - 10mn) draft-leroux-pce-pcecp-multiarea-reqs-00.txt 8) Inter-AS/Provider PCE requirement draft (Nabil Bitar - 10mn) draft-bitar-interas-PCE-req-00.txt 9)Discussion on inter-layer deployment scenario, similarities with inter-area/AS, application specific requirements draft-oki-pce-inter-layer-req-00.txt (Eiji Oki - 10mn) 10) Cost object draft-dolganow-pce-cost-object-00.txt (Andrew Dolganow - 10mn) 11) Next Steps (Chairs - 10mn) 64th IETF, Vancouver, November 2005

3. 2) PCE WG Milestones update (Chairs - 10mn) • DoneSubmit first draft of PCE architecture document • New revisions posted: draft-ietf-pce-architecture-02.txt (September 2005) • Still need to address Lou’s comments on policy: to be done in rev-03 • Aug 05 Submit PCE architecture specification to the IESG to be considered as Informational RFC • Feb 05 (Half Done)Submit first draft of PCE discovery requirements and protocol extensions documents - draft-ietf-pce-discovery-reqs-02 (October 2005) just passed WG LC. - protocol extensions to be done 64th IETF, Vancouver, November 2005

4. 2) PCE WG Milestones update (Cont’) • Done Submit first draft of the PCE communication protocol requirements • draft-ietf-pce-comm-protocol-gen-reqs-02.txt (September 2005) • Not quite yet ready for WG LC … several requirements listed in application-specific IDs are in fact generic. More discussion on the list. Example: -> Computation of a set of LSPs such that the sum of their bw=requested bw (load balancing, VCAT) -> Reoptimization requests -> LSP Rerouting 64th IETF, Vancouver, November 2005

5. 2) PCE WG Milestones update (Cont’) • May 05 Submit first draft of the definition of objective metrics • Likely to be done later (requires other work to be done first) • Action item from JP/Adrian: when ready, draft a mini framework for this item. • Set of co-authors already identified (Emile Stephan, Anwar Elwalid, Richard Rabbat, Hani El-Sakkout) • Jul 05 Submit first draft of the PCE communication protocol specification ==> WG decision to be made very soon on which protocol to pursue • Nov 05 Submit first draft of applicability statement (describing the processes and procedures for the use of the PCE architecture, protocols and protocol extensions for inter-area MPLS and GMPLS Traffic Engineering) • Nov 05 Submit first draft of the MIB module for the PCE protocol => PCECP to be chosen first … 64th IETF, Vancouver, November 2005

6. 11) Key Next steps (Chairs - 10mn) • Submit a new revision of the PCE Architecture I-D, with the objective to go for WG last call soon after this IETF • Addressing Lou’s comments on Policy • Finalize the PCECP requirements IDs: make progress on application-specific IDs (Inter-area, Inter-AS, Inter-layer) and move the generic requirements to the generic IDs • Select a PCECP protocol • New I-D for PCE Discovery protocol extensions • Select a protocol for PCE discovery • New I-D on the “less-constrained path” problem comprising the requirement + solution • “Requirements and Protocol Extensions to Support Relaxation of Computation Constraints with PCE” • Separation means that basic requirements and solution can go ahead 64th IETF, Vancouver, November 2005