Skip to main content

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

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Quintin Zhao , Zhenbin Li , Boris Khasanov , Zekung Ke, Luyuan Fang , Chao Zhou , Telus Communications , Artem Rachitskiy
Last updated 2017-11-27 (Latest revision 2017-05-26)
RFC stream Internet Engineering Task Force (IETF)
Formats
Reviews
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
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

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