SDxCentral
Join Log In
SD-WAN 5G Edge 1 IoT SDN NFV Containers Cloud Security AI Data Center Storage APM/NPM Open Source

Log In to SDxCentral

Log in with your email? Forgot your password?
  • Newsletters
  • eBriefs
  • Podcasts
  • Webinars
  • Videos
  • Directory
  • White Papers
  • Resources
  • Use Cases
  • Support

Join SDxCentral and get information tailored to your particular interests everyday.

Join
Sponsored:
Dell EMC Citrix Riverbed

‘Valentine’s Day Draft’ Seeks a Virtual Network Group Hug

Valentines Day Draft Virtual Group
Craig Matsumoto
Craig MatsumotoFebruary 15, 2014
11:53 am MT
Email LinkedIn Facebook Twitter Reddit Hacker News

We’ve heard a couple of times that it’s pointless for VXLAN and NVGRE to stay at odds. Both are encapsulation frameworks for virtualized networks; they do pretty much the same thing but happen to have different corporate backers. We’ve even written that NVGRE maybe ought to concede.

Peace might now be at hand. A superset of both protocols, called Generic Network Virtualization Encapsulation (Geneve), got submitted to the IETF in a draft published Feb. 14, just at the IETF’s 4:00 p.m. deadline.

You could call it the Valentine’s Day Draft. (Martin Casado, chief scientist of VMware, did.)

“This’ll be a big deal once people figure out what’s happening,” Casado says. “It had to happen. You don’t want to have a bifurcation in the market.”

Casado and others found it grating that VXLAN, NVGRE, STT, and possibly other protocols are all lingering around. They all create Layer 3 tunnels between virtual machines (a key bit of infrastructure for a virtualized network), and they’re similar to the point that they’ve even got common authors. Starting at Interop in spring 2013, representatives of the companies behind those standards started working to find some common ground.

The Geneve draft was written by representatives of VMware, Microsoft, Red Hat, and Intel. (That’s the order in which they’re listed. Casado is not an author, but he’s one of the folks thanked in the draft for providing consultation.) VMware has been arguably the biggest VXLAN proponent, while Microsoft is usually held up as the biggest NVGRE backer, so there does seem to be a joining of paths here.

It’s a promising development, but there’s a catch: It appears that switch chips, such as the Trident series from Broadcom, will have to be updated to accommodate Geneve.

Unity on the Data Plane

Geneve is described not as a compromise or love letter, but as a superset of VXLAN, NVGRE, and STT. The core idea is that these data-plane protocols are “only superficially different” and might as well be unified to avoid duplicated effort.

Control planes, on the other hand, can and should be vastly different and will be continually changing, the draft states. To avoid obsolescence in the event of future control-plane innovations, the Geneve draft says it’s “providing a framework for tunneling rather than being prescriptive about the entire system.” Moreover, “it should be straightforward to port an existing control plane to run on top of [Geneve] with minimal effort,” according to the draft.

Casado says we should view VXLAN, NVGRE, and STT as the first go-around for tunneling protocols. They gave VLANs Layer 3 powers, but they did not account for more “rich” virtual-network functionality that developed later, such as service chaining. “This allows one framework that will evolve in the future,” he says.

Geneve has a mechanism for supporting extensions and multiple versions, giving the protocol room to grow. It also adds a way to recognize system state, conveyed through metadata.

What About Broadcom?

Geneve could run on an x86 chip today, and some current network interface cards (NICs) will be able to support it via software upgrades. But Ethernet switch chips will need modifications to support it.

The industry just got done waiting for Broadcom to directly support VXLAN and NVGRE, a feature that’s supported in the company’s new Trident II chips. Assuming Geneve gains favor, there could be a similar wait as the next generation of chip designs gets completed. (Because the story broke Friday evening, we haven’t yet polled chip vendors on whether they’ve already started this work.)

On the plus side, Geneve’s future-proofed design could mean this is the last tunneling protocol the chips need to accommodate for a while.

Hardware issues aside, Casado is head-over-heels for Geneve. “I think a lot of protocol development gets dictated by ASIC design,” where a feature already baked into someone’s proprietary hardware gets proposed as a standard, he said. (Cisco gets accused of this a lot.)

By contrast, Geneve was crafted from the software side by a group that stuck to a unified goal, to hear Casado tell it. “When you have two of the most successful software companies on the planet doing this, you know change is afoot.”

Related Articles

Security Unicorn Illumio Raises $65M, Hires Its First CFO
Security Unicorn Illumio Raises $65M, Hires a New CFO
Cisco Pushes ACI to AWS and Azure, Embraces ‘Data Center Anywhere’ Strategy
Cisco Pushes ACI to AWS and Azure, Embraces ‘Data Center Anywhere’ Strategy
The-Top-Acquisitions-of-2018
The Top Acquisitions of 2018 in SDxCentral's World
SD-WAN-Will-Be-Fueled-By-Collaboration-Between-Cloud-Providers-and-Vendors
SD-WAN Will Be Fueled By Collaboration Between Cloud Providers and Vendors
VMware CEO Lists Top 3 Priorities for 2019: NSX, Cloud and Containers
VMware CEO Lists Top 3 Priorities for 2019: NSX, Cloud, and Containers
Kubernetes Discloses Major Security Flaw
Kubernetes Discloses Major Security Flaw
SDxCentral Daily News

Join your Peers! Subscribe to SDxCentral's Newsletter

Article Tags:

Breaking News Intel Microsoft Network Virtualization Red Hat SDxCentral VMware

Craig Matsumoto

About Craig Matsumoto

Craig Matsumoto is managing editor at SDxCentral.com, responsible for the site's content and for covering news. He is a "veteran" of the SDN scene, having started covering it way back in 2010, and his background in technology journalism goes back to 1994. Craig is based in Silicon Valley. He can be reached at craig@sdxcentral.com.

Subscribe to Get the Daily News!

About SDxCentral

  • Newsletters
  • About Us
  • Contact Us
  • Work With Us
  • Editorial Team
  • Careers
  • Legal
  • Support

Engage With us

This material may not be copied, reproduced, or modified in whole or in part for any purpose except with express written permission from an authorized representative of SDxCentral, LLC. In addition to such written permission to copy, reproduce, or modify this document in whole or part, an acknowledgement of the authors of the document and all applicable portions of the copyright notice must be clearly referenced. All Rights Reserved.

© 2012-2019 SDxCentral, LLC, All Rights Reserved. SDNCentral™, the SDNCentral logo, SDxCentral™, SDxCentral logo, SDxNews™, SDxTech™, SDx™, the SDx logo, and DemoFriday™ are trademarks of SDxCentral, LLC in the U.S. and other countries.

  • Terms of Service
  • Privacy