Closed italobusi closed 1 year ago
2023-05-19 TE call
Agreed resolution (see slide 4 of tunnel-paths-05.zip):
Candidate-Secondary-list (fwd)
Secondary-1-ref (fwd)
Secondary-4-ref (rev)
Secondary-2-ref (fwd)
Secondary-3-ref (rev)
2023-05-26 TE Call
Agreed to add a secondary-reverse-path leafref to the secondary path:
+--rw tunnels
| +--rw tunnel* [name]
| +--rw name string
| +---rw bidirectional? boolean
| +--rw primary-paths
| | +--rw primary-path* [name]
| | +--rw name string
| | +--rw co-routed? boolean
| | +--rw primary-reverse-path
| | | +--rw name? string
| | | +--rw candidate-secondary-reverse-paths
| | | +--rw candidate-secondary-reverse-path*
| | | [secondary-path]
| | | +--rw secondary-path leafref
| | +--rw candidate-secondary-paths
| | +--rw candidate-secondary-path* [secondary-path]
| | +--rw secondary-path leafref
| | +--ro active? boolean
| +--rw secondary-paths
| | +--rw secondary-path* [name]
| | +--rw name string
| | +--rw secondary-reverse-path? leafref // ADD
| +--rw secondary-reverse-paths
| | +--rw secondary-reverse-path* [name]
| | +--rw name string
While working on the examples in section 12.6, some questions about how to associated forward and reverse secondary paths have been raised:
See: https://github.com/tsaad-dev/te/issues/56#issuecomment-1279400042
Discussion on this issue is pending resolution of issue #203