traffic direction to the represented entity or ethdev port itself
in DPDK 21.11.
+* ethdev: Flow API documentation is unclear if ethdev port used to create
+ a flow rule adds any implicit match criteria in the case of transfer rules.
+ The semantics will be clarified in DPDK 21.11 and it will require fixes in
+ drivers and applications which interpret it in a different way.
+
* ethdev: The flow API matching pattern structures, ``struct rte_flow_item_*``,
should start with relevant protocol header.
Some matching pattern structures implements this by duplicating protocol header
data length so that driver/HW can write expanded size data after encryption.
This change is targeted for DPDK 21.11.
+* cryptodev: Hide structures ``rte_cryptodev_sym_session`` and
+ ``rte_cryptodev_asym_session`` to remove unnecessary indirection between
+ session and the private data of session. An opaque pointer can be exposed
+ directly to application which can be attached to the ``rte_crypto_op``.
+
* cryptodev: The interface between library and drivers will be marked
as internal in DPDK 21.11.
SA lifetime configuration. A new structure would be introduced to replace the
current member, ``esn_soft_limit``.
+* security: The structure ``rte_security_ipsec_xform`` will be extended with
+ multiple fields: source and destination port of UDP encapsulation,
+ IPsec payload MSS (Maximum Segment Size), and ESN (Extended Sequence Number).
+
* security: The IPsec SA config options ``struct rte_security_ipsec_sa_options``
will be updated with new fields to support new features like IPsec inner
checksum, tunnel header verification, TSO in case of protocol offload.
+* ipsec: The structure ``rte_ipsec_sa_prm`` will be extended with a new field
+ ``hdr_l3_len`` to configure tunnel L3 header length.
+
* eventdev: The file ``rte_eventdev_pmd.h`` will be renamed to ``eventdev_driver.h``
to make the driver interface as internal and the structures ``rte_eventdev_data``,
``rte_eventdev`` and ``rte_eventdevs`` will be moved to a new file named