It's a matter of interpretation (you could ask the same question about some ways of using the flow label for diffserv classification).
In my interpretation, a server load balancing mechanism that recognizes and caches new labels is a flow state establishment method. Brian Thomas Narten wrote: > > > "The method by which the flow state is cleared from the IPv6 nodes > > is to be defined by the flow state establishment method used to set > > up the state. This implies that IPv6 nodes unable to classify a > > packet to an existing flow SHOULD NOT establish any flow-specific > > state unless so instructed by a flow state establishment > > method. With some flow state establishment methods, signaling new > > state simultaneously clearing the old state from the new path may be > > sufficient. A mechanism with a sufficiently long timeout period > > before reusing the Flow Label values can also be used." > > How does the above text relate to the idea (which I thought the WG was > interested in) in allowing the Flow Label field to be used for load > balancing (i.e., hash the src/dest/label to select the next-hop when > there are more than one). Seems like load balancing might not be > allowed by the above wording. Is that the intent? > > Note in the case of simple load balancing, there is no flow state > establishment method. > > Thomas -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
