Support with clarification comments: The VN Name-to-VN ID mapping: is there a reason it has to be part of the control protocol? The protocol may need an index for the VN context, either the name or the ID as far as it is unique. It does not have to be two index, right? In section 4, there is a statement that " NVEs are expected to be implemented within both hypervisors (or Network Service Appliances) and within access switches. " In the framework draft which the NVE is defined as "An NVE could be implemented as part of a virtual switch within a hypervisor, a physical switch or router, a Network Service Appliance, or be split across multiple devices."
Have a nice day Zu Qiang >-----Original Message----- >From: [email protected] [mailto:[email protected]] On Behalf Of >Benson Schliesser >Sent: Thursday, June 27, 2013 9:26 PM >To: [email protected] >Subject: [nvo3] Poll for WG Adoption of draft-kreeger-nvo3-overlay-cp-04 > >This email begins a two week poll to help the chairs judge if there is >consensus >to adopt draft-kreeger-nvo3-overlay-cp-04 as an NVO3 working group draft. > >Please respond to this email on the list with 'support' or 'do not support'. > >Please also send any comments on the draft to the NVO3 list. > >We are also polling for knowledge of any IPR that applies to this draft, to >ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs >3979, 4879, 3669 and 5378 for more details). > >If you are listed as a document author or contributor, please respond to this >email whether or not you are aware of any relevant IPR. The draft will not be >adopted until a response has been received from each author and contributor. > >If you are on the NVO3 WG email list but are not listed as an author or >contributor, then please explicitly respond only if you are aware of any IPR >that has not yet been disclosed in conformance with IETF rules. > >This poll closes on 11 July 2013. > >Cheers, >-Benson & Matthew >_______________________________________________ >nvo3 mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/nvo3 >_______________________________________________ >nvo3 mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
