Skip to main content

Path Computation Element (pce)

Group history

Date By Action
2022-07-23 Amy K. Vezza Resources changed to wiki https://wiki.ietf.org/en/group/pce (Wiki), zulip https://zulip.ietf.org/#narrow/stream/253-pce (Zulip stream) from wiki https://wiki.ietf.org/e/en/group/pce (Wiki), zulip https://zulip.ietf.org/#narrow/stream/253-pce (Zulip stream)
2022-07-23 Dhruv Dhody Resources changed to wiki https://wiki.ietf.org/e/en/group/pce (Wiki), zulip https://zulip.ietf.org/#narrow/stream/253-pce (Zulip stream) from wiki https://trac.ietf.org/trac/pce/wiki (Wiki), zulip https://zulip.ietf.org/#narrow/stream/253-pce (Zulip stream)
2022-07-21 Dhruv Dhody Delegate changed to Hariharan Ananthakrishnan, John Scudder from Hariharan Ananthakrishnan
2022-07-15 Dhruv Dhody Mailing list subscribe address changed to https://www.ietf.org/mailman/listinfo/pce from http://www.ietf.org/mailman/listinfo/pce
2022-07-15 Dhruv Dhody Liaison CC Contact changed to John Scudder from
2022-07-15 Dhruv Dhody Liaison Contact changed to Dhruv Dhody, Hariharan Ananthakrishnan, Julien Meuric from
2022-07-01 Liz Flynn sent scheduled notification for IETF-114
2022-05-06 Jenny Bui Resources changed to wiki https://trac.ietf.org/trac/pce/wiki (Wiki), zulip https://zulip.ietf.org/#narrow/stream/253-pce (Zulip stream) from wiki https://trac.ietf.org/trac/pce/wiki (Wiki)
2022-03-16 Dhruv Dhody Resources changed to wiki https://trac.ietf.org/trac/pce/wiki (Wiki) from tracker https://trac.ietf.org/trac/pce/report/1 (Issue tracker), wiki https://trac.ietf.org/trac/pce/wiki (Wiki)
2022-03-16 Dhruv Dhody Delegate changed to Hariharan Ananthakrishnan from
2022-02-25 Liz Flynn sent scheduled notification for IETF-113
2021-10-15 Liz Flynn sent scheduled notification for IETF-112
2021-07-22 Dhruv Dhody
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a …
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a head-end router) to request paths from, or have paths created by, a Path Computation Server (PCE).

The WG is discussing various enhancements to the stateful PCE. PCE is actively being used for computing and programing of segment routed (SR) paths. There are new proposals for use of PCE for Bit Indexed Explicit Replication (BIER) networks. Further, PCE is a core component of Software Defined Networking (SDN) systems. PCE WG has been working towards enhancing PCEP as an SDN southbound interface (SBI).

[Last Updated: July 22, 2021.]
2021-07-02 Liz Flynn sent scheduled notification for IETF-111
2021-03-10 Cindy Morgan Area Director changed to John Scudder from Deborah Brungard
2021-02-12 Liz Flynn sent scheduled notification for IETF-110
2020-10-23 Liz Flynn sent scheduled notification for IETF-109
2020-07-02 Liz Flynn sent scheduled notification for IETF-108
2020-02-28 Liz Flynn sent scheduled notification for IETF-107
2019-10-25 Liz Flynn sent scheduled notification for IETF-106
2019-09-11 Cindy Morgan Chairs changed to Dhruv Dhody, Julien Meuric from Adrian Farrel, Dhruv Dhody, Julien Meuric
2019-08-07 Dhruv Dhody
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a …
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a head-end router) to request paths from, or have paths created by, a Path Computation Server (PCE).

The WG is actively working on adding to PCEP the concept of an "association group" which binds together arbitrary sets of LSPs and/or policies for the purposes of path computation.  The base draft for this [1] is very flexible and allows for many follow-on innovations, ranging from associations reflecting common policies to those mandating resource diversity and other relationships such as bidirectionality and resource sharing. Another significant piece of work in progress is the extension that allows a PCE to act as a central controller, by instantiating path state on each hop in an LSP [2] and using a flow specifier to add traffic classification to the head-end node of the LSP [3].

