Hi all,
The use case is without TE. And this is how network designs are working today,
and I do not see any valid reason to complexify and change the existing designs
by introducing controllers or BGP-LS.
We have to accommodate with what is deployed today and the proposed change is
quite
Aijun �C
In the inter-AS case, what is needed is to know ELC of the originating node.
Simply knowing who the originator of an advertisement is not sufficient.
If ELC is advertised as a node capability, then a controller with access to
BGP-LS database for both ASs could determine ELC by piecing
Hi, Les and Stephane:
https://tools.ietf.org/html/draft-wang-lsr-ospf-prefix-originator-ext-00 is
trying to solve what you are concerning for.
As you said, ELC/ERLD are functionally node capabilities, but when we try to
send traffic, we should consider the prefixes itself.
The above draft
Stephane -
The use case for this proposal is to support inter-AS scenarios in the absence
of a controller.
If the WG agrees that this use case needs to be addressed I believe the
proposal below is a good and viable compromise.
I say "compromise" because - as you mention below - ELC/ELRD are
