Path Computation Element Communication Protocol (PCEP) extensions for Circuit Style Policies
draft-ietf-pce-circuit-style-pcep-extensions-16

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>, dd@dhruvdhody.com, draft-ietf-pce-circuit-style-pcep-extensions@ietf.org, ketant.ietf@gmail.com, pce-chairs@ietf.org, pce@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Path Computation Element Communication Protocol (PCEP) extensions for Circuit Style Policies' to Proposed Standard (draft-ietf-pce-circuit-style-pcep-extensions-16.txt)

The IESG has approved the following document:
- 'Path Computation Element Communication Protocol (PCEP) extensions for
   Circuit Style Policies'
  (draft-ietf-pce-circuit-style-pcep-extensions-16.txt) as Proposed Standard

This document is the product of the Path Computation Element Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and Ketan
Talaulikar.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-circuit-style-pcep-extensions/

Ballot Text

Technical Summary

   Segment Routing (SR) enables a node to steer packet flows along a
   specified path without the need for intermediate per-path states, due
   to the utilization of source routing.  An SR Policy can consist of
   one or a set of candidate paths, where each candidate path is
   represented by a segment list or a set of segment lists, which are
   essentially instructions that define a source-routed path.

   This document specifies a set of extensions to the Path Computation
   Element Communication Protocol (PCEP) for Segment Routing Policies
   that are designed to satisfy requirements for connection-oriented
   transport services (Circuit-Style SR policies).  They include the
   ability to control path modification and the option to request a
   strict hop-by-hop path, being also applicable for generic SR policy
   use cases where controlling path modification or deterministic and
   persistent path requirements are applicable.

Working Group Summary

   There was broad consensus in the WG and no controversy or
   contention during its progress. This work is related to the 
   work on Circuit Style Segment Routing Policies in the
   SPRING WG but was extended beyond SR more generically in PCEP.

Document Quality

   There is at least one known commercial shipping implementation
   of this specification. The work is closely related to ongoing
   work in the SPRING WG which references this document. There is
   sufficient overlap of WG participants of SPRING and PCE that
   worked on and reviewed this document. The document has got
   RTGDIR and OPSDIR early reviews and no other reviews have been
   sought as it does not contain any YANG, Media Types, or such
   contents.

Personnel

   The Document Shepherd for this document is Dhruv Dhody. The Responsible
   Area Director is Ketan Talaulikar.

RFC Editor Note