There have been some new proposals to clarify RFC 8231 as well as refinement to stateful PCE extensions for state synchronisation between stateful PCEs [4] and relaxing constraints [5].

[Last Updated: August 08, 2019.]

[1] https://datatracker.ietf.org/doc/draft-ietf-pce-association-group/
[2] https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-controller/
[3] https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-flowspec/
[4] https://datatracker.ietf.org/doc/draft-litkowski-pce-state-sync/
[5] https://datatracker.ietf.org/doc/draft-dhody-pce-stateful-pce-optional/
2019-06-28 Liz Flynn sent scheduled notification for IETF-105
2019-04-02 Adrian Farrel Changed milestone "Submit extensions for hierarchical model to the IESG to be considered as a Proposed Standard", resolved as "Done", added draft-ietf-pce-hierarchy-extensions to milestone
2019-04-02 Adrian Farrel Changed milestone "Submit inter-area/AS applicability statement to the IESG as an informational RFC", resolved as "Done", added draft-ietf-pce-inter-area-as-applicability to milestone
2019-04-01 Dhruv Dhody Secretaries changed to Hariharan Ananthakrishnan from Dhruv Dhody
2019-03-26 Dhruv Dhody
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a …
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a head-end router) to request paths from, or have paths created by, a Path Computation Server (PCE).

The WG is concluding the recent effort on generalizing PCEP to include segment routing paths for an MPLS data plane [1].  Another piece of work reaching its conclusion is the extension of PCEP for GMPLS networks [2]. 

The WG is progressing the work related to use of PCE (and PCEP) for the hierarchy of controllers (as per the Abstraction and Control of TE networks (ACTN) framework). We are also concluding the protocol extensions to allow for a hierarchical structure of PCEs (H-PCE) which provides a parent PCE to coordinate the operation of per-domain child PCEs [3]. We have made progress in moving the Stateful operations for P2MP TE tunnels [7] (used by Multicast applications) and automatic bandwidth adjustments [8]. 

The WG is actively working on adding to PCEP the concept of an "association group" which binds together arbitrary sets of LSPs and/or policies for the purposes of path computation.  The base draft for this [4] is very flexible and allows for many follow-on innovations, ranging from associations reflecting common policies to those mandating resource diversity and other relationships such as bidirectionality and resource sharing. Another significant piece of work in progress is the extension that allows a PCE to act as a central controller, by instantiating path state on each hop in an LSP [5] and using a flow specifier to add traffic classification to the head-end node of the LSP [6].

[Last Updated: March 26, 2019.]

[1] https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing/
[2] https://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-pcep-extensions/
[3] https://datatracker.ietf.org/doc/draft-ietf-pce-hierarchy-extensions/
[4] https://datatracker.ietf.org/doc/draft-ietf-pce-association-group/
[5] https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-controller/
[6] https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-flowspec/
[7] https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-p2mp/
[8] https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/
2019-03-01 Liz Flynn sent scheduled notification for IETF-104
2019-01-28 Cindy Morgan Chairs changed to Adrian Farrel, Dhruv Dhody, Julien Meuric from Julien Meuric, Jonathan Hardwick
2018-11-07 Jonathan Hardwick
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a …
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a head-end router) to request paths from, or have paths created by, a Path Computation Server (PCE).

The WG is concluding the recent effort on generalizing PCEP to include segment routing paths for an MPLS data plane [1].  Another piece of work reaching its conclusion is the extension of PCEP for GMPLS networks [2].  We are also concluding the protocol extensions to allow for a hierarchical structure of PCEs (H-PCE) which provides a parent PCE to coordinate the operation of per-domain child PCEs [3].

The WG is actively working on adding to PCEP the concept of an "association group" which binds together arbitrary sets of LSPs and/or policies for the purposes of path computation.  The base draft for this [4] is very flexible and allows for many follow-on innovations, ranging from associations reflecting common policies to those mandating resource diversity and other relationships such as bidirectionality and resource sharing. Another significant piece of work in progress is the extension that allows a PCE to act as a network controller, by instantiating path state on each hop in an LSP [5] and using a flow specifier to add traffic classification to the head-end node of the LSP [6].

