On Wed, Nov 22, 2017 at 07:43:13PM +0530, Anoob wrote:
> Hi,
>
> Please see inline.
>
>
> On 11/22/2017 06:57 PM, Neil Horman wrote:
> > On Wed, Nov 22, 2017 at 06:55:15AM +, Anoob Joseph wrote:
> > > In case of inline protocol processed ingress traffic, the packet may not
> > > have enough
Hi,
Please see inline.
On 11/22/2017 06:57 PM, Neil Horman wrote:
On Wed, Nov 22, 2017 at 06:55:15AM +, Anoob Joseph wrote:
In case of inline protocol processed ingress traffic, the packet may not
have enough information to determine the security parameters with which
the packet was proce
On Wed, Nov 22, 2017 at 06:55:15AM +, Anoob Joseph wrote:
> In case of inline protocol processed ingress traffic, the packet may not
> have enough information to determine the security parameters with which
> the packet was processed. For such cases, application could register a
> 64 bit metada
On 11/22/2017 11:52 AM, Anoob wrote:
Hi,
See inline.
Thanks,
Anoob
On 11/22/2017 04:59 PM, Radu Nicolau wrote:
On 11/22/2017 6:55 AM, Anoob Joseph wrote:
In case of inline protocol processed ingress traffic, the packet may
not
have enough information to determine the security parameter
Hi,
See inline.
Thanks,
Anoob
On 11/22/2017 04:59 PM, Radu Nicolau wrote:
On 11/22/2017 6:55 AM, Anoob Joseph wrote:
In case of inline protocol processed ingress traffic, the packet may not
have enough information to determine the security parameters with which
the packet was processed. Fo
On 11/22/2017 6:55 AM, Anoob Joseph wrote:
In case of inline protocol processed ingress traffic, the packet may not
have enough information to determine the security parameters with which
the packet was processed. For such cases, application could register a
64 bit metadata in security session,
6 matches
Mail list logo
