From: Brian Russell
Date: Fri, 4 Mar 2016 15:38:47 +
> So it seems reasonable to have a hook to hang metadata
> interpretation on?
Nope.
On Tue, Mar 1, 2016 at 3:11 AM, Brian Russell wrote:
> These patches add a new module to support encap/decap of Network
> Service Header (NSH) as defined in:
>
> https://tools.ietf.org/html/draft-ietf-sfc-nsh-01
>
> Both NSH Type 1 and Type 2 metadata are supported with a simple registration
> hoo
On 01/03/16 18:12, Alexei Starovoitov wrote:
> On Tue, Mar 01, 2016 at 11:11:46AM +, Brian Russell wrote:
>> These patches add a new module to support encap/decap of Network
>> Service Header (NSH) as defined in:
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_dr
On Tue, Mar 01, 2016 at 11:11:46AM +, Brian Russell wrote:
> These patches add a new module to support encap/decap of Network
> Service Header (NSH) as defined in:
>
> https://tools.ietf.org/html/draft-ietf-sfc-nsh-01
>
> Both NSH Type 1 and Type 2 metadata are supported with a simple registr
These patches add a new module to support encap/decap of Network
Service Header (NSH) as defined in:
https://tools.ietf.org/html/draft-ietf-sfc-nsh-01
Both NSH Type 1 and Type 2 metadata are supported with a simple registration
hook to allow listeners to register to see packets with Type 1 or a s