>> 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.
itjun
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
- Re: Usage of IPv6 flow label Jim Bound
- Re: Usage of IPv6 flow label Grenville Armitage
- Re: Usage of IPv6 flow label Jim Bound
- Re: Usage of IPv6 flow label Brian E Carpenter
- Re: Usage of IPv6 flow label Francis Dupont
- Re: Usage of IPv6 flow label Jim Bound
- Re: Usage of IPv6 flow label Michael Thomas
- Re: Usage of IPv6 flow label Brian E Carpenter
- Re: Usage of IPv6 flow label Brian E Carpenter
- Re: Usage of IPv6 flow label Alex Conta
- Re: Usage of IPv6 flow label Jun-ichiro itojun Hagino
- Re: Usage of IPv6 flow label Brian E Carpenter
- RE: Usage of IPv6 flow label Christian Huitema
- Re: Usage of IPv6 flow label Brian E Carpenter
- RE: Usage of IPv6 flow label Elwyn Davies
- Re: Usage of IPv6 flow label Alex Conta
- Re: Usage of IPv6 flow label Juan Fco Rodriguez Hervella
- Re: Usage of IPv6 flow label Brian E Carpenter
- Re: Usage of IPv6 flow label Alex Conta
- Re: Usage of IPv6 flow label Brian E Carpenter
- Re: Usage of IPv6 flow label itojun
