Indeed, so the question is what we want to achieve short/long term. From: AshwoodsmithPeter [mailto:[email protected]] Sent: woensdag 23 mei 2012 21:41 To: Henderickx, Wim (Wim); Carlos Pignataro; Balus, Florin Stelian (Florin) Cc: LASSERRE, MARC (MARC); Lizhong Jin; [email protected]; [email protected] Subject: RE: [nvo3] New dataplane requirements draft
Well that's the key point really. VXLAN puts its entropy in the normal 5 tuple and NVGRE either requires the intermediate hardware to look at the KEY for entropy, or it has to use additional V4 addresses for the outer header, or it has to use V6 and a flow label. Peter ________________________________ From: Henderickx, Wim (Wim) [mailto:[email protected]] Sent: Wednesday, May 23, 2012 3:35 PM To: Carlos Pignataro; Balus, Florin Stelian (Florin) Cc: LASSERRE, MARC (MARC); Lizhong Jin; [email protected]; [email protected]; AshwoodsmithPeter Subject: RE: [nvo3] New dataplane requirements draft I believe there are multiple ways to solve the hashing with GRE, but if you look at requirements do we need to make this work across existing HW w/o extensions or not. If so the solution set becomes limited. From: [email protected] [mailto:[email protected]] On Behalf Of Carlos Pignataro Sent: woensdag 23 mei 2012 21:31 To: Balus, Florin Stelian (Florin) Cc: LASSERRE, MARC (MARC); Lizhong Jin; [email protected]; [email protected]; AshwoodsmithPeter Subject: Re: [nvo3] New dataplane requirements draft On May 23, 2012, at 1:20 PM, Balus, Florin Stelian (Florin) wrote: Peter, We were not trying to exclude any solutions, we tried to really focus on what the requirements should be. Note that the text does not exclude NVGRE anyhow.. We said "...and/or tunnelling methods" and I believe there was a NVGRE thread on this list where the authors discussed how this can be done using tunneling header. There was also some hall discussion in IETF on how this can be done with part of a GRE key. One way is described in http://tools.ietf.org/html/rfc5640 in the context of tunneling for softwires. Thanks, -- Carlos. On the other hand we would like to hear from cloud providers on this: i.e. Is it a MUST or a SHOULD? Florin On May 23, 2012, at 8:38 AM, "AshwoodsmithPeter" <[email protected]<mailto:[email protected]>> wrote: In section 3.3.2.1 LAG and ECMP "encpsulation headers and/or tunneling methods MUST contain a 'entropy field' or 'entropy label' " This of course explicitly excludes NVGRE. I suppose for VXLAN the UDP SourcePort would be considered the entropy field. Was it the intention to exclude NVGRE? Peter _______________________________________________ nvo3 mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
