Skip to main content

PCE Path Profiles
draft-alvarez-pce-path-profiles-04

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Santiago Alvarez , Siva Sivabalan , Zafar Ali , Luis Tomotaki , Victor Lopez , Rob Shakir , Jeff Tantsura
Last updated 2015-05-13 (Latest revision 2014-11-09)
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

This document describes extensions to the Path Computation Element (PCE) Communication Protocol (PCEP) to signal path profile identifiers. A profile represents a list of path parameters or policies that a PCEP peer may invoke on a remote peer using an opaque identifier. When a path computation client (PCC) initiates a path computation request, the PCC can signal profile identifiers to invoke path parameters or policies defined on the PCE which would influence the path computation. Similarly, when a PCE initiates or updates a path, the PCE can signal profile identifiers to invoke path parameters or policies defined on the PCC which would influence the path setup.

Authors

Santiago Alvarez
Siva Sivabalan
Zafar Ali
Luis Tomotaki
Victor Lopez
Rob Shakir
Jeff Tantsura

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