Dear authors of draft-wang-bess-evpn-context-label-04, Section 2 "Problem Statement" of draft-wang-bess-evpn-context-label-04 states that " MPLS EVPN can't support hub/spoke use case, where the spoke PEs can only connect to each other through the hub PE. Especially when at least two of the spoke PEs are connected to a common route reflector".
I have to admit that I do not understand why support of the generic E-Tree functionality in EVPN defined in RFC 8317<https://tools.ietf.org/html/rfc8317> is not sufficient for handling this use case. In particular I do not see why connection of Spoke PEs to a common RR affects the EVPN behavior (or L3vPN Hub-and-Spoke VPN behavior as defined in Section 4.3.5 of RFC 4364<https://tools.ietf.org/html/rfc4364#section-4.3.5>) in any way. Regards, and lots of thanks in advance, Sasha Office: +972-39266302 Cell: +972-549266302 Email: [email protected] ----------------------------------------------------------------------------------------------------------------------- Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. 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 [email protected] https://www.ietf.org/mailman/listinfo/bess
