From: Chris Wright <chrisw@sous-sol.org>
To: David Miller <davem@davemloft.net>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
kduda@aristanetworks.com, chrisw@sous-sol.org
Subject: Re: [PATCH net] vxlan: use IANA assigned port
Date: Fri, 26 Apr 2013 18:51:29 -0700 [thread overview]
Message-ID: <20130427015129.GJ8882@sequoia.sous-sol.org> (raw)
In-Reply-To: <20130426.194405.764067901709113311.davem@davemloft.net>
* David Miller (davem@davemloft.net) wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Fri, 26 Apr 2013 16:33:46 -0700
>
> > Ken Duda of Arista Networks, one of the VXLAN RFC authors notified
> > me that IANA has assigned an official port for VXLAN. My initial version
> > of the driver used the value from CISCO LISP that was also being used by
> > OpenVswitch.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> So how does this interact with already deployed VXLAN links?
>
> What is the backwards compatability story? What if one node upgrades
> with this patch installed, but all the other nodes are left using
> the older port number by default?
With this patch, I think one node upgrading would need to override
the default vxlan_port module param (falling back to the pre IANA
default) to keep active with the existing overlays.
next prev parent reply other threads:[~2013-04-27 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 23:33 [PATCH net] vxlan: use IANA assigned port Stephen Hemminger
2013-04-26 23:44 ` David Miller
2013-04-27 1:51 ` Chris Wright [this message]
2013-04-27 3:22 ` David Miller
[not found] ` <CAOaVG14yv=TixikAkrjEOTBznoC6YDqm1vb4ByZ32bgXM3Q7xQ@mail.gmail.com>
2013-04-27 7:43 ` David Miller
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=20130427015129.GJ8882@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=davem@davemloft.net \
--cc=kduda@aristanetworks.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.