Re: [nvo3] Review of draft-dt-nvo3-encap-01

2017-05-06 Thread Tom Herbert
- The combinatorics of TLVs and sequential processing requirements are hard to make efficient in both software and hardware implementations. Bit-fields do not have this problem DT: This is not true according to the HW vendors presented in the design team. So the long standing known

Re: [nvo3] Review of draft-dt-nvo3-encap-01

2017-05-06 Thread Tom Herbert
- As I mentioned in a rebuttal to this objection the flag-fields can be extended with for flags. This has already been implemented, the objection is not valid. DT: We are documenting the concerns based on what is already out there – a mailing list rebuttal or how it can be sorted out with “this

Re: [nvo3] One comment for draft-dt-nvo3-encap-01

2017-05-06 Thread Tom Herbert
On Sat, May 6, 2017 at 9:05 AM, Greg Mirsky wrote: > Hi Tom and Lizhong, > I the strongest terms agree with your view that intermediate nodes should > not use DPI to do flow steering. Decisions should be based on information > expressed in the transport layer, not derived

Re: [nvo3] One comment for draft-dt-nvo3-encap-01

2017-05-06 Thread Tom Herbert
On Sat, May 6, 2017 at 9:15 AM, lizho.jin wrote: > Tom, see inline below. > > > Regards > Lizhong > > On 05/6/2017 23:45，Tom Herbert wrote： > > On Sat, May 6, 2017 at 8:37 AM, lizho.jin wrote: >> I am not referring RSS, but RFS with

Re: [nvo3] One comment for draft-dt-nvo3-encap-01

2017-05-06 Thread lizho.jin
Tom, see inline below. RegardsLizhong On 05/6/2017 23:45，Tom Herbert wrote： On Sat, May 6, 2017 at 8:37 AM, lizho.jin  wrote: > I am not referring RSS, but RFS 

Re: [nvo3] One comment for draft-dt-nvo3-encap-01

2017-05-06 Thread Greg Mirsky
Hi Tom and Lizhong, I the strongest terms agree with your view that intermediate nodes should not use DPI to do flow steering. Decisions should be based on information expressed in the transport layer, not derived from the payload. Otherwise, active OAM cannot be viewed as in-band thus making

Re: [nvo3] One comment for draft-dt-nvo3-encap-01

2017-05-06 Thread Tom Herbert
On Sat, May 6, 2017 at 8:37 AM, lizho.jin wrote: > I am not referring RSS, but RFS with HW acceleration. What I > > proposed is to use hash value instead of 5-tuple to do flow steering. > RFS works as is also. The only requirement for RFS is that the hash is reasonably

Re: [nvo3] One comment for draft-dt-nvo3-encap-01

2017-05-06 Thread lizho.jin
I am not referring RSS, but RFS with HW acceleration. What I proposed is to use hash value instead of 5-tuple to do flow steering.Sorry for the misunderstanding. RegardsLizhong On 05/6/2017 23:24，Tom

Re: [nvo3] One comment for draft-dt-nvo3-encap-01

2017-05-06 Thread Tom Herbert
On Fri, May 5, 2017 at 6:39 PM, lizho.jin wrote: > Tom, thanks for the reply, see inline below. > > Regards > Lizhong > > On 05/6/2017 00:14，Tom Herbert wrote： > > [Lizhong] Total option length will not solve the parser buffer issue. > The parser buffer