Subject: [Teas] Representing explicit route objects and recorded route objects for fast-reroute protected and backup LSPs

From: Aidan Copeland <[email-masked]>
Date: Thu, 29 Jun 2017 08:41:10 +0000

Authors,

Draft draft-ietf-teas-yang-rsvp-te defines state lists within the scope of the LSP to report

*         the set of incoming explicit route hops

*         the set of outgoing explicit route hops

*         the set of incoming record route subobjects

*         the set of outgoing record route subobjects.

I am interested in how the YANG might be used to report this information for an LSP using the one-to-one-backup method of providing Fast Reroute protection.  When using this method, any LSP might be expected to have N downstream paths and M upstream paths, each with a different set of incoming/outgoing ER hops/RR subobjects.

Is this something that the current version of the YANG is intended to support; or is it likely to support it in a future version?  Do you consider that it would be suitable to introduce lists of upstream and downstream paths, each of which would report the ERO and RRO information, as well as potentially the bandwidth information, corresponding to that path?

Thank you

Aidan Copeland