Hi Marc,
I am fine with that. Thanks.

Regards
Lizhong

在 2013-5-7 上午12:12,"LASSERRE, MARC (MARC)" <[email protected]
>写道:
>
> Lizhong,
>
> As already mentioned by others, this is not a hard requirement.
>
> If deemed useful, we can add in the DP reqs that packet re-ordering
issues SHOULD be avoided.
>
> Marc
>
>> ________________________________
>> From: [email protected] [mailto:[email protected]] On Behalf Of
Lizhong Jin
>> Sent: Monday, May 06, 2013 4:46 AM
>>
>> To: Black, David
>> Cc: [email protected]
>> Subject: Re: [nvo3] The packet sequence problem in NVO3
>>
>> Thanks David.
>> Since the draft-ietf-nvo3-dataplane-requirements is already a WG draft,
we need the WG consensus to add this new requirement.
>> Any solutions deployed with openvswitch should care about the potential
influence of packet out-of-order.
>>
>> Regards
>> Lizhong
>>
>>
>>
>> On Mon, May 6, 2013 at 3:42 AM, Black, David <[email protected]> wrote:
>>>
>>> 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

Reply via email to