Thanks Lou, it is great that you have clarified it too. Good to know BGP fully supported it for both RFC5512 and RFC5566, only Zebra and data plane needs more work. Thanks, Jay On 11/14/18, 1:27 PM, "Lou Berger" <lberger@labn.net> wrote: Hi Sorry about the slow response. The bgp code has full support for 5512, and the code has been tested in controller only configurations using rfapi. (Donald is 100% correct about no zebra or data plane support in the frr code.) The code contains support for both encap attribute and safi, per 5512 and 5566. To my knowledge we are the only ones to implement encap Safi - I recommended deprecating the encap Safi and this was agreed to in the encap update. This said, there has been discussions at the last two IETFs related to a "sdwan" that is basically the same as encap Safi so it may still be relevant. Lou ---------- On November 15, 2018 2:27:52 AM Jia Chen <jchen1@paloaltonetworks.com> wrote: > Thanks Donald, I will put it in to-do list on our side. The cloud service > better to have this feature or “the BGP remote nexthop”, which seems still > in draft (not RFC) though. > Jay > > > On 11/14/18, 9:13 AM, "Donald Sharp" <sharpd@cumulusnetworks.com> wrote: > > I believe someone would need to implement support in bgp and a > methodology to instruct the underlying dataplane on how to reach those > routes. > > donald > On Wed, Nov 14, 2018 at 12:08 PM Jia Chen <jchen1@paloaltonetworks.com> wrote: > > > > A question to FRR exports, what is the status of RFC 5512 or its > alternative supporting plan? > > > > Thanks, > > Jay > > > > > > > _______________________________________________ > dev mailing list > dev@lists.frrouting.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.frrouting.org_lis...