From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: Nandini Persad <nandinipersad361@gmail.com>, dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v2] doc: add security document
Date: Tue, 19 Nov 2024 10:31:16 +0530 [thread overview]
Message-ID: <ea0b995f-f148-5ca3-20bb-60c7d2afc020@oss.nxp.com> (raw)
In-Reply-To: <20241118171325.10871-1-nandinipersad361@gmail.com>
Hi Nandini,
One minor comment..
- Hemant
On 18-11-2024 22:43, Nandini Persad wrote:
> This is a new document covering security protocols
> implemented in DPDK.
>
> +PDCP
> +~~~~
> +
> +Packet Data Convergence Protocol (PDCP) is a sublayer in the LTE radio protocol stack
> +that provides security and integrity protections to Protocol Data Units (PDU) in both
> +the control and data planes. PDCP is located between the Radio Link Control (RLC) layer
> +and the upper layers of the network, such as the IP layer.
> +
> +
> +**Wikipedia Link**
> + * https://en.wikipedia.org/wiki/Packet_Data_Convergence_Protocol
> +
> +**Standard Link**
> + * https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1177
> +
> +**Level of Support in DPDK**
> + * Supported. High-level library: :doc:`PDCP Library <../prog_guide/pdcp_lib>`
> + * rte_security based PDCP sessions are also supported
> +
> +**Supported Algorithms**
> + * Encryption algo - NULL, AES-CTR, SNOW, ZUC
> + * Authentication algo - NULL, AES-CMAC, SNOW, ZUC
> +
> +
> +**Supported Drivers**
> + * Drivers supporting rte_security PDCP:
> + * XPdpaa2_sec, dpaa_sec
Change it to NXP dpaa2_sec, dpaa_sec
prev parent reply other threads:[~2024-11-19 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 4:38 [PATCH] doc/guides: " Nandini Persad
2024-11-13 5:03 ` Stephen Hemminger
2024-11-13 5:12 ` Hemant Agrawal
2024-11-18 17:13 ` [PATCH v2] doc: " Nandini Persad
2024-11-19 5:01 ` Hemant Agrawal [this message]
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=ea0b995f-f148-5ca3-20bb-60c7d2afc020@oss.nxp.com \
--to=hemant.agrawal@oss.nxp.com \
--cc=dev@dpdk.org \
--cc=nandinipersad361@gmail.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).