Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
RFC 5521

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    pce mailing list <pce@ietf.org>, 
    pce chair <pce-chairs@tools.ietf.org>
Subject: Protocol Action: 'Extensions to the Path Computation 
         Element Communication Protocol (PCEP) for Route Exclusions' to 
         Proposed Standard 

The IESG has approved the following document:

- 'Extensions to the Path Computation Element Communication Protocol 
   (PCEP) for Route Exclusions '
   <draft-ietf-pce-pcep-xro-06.txt> as a Proposed Standard

This document is the product of the Path Computation Element Working 

The IESG contact persons are Ross Callon and David Ward.

A URL of this Internet-Draft is:

Technical Summary

   The PCE Communication Protocol (PCEP) is designed as a communication
   protocol between PCCs and PCEs. This document presents PCEP
   extensions for route exclusions.

   The Path Computation Element (PCE) provides functions of path
   computation in support of traffic engineering in Multi-Protocol
   Label Switching (MPLS) and Generalized MPLS (GMPLS) networks.

   When a Path Computation Client (PCC) requests a PCE for a route, it
   may be useful for the PCC to specify, as constraints to the path
   computation, abstract nodes, resources, and Shared Risk Link Groups
   (SRLGs) that are to be explicitly excluded from the computed route.
   Such constraints are termed route exclusions.

Working Group Summary

   The document has been discussed and reviewed by several key WG
   members. Good consensus reported within the WG. No review by non
   WG members that has been considered necessary. The solution 
   specified in this document has a good support in the WG, and
   satisfies a well specified requirement for the PCEP protocol   

Document Quality

   There is one known implementation of this document with several  
   other unknown implementations. An interoperability event (ISOCRE)
   with multiple implementations is planned.


   JP Vasseur is the document shepherd. Ross Callon is the responsible