Path Computation Element (PCE) Protocol Extensions for Stateful PCE usage for Point-to-Multipoint Traffic Engineering Label Switched Paths
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: The IESG <email@example.com>, firstname.lastname@example.org, email@example.com, Adrian Farrel <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Protocol Action: 'Path Computation Element (PCE) Protocol Extensions for Stateful PCE usage for Point-to-Multipoint Traffic Engineering Label Switched Paths' to Proposed Standard (draft-ietf-pce-stateful-pce-p2mp-13.txt) The IESG has approved the following document: - 'Path Computation Element (PCE) Protocol Extensions for Stateful PCE usage for Point-to-Multipoint Traffic Engineering Label Switched Paths' (draft-ietf-pce-stateful-pce-p2mp-13.txt) as Proposed Standard This document is the product of the Path Computation Element Working Group. The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah Brungard. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-p2mp/
Technical Summary The Path Computation Element (PCE) has been identified as an appropriate technology for the determination of the paths of point-to-multipoint (P2MP) TE Label Switched Paths (LSPs). This document provides extensions required for Path Computation Element Communication Protocol (PCEP) so as to enable the usage of a stateful PCE capability in supporting P2MP TE LSPs. Working Group Summary The working group process has been uneventful. The author team comes from vendors and operators who ship and deploy P2MP RSVP-TE and so have a very strong interest in these PCE extensions. Document Quality This document received only moderate review during its time in the working group. P2MP function is somewhat fringe, and so only a small group of people worked on it. As a result, WG last call was quiet. The document shepherd (Adrian Farrel) and the out-going chair (Jon Hardwick) made detailed reviews that led to a number of minor changes. Implementation status is not known, but it is believed that two vendors have roadmap plans. Personnel Who is the Document Shepherd for this document? Adrian Farrel Who is the Responsible Area Director? Deborah Brungard IANA Note IANA Early code point allocation was made for the code points needed by this work.