Conveying policies associated with traffic engineering paths over PCEP session
draft-sivabalan-pce-policy-identifier-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2016-04-09 (latest revision 2015-10-07) | ||
| Replaced by | draft-dhody-pce-association-policy | ||
| 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 | Replaced by draft-dhody-pce-association-policy | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-sivabalan-pce-policy-identifier-00.txt
Abstract
This document describes a simple extension to the Path Computation Element (PCE) Communication Protocol (PCEP) using which a PCEP speaker can enforce one or more policies on the other PCEP speaker. A policy is represented by a numeric value which can be interpreted only by the receiving PCEP speaker. Using the proposed extension, a path computation client (PCC) can signal one or more policies that must be taken into consideration by a PCE during path computation. Similarly, when initiating or updating a path, a stateful PCE can signal one or more policies (e.g., traffic steering rules) that a PCC is expected to apply to the path.
Authors
Siva Sivabalan
(msiva@cisco.com)
Clarence Filsfils
(cfilsfil@cisco.com)
Jeff Tantsura
(jeff.tantsura@ericsson.com)
Jonathan Hardwick
(jonathan.hardwick@metaswitch.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)