I think in the end this is an argument about nothing.
> This implies that IPv6 nodes SHOULD NOT establish any
> flow-specific state unless so instructed by a specific flow state establishment
>method.
>
What Margaret and itojun refer to are flow state establishment methods that
happen to co
Margaret,
The draft explicitly states that each transport connection SHOULD be labeled, and
explicitly mentions labeling enabling load-balancing that you described.
So I do not think there is any conflict with the intent of the authors (and the text)
and the uses you describe.
The intent of t
Itojun,
Let's agree first what the "SHOULD NOT" applies to, see my response to Margaret.
Anyway, we have explicitly tried to encourage KAME-style flow labeling as the default
by the IPv6 stacks. But obviously there still are some details to get cleared up to
avoid ambiguous interpretation of t
Robert Elz <[EMAIL PROTECTED]> writes:
> Date:Wed, 31 Jul 2002 15:12:18 -0400
> From:Thomas Narten <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> | Section 4 has some "mays", some of which might better be
> | should/SHOULDs. I.e., an admin SHOULD set a l
The following is an example from R Stevens book "UNP". I am having difficulties
with the code shown below.
When I try to compile it using..
gcc tcp_connect.c -lsocket -lnsl -lresolv -lc
I get the following error messages
baja{shroff}% gcc tcp_connect.c -lsocke
Thanks for your reply. I included the defination when i added again i got the
following message:
baja{shroff}% gcc tcp_connect.c -lsocket -lnsl -lresolv -lc
Undefined first referenced
symbol in file
getaddrinfo /var/tmp/
>we might have the following choices (I can't think of other combinations that
>make sense to me):
>1. all are optional
>2. load sharing is mandatory; others are optional
>3. load sharing and router preferences are mandatory; more specific is
>optional
>4. all are mandatory
The current proposa
>The following is an example from R Stevens book "UNP". I am having difficulties
>with the code shown below.
the book has more than a couple of errors in IPv6 section, so be
warned...
>When I try to compile it using..
> gcc tcp_connect.c -lsocket -lnsl -lresolv -lc
>I
