Hi Authors, After reading this draft, I find it still combines many possible options (e.g, dataplane). Hope to see a draft with much more clear opinion in next version.
Several comments below: 1. Since TS is the end of the network, flow (e.g, 5 tuple) based VN forwarding would bring much network flexibility. The L2/L3 VN service is the traditional service, but I believe the VN should have the capability to provide a flow based forwarding service. 2. Is there a standard interface between NVA and VM orchestration, or a private interface? Hope to see more description in detail. 3. If push and pull are supported, then how to combine the pull and push mode should be described, which is closely related with NVE-NVA protocol. 4. section 12, why dataplane definition is not considered as the main area of work? Regards Lizhong
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
