Please accept this project proposal for CSIT for consideration. https://wiki.fd.io/view/Project_Proposals/CSIT -- Maciek

The TSC Agenda for the 8am PST meeting on Thu Mar 3, 2016 is posted here: https://wiki.fd.io/view/TSC#Agenda The major item being covered is security response procedures. Please suggest any other

CSIT proposed a project on 26 Feb 2016, at 18:29UTC: https://lists.fd.io/pipermail/tsc/2016-February/000020.html I would like to request a creation review for CSIT on 17-MAR-2016. -- Maciek P.S.

Agenda updated with: - Events - TSC Proxy (ie, how do we want to handle proxies as a TSC)

Also added making infrastructure tickets visible to the community to the agenda: https://wiki.fd.io/view/TSC#Agenda Ed

As was discussed at the TSC today, we have an opportunity to do training and HackFest in Santa Cruz Apr 4-7. The point was made that this is also the week of IETF, and a question was asked as to

Please accept this project proposal for Honeycomb for consideration. https://wiki.fd.io/view/Project_Proposals/Honeycomb

Other TSC members, given the tightness of time, if you would please indicate if you have any objections to scheduling this Hackfest by Monday. Past then, I'll take silence as golden :) Ed

Please accept this project proposal for NSH-based Service Function Chaining for consideration. We would like to request scheduling for the first TSC meeting after 2 weeks have passed to allow for

Honeycomb proposed a project on March 4th 2016: https://lists.fd.io/pipermail/tsc/2016-March/000026.html I would like to request a creation review for Honeycomb on March 24th 2016 (Thursday

Hmmm. I am a little confused by saying that the dates can not be moved. I can believe that the host in Santa Cruz can’t do it the next week, but it would seem that between us we could find some

Hi Jim, I have a few comments below after reviewing the proposal: 1) Do we need to add a bullet mentioning to-be-supported NSH transport, such as VxLAN-GPE, GRE and Ethernet. I think

Comments in line. Thank you for the suggestions. We started out by putting a list of the detailed encaps in the charter. Ed then pointed out that the charter is the scope, not the release plan. The

More comments inline.

With regard to the service functions, I beliee we agree that service functions enabled and assisted by VPP is in scope for the entirety of fd.io. And is useful. I have not done much project

I think this is all good. If we keep the context that VPP is a dataplane, that needs to interface with a control plane it's all good. Then things like SF proxy/bypass become use-cases for

Makes sense to me.

The TSC Agenda for the 8am PST meeting on Thu Mar 10, 2016 is posted here: https://wiki.fd.io/view/TSC#Agenda In addition, because we have several agenda items for subsequent meetings that we already

This event has been changed. more details » VPP Weekly Project Meeting Changed: This is the weekly VPP Project Meeting Agenda: https://wiki.fd.io/view/VPP/Meeting#Agenda Meeting Logistics:

This event has been changed. more details » VPP Weekly Project Meeting This is the weekly VPP Project Meeting Agenda: