DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "'akhil.goyal@nxp.com'" <akhil.goyal@nxp.com>,
	"'borisp@mellanox.com'" <borisp@mellanox.com>,
	"'aviadye@mellanox.com'" <aviadye@mellanox.com>,
	"Nicolau, Radu" <radu.nicolau@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>
Subject: [dpdk-dev] some question about rte_security_ipsec_sa_options
Date: Mon, 28 Jan 2019 15:34:07 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258010D9084DD@irsmsx105.ger.corp.intel.com> (raw)


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   
 

                 reply	other threads:[~2019-01-28 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2601191342CEEE43887BDE71AB977258010D9084DD@irsmsx105.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=marko.kovacevic@intel.com \
    --cc=radu.nicolau@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).