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
The IESG has approved the following document:
- 'Integrated Routing and Bridging in EVPN'
(draft-ietf-bess-evpn-inter-subnet-forwarding-15.txt) as Proposed Standard
This document is the product of the BGP Enabled ServiceS Working Group.
The IESG contact persons are Alvaro Retana, John Scudder
Hi Jorge,
I still don't agree that the procedures on Leaf-5 are already in
draft-ietf-bess-evpn-prefix-advertisement-11.
Note that the key of RT1 route is , not just .
Take the DGW1 of the Bump-in-the-wire use case for example,
If the DGW1 receives a RT-5 route R5 (IPL=24,
