Ability for a Stateful Path Computation Element (PCE) to Request and Obtain Control of a Label Switched Path (LSP)
draft-ietf-pce-lsp-control-request-11

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, db3546@att.com, Hariharan Ananthakrishnan <hari@netflix.com>, hari@netflix.com, pce@ietf.org, pce-chairs@ietf.org, draft-ietf-pce-lsp-control-request@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Ability for a Stateful Path Computation Element (PCE) to request and obtain control of a Label Switched Path (LSP)' to Proposed Standard (draft-ietf-pce-lsp-control-request-11.txt)

The IESG has approved the following document:
- 'Ability for a Stateful Path Computation Element (PCE) to request and
   obtain control of a Label Switched Path (LSP)'
  (draft-ietf-pce-lsp-control-request-11.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-lsp-control-request/

Ballot Text

Technical Summary

A Stateful Path Computation Element (PCE) retains information about the placement of Multiprotocol Label Switching (MPLS) Traffic
Engineering Label Switched Paths (TE LSPs).  When a PCE has stateful
control over LSPs it may send indications to LSP head-ends to modify
the attributes (especially the paths) of the LSPs.  A Path Computation Client (PCC) has set up LSPs under local configuration may delegate control of those LSPs to a stateful PCE.

There are use-cases in which a Stateful PCE may wish to obtain
control of locally configured LSPs of which it is aware but that have
not been delegated to the PCE.

This document describes an extension to the Path Computation Element communication Protocol (PCEP) to enable a PCE to make
such requests.

Working Group Summary

No concerns.
  
Document Quality

One implementation is confirmed and at least one more have been placed on product roadmaps.

Personnel

Who is the Document Shepherd for this document?  Hariharan Ananthakrishnan

Who is the Responsible Area Director? Deborah Brungard

RFC Editor Note