G-NVGRE Header Protocol Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network virtualization technologies, specifically Generic Routing Encapsulation (GRE) and Network Virtualization Generic Routing Encapsulation (NVGRE), are limited in their ability to support the transport of multiple protocols beyond Ethernet, requiring manual configuration or out-of-band mechanisms to identify payload types, which can be cumbersome and inefficient.
Innovation Solution
The implementation of Generic NVGRE (G-NVGRE) headers, such as G-NVGRE-1 and G-NVGRE-2, which encode protocol information within the Ethertype field, allowing for the transparent transport of various protocols over NVGRE networks without explicit payload type indication, enabling support for non-standard and standard protocols alike.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual configuration or out-of-band mechanisms are used to identify payload types in NVGRE networks, then protocol transport capability is improved, but system complexity and operational overhead increase
Solution Approach 1:
The NVGRE header automatically identifies payload types using the Ethertype field without requiring external configuration mechanisms. The system serves itself by embedding protocol identification information directly in the packet header, eliminating the need for manual configuration or out-of-band negotiations.
Solution Approach 2:
The Ethertype field is pre-configured in the NVGRE header structure to carry protocol identification information. This preliminary design of the header format enables automatic protocol identification before packets are processed, avoiding the need for runtime configuration or negotiation.
2Productivity
If protocol information is encoded within the NVGRE header, then operational efficiency is improved, but header structure complexity increases
Solution Approach 1:
The Ethertype field in the NVGRE header serves multiple functions: it identifies the payload protocol type, enables automatic routing decisions, and supports both standard and non-standard protocols. This multi-functionality improves operational efficiency without requiring separate identification mechanisms.
Solution Approach 2:
The NVGRE header uses the Ethertype parameter to encode protocol identification information. By changing the value of this existing parameter field, the system can identify different protocol types without adding new header fields or increasing overall header structure complexity.
3Adaptability or versatility
If NVGRE supports multiple protocols beyond Ethernet, then protocol versatility is improved, but compatibility with existing NVGRE implementations may be compromised
Solution Approach 1:
The protocol identification function is segmented into the Ethertype field within the NVGRE header, separating it from the rest of the header structure. This segmentation allows existing NVGRE processing logic to remain unchanged while adding multi-protocol support through the Ethertype field value interpretation.
Solution Approach 2:
The Ethertype field acts as an intermediary between the NVGRE header and the payload protocol. It provides a standardized interface for protocol identification that maintains compatibility with existing Ethernet-based NVGRE implementations while enabling support for non-Ethernet protocols through extended Ethertype value interpretation.
Data Source
AI summary
Various example embodiments for supporting transport of various protocols over network virtualization technology are presented herein. Various example embodiments for supporting transport of various protocols over network virtualization technology may be configured to support transport of various protocols over network virtualization generic routing encapsulation. Various example embodiments for supporting transport of various protocols over network virtualization technology may be configured to support communication of a packet including a payload and a header of a network virtualization generic routing encapsulation protocol, wherein the payload is based on a protocol other than Ethernet. Various example embodiments for supporting transport of various protocols over network virtualization technology may be configured to support communication of a packet including a payload and a header of a network virtualization generic routing encapsulation protocol, wherein the payload is based on a protocol at a communication layer above a data link layer.