Skip to main content

The Use Cases for Using PCE as the Central Controller(PCECC) of LSPs
draft-zhao-teas-pcecc-use-cases-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Quintin Zhao , Zhenbin Li , Boris Khasanov , Zekung Ke, Luyuan Fang , Chao Zhou , Telus Communications , Artem Rachitskiy , Anton Gulida
Last updated 2017-04-29 (Latest revision 2016-10-26)
Replaces draft-zhao-pce-central-controller-user-cases
Replaced by draft-ietf-teas-pcecc-use-cases
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-teas-pcecc-use-cases
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

In certain networks deployment scenarios, service providers would like to keep all the existing MPLS functionalities in both MPLS and GMPLS network while reducing existing complexity.In this document, we propose to use the PCE as a central controller so that LSP can be calculated/signaled/initiated/downloaded/managed through a centralized PCE server to each network devices along the LSP path while leveraging the existing PCE technologies as much as possible. This draft describes the use cases for using the PCE as the central controller where LSPs are calculated/setup/initiated/downloaded/ maintained through extending the current PCE architectures and extending the PCEP.

Authors

Quintin Zhao
Zhenbin Li
Boris Khasanov
Zekung Ke
Luyuan Fang
Chao Zhou
Telus Communications
Artem Rachitskiy
Anton Gulida

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)