I would change the introduction to the following to mention the use of VXLAN by BGP EVPN.
Thanks, Anoop == "Virtual eXtensible Local Area Network" (VXLAN) [RFC7348] provides an encapsulation scheme that allows building an overlay network by decoupling the address space of the attached virtual hosts from that of the network. One use of VXLAN is in data centers interconnecting VMs of a tenant. VXLAN addresses requirements of the Layer 2 and Layer 3 data center network infrastructure in the presence of VMs in a multi-tenant environment, discussed in section 3 of [RFC7348], by providing Layer 2 overlay scheme on a Layer 3 network. Another use is as an encapsulation for EVPN [RFC 8365]. In the remainder of this document the terms VM and End Station are used interchangeably. In the absence of a router in the overlay, a VM can communicate with another VM only if they are on the same VXLAN segment. VMs are unaware of VXLAN tunnels as a VXLAN tunnel is terminated on a VXLAN Tunnel End Point (VTEP) (hypervisor/TOR). VTEPs (hypervisor/TOR) are responsible for encapsulating and decapsulating frames exchanged among VMs. On Wed, Dec 12, 2018 at 6:02 AM Jeffrey Haas <jh...@pfrc.org> wrote: > > BESS Working Group members, > > https://tools.ietf.org/html/draft-ietf-bfd-vxlan-04 > > BFD has finished working group last call on BFD for Vxlan and is about ready > to request publication as an RFC. A last minute comment suggested that we > should consider inviting comment from your working group for expertise. > > We will be leaving the last call open until December 21 to leave time for > final comments. > > -- Jeff (for BFD) > > _______________________________________________ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess _______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
