[EMAIL PROTECTED] writes:
> I admit there could be people who wants to use:
> - multiple flows (= multiple flow label value) in a single TCP session
That doesn't make much sense to me. A TCP connection is by definition
a single flow (or two, if you count directions). Hmm. Or more
precisely, it doesn't make sense to switch back and forth between
several flow-labels on the same tcp connection, but it might make
sense to switch to a _new_ flow-label.
Then one views the connection as a sequence of different flows, but
*not* as several flows that are in some way parallell or independent.
> - multiple TCP sessions with single flow label value
That makes sense, even if I have no idea if it is actually useful.
> however, I could not find a good (a simple and usable) UNIX API to make
> the above option happen, so I simplified the story.
> At least, the latter case can easily be handled by "single TCP session
> per single flow label".
What about associating a flow-label with each open socket (which is
used for all outgoing packets), and supporting these three operations:
1. Make up a new, unique, flow-label and associate it with the given
socket.
2. Copy the flow-label association from one socket to another.
3. Reset the flow-label for a socket to zero.
I think you could do each of those as a ioctl or setsockopt or
something.
This way, applications never see the actual flow-label values, and the
network code always knows which flow-labels are in use and which are
dead.
/Niels
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
