From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id A1445A3 for ; Mon, 28 Jan 2019 16:34:12 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Jan 2019 07:34:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,534,1539673200"; d="scan'208";a="133788406" Received: from irsmsx110.ger.corp.intel.com ([163.33.3.25]) by orsmga001.jf.intel.com with ESMTP; 28 Jan 2019 07:34:10 -0800 Received: from irsmsx155.ger.corp.intel.com (163.33.192.3) by irsmsx110.ger.corp.intel.com (163.33.3.25) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 28 Jan 2019 15:34:09 +0000 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.116]) by irsmsx155.ger.corp.intel.com ([169.254.14.157]) with mapi id 14.03.0415.000; Mon, 28 Jan 2019 15:34:09 +0000 From: "Ananyev, Konstantin" To: "dev@dpdk.org" CC: "'akhil.goyal@nxp.com'" , "'borisp@mellanox.com'" , "'aviadye@mellanox.com'" , "Nicolau, Radu" , "Doherty, Declan" , "Kovacevic, Marko" Thread-Topic: some question about rte_security_ipsec_sa_options Thread-Index: AdS3Gw1BqpNo+R3RQmS//rL2GRXJiA== Date: Mon, 28 Jan 2019 15:34:07 +0000 Message-ID: <2601191342CEEE43887BDE71AB977258010D9084DD@irsmsx105.ger.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMzE0NzNmODYtNzhiZS00YTI0LTljMWYtNDIxY2RkMTkwM2ZkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTm5PQ1UxN0N5ejNFVTV1eitmbmdqU0F5eTRNZlhPSG9TeHNrMENNcUcwUUM5VWdYMTI4UEwwMGJETm52VFU0WiJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [dpdk-dev] some question about rte_security_ipsec_sa_options X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 15:34:13 -0000 Hi everyone, For 19.05 we plan to extend librte_ipsec with proper support of construction/updating inner/outer ipv4/ipv6 fields as described in https://tools.ietf.org/html/rfc4301#section-5.1.2. So few questions regarding struct rte_security_ipsec_sa_options fields. 1. dec_ttl - as I can see there is no PMD that supports this option right now. I wonder are there any plans to add support for it? If yes, what is expected HW/PMD behavior when TTL reaches zero? Would the packet will be silently dropped by HW/PMD, or would some sort of error returned to the user (via mbuf->ol_flags)? From SW point of view - it probably much easier/cleaner to remove that option and let upper layer to decrement TTL if needed (as it is inner IP header only). 2. It seems there is no fields to configure ECN construction/update settings. Hopefully there would be no generic objections to add some new field(s) here for ECN? Thanks Konstantin =20 =20