Yizhou is correct that our liaison statement needs to reflect nvo3 consensus. Please feel free to continue discussing this topic to see if consensus emerges. But also keep in mind that we can always send additional liaisons in the future in order to collaborate further with our colleagues working in IEEE.
Thanks, -Benson On Wednesday, April 29, 2015, Liyizhou <[email protected]> wrote: > Hi Zhongyu, > > > > Thanks for pointing out you would like to see the VDP extension work in > previous emails. > > > > For the use case you brought up, I am not too sure why such a scenario is > required and has not seen any discussions on it. It would be good if > consensus to be reached on adding such use case to architecture or use case > document before it is taken into consideration in liaison. > > > > Thanks, > > Yizhou > > > > > > *From:* [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');> [mailto: > [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>] > *Sent:* Wednesday, April 29, 2015 10:55 AM > *To:* Liyizhou > *Cc:* Liyizhou; [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>; nvo3; Pat Thaler > *Subject:* 答复: [nvo3] proposed liaison text to IEEE 802.1 for VDP > extension work > > > > Hi Yizhou and all, > > This is a formal liaison to IEEE, so it should cover all possible > extension consideration in NVO3. > The following are two more consideration. > > Firstly, as you may know, we posted a message: > http://www.ietf.org/mail-archive/web/nvo3/current/msg04418.html. In it, > we discussed and concluded it's possible to extend VDP to realize the VN > automatic provisioning. > > Secondly, we wonder if VDP suitable for all the usage scenarios in NVO3, > especially for the typical Hypervisor/NVE-ToR/NVE scenario, because it is > different from VDP/EVB architecture (Hypervisor/EVB station - ToR/EVB > Bridge). For example, when some VMs/VNs reside in Hypervisor/NVE and at the > same time other VMs/VNs(VMs belong to the same Hypervisor) reside in > ToR/NVE, results in Hypervisor works as EVB station while working as EVB > brige simultaneously. If this understanding is right, it’s critical to VDP > extension. > > Of course, these points are not discussed before in NVO3. > If possible, please take them into account here. > > Thanks in advance! > > Zhongyu > > > > > > *Liyizhou <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>>* > 发件人: "nvo3" <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> > > 2015/04/28 10:07 > > 收件人 > > "[email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');>" < > [email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');>>, > > 抄送 > > Pat Thaler <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>>, Liyizhou < > [email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');>> > > 主题 > > [nvo3] proposed liaison text to IEEE 802.1 for VDP extension work > > > > > > Hi folks, > > We are going to send a liaison to IEEE 802.1 to bring their attention to > ietf-nvo3-hpvr2nve-cp-req draft and to suggest the work to extend VDP > protocol based on the consensus reached during Dallas meeting. > > Chairs asked me to post the proposed text here for your review. > > Thanks a lot, > > Yizhou > > > ----------- > > Liaison Statement： NVO3 Liaison to IEEE 802.1 > > From: Matthew Bocci and Benson Schliesser > (Co-Chairs, IETF NVO3 Working Group) > > To: Glenn Parsons (Chair, IEEE 802.1 Working Group) > <javascript:_e(%7B%7D,'cvml','[email protected]');> > > Cc: > Ron Bonica <javascript:_e(%7B%7D,'cvml','[email protected]');>* (IETF > NVO3 Technical Advisor)* > Eric Gray <javascript:_e(%7B%7D,'cvml','[email protected]');>* (IETF > Liaison to IEEE 802.1)* > Alia Atlas <javascript:_e(%7B%7D,'cvml','[email protected]');>* (IETF > Area Director for NVO3)* > Dan Romascanu (IETF Liaison to the IEEE SA) > <javascript:_e(%7B%7D,'cvml','[email protected]');> > Jari Arkko <javascript:_e(%7B%7D,'cvml','[email protected]');>* > (Chair, IETF)* > Pat Thaler <javascript:_e(%7B%7D,'cvml','[email protected]');>* > (Chair, IEEE 802.1 DCB Task Group)* > Paul Nickolich (Chair, IEEE 802) > <javascript:_e(%7B%7D,'cvml','[email protected]');> > > Purpose: For action > > Attachments: (none) > > Body: > Dear Glenn, > > The IETF NVO3 Working Group has been developing the requirements for a > Control Plane Protocol between server Hypervisors and Network Virtual Edge > (NVE) devices in virtualized overlay networks. The current draft can be > found at http://datatracker.ietf.org/doc/draft-ietf-nvo3-hpvr2nve-cp-req/. > > > This requirements document suggests extending the VDP (VSI Discovery and > Configuration Protocol) protocol specified by IEEE Std 802.1Qbg as a > solution. We would particularly welcome IEEE 802.1 Working Group’s review > of Section 5 of the draft. That section compares the conceptually similar > terms in NVO3 and the VDP context. It also summarizes the potential > technical extension work required for VDP to be used as the control plane > protocol between the hypervisor and NVE. > > In view of the progress of this work, we would like to suggest IEEE 802.1 > Working Group to use that draft as a base requirement reference for VDP > extensions in the aforementioned context. Please note that the status of > this draft in the IETF, that it is a “Working Group draft”, indicates that > the Working Group considers it an appropriate starting point but it is > still subject to change. While a determination has not yet been made that > there is technical consensus on all the details of the draft, there is > consensus on basing the Hypervisor to NVE protocol on VDP with appropriate > extensions. > > Sincerely Yours, > > Matthew Bocci & Benson Schliesser > IETF NVO3 Working Group Co-Chairs > _______________________________________________ > nvo3 mailing list > [email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');> > https://www.ietf.org/mailman/listinfo/nvo3 >
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
