PCEP Extensions for service segment used in Segment Routing
draft-dw-pce-service-segment-routing-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Dhruv Dhody , Qin Wu | ||
| Last updated | 2014-12-29 (Latest revision 2014-06-27) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
Segment Routing (SR) technology leverages the source routing and tunneling paradigms where a source node can choose a path without relying on hop-by-hop signaling. The same mechanism can also be utilized for Service Function Chaining (SFC) to steer packets through service functions performing specific services such as DPI, Firewall, accounting etc. This document specifies extensions to the Path Computation Element Protocol (PCEP) that allow a stateful PCE to compute and instantiate SR-TE paths that have service functions (SF) (or service segments) involved.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)