Hi Wim, That wasn't my most glorious moment :-)
I don't think that draft-drake-bess-datacenter-gateway and draft-ietf-idr-segment-routing-te-policy are anything other than complementary. Nor, apparently does Eric as he is a co-author of both documents :-) I think high-level document names can sometimes lead to some confusion, but the combination of "BGP", "SR", and "TE" in the same overviews only goes to show that they are in the same general space, not that they overlap. If you take a look at draft-farrel-spring-sr-domain-interconnect-00 you'll see it references [I-D.previdi-idr-segment-routing-te-policy] (now adopted by the IDR working group) as the assumed mechanism for advertising intra-AS links that are SR TE policies. We also note that [I-D.previdi-idr-segment-routing-te-policy] offers a method for label stack compression. I think the two mechanisms provide different functions, but functions that could (or even should) be integrated into a deployable solution. Thanks (and sorry again), Adrian _______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
