Re: [lng-odp] [API-NEXT][RFC][rebased] linux-gen: ipsec: draft IPsec implementation

2017-04-18 Thread Dmitry Eremin-Solenikov
as you've stated in another email. > > Janne > > >> -----Original Message----- >> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Dmitry >> Eremin- >> Solenikov >> Sent: Friday, April 14, 2017 3:00 PM >> To: Bill

Re: [lng-odp] [API-NEXT][RFC][rebased] linux-gen: ipsec: draft IPsec implementation

2017-04-18 Thread Peltonen, Janne (Nokia - FI/Espoo)
cannot use random IV since IV values must never be reused in GCM. With AES-GCM a counter or alike would work. Janne > -Original Message- > From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Dmitry > Eremin- > Solenikov > Sent: Friday, April 14, 2017

Re: [lng-odp] [API-NEXT][RFC][rebased] linux-gen: ipsec: draft IPsec implementation

2017-04-18 Thread Peltonen, Janne (Nokia - FI/Espoo)
v > Sent: Tuesday, April 11, 2017 4:42 PM > To: lng-odp@lists.linaro.org > Subject: [lng-odp] [API-NEXT][RFC][rebased] linux-gen: ipsec: draft IPsec > implementation > > For now it's only a preview with the following limitation: > - No inline processing support > - No

Re: [lng-odp] [API-NEXT][RFC][rebased] linux-gen: ipsec: draft IPsec implementation

2017-04-14 Thread Dmitry Eremin-Solenikov
Bill, Thanks a lot for the review! I will send updated patches in few hours hopefully. On 14.04.2017 00:42, Bill Fischofer wrote: > Next version should be marked API-NEXT, whether or not it is still an Yes, that was an error from my side. > On Tue, Apr 11, 2017 at 8:41 AM, Dmitry

Re: [lng-odp] [API-NEXT][RFC][rebased] linux-gen: ipsec: draft IPsec implementation

2017-04-13 Thread Bill Fischofer
Next version should be marked API-NEXT, whether or not it is still an RFC since IPsec APIs cannot move to master until we have a complete implementation / validation test suite. I realize this is an RFC, but it doesn't apply to the current api-next: Applying: linux-gen: ipsec: draft IPsec

[lng-odp] [API-NEXT][RFC][rebased] linux-gen: ipsec: draft IPsec implementation

2017-04-11 Thread Dmitry Eremin-Solenikov
For now it's only a preview with the following limitation: - No inline processing support - No SA lookups - Only IPv4 support - No tunnel support - No header modification according to RFCs Signed-off-by: Dmitry Eremin-Solenikov ---