A few years back, the number of data center-oriented overlays the market saw got to be a bit humorous. There was VXLAN, NVGRE, and STT all targeted (mostly) at helping with network virtualization and scale inside the data center.
The funny part was how similar these overlays all seemed to be. Why not get behind one standard as an industry?
Then in February 2014, Geneve was announced. Some of us face-palmed. Another overlay? What could possibly be the point of another one? Well, there was — and is — a point.
Geneve, which is an IETF project, aims to take the best parts of STT, NVGRE, and VXLAN. And while you might assume VXLAN has won the overlay war, Geneve is seeing active development for some good reasons we’ll discuss today.
Several folks who are involved in Geneve were kind enough to give up some of their time for this conversation:
-Why was Geneve conceived in the first place? What was going on at the time?
-In the IETF project hierarchy, Geneve is grouped with NVO3. What is NVO3, and how does Geneve fit into that framework?
-Geneve wants to take the best parts of STT, NVGRE, and VXLAN. What are those parts, and why do they represent significant advantages?
-Geneve is extensible, which gives it a long-term market advantage. What do we mean by extensible here?
-What is the IETF status of Geneve as a standard?
-I thought VXLAN won. If that’s not the case, what market adoption are we seeing for Geneve?
- Hardware (silicon) vendors
- Software/NFV vendors
- Open source community projects
Will Geneve ultimately replace VXLAN, etc.? Or will it be just another overlay option?
Geneve – Russ White
Geneve, VXLAN, And Network Virtualization Encapsulation – Bruce Davie, VMware