[dpdk-dev,v2,8/8] examples/ipsec-secgw: update release notes
Commit Message
Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
---
doc/guides/rel_notes/release_16_11.rst | 9 +++++++++
1 file changed, 9 insertions(+)
Comments
Hi Sergio,
> -----Original Message-----
> From: Gonzalez Monroy, Sergio
> Sent: Friday, September 23, 2016 12:46 AM
> To: dev@dpdk.org; De Lara Guarch, Pablo
> Subject: [PATCH v2 8/8] examples/ipsec-secgw: update release notes
>
> Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
> ---
> doc/guides/rel_notes/release_16_11.rst | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_16_11.rst
> b/doc/guides/rel_notes/release_16_11.rst
> index 373053a..12f507b 100644
> --- a/doc/guides/rel_notes/release_16_11.rst
> +++ b/doc/guides/rel_notes/release_16_11.rst
> @@ -89,6 +89,15 @@ Examples
> ipsec-secgw sample application now supports configuration file to specify
> SP, SA, and routing rules.
>
> +* **ipsec-secgw: AES GCM/CTR mode support**
> +
> + Support AES Counter (CTR) and Galois-Counter Mode (GCM) in IPSec ESP.
> +
> +* **ipsec-secgw: AES CBC IV generation**
> +
> + Use cipher forward function on unique counter blocks (same approach as
> + CTR/GCM) to generate the IV instead of a random value.
> +
> Other
> ~~~~~
>
> --
> 2.5.5
This should go under "New features" section, not under "Resolved issues".
I have seen that other people have made the same mistake,
which tells me that we might need to change this
(there are different subsections only under Resolved Issues).
Thanks,
Pablo
On 28/09/2016 05:05, De Lara Guarch, Pablo wrote:
> Hi Sergio,
>
>> -----Original Message-----
>> From: Gonzalez Monroy, Sergio
>> Sent: Friday, September 23, 2016 12:46 AM
>> To: dev@dpdk.org; De Lara Guarch, Pablo
>> Subject: [PATCH v2 8/8] examples/ipsec-secgw: update release notes
>>
>> Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
>> ---
>> doc/guides/rel_notes/release_16_11.rst | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/doc/guides/rel_notes/release_16_11.rst
>> b/doc/guides/rel_notes/release_16_11.rst
>> index 373053a..12f507b 100644
>> --- a/doc/guides/rel_notes/release_16_11.rst
>> +++ b/doc/guides/rel_notes/release_16_11.rst
>> @@ -89,6 +89,15 @@ Examples
>> ipsec-secgw sample application now supports configuration file to specify
>> SP, SA, and routing rules.
>>
>> +* **ipsec-secgw: AES GCM/CTR mode support**
>> +
>> + Support AES Counter (CTR) and Galois-Counter Mode (GCM) in IPSec ESP.
>> +
>> +* **ipsec-secgw: AES CBC IV generation**
>> +
>> + Use cipher forward function on unique counter blocks (same approach as
>> + CTR/GCM) to generate the IV instead of a random value.
>> +
>> Other
>> ~~~~~
>>
>> --
>> 2.5.5
> This should go under "New features" section, not under "Resolved issues".
> I have seen that other people have made the same mistake,
> which tells me that we might need to change this
> (there are different subsections only under Resolved Issues).
Will fix on v3.
Sergio
> Thanks,
> Pablo
@@ -89,6 +89,15 @@ Examples
ipsec-secgw sample application now supports configuration file to specify
SP, SA, and routing rules.
+* **ipsec-secgw: AES GCM/CTR mode support**
+
+ Support AES Counter (CTR) and Galois-Counter Mode (GCM) in IPSec ESP.
+
+* **ipsec-secgw: AES CBC IV generation**
+
+ Use cipher forward function on unique counter blocks (same approach as
+ CTR/GCM) to generate the IV instead of a random value.
+
Other
~~~~~