From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] doc: release note for the IPsec library and application
Date: Fri, 26 Jul 2019 13:17:06 +0000 [thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C260DD4B72@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <VE1PR04MB6639F1F586928989108DFC35E6C00@VE1PR04MB6639.eurprd04.prod.outlook.com>
Hi Akhil,
> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Friday, July 26, 2019 1:36 PM
> To: Iremonger, Bernard <bernard.iremonger@intel.com>; dev@dpdk.org;
> Ananyev, Konstantin <konstantin.ananyev@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Subject: RE: [PATCH v4] doc: release note for the IPsec library and application
>
>
> >
> > Update release notes for changes to the IPsec library.
> > Update release notes for changes to the IPsec Security Gateway
> application
>
> Description and the release note updates use redundant words which can be
> avoided.
> It could be something like
>
> "Update release notes for recently supported features in ipsec lib and
> application."
Ok, will change.
> > Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> > ---
> > doc/guides/rel_notes/release_19_08.rst | 17 +++++++++++++----
> > 1 file changed, 13 insertions(+), 4 deletions(-)
> >
> > diff --git a/doc/guides/rel_notes/release_19_08.rst
> > b/doc/guides/rel_notes/release_19_08.rst
> > index c9bd3ce..48319be 100644
> > --- a/doc/guides/rel_notes/release_19_08.rst
> > +++ b/doc/guides/rel_notes/release_19_08.rst
> > @@ -200,11 +200,20 @@ New Features
> > handshake between two separate hosts and can share local memory for
> peer
> > host to directly access.
> >
> > -* **Updated IPSec library Header Reconstruction.**
> > +* **Updated IPSec library and IPsec Security Gateway application.**
> >
> > - Updated the IPSec library with ECN and DSCP field header reconstruction
> > - feature followed by RFC4301. The IPSec-secgw sample application is also
> > - updated to support this feature by default.
> > + Added the following functionality to ``librte_ipsec`` and ``ipsec-secgw``
>
> Added following features to ``librte_ipsec``. Corresponding changes are also
> added in ``ipsec-secgw`` sample application.
Ok, will change.
> > +
> > + * Updated ``librte_ipsec`` with ECN and DSCP field header reconstruction
> > + feature followed by RFC4301.
>
> * ECN and DSCP field header reconstruction as per RFC4301
>
> > +
> > + * Added support for transport mode with IPv6 extension headers to
> > + ``librte_ipsec``.
>
> * Transport mode with IPv6 extension headers
Ok, will change
> > +
> > + * Added support for packets that consist of multiple segments to
> > + ``librte_ipsec``.
>
> * Support packets with multiple segments.
>
Ok, will change.
> > +
>
> > + * Updated the ``ipsec-secgw`` sample application to support these
> features.
>
> This bullet can be removed.
Ok, will remove.
> >
> > * **Updated telemetry library for global metrics support.**
> >
>
> -Akhil
Regards,
Bernard.
next prev parent reply other threads:[~2019-07-26 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:59 [dpdk-dev] [PATCH] doc: release note for the IPsec library Bernard Iremonger
2019-07-25 12:58 ` [dpdk-dev] [PATCH v2] " Bernard Iremonger
2019-07-25 14:39 ` [dpdk-dev] [PATCH v3] " Bernard Iremonger
2019-07-25 14:52 ` Ananyev, Konstantin
2019-07-26 10:27 ` Akhil Goyal
2019-07-26 10:49 ` Iremonger, Bernard
2019-07-26 11:57 ` [dpdk-dev] [PATCH v4] doc: release note for the IPsec library and application Bernard Iremonger
2019-07-26 12:36 ` Akhil Goyal
2019-07-26 13:17 ` Iremonger, Bernard [this message]
2019-07-26 13:42 ` [dpdk-dev] [PATCH v5] " Bernard Iremonger
2019-07-26 13:44 ` Akhil Goyal
2019-07-26 13:54 ` Akhil Goyal
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=8CEF83825BEC744B83065625E567D7C260DD4B72@IRSMSX108.ger.corp.intel.com \
--to=bernard.iremonger@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=roy.fan.zhang@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).