Hello; We've submitted a draft for the group's consideration. We know that stateful PCE has been discussed by the working group in the past. We believe that we have addressed some of the issues that have been raised in previous discussions and have specific use cases that make stateful PCE valuable. We hope you'll find the time to look through the draft and comment on the list before the WG meeting in Taipei, and hope that we'll be able to have a fruitful and lively discussion there.
best, -Edward ---------- Forwarded message ---------- From: <internet-dra...@ietf.org> Date: Sun, Oct 16, 2011 at 7:51 PM Subject: New Version Notification for draft-crabbe-pce-stateful-pce-00.txt To: e...@google.com Cc: jmed...@juniper.net, e...@google.com, rva...@juniper.net A new version of I-D, draft-crabbe-pce-stateful-pce-00.txt has been successfully submitted by Edward Crabbe and posted to the IETF repository. Filename: draft-crabbe-pce-stateful-pce Revision: 00 Title: PCEP Extensions for Stateful PCE Creation date: 2011-10-16 WG ID: Individual Submission Number of pages: 39 Abstract: The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Clients (PCCs) requests. Although PCEP explicitly makes no assumptions regarding the information available to the PCE, it also makes no provisions for synchronization or PCE control of timing and sequence of path computations within and across PCEP sessions. This document describes a set of extensions to PCEP to enable this functionality, providing stateful control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSP) via PCEP. The IETF Secretariat
_______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce
