Jun-ichiro itojun Hagino wrote:
>
> >> except for IP address, they may be embedded into ESP, or may be buried
> >> in IP header chain. so for efficient router operation we need to
> >> use flow label, which will effectively give us the following 3 items
> >> (depending on the definition of "flow"):
> >> - layer 4 port number pair
> >> - protocol type
> >Only if we define a standard way of compressing the ports and protocol type
> >into the flow label.
>
> i don't think there needs to be a standard way. if there's some
> pseudorandom and unique number in flow label field (as suggested in
> RFC2460) it is more than enough.
No, not for diffserv and not for any solution where intserv is used only
somewhere downstream from the host. The classifier needs something
that *encodes* the ports and protocol, so that a QOS policy can
be applied. That's how QOS classifiers work; they can't use pseudorandom
numbers.
Brian
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