[Last Updated: November 8, 2018.]

[1] https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing/
[2] https://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-pcep-extensions/
[3] https://datatracker.ietf.org/doc/draft-ietf-pce-hierarchy-extensions/
[4] https://datatracker.ietf.org/doc/draft-ietf-pce-association-group/
[5] https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-controller/
[6] https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-flowspec/
2018-11-07 Jonathan Hardwick Changed milestone "Submit the stateful PCE document(s) to the IESG", resolved as "Done"
2018-11-07 Jonathan Hardwick Deleted milestone "Submit P2MP MIB to the IESG to be considered as a Proposed Standard"
2018-11-07 Jonathan Hardwick Deleted milestone "Submit the discovery MIB to the IESG to be considered as a Proposed Standard"
2018-11-07 Jonathan Hardwick Changed milestone "Submit inter-layer extensions to the IESG to be considered as a Proposed Standard", resolved as "Done"
2018-11-07 Jonathan Hardwick Changed milestone "Submit PCEP extensions for GMPLS to the IESG to be considered as a Proposed Standard", resolved as "Done"
2018-11-07 Jonathan Hardwick
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a …
The PCE working group is responsible for the Path Communication Element Communication Protocol (PCEP).  PCEP allows a Path Computation Client (PCC - for example, a head-end router) to request paths from, or have paths created by, a Path Computation Server (PCE).

The WG is concluding the recent effort on generalizing PCEP to include segment routing paths for an MPLS data plane [1].  Another piece of work reaching its conclusion is the extension of PCEP for GMPLS networks [2].  We are also concluding the protocol extensions to allow for a hierarchical structure of PCEs (H-PCE) which provides a parent PCE to coordinate the operation of per-domain child PCEs [3].

The WG is actively working on adding to PCEP the concept of an "association group" which binds together arbitrary sets of LSPs and/or policies for the purposes of path computation.  The base draft for this [4] is very flexible and allows for many follow-on innovations, ranging from associations reflecting common policies to those mandating resource diversity and other relationships such as bidirectionality and resource sharing. Another significant piece of work in progress is the extension that allows a PCE to act as a network controller, by instantiating path state on each hop in an LSP [5] and using a flow specifier to add traffic classification to the head-end node of the LSP [6].

