Here is the proposal: https://wiki.opendaylight.org/view/Project_Proposals:General_Network_Topology Previous discussion can be found here: https://lists.opendaylight.org/pipermail/project-proposals/20

I'll just send an e-mail to the TSC mailing list opening the creation review, and we'll let people ask questions and you can answer them. If the coversation has mostly died down in a week, I'll ask fo

OK. We can also do it over e-mail if you'd like to try to get it done sooner than next month. --Colin

A long-belated time later, congrats: https://lists.opendaylight.org/pipermail/tsc/2017-July/007714.html Feel free to start the process of creating the project: https://wiki.opendaylight.org/view/Proje

It just seems easier to me to put the code in OpenFlow plugin than to pull a new project out of a hat that somehow doesn't behave like normal projects. If we can move it to OpenFlow plugin for now, th

I'm happy either way. The fact that lldp "is a protocol" doesn't seem like a compelling argument for why it can't go in the OpenFlow plugin project to me, but maybe I'm missing something. Abhijit, is

Thanks! I take it the conclusion was that this shouldn't be part of the OpenFlow plugin project? --Colin

I think OVIL is more than fine. I'll kick off the discussion on the TSC list. --Colin

So, assuming the name is fixed, should we start a formal creation review thread on the TSC mailing list? --Colin

The next APAC-friendly TSC call is scheduled for July 27th. If you're willing to wait until then, that call is at 11:30a Beijing time. Otherwise, we can have the creation review happen over e-mail if

So, it sounds to me like the project proposal wanted to try to factor out the common elements of how SFC, NetVirt, and GBP would talk to VPP to do service chaining int one place so that (a) the code c

Cool! Thank you for your time and understanding. It seems like a really cool project and we look forward to seeing more. For what it's worth, BIER is getting some broader attention: http://packetpushe

OK. So, the plan is that this won't be it's own project, but will just be part of the the existing BIER proejct in the same repository? --Colin

Following up from the TSC call, which has notes here: https://meetings.opendaylight.org/opendaylight-meeting/2017/tsc/opendaylight-meeting-tsc.2017-06-22-03.30.html There are two items. That we'd love

The meeting should be at 0330 UTC on Thursday this week and we should use the Zoom info here: https://wiki.opendaylight.org/view/TSC:Main#Meeting_Schedule_and_Logistics Specifically: APAC Meeting (Hel

Thank you. --Colin

Understood. The next regularly scheduled TSC meeting after the two-week public review period is 6/22, which is actually the Asia-friendly TSC call time too, which is probably good. Does that time work

Understood. The next regularly scheduled TSC meeting after the two-week public review period is 6/22, which is actually the Asia-friendly TSC call time too, which is probably good. Does that time work

Thanks for the request. Two quick questions: 1.) Do you actually want to participate in Nitrogen, it will be a very fast release with API freeze (including support for Karaf 4) being 7/14 at the lates

I've given the P4 plugin proposal roughly that advice. --Colin