> -----Original Message----- > From: [email protected] [mailto:[email protected]] On
> If we can count on hosts setting the flow label with suitable > granularity, then we can use the flow label (plus src and dest IPv6 > address) in our ECMP and LAG hashes without having to look > for protocol > and port numbers. That avoids much complexity related to > next headers > and similar problems. And it is not subject to an attack by someone > mis-setting the flow label field. > > The one obvious conclusion here is that if we want hosts to > actually set > flow labels, then we are largely preempting network modification of > those flow labels. Looks to me like this is true as well. In Brian's I-D 02, an edge router at the destination side would be able to tell whether the flow label had been set by a source host or an intervening router. So, that makes flow labels unusable for end-to-end QoS. Question: if we don't want to specify different flow label ranges, e.g. to show whether the lable was set by a host vs the ISP's network, then isn't there a combination of flow label and traffic class that could accomplish this? Something like this could be an option, instead of using the traditional 5-tuples? Bert -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
