From: Jiri Benc <jbenc@redhat.com>
To: Tom Herbert <tom@herbertland.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Thomas Graf <tgraf@suug.ch>
Subject: Re: [RFC PATCH net] vxlan: fix incorrect RCO bit in VXLAN header
Date: Mon, 7 Dec 2015 11:48:30 +0100 [thread overview]
Message-ID: <20151207114830.78912df5@griffin> (raw)
In-Reply-To: <CALx6S34_MazNmhACWBnVYFzXT9qZPLy2CZK3BBhP8RJzoHYo4w@mail.gmail.com>
<On Fri, 4 Dec 2015 09:13:28 -0800, Tom Herbert wrote:
> That's awesome! One favor, can you make sure VXLAN-GPE works with IPv6
> from the start. :-)
Absolutely. I've not spent so much effort adding IPv6 counterparts to
various vxlan stuff to submit vxlan-gpe for IPv4 only :-)
> Also, I'll need to spin an I-D for RCO in VXLAN-GPE. Do you see any
> reason to use a different bit for it?
As for the flags, VXLAN-GBP, VXLAN-GPE and VXLAN-RCO are compatible
with each other. It's not possible to use GBP and GPE together because
the group policy id and the next protocol field are overlapping but
it's possible to distinguish whether it's GBP or GPE based on the
flags.
There should be no problem using GPE and RCO together (at least now,
when this patch is applied). It needs to be explicitly configured as
such when creating the interface, though.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2015-12-07 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 12:54 [RFC PATCH net] vxlan: fix incorrect RCO bit in VXLAN header Jiri Benc
2015-12-04 16:43 ` Tom Herbert
2015-12-04 17:06 ` Jiri Benc
2015-12-04 17:13 ` Tom Herbert
2015-12-07 10:48 ` Jiri Benc [this message]
2015-12-05 23:16 ` David Miller
2015-12-07 15:46 ` Thomas Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151207114830.78912df5@griffin \
--to=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=tom@herbertland.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).