It may well be that I am dense. I have looked at the definition you pointed to. I have looked at the project proposal page. I cannot tell what the netvirt project would actually do. I can’t

Fair enough. As the TSC, we try to avoid forcing collaboration where the developers decide that it's not the right idea from a technical perspective. I'd still love to see some intermediate YANG model

Hello Ed, The following looks like a reasonable definition: https://www.sdxcentral.com/resources/network-virtualization/whats-network-virtualization/ For example, the NetVirt component of the existing

Hi, Thank you for agreeing with me, Weiqiang Cheng. I understand that MPLS-TP YANG models are in your scope. But I am guessing our MPLS-TP model is fundamentally different from MPLS-TP Solution

Hi， I agree with Justin. It is better to have separate projects. One point I want to clarify is that the MPLS-TP YANG models for NBI is also in our scope. B.R. Weiqiang Cheng 发件人:

Hi, I’m cc’ing tsc mailing list to get a creation review. We carefully searched for a common ground to collaborate with China Mobile. But as far as I understand, it seems like our common

Also, the sooner you can your M1 status report in, the better. You can find the request here: https://lists.opendaylight.org/pipermail/release/2016-March/006027.html Please send it to the release list

Given that there is a PoC alread, I'm guessing that you will need to have an incoming code intellectual property review (IPR). Phil will help you with that if you send him a zip file or tarball with

Sam, Question... in the scope... what constitutes 'network virtualization' in your mind? (trying to wrap my head around the scope :) ). Ed

I'm cc'ing project-proposals just so this gets logged somewhere. It sounds like common areas here would be the MPLS-TP TTP and the MPLS-TP support for OF-CONFIG. Beyond that, it sounds like we have

Thanks to Colin for your suggestion. Please excuse me for taking the liberty to write to MPLS-TP service team. It is nice to see you have the similar requirements on MPLS-TP with us. It just to

It would be good to see if you could coordinate to see if you could build the common parts in a single place. For example, maybe the southbound driver for MPLS-TP would be a common project and there

I've added it to the project proposals here: https://wiki.opendaylight.org/view/Project_Proposals:Main#New_Pending_Creation_Review And I've scheduled it tentatively for two weeks from today on April

Hello, we would like to submit the follow proposal [1] to split NetVirt from OVSDB. All committers have +1'd the proposal. Since the split of NetVirt from the OVSDB project has already been discussed

Hi Pradeeban, Thank you very much for your comments. Please see in line below for my response to your comments. B.R. Weiqiang Cheng 发件人: Pradeeban Kathiravelu [mailto:kk.pradeeban@...]

Hi Weiqiang, If only the implementation approach is different with a large overlap in the goal (even the names suggest so), doesn't it make sense to collaborate and make a stronger project instead of

Hi Colin and George, Thank you very much for your reply. I just looked at the MPLS-TP service project proposal briefly. It seems that there are some overlaps for the requirement. However, the

Great, thank you. Best, Vina On Mar 17, 2016, at 3:44 AM, Colin Dixon <colin@...> wrote:

I was going to say the same thing. --Colin

Hi Weiqiang, I added your proposal to the wiki page under proposals submitted for review section. Without digging into details, somehow, MPLS-TP Solution proposal looks similar with MPLS-TP