Hi Lothar, Please see inline below.
From: nvo3 [mailto:[email protected]] On Behalf Of Reith, Lothar Sent: Friday, September 09, 2016 3:36 AM To: Bocci, Matthew (Nokia - GB); NVO3 Subject: Re: [nvo3] WG last call for draft-ietf-nvo3-use-case-09 Dear all, in section 4.3 there is a reference to “Figure 3 below”, however the referenced figure is undertitled as “Figure 2” and a figure 3 does not exist. I suggest to correct the reference to the figure as “Figure 2 below”. [Lucy] Ack. Thanks. Besides this minor flaw I have a question regarding what is shown in this figure combined with the suggestion to consider some clarification text. It is not clear to me if the shown L2VNs named VNx, VNy and VNz are nested in the shown L3 VNa and if yes how that is reflected in the respetive identifier relations (or not at all reflected in the identifier relations such as VNI). So in a nutshell, my question is: Is there something like “nested VNIs” (in particular regarding L2 VNIs nested in L3 VNIs) or not? I like to not that clarity about identifier relations is absolutely critical when it comes to the associated data modelling. [Lucy] Section 4.3 intends describing virtual Data Center service and showing an abstraction view of virtual Data Center. It does not describe how DC operator construct individual NVO3 networks to realize it. I agree that data model is important for a solution but that should be addressed in a solution draft. A Virtual Data Center may contain multiple overlay networks that may be interconnected and some service functions. I will make this indent more clear in next version. IMO: a virtual data center should contain one address space. It could assign a subnet for each application of a customer. Thanks/Regards, Lucy Best Regards, Lothar For ease of reference please find below the portion of the figure which my question relates to: I ...+.... |..| +-------: L3 VNa :---------+ LANs +-+-+ ........ | |LB | | | Enterprise Site +-+-+ | | ...+... ...+... ...+... : L2VNx : : L2VNy : : L2VNz : ....... ....... ....... |..| |..| |..| | | | | | | Web App. Mail App. VoIP App. Von: nvo3 [mailto:[email protected]] Im Auftrag von Bocci, Matthew (Nokia - GB) Gesendet: Dienstag, 6. September 2016 12:14 An: NVO3 <[email protected]<mailto:[email protected]>> Betreff: [nvo3] WG last call for draft-ietf-nvo3-use-case-09 This email begins a two week working group last call for draft-ietf-nvo3-use-case-09.txt. Please review the draft and post any comments to the NVO3 working group list. If you have read the latest version of the draft but have no comments and believe it is ready for publication as an Informational RFC, please also indicate so to the WG email list. This working group last call will close on Tuesday 20th September 2016. Best regards Matthew and Sam
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
