Hi Thomas, Please see my reply inline.
On 12/5/17, 6:25 AM, "BESS on behalf of [email protected]" <[email protected] on behalf of [email protected]> wrote: All, Martin Vigoureux, 2017-12-05 11:34: Perhaps draft-ietf-bess-evpn-overlay could hint on such a Geneve work for EVPN; something like: "Adapting the EVPN control plane to the Geneve encapsulation is out of the scope of this document, and is expected to be covered in a separate document based on the same architectural principles" I will add the following sentence to the abstract. “This specification is also applicable to other NVO encapsulations such as GENEVE, GPE, and GUE; however, these encapsulations may require additional incremental work and thus will be specified in separate document(s).” (Related to this sentence, but not related to your question:) I recently realized that I'm unclear on this point: the way the MPLS label fields are decoded is not the same for a VXLAN or NVGRE encap (where the whole 3 bytes are used) than for an MPLS encap (where only the topmost 20 bits of the 3 bytes are used). This means that, although the encoding is unambiguous when one encap is used (or when VXLAN and NVGRE would be used at the same time), it becomes ambiguous when a mix is used, for instance MPLS and VXLAN, unless the dataplane MPLS label to use is equal to the VNI after a 4-bit left shifting. If I'm not wrong "...routes MAY be advertised with multiple encapsulation types" needs to be restricted to the cases that work. I added the following paragraph to section 6 for clarification: “When a PE advertises multiple supported encapsulations, it MUST advertise encapsulations that use the same EVPN procedures including procedures associated with split-horizon filtering described in section 8.3.1. For example, VxLAN and NvGRE (or MPLS and MPLS over GRE) encapsulations use the same EVPN procedures and thus a PE can advertise both of them and can support either of them or both of them simultaneously. However, a PE MUST NOT advertise VxLAN and MPLS encapsulations together because a) MPLS field of EVPN routes is set to either a MPLS label for a VNI but not both and b) some of EVPN procedures (such as split-horizon filtering) are different for VxLAN/NvGRE and MPLS encapsulations.” Cheers, Ali _______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
