From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 5196D8DAA for ; Tue, 1 Dec 2015 12:57:31 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP; 01 Dec 2015 03:57:30 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,368,1444719600"; d="scan'208";a="851352503" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by fmsmga001.fm.intel.com with ESMTP; 01 Dec 2015 03:57:29 -0800 Received: from irsmsx155.ger.corp.intel.com (163.33.192.3) by IRSMSX108.ger.corp.intel.com (163.33.3.3) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 1 Dec 2015 11:57:27 +0000 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.23]) by irsmsx155.ger.corp.intel.com ([169.254.14.190]) with mapi id 14.03.0248.002; Tue, 1 Dec 2015 11:57:27 +0000 From: "O'Driscoll, Tim" To: Dave Neary , "dev@dpdk.org" Thread-Topic: [dpdk-dev] 2.3 Roadmap Thread-Index: AdErsIjfg5kVwCCOTr635FzIeMmmbwADJpWAABxtfGA= Date: Tue, 1 Dec 2015 11:57:26 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA67470B5E@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA674705F1@IRSMSX108.ger.corp.intel.com> <565CCB5F.8030700@redhat.com> In-Reply-To: <565CCB5F.8030700@redhat.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-inteldataclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsIiwiaWQiOiJkY2I5Nzc5Yi1iZWIxLTQ3YmMtOTZjZC0yMmZkNGE1ODQ5YzQiLCJwcm9wcyI6W3sibiI6IkludGVsRGF0YUNsYXNzaWZpY2F0aW9uIiwidmFscyI6W3sidmFsdWUiOiJDVFBfSUMifV19XX0sIlN1YmplY3RMYWJlbHMiOltdLCJUTUNWZXJzaW9uIjoiMTUuNC4xMC4xOSIsIlRydXN0ZWRMYWJlbEhhc2giOiJ0VlJNXC9iMDUrdE1mbm90VXZKODlTQ1hIb0RJcHNwMWNvcFJGMnhlMkdVZz0ifQ== x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] 2.3 Roadmap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2015 11:57:31 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Dave Neary > Sent: Monday, November 30, 2015 10:19 PM > To: O'Driscoll, Tim; dev@dpdk.org > Subject: Re: [dpdk-dev] 2.3 Roadmap >=20 > Hi Tim, >=20 > Just curious about one item on the list: >=20 > On 11/30/2015 03:50 PM, O'Driscoll, Tim wrote: > > IPsec Sample Application: A sample application will be created which > will show how DPDK and the new cryptodev API can be used to implement > IPsec. Use of the cryptodev API will allow either hardware or software > encryption to be used. IKE will not be implemented so the SA/SP DBs will > be statically configured. >=20 > Do you anticipate this application living in the dpdk repo, or in a > separate tree? Good question. As a sample application showing how DPDK can be used to impl= ement IPsec, I believe it belongs within the DPDK repo. When we have an Architecture Board in place, I think one of the first tasks= for the board should be to clarify the scope of DPDK. Venky agreed at the = Userspace event to draft an initial statement on this. If the outcome of th= at is that the IPsec sample app doesn't belong within DPDK, then we can put= it into a separate tree. Tim >=20 > Thanks, > Dave. >=20 > -- > Dave Neary - NFV/SDN Community Strategy > Open Source and Standards, Red Hat - http://community.redhat.com > Ph: +1-978-399-2182 / Cell: +1-978-799-3338