From: Kacheong Poon <ka-cheong.poon@oracle.com>
To: linux-sctp@vger.kernel.org
Subject: Re: Inconsistency in spinfo_state between Linux and FreeBSD sctp
Date: Thu, 20 Jan 2011 04:41:11 +0000 [thread overview]
Message-ID: <4D37BCE7.7070806@oracle.com> (raw)
In-Reply-To: <20110119232732.1605564zwkq5jj9w@webmail.tuwien.ac.at>
On 01/20/11 06:27 AM, Schoch Christian wrote:
> I could figure a problem with spinfo_state between Linux and FreeBSD
> sctp stack.
>
> While in linux stack the return value of spinfo_state is defined as enum
> with four items, FreeBSD defines a lot more states. The problem is that
> these values do not match with each other. For example if FreeBSD means
> INACTIVE this value in linux results in UNCONFIRMED.
>
> In sctp socket api these states are namely defined but not assoziated
> with any value.
>
> Is there any possibility to standardize these values ??
In version 25 of the draft, there are 3 defined values for
spinfo_state, which are
SCTP_UNCONFIRMED: The initial state of a peer address.
SCTP_ACTIVE: The state is entered the first time after path
verification. It can also be entered if the state is
SCTP_INACTIVE and the path supervision detects that the peer
address is reachable again.
SCTP_INACTIVE: This state is entered whenever a path failure is
detected.
The above values should be used. App should not use actual integer
value in the code.
What is your reason that actual integer values are needed?
--
K. Poon.
ka-cheong.poon@oracle.com
next prev parent reply other threads:[~2011-01-20 4:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 22:27 Inconsistency in spinfo_state between Linux and FreeBSD sctp Schoch Christian
2011-01-20 4:41 ` Kacheong Poon [this message]
2011-01-20 7:53 ` Randy Stewart
2011-01-20 7:57 ` Michael Tuexen
2011-01-20 8:01 ` Randy Stewart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D37BCE7.7070806@oracle.com \
--to=ka-cheong.poon@oracle.com \
--cc=linux-sctp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.