IETF-74, San Francisco, March 2009

PCE Working Group MeetingIETF-74, March 2009, San Francisco

Online Agenda and Slides at:

https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi

Co-chairs: JP Vasseur/Adrian FarrelADs: Ross Callon/Dave Ward

Agenda - PCE Working Group Meeting - IETF-74 – San Francisco – March 2009

1) Administrivia (Chairs) - 5 minutes [5]

2) WG status (Chairs) 5 minutes [10]

3) PCEP Requirements and Extensions for WSON (Young - 5mn) [15]draft-lee-pce-wson-routing-wavelength-02.txt

4) Alternative Approaches to Traffic Engineering Database Creation andMaintenance for Path Computation Elements (Greg - 5mn) [20]draft-lee-pce-ted-alternatives-01.txt

5) The use of SVEC (Synchronization VECtor) list for Synchronizeddependent path computations (Itaru Nishhioka - 5mn) [25]draft-ietf-pce-pcep-svec-list-01

6) Status on Extensions to the Path Computation ElementCommunication Protocol (PCEP) for Point-to-Multipoint TrafficEngineering Label Switched Paths (Dan King - 5mn) [30]draft-ietf-pce-pcep-p2mp-extensions-02.txt

7) PCE-based Computation Procedure To ComputeShortest Constrained P2MP Inter-domain Traffic Engineering Label Switched(Dan King - 10mn) [40]draft-pce-pcep-inter-domain-p2mp-procedures-00.txt (Dan King - 10mn)

8) Requirements for PCE applied in Time-Division Multiplexing (TDM) Networks(Fatai Zhang - 10mn) [50]draft-xx-PCE-reqs-for-TDM-00.txt

9) BGP protocol extensions for Path Computation Element (PCE) Discoveryin a BGP/MPLS IP-VPN (Kenji - 10mn) [60]draft-kumaki-pce-bgp-disco-attribute-03

IETF-74, San Francisco, March 2009

Working Group Status

• Major progress:• RFC 5440 :Path Computation Element (PCE) Communication Protocol (PCEP)• [AUTH 48] RFC 5441: A Backward Recursive PCE-based Computation (BRPC) Procedure

To Compute Shortest Constrained Inter-domain Traffic Engineering Label Switched Paths• [AUTH 48] Draft-ietf-pce-dste: Diffserv-Aware Class-Type Object for the Path Computation

Element Communication Protocol

• RFC editor queue:• [Pending PCEP] Preserving Topology Confidentiality in Inter-Domain Path Computation

Using a Key-Based Mechanism draft-ietf-pce-path-key-05.txt• [Pending Path-key and BRPC] Extensions to the Path Computation Element

Communication Protocol (PCEP) for Route Exclusions - draft-ietf-pce-pcep-xro-06.txt

• IESG Review:• Encoding of Objective Functions in the Path Computation Element

Communication Protocol (PCEP) - draft-ietf-pce-of-06.txt (One DISCUSS)• Quick poll: anyone concerned about using normalized bandwidth in the definition of the

Minimum Load Path objective function (as opposed to absolute value) ?

IETF-74, San Francisco, March 2009

Working Group Status

• Waiting for AD to Go-Ahead: Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions In Support of Global Concurrent Optimization - draft-ietf-pce-global-concurrent-optimization-08.txt

• Publication Requested: • A set of monitoring tools for Path Computation Element based

Architecture - draft-ietf-pce-monitoring-04.txt• Applicability of the Path Computation Element (PCE) to Point-to-Multipoint (P2MP)

Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) draft-ietf-pce-p2mp-app-01.txt

• Two New Working Group Documents:• PCE communication protocol (PCEP) Management Information Base: draft-ietf-pce-

pcep-mib-00.txt• PCC-PCE Communication Requirements for VPNs: draft-ietf-pce-vpn-req-00 (draft-

yasukawa-pce-vpn-req-05)