From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <borisp@mellanox.com> Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0067.outbound.protection.outlook.com [104.47.2.67]) by dpdk.org (Postfix) with ESMTP id 30AE37CAB; Mon, 21 Aug 2017 12:32:29 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=JSI78jb80DnfW2oQARn0ETpbrh62a5TzpMNGl5yBrnM=; b=nClTu+sPlOh4wYErHOk6YvoJKERvXBHu6WTqgtWKGXGb9/JS+dT3coxJqpM6MFNf8BA15QX/GGdlPnrsn27ll7jRy8RP+5htrYXG2bLwJnmzeM9kbfH9+Pto59BbkJajCnDm55DXhyaIZzU2/I3H8ym9K35zkYgomsGJRVssyKk= Received: from DB6PR05MB3176.eurprd05.prod.outlook.com (10.170.221.26) by DB6PR05MB3431.eurprd05.prod.outlook.com (10.170.223.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1362.18; Mon, 21 Aug 2017 10:32:28 +0000 Received: from DB6PR05MB3176.eurprd05.prod.outlook.com ([fe80::d90a:78d2:8971:64e1]) by DB6PR05MB3176.eurprd05.prod.outlook.com ([fe80::d90a:78d2:8971:64e1%13]) with mapi id 15.01.1362.019; Mon, 21 Aug 2017 10:32:28 +0000 From: Boris Pismenny <borisp@mellanox.com> To: Thomas Monjalon <thomas@monjalon.net>, Hemant Agrawal <hemant.agrawal@nxp.com> CC: Akhil Goyal <akhil.goyal@nxp.com>, Radu Nicolau <radu.nicolau@intel.com>, "dev@dpdk.org" <dev@dpdk.org>, "declan.doherty@intel.com" <declan.doherty@intel.com>, Aviad Yehezkel <aviadye@mellanox.com>, "pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>, "sergio.gonzalez.monroy@intel.com" <sergio.gonzalez.monroy@intel.com>, Sandeep Malik <sandeep.malik@nxp.com>, "techboard@dpdk.org" <techboard@dpdk.org> Thread-Topic: [RFC PATCH 1/4] rte_security: API definitions Thread-Index: AQHTFbZOg4lklAP1L0+CqzV5F3ZF9KKFQW+AgAFZGwCAAIW7UIACubOAgATLJbA= Date: Mon, 21 Aug 2017 10:32:28 +0000 Message-ID: <DB6PR05MB31761B2629068C2B458D4988B0870@DB6PR05MB3176.eurprd05.prod.outlook.com> References: <20170725112153.29699-1-akhil.goyal@nxp.com> <4cee6900-f886-6997-6911-6c9ca1735e65@nxp.com> <AM2PR04MB075365F0374B7F006106BB1489820@AM2PR04MB0753.eurprd04.prod.outlook.com> <4861108.dgZJ5lNHcd@xps> In-Reply-To: <4861108.dgZJ5lNHcd@xps> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=borisp@mellanox.com; x-originating-ip: [193.47.165.251] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; DB6PR05MB3431; 6:Nm1ZppI8kQmqFLJcXmkHIkHxhVHOZv8LddplPcIomZMZNQZa5Xo32oJ10aOBqY+RfJvfUVze+dfm4lhAh+M0ytltiL74dvu9jzp2MupuAfSnhln36tBcs4Mr+ON1tO0aJRBMzfqiU2wQkyKyTmM42X+/z3fIzajwGPZv5eZjTOm6sRMPXnoTrfIoA8qlCUURAxkx0jG1okWRI2P0C1/E0hgx3DBL2xD8Vavb5dkYbpcxlUxpsBunnLEx3q+yv5V0AaUEI2VPqnAHgIicNA7ecBcHxaAS7XYna0BvW+hb6uxsromlDTqbJvXOZTrvfXSeM6KRHfMiP8uSbyPE6lRD1Q==; 5:HGOKccUNfarM80WnAu55p2KSqeGayqLmrmWSbNPqZeO5Jx6Jy6qx5TfuDAsQiXgte6W2/o5vih/vxMZoWkdp/8y2ZrmEBha/Ny3TX/8hlNXbXBq8+xPcE4CL18SWcHwb9gw6kSLug0YZUcRGXkoXyQ==; 24:d7lwt2p55KIkempoJAq9SI5CXj9YRieY1kysouf4RzKgmM5Uxtw8Mooou04N4qmXhoK5FNbh8oIOpCk1RE029DE/mnVRk9NSrF813pSzGaI=; 7:NOgmL3tZCPKicFdoUwwAKNk/PB2uzSDS7J4J8njDAZzGL+Rb4JtS/3iGnq9tsTVO5kN49C33tdfSHTuWT9+5q9Xcpl095IkDo3Ssifg3qpbTHMGP2+FE87slSTyobFfY7I4hm2xLQDPmrVCbwqduwZBdDXEBZrZR/Bmi5zwyWGHIy2yxB9vptEHQWC0Mwig5HQf0LdT0M0OeVh4rjazo7W3CDFygNaxZcglXFgMMbOA= x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ld-processed: a652971c-7d2e-4d9b-a6a4-d149256f461b,ExtAddr x-ms-office365-filtering-correlation-id: 955f5e0c-4f01-42cd-44ae-08d4e87febdf x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(48565401081)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DB6PR05MB3431; x-ms-traffictypediagnostic: DB6PR05MB3431: x-exchange-antispam-report-test: UriScan:(166708455590820)(185117386973197)(228905959029699); x-microsoft-antispam-prvs: <DB6PR05MB34311A08386D97FA2E26838DB0870@DB6PR05MB3431.eurprd05.prod.outlook.com> x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123555025)(20161123560025)(20161123558100)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB6PR05MB3431; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB6PR05MB3431; x-forefront-prvs: 040655413E x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39860400002)(189002)(199003)(13464003)(54356999)(76176999)(966005)(66066001)(50986999)(3280700002)(229853002)(54906002)(14454004)(6116002)(3846002)(6306002)(102836003)(99286003)(4326008)(93886005)(9686003)(106356001)(97736004)(105586002)(53936002)(3660700001)(53546010)(189998001)(2906002)(5660300001)(561944003)(25786009)(8656003)(68736007)(81156014)(8676002)(86362001)(81166006)(33656002)(7416002)(7736002)(478600001)(305945005)(55016002)(7696004)(6506006)(6246003)(101416001)(2950100002)(5250100002)(6436002)(8936002)(74316002)(2900100001)(217873001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB6PR05MB3431; H:DB6PR05MB3176.eurprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: Mellanox.com X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Aug 2017 10:32:28.1069 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR05MB3431 Subject: Re: [dpdk-dev] [RFC PATCH 1/4] rte_security: API definitions X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Mon, 21 Aug 2017 10:32:29 -0000 For drafting, we have opened this github repository: https://github.com/Mellanox/dpdk-next-crypto Akhil/Hemant could you please push your rte_security patches there? > -----Original Message----- > From: Thomas Monjalon [mailto:thomas@monjalon.net] > Sent: Friday, August 18, 2017 12:17 > To: Hemant Agrawal <hemant.agrawal@nxp.com> > Cc: Akhil Goyal <akhil.goyal@nxp.com>; Radu Nicolau > <radu.nicolau@intel.com>; dev@dpdk.org; declan.doherty@intel.com; Aviad > Yehezkel <aviadye@mellanox.com>; Boris Pismenny <borisp@mellanox.com>; > pablo.de.lara.guarch@intel.com; sergio.gonzalez.monroy@intel.com; Sandeep > Malik <sandeep.malik@nxp.com>; techboard@dpdk.org > Subject: Re: [RFC PATCH 1/4] rte_security: API definitions >=20 > Hi, >=20 > 16/08/2017 17:40, Hemant Agrawal: > > Hi Thomas, > > Can we get a next-security tree to do development around this > proposal? > > > > Also, we can discuss about this proposal in general in next techboard m= eeting. >=20 > First question to ask: > Why not create a repository elsewhere for your trials? >=20 > The benefit of creating a dpdk.org repo is to show it as an official feat= ure. > So the idea behind this new library must be accepted by the technical boa= rd > first. >=20 > The other use of official repos is prepare pull request for subsequent re= leases. > Do we want to have a -next tree for IPsec development and keep it for nex= t > releases? >=20 > I think it makes sense to have a -next tree for IPsec offloading in gener= al. > Before the techboard approves it, we need to define the name (and the sco= pe) > of the tree, and who will be the maintainer of the tree.