PCEP Extensions for Signaling Multipath Information
draft-koldychev-pce-multipath-05
| Document | Type |
Replaced Internet-Draft
(pce WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mike Koldychev , Siva Sivabalan , Tarek Saad , Vishnu Pavan Beeram , Hooman Bidgoli , Bhupendra Yadav , Shuping Peng | ||
| Last updated | 2021-05-03 (Latest revision 2021-02-16) | ||
| Replaced by | draft-ietf-pce-multipath | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-pce-multipath | |
| Consensus boilerplate | Unknown | ||
| 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
Current PCEP standards allow only one intended and/or actual path to be present in a PCEP report or update. Applications that require multipath support such as SR Policy require an extension to allow signaling multiple intended and/or actual paths within a single PCEP message. This document introduces such an extension. Encoding of multiple intended and/or actual paths is done by encoding multiple Explicit Route Objects (EROs) and/or multiple Record Route Objects (RROs). A special separator object is defined in this document, to facilitate this. This mechanism is applicable to SR-TE and RSVP-TE and is dataplane agnostic.
Authors
Mike Koldychev
Siva Sivabalan
Tarek Saad
Vishnu Pavan Beeram
Hooman Bidgoli
Bhupendra Yadav
Shuping Peng
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)