From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Benc Subject: Re: [PATCH net-next v2] openvswitch: enable NSH support Date: Mon, 14 Aug 2017 12:47:42 +0200 Message-ID: <20170814124742.7c04b72c@griffin> References: <1502371275-52446-1-git-send-email-yi.y.yang@intel.com> <20170811102418.6b1be4f7@griffin> <20170811084722.GA19968@cran64.bj.intel.com> <20170811111055.482bd42b@griffin> <79BBBFE6CB6C9B488C1A45ACD284F51961C427FE@SHSMSX103.ccr.corp.intel.com> <20170811114449.745c49c5@griffin> <20170811122256.2cec123e@griffin> <20170814095117.056fdf96@griffin> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: "netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org" To: Jan Scheurich Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ovs-dev-bounces-yBygre7rU0TnMu66kgdUjQ@public.gmane.org Errors-To: ovs-dev-bounces-yBygre7rU0TnMu66kgdUjQ@public.gmane.org List-Id: netdev.vger.kernel.org On Mon, 14 Aug 2017 10:35:42 +0000, Jan Scheurich wrote: > Is it worth to speculate on how a hypothetical future NSH version > (with a different Version value in the Base header) might look like? Absolutely. This is uAPI we're talking about and once merged, it's set in stone. Whatever we come up with should allow future extensibility. > If this should ever arise, we could introduce a new push_nsh_v2 > action. Which would mean we failed with the design. We would have to maintain two parallel APIs forever. This is not how the design should be made. Jiri