Thanks for the diagram.

One probably naive question prompted by that.  Don't the check for "end"
and the determination of "next" both rely on doing the NSH SPI/SI
lookup?  And it is the result of that lookup that is either "terminate"
or "NSH Forward"?

Thanks,
Joel

On 4/25/16 9:43 AM, Keith Burns wrote:
>
>
> On Mon, Apr 25, 2016 at 6:33 AM Jim Guichard (jguichar)
> <jguichar@... <mailto:jguichar@...>> wrote:
>
>     Hi Keith,
>
>     The agenda is already posted and the main topic is to discuss the
>     work you have been doing.
>
>
> Thanks, removed vpp-dev, see link below for diagram:
>
> https://drive.google.com/open?id=0B_RDwdFu5VJDX2pVMHk5Ni1FNWc
>
>
>
>     Jim
>
>     From: <vpp-dev-bounces@...
>     <mailto:vpp-dev-bounces@...>> on behalf of Keith Burns
>     <alagalah@... <mailto:alagalah@...>>
>     Date: Sunday, April 24, 2016 at 11:40 AM
>     To: "nsh_sfc-dev@... <mailto:nsh_sfc-dev@...>"
>     <nsh_sfc-dev@... <mailto:nsh_sfc-dev@...>>, vpp-dev
>     <vpp-dev@... <mailto:vpp-dev@...>>
>     Subject: [vpp-dev] Moving NSH code to NSH_SFC repo from VPP
>
>     Folks,
>
>     I have a design I would like to pursue to move the work I already
>     did in VPP over to NSH_sfc and make that project a plugin.
>
>     Note this doesn't have to be a "final" or absolute design for how
>     this works but I do feel the NSH work I've already started is
>     unfinished based on the limited functionality it was targeting
>     (simplistic SFF and classifier PoC), so it's important to me
>     personally to complete that.
>
>     Should that be merged (note that this will be two patches, one for
>     VPP removing the code and another for NSH_SFC to add to a different
>     repo) we would need to coordinate across projects.
>
>     Thats not a big deal, and I'll be sure to link both patches but note
>     any changes suggested to one will potentially mean changes to the
>     other.
>
>     I expect this to be ready before midweek. I would have loved to have
>     had it ready for the NSH meeting tomorrow but perhaps we can review
>     some diagrams I have as part of the agenda (agenda link coming)
>     instead.
>
>     Thanks.
>
>
>
>
>
>
>
>
> _______________________________________________
> nsh_sfc-dev mailing list
> nsh_sfc-dev@...
> https://lists.fd.io/mailman/listinfo/nsh_sfc-dev
>

On Mon, Apr 25, 2016 at 6:33 AM Jim Guichard (jguichar) <jguichar@...> wrote:

Hi Keith,

The agenda is already posted and the main topic is to discuss the work you have been doing. 

Thanks, removed vpp-dev, see link below for diagram:

https://drive.google.com/open?id=0B_RDwdFu5VJDX2pVMHk5Ni1FNWc

 

Jim

From: <vpp-dev-bounces@...> on behalf of Keith Burns <alagalah@...>
Date: Sunday, April 24, 2016 at 11:40 AM
To: "nsh_sfc-dev@..." <nsh_sfc-dev@...>, vpp-dev <vpp-dev@...>
Subject: [vpp-dev] Moving NSH code to NSH_SFC repo from VPP

Folks,

I have a design I would like to pursue to move the work I already did in VPP over to NSH_sfc and make that project a plugin. 

Note this doesn't have to be a "final" or absolute design for how this works but I do feel the NSH work I've already started is unfinished based on the limited functionality it was targeting (simplistic SFF and classifier PoC), so it's important to me personally to complete that. 

Should that be merged (note that this will be two patches, one for VPP removing the code and another for NSH_SFC to add to a different repo) we would need to coordinate across projects. 

Thats not a big deal, and I'll be sure to link both patches but note any changes suggested to one will potentially mean changes to the other. 

I expect this to be ready before midweek. I would have loved to have had it ready for the NSH meeting tomorrow but perhaps we can review some diagrams I have as part of the agenda (agenda link coming) instead. 

Thanks.