[1] https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing/
[2] https://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-pcep-extensions/
[3] https://datatracker.ietf.org/doc/draft-ietf-pce-hierarchy-extensions/
[4] https://datatracker.ietf.org/doc/draft-ietf-pce-association-group/
[5] https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-controller/
[6] https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-flowspec/
2018-10-19 Liz Flynn sent scheduled notification for IETF-103
2018-07-03 Liz Flynn sent scheduled notification for IETF-102
2018-02-27 Liz Flynn sent scheduled notification for IETF-101
2017-10-20 Stephanie McCammon sent scheduled notification for IETF-100
2017-08-22 Deborah Brungard Chairs changed to Jonathan Hardwick, Julien Meuric from Jonathan Hardwick, JP Vasseur, Julien Meuric
2017-06-23 Stephanie McCammon sent scheduled notification for IETF-99
2017-06-22 Jonathan Hardwick Secretaries changed to Dhruv Dhody from Daniel King
2017-03-03 Stephanie McCammon sent scheduled notification for IETF-98
2016-10-21 Stephanie McCammon sent scheduled notification for IETF-97
2016-06-24 Stephanie McCammon sent scheduled notification for IETF-96
2016-03-11 Stephanie McCammon sent scheduled notification for IETF-95
2015-10-09 Stephanie McCammon sent scheduled notification for IETF-94
2015-10-07 Cindy Morgan Shepherding AD changed to Deborah Brungard from
2015-10-07 Jonathan Hardwick Changed milestone "Submit the PCEP MIB to the IESG to be considered as a Proposed Standard", resolved as "Done"
2015-10-06 Cindy Morgan Chairs changed to Jonathan Hardwick, JP Vasseur, Julien Meuric from JP Vasseur, Julien Meuric
2015-10-06 Cindy Morgan Shepherding AD changed to Deborah Brungard from Deborah Brungard
2015-06-26 Stephanie McCammon sent scheduled notification for IETF-93
2015-06-15 Cindy Morgan Mailing list archive changed to https://mailarchive.ietf.org/arch/browse/pce/ from http://www.ietf.org/mail-archive/web/pce/
2015-03-25 Amy K. Vezza Shepherding AD changed to Deborah Brungard from
2015-02-27 Stephanie McCammon sent scheduled notification for IETF-92
2014-06-23 Stephanie McCammon sent scheduled notification for IETF-90
2013-05-21 Adrian Farrel Changed milestone "Submit the stateful PCE document(s) to the IESG", set state to active from review, accepting new milestone
2013-05-21 Julien Meuric Deleted milestone "Submit P2MP MIB as a WG document"
2013-05-21 Julien Meuric Changed milestone "Evaluate WG progress, recharter or close", set due date to February 2015 from March 2013
2013-05-21 Julien Meuric Added milestone "Submit the stateful PCE document(s) to the IESG" for review, due September 2014
2013-05-21 Julien Meuric Changed milestone "Submit P2MP MIB to the IESG to be considered as a Proposed Standard", set due date to April 2014 from October 2012
2013-05-21 Julien Meuric Changed milestone "Submit P2MP MIB as a WG document", set due date to April 2014 from January 2012
2013-05-21 Julien Meuric
Changed milestone "Submit the discovery MIB to the IESG to be considered as a Proposed Standard", set due date to April 2014 from February 2012, …
Changed milestone "Submit the discovery MIB to the IESG to be considered as a Proposed Standard", set due date to April 2014 from February 2012, added draft-ietf-pce-disc-mib to milestone
2013-05-21 Julien Meuric
Changed milestone "Submit the PCEP MIB to the IESG to be considered as a Proposed Standard", set due date to January 2014 from January 2012, …
Changed milestone "Submit the PCEP MIB to the IESG to be considered as a Proposed Standard", set due date to January 2014 from January 2012, added draft-ietf-pce-pcep-mib to milestone
2013-05-21 Julien Meuric
Changed milestone "Submit extensions for hierarchical model to the IESG to be considered as a Proposed Standard", set due date to November 2013 from February …
Changed milestone "Submit extensions for hierarchical model to the IESG to be considered as a Proposed Standard", set due date to November 2013 from February 2013
2013-05-21 Julien Meuric Changed milestone "Submit inter-layer extensions to the IESG to be considered as a Proposed Standard", set due date to November 2013 from February 2012
2013-05-21 Julien Meuric
Changed milestone "Submit PCEP extensions for GMPLS to the IESG to be considered as a Proposed Standard", set due date to September 2013 from June …
Changed milestone "Submit PCEP extensions for GMPLS to the IESG to be considered as a Proposed Standard", set due date to September 2013 from June 2012, added draft-ietf-pce-gmpls-pcep-extensions to milestone
2013-05-21 Julien Meuric Changed milestone "Submit inter-area/AS applicability statement to the IESG as an informational RFC", set due date to September 2013 from March 2012
2013-05-21 Julien Meuric Deleted milestone "Submit PCEP extensions for WSON to the IESG to be considered as a Proposed Standard"
2013-05-21 Julien Meuric Changed milestone "Submit the GMPLS requirements to the IESG to be considered as an Informational RFC", resolved as "Done", added draft-ietf-pce-gmpls-aps-req to milestone
2013-05-21 Julien Meuric Deleted milestone "Submit PCEP extensions for WSON as a WG document"
2013-05-21 Julien Meuric Deleted milestone "Submit extensions for hierarchical PCE path computation model as WG document"
2013-05-21 Julien Meuric Deleted milestone "Submit WSON requirements to the IESG to be considered as an Informational RFC"
2013-05-21 Julien Meuric Changed milestone "Submit applicability and metrics documents to the IESG", set due date to February 2009 from February 2009
2013-05-21 Julien Meuric
Changed milestone "Submit PCE P2MP PCEP protocol extensions to the IESG to be considered as an Proposed Standard RFC", set due date to December 2008 …
Changed milestone "Submit PCE P2MP PCEP protocol extensions to the IESG to be considered as an Proposed Standard RFC", set due date to December 2008 from December 2008
2013-05-21 Julien Meuric Changed milestone "Submit first draft of the PCE P2MP PCEP protocol extensions", set due date to July 2008 from July 2008
2013-05-21 Julien Meuric
Changed milestone "Submit PCE communication protocol specification to the IESG to be considered as a Proposed Standard", set due date to December 2005 from December …
Changed milestone "Submit PCE communication protocol specification to the IESG to be considered as a Proposed Standard", set due date to December 2005 from December 2005
2013-05-21 Julien Meuric
Changed milestone "Submit PCE discovery protocol extensions specifications to the IESG to be considered as a Proposed Standard", set due date to December 2005 from …
Changed milestone "Submit PCE discovery protocol extensions specifications to the IESG to be considered as a Proposed Standard", set due date to December 2005 from December 2005
2013-05-21 Julien Meuric
Changed milestone "Submit PCE communication protocol requirements to the IESG to be considered as an Informational RFC", set due date to December 2005 from December …
Changed milestone "Submit PCE communication protocol requirements to the IESG to be considered as an Informational RFC", set due date to December 2005 from December 2005
2013-05-21 Julien Meuric Changed milestone "Submit PCE architecture specification to the IESG to be considered as Informational RFC", set due date to August 2005 from August 2005
2013-05-21 Julien Meuric Changed milestone "Submit first draft of the PCE communication protocol specification", set due date to July 2005 from July 2005
2013-05-21 Julien Meuric Changed milestone "Submit first draft of the definition of objective metrics", set due date to May 2005 from May 2005
2013-05-21 Julien Meuric Changed milestone "Submit first draft of PCE architecture document", set due date to February 2005 from February 2005
2010-07-09 (System) Changed milestone "Submit PCE P2MP PCEP protocol extensions to the IESG to be considered as an Proposed Standard RFC", resolved as "Done"
2010-07-09 (System) Changed milestone "Submit PCE P2MP communication requirements to the IESG to be considered as an Informational RFC", resolved as "Done"
2009-02-12 (System) Changed milestone "Submit applicability and metrics documents to the IESG", resolved as "Done"
2008-11-02 (System) Changed milestone "Submit first draft of the PCE P2MP PCEP protocol extensions", resolved as "Done"
2008-11-02 (System) Changed milestone "Submit first draft of the PCE P2MP communication requirements", resolved as "Done"
2008-04-14 (System) Changed milestone "Submit PCE communication protocol specification to the IESG to be considered as a Proposed Standard", resolved as "Done"
2008-04-14 (System) Changed milestone "Submit first draft of the definition of objective metrics", resolved as "Done"
2007-05-09 (System) Changed milestone "Submit PCE discovery protocol extensions specifications to the IESG to be considered as a Proposed Standard", resolved as "Done"
2007-05-09 (System) Changed milestone "Submit first draft of the MIB module for the PCE protocol", resolved as "Done"
2006-02-20 (System) Changed milestone "Submit PCE communication protocol requirements to the IESG to be considered as an Informational RFC", resolved as "Done"
2006-01-20 (System) Changed milestone "Submit PCE architecture specification to the IESG to be considered as Informational RFC", resolved as "Done"
2005-11-30 (System) Changed milestone "Submit first draft of the PCE communication protocol specification", resolved as "Done"
2005-11-30 (System) Changed milestone "Submit first draft of PCE discovery requirements and protocol extensions documents", resolved as "Done"
2005-05-16 (System) Changed milestone "Submit first draft of the PCE communication protocol requirements", resolved as "Done"
2005-03-21 (System) Changed milestone "Submit first draft of PCE architecture document", resolved as "Done"
2005-01-06 (System) Started group
2004-03-01 (System) Proposed group