dwcarder / draft-cc-v6ops-wlcg-flow-label-marking

0 stars 2 forks source link

VMware issue #29

Open timchown opened 1 year ago

timchown commented 1 year ago

Should we add a note about the cause of this, and note that load balancing is dependent on proper use of the flow label (not stopping at the flow label)?

Brian's comment: "Because the 3-tuple {dest address, source address, flow label} is exactly what is needed to distinguish "L4 flows between two given IPv6 addresses", so they must mean something else. RFC7098 discusses this issue at length. In fact, you shouldn't stop at the flow label, you should include the flow label to get a useful hash for L4 load balancing."