Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IOAM VXLAN GPE: Conversion to/from VXLAN (without GPE) #130

Open
mickeyspiegel opened this issue May 7, 2019 · 0 comments
Open

IOAM VXLAN GPE: Conversion to/from VXLAN (without GPE) #130

mickeyspiegel opened this issue May 7, 2019 · 0 comments

Comments

@mickeyspiegel
Copy link
Collaborator

In many potential VXLAN deployment scenarios, IOAM domain boundaries might not align with VTEP locations. At the IOAM encapsulating node, a packet might be received from outside of the IOAM domain, that already has a VXLAN or VXLAN-GPE encapsulation.

Given current deployment trends, it is much more likely that such a packet has a VXLAN (without GPE) encapsulation. Rather than throwing on multiple layers of VXLAN / VXLAN-GPE encasulations, it would be much more efficient for the IOAM encapsulating node to convert the existing VXLAN encapsulation to a VXLAN-GPE encapsulation.

Such an approach leads to an issue at the IOAM decapsulating node:
How can the IOAM decapsulating node determine whether to leave the VXLAN-GPE encapsulation as is, or to convert the VXLAN-GPE encapsulation back to VXLAN?

Should a bit be defined in the "reserved" part of the VXLAN header that indicates whether the original encapsulation was VXLAN or VXLAN-GPE?
This would allow the IOAM decapsulating node to determine whether it needs to convert back to a VXLAN (without GPE) encapsulation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant