[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130426.194405.764067901709113311.davem@davemloft.net>
Date: Fri, 26 Apr 2013 19:44:05 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: stephen@...workplumber.org
Cc: netdev@...r.kernel.org, kduda@...stanetworks.com,
chrisw@...s-sol.org
Subject: Re: [PATCH net] vxlan: use IANA assigned port
From: Stephen Hemminger <stephen@...workplumber.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@...workplumber.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?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists