Summary: Has enough positions to pass.
I prefer the comments about Geneve being left in the draft. The other 2 encapsulations are ISE. Geneve will be the Standards Track encapsulation - so I find the framing useful.
Both the Abstract and Introduction contain text like this: This specification is also applicable to GENEVE encapsulation; however, some incremental work is required which will be covered in a separate document. and the Introduction references draft-boutros-bess-evpn-geneve-00.txt, which looks like an individual -00 draft. I wonder if it would be better to drop the promise from this document, and make the relationship clear in whatever version of draft-boutros-bess-evpn-geneve is published. I'm fine with the working group publishing this draft with the promise included, but wanted to ask while we're reviewing it, rather than later.
Please expand the following acronyms upon first use; see https://www.rfc-editor.org/materials/abbrev.expansion.txt for guidance. - VXLAN - NVGRE - POD - GRE - Generic Routing Encapsulation - GENEVE - NV - ARP - Address Resolution Protocol - RR - Resource Record - ECMP - Equal-Cost Multipath - PIM-SM - Protocol Independent Multicast - PIM-SSM - BIDIR-PIM - IP-VRF - LSP - Label Switched Path - iBGP Also, please be consistent about capitalization of "ToR" versus "TOR", "VxLAN" versus "VXLAN", and "NvGRE" versus "NVGRE".