I only have a very limited understanding of VXLAN ands BFD technology. Hence, some of my question may look odd to the insiders. - RFC 7348 defining VXLAN is informational, why would BFD for VXLAN be standards track? - Section 2.1 "Terminology" expands acronyms but it does say where these "terms" are actually defined. Some pointers to the relevant RFCs may be useful. - Section 3 starts talking about VNI numbers but acronym VNI has not been introduced before. I assume VNI = VXLAN Network Identifier. - I am not familiar with VXLAN but I wonder how the endpoints addresses are obtained in practice. This BFD document says for example "The details of how the MAC address of the destination VTEP is obtained are outside the scope of this document." Well, OK, but how does this work? Is there a document where this is explained? Well, I am actually less concerned about how the inner address is obtained, I think I am more urgently missing how the VTEP determines the remote tunnel endpoint address. - Why do you need a special MAC address? The text says I can use this address or the address of the destination VTEP but there is no reasoning when to use what or why a dedicated address is needed. - What is a 'reasonable upper bound' on the number of BFD sessions that can be created between the same pair of VTEPs? 1? 2? 8? 64? 256? 4096? How does the choice of this upper bound impact security? - Which BFD mode is assumed to be used, asynchronous or demand? Or does this not matter for this usage of BFD, i.e., both work just fine and will be interoperable? - Why is echo BFD outside the scope of this document? Can I just turn on echo mode or will extra specifications be needed?