Make-Before-Break (MBB) MPLS-TE LSP restoration and reoptimization procedure using Stateful Path Computation Element (PCE).
draft-tanaka-pce-stateful-pce-mbb-08

Document Type Expired Internet-Draft (individual)
Last updated 2019-09-08 (latest revision 2019-03-07)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-tanaka-pce-stateful-pce-mbb-08.txt

Abstract

Stateful Path Computation Element (PCE) and its corresponding protocol extensions provide a mechanism that enables PCE to do stateful control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSP). Stateful PCE supports manipulating of the existing LSP's state and attributes (e.g., bandwidth and path) via delegation and also instantiation of new LSPs in the network via PCE Initiation procedures. In the current MPLS TE network using Resource ReSerVation Protocol (RSVP-TE), LSPs are often controlled by Make-before-break (M-B-B) signaling by the headend for the purpose of LSP restoration and reoptimization. In most cases, it is an essential operation to reroute LSP traffic without any data disruption. This document specifies the procedure of applying stateful PCE's control to make-before-break RSVP-TE signaling. In this document, two types of restoration/reoptimization procedures are defined, implicit mode and explicit mode. This document also specifies the usage and handling of stateful PCEP (PCE Communication Protocol) messages, expected behavior of PCC as RSVP-TE headend and necessary extensions of additional PCEP objects.

Authors

Yosuke Tanaka (yosuke.tanaka@ntt.com)
Yuji Kamite (y.kamite@ntt.com)
Ramanjaneya Palleti (ramanjaneya.palleti@huawei.com)
Cheng Li (chengli13@huawei.com)
Haomian Zheng (zhenghaomian@huawei.com)

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