Skip to main content

Extensions to the Path Computation Element Communication Protocol(PCEP) for Crank-back Routing
draft-huangshg-pce-crank-back-routing-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Dajiang Wang , Xihua Fu , Wanyi Gu , Shanguo Huang
Last updated 2010-10-18
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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

Path computation in large multi-layer and multi-region networks is complex and may require special computational components and cooperation between different network domains, whereby a failure affect to establish a path or a failure of an existing path may be corrected by a new path computation and fresh signaling. This document specifies the crank-back routing mechanism based on re- routing in crank back Path Computation Element (PCE). When a Path Computation Client (PCC) requests a PCE for a route, it may be useful for the PCC to specify Crank-back routing to the path computation, abstract nodes, resources, and domains that are to be explicitly excluded from the computed route. Such mechanism is termed Crank- back routing. The PCE Communication Protocol (PCEP) is designed as a communication protocol between PCCs and PCEs. To support this mechanism, function of PCE and procedure of PCEP signaling performance are extended.

Authors

Dajiang Wang
Xihua Fu
Wanyi Gu
Shanguo Huang

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