PCEP Extensions for Signaling Multipath Information

Document Type Replaced Internet-Draft (pce WG)
Authors Mike Koldychev  , Siva Sivabalan  , Tarek Saad  , Vishnu Beeram  , Hooman Bidgoli  , Bhupendra Yadav  , Shuping Peng 
Last updated 2021-05-03 (latest revision 2021-02-16)
Replaced by draft-ietf-pce-multipath
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
plain text xml htmlized pdfized bibtex
Stream WG state Adopted by a WG
Other - see Comment Log
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-pce-multipath
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Mike Koldychev (mkoldych@cisco.com)
Siva Sivabalan (ssivabal@ciena.com)
Tarek Saad (tsaad@juniper.net)
Vishnu Beeram (vbeeram@juniper.net)
Hooman Bidgoli (hooman.bidgoli@nokia.com)
Bhupendra Yadav (byadav@ciena.com)
Shuping Peng (pengshuping@huawei.com)

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