Hi, Osama. On Mon, Aug 25, 2014 at 4:30 PM, Osama Zia <[email protected]> wrote:
> 1. I am getting the impression that NVO3 WG will only look at logically > centralized control plane. All decentralized solutions such as BGP based > should be looked separately. Is this correct? > Yes. To elaborate: Existing and new solutions that are based on BGP to provide network virtualization would be developed in the (to-be-formed) BESS working group. This would be the case for all BGP-based solutions, regardless of whether they have a control plane architecture that is distributed or centralized. It is possible that NVO3 solutions could leverage BGP and/or that BGP-based solutions could leverage NVO3 work. In these cases we would work cross-WG to make sure that the solution is documented completely and accurately, with work happening in the most appropriate place(s). For example one could imagine combining a NVO3-developed data plane encap, a NVO3-developed TS-NVE control plane, and a BESS-developed NVA control plane. (There are many other possible combinations here; I'm not trying to be exhaustive, just illustrate the idea.) Similar to what I've described above, NVO3 solutions might leverage distributed protocols in various ways, resulting in cross-WG work with other WGs. For example, it is possible that the centralized NVE-NVA control plane protocol is responsible for certain mapping functions whilst other functions are provided by distributed protocols, such as liveness detection via IGP-provided link state etc. (Again, not trying to be exhaustive, just illustrating the idea.) 2. The statement says that "The NVO3 WG will develop solutions for network > virtualization based on the following architectural tenets". However, the > control plane requirements and data plane requirements are optional. > Shouldn't architecture be based on certain requirements? Requirements are certainly helpful, and as an NVO3 chair I do intend to encourage their development. But one of the goals of this recharter is to begin working on solutions in parallel, rather than in serial, with requirements. Indeed, the purpose of working on requirements is to assist the WG in developing solutions (requirements on their own have little value). And so with this new charter text we have given ourselves the flexibility to manage the production of requirements in whatever way is best for the WG. Cheers, -Benson
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
