Dear draft-ietf-bess-evpn-modes-interop co-authors, Your help with the following clarification will be most appreciated.
On the introduction section of this draft you introduce three major cases of interoperability between EVPN modes, the motivation of which is not clear enough. Some may say that these situations are the result of a broken configuration across the network. Some use cases may even force limitations on the EVPN modes implementation. E.g. In the case of VLAN aware service interface type interoperability with VLAN based interface type; being able to use a Zero tag on VLAN aware implies that there shall be only single BD in the related VLAN aware EVI, in which case why would an operator use a VLAN aware service interface type to begin with? (A VLAN based would be the right configuration) Could you please clarify/elaborate on the motivations for all three interoperability use cases? Looking forward to getting your feedback, Nitsan Dolev Ribbon Communications Disclaimer This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
