My initial reaction is that this seems no worse than the typical route-flapping effects of some routing updates - it's certainly worth noting, but I would not require that it be eliminated completely in all solutions.
Thanks, --David ---------------------------------------------------- David L. Black, Distinguished Engineer EMC Corporation, 176 South St., Hopkinton, MA 01748 +1 (508) 293-7953 FAX: +1 (508) 293-7786 [email protected] Mobile: +1 (978) 394-7754 ---------------------------------------------------- From: [email protected] [mailto:[email protected]] On Behalf Of Lizhong Jin Sent: Friday, May 03, 2013 9:51 PM To: [email protected] Subject: [nvo3] The packet sequence problem in NVO3 Hi all, Recently, I found the packet sequence problem in openVswitch(with VXLAN), please refer to the detail http://openvswitch.org/pipermail/discuss/2012-April/007002.html. Although this is caused by the specific openvswitch implementation, but such kind of implementation does gain better performance, while the side effect is the sequence problem. Then I suggest to consider the sequence requirement in NVO3-dataplane, and try to provide some solutions in the later stage. Regards Lizhong
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
