> hello, I'm having hard time trying to remember sin6_flowinfo semantics.
> RFC2553/2292 are not very clear to me. for example, could someone
> answer these questions?
> (1) on recvfrom, how sin6_flowinfo should be filled?
> (2) on sendto, how will the kernel interpret sin6_flowinfo from the
> userland?
> (3) any other interface to manipulate traffic class/flow label?
more questions (I could not find answer from my archive):
(4) what happens if we connect(2) with sin6_flowinfo filled?
my guess is that sin6_flowinfo sticks into pcb, and
will be attached to every packet we will send.
(5) what happens if we bind(2) with sin6_flowinfo filled?
my guess is (a) to raise some error, or (b) accept packets
only if they carry specified ip6->ip6_flow field.
(6) what is the endian of sin6_flowinfo?
I guess it is network byte order, since it appears on the wire.
(7) what happens if the peer transmits packets with ip6->ip6_flow set,
and it is connection oriented socket (SOCK_STREAM)?
itojun
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
