From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: 2.3 Roadmap Date: Tue, 1 Dec 2015 08:44:57 -0500 Message-ID: <20151201134457.GB21396@mhcomputing.net> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA674705F1@IRSMSX108.ger.corp.intel.com> <20151201125935.GA20658@mhcomputing.net> <26FA93C7ED1EAA44AB77D62FBE1D27BA67470C36@IRSMSX108.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" To: "O'Driscoll, Tim" Return-path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id 092648D95 for ; Tue, 1 Dec 2015 14:45:00 +0100 (CET) Content-Disposition: inline In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA67470C36@IRSMSX108.ger.corp.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Dec 01, 2015 at 01:16:47PM +0000, O'Driscoll, Tim wrote: > True. The goal is to merge the best of the various patches that were > submitted on this. This could involve changes to IPv6 as well as IPv4. > > > Tim If it's possible to fix IPv6 as well this would be good for me. Offering a large nexthop space on all protocols is very good for BGP / core routing and security inspection applications. Using this feature, I will be able to detect interactions with bad subnets and IPs at tremendous speed compared to competing solutions. Matthew.