datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Encoding of Data Structure (DS) in the Path Computation Element Communication Protocol (PCEP)
draft-dhody-pce-pcep-ds-04

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-03-03 (latest revision 2013-08-20)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-dhody-pce-pcep-ds

Abstract

The ability to compute shortest constrained Traffic Engineering Label Switched Paths (TE LSPs) in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks across multiple domains has been identified as a key requirement for point-to-point (P2P) and point- to-multipoint (P2MP) scenarios. Backward-Recursive Path Computation (BRPC) [RFC5441] defines Virtual Shortest Path Tree (VSPT) as a default de-facto data structure for path reply message in inter- domain scenarios. As Path Computation Element (PCE) will get used in newer scenarios like inter-domain, protection, P2MP etc. As well as PCE is being explored to be used in Cross Stratrum Optimization (CSO) environment (see [CSO-PCE]) as well as in [ABNO]. Limiting PCE communication Protocol (PCEP) to just one data structure limits the usage of PCEP. Its important to keep PCEP generic enough to use differnt data structure and apply different algorithms. This document defines extensions to the PCEP to allow multiple data structures. Extensions are defined for PCE to indicate the set of Data Structure (DS) it supports; also Path Computation Client (PCC) or PCE can indicate in a path computation request the required DS, and a PCE can report in a path computation reply the Data Structure that was used in the path reply message.

Authors

Dhruv Dhody <dhruv.dhody@huawei.com>
Udayasree Palle <udayasree.palle@huawei.com>

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