Hi Jorge,
Please see in-line with [yubao].
Thanks
Yubao
原始邮件
发件人：Rabadan,Jorge(Nokia-US/MountainView)
收件人：王玉保10045807;
抄送人：bess@ietf.org;
日 期 ：2021年11月13日 03:00
主 题 ：Re: Re:Comments on draft-ietf-bess-evpn-prefix-advertisement and
draft-wang-bess-evpn-distributed-bu
Hi Yubao,
Thanks for explaining, although I’m afraid we disagree on both things 😊 but
that’s ok. Others can chime in as well.
* If you receive an RT1 with ESI-1 and a route-target identifying BD1, the
RT5 with ESI-1 can be resolved to the RT1, hence the traffic will use the IRB
connected t
Hi Jorge,
Please see in-line with [yubao].
Thanks
Yubao
原始邮件
发件人：Rabadan,Jorge(Nokia-US/MountainView)
收件人：王玉保10045807;
抄送人：bess@ietf.org;
日 期 ：2021年11月12日 04:06
主 题 ：Re: Re:Comments on draft-ietf-bess-evpn-prefix-advertisement and
draft-wang-bess-evpn-distribute
Hi Yubao,
I realized I did not respond to this (my apologies), and you reflected the same
questions in your slides about
draft-wang-bess-evpn-distributed-bump-in-the-wire during the BESS session.
I think it is okay if you want to describe a “distributed” bump-in-the-wire
scenario, but I don’t u
Hi Jorge,
Thank you for your email.
I know that EVPN application will pick up one.
But my question is how can you make sure that the exact one in your expectation
will be picked out?
Other scenarios just need to pick up one for all RT-2 routes that refers to
that ESI,
but the Bu
Hi Yubao,
For GW-IP overlay indexes, until the PE does not receive at least one RT2 for
the GW-IP, you can’t resolve the RT5. If you receive multiple for the same IP
with the same key, it is bgp best path selection. If you receive multiple for
the same IP, different key, the EVPN application pi
Hi Jorge,
In our discussion in another thread, we discussed two types ot the use cases of
draft-ietf-bess-evpn-prefix-advertisement,
They are the GW-IP as overlay index use cases (just let me call them
GW-IP-Style use-cases for short) and the Bump-in-the-wire use case.
I think it is b
