-
sctp
SCTP Discussions
Text archives Help
- From: "buskila@gmail,com" <buskila AT gmail.com>
- To: <discussion AT sctp.de>
- Subject: [SCTP-Discussion] Peer restart question
- Date: Tue Aug 15 05:53:24 2006
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=mniKP8C7OXCxYcdcO83ehX9KBHb9G2RbNTp9kKkWOS4niMWMCACXCRlAKmSRD9UEBMoInoY+jyW+t20Z8VONdZXuAjm/efWdtcITJwll/vC8AcZfX5po/BcHL3UjgI1HfD92a3/MbSc9BMPTq4SAojWFDEo9XLKOiyNX/dvZybg=
- List-id: SCTP Discussions <discussion.sctp.de>
Hello
I'm receiving the RESTART notification from the
SCTP stack. The scenario is this:
0) Association is established between A and
B
1) Side B calls sctp_shutdown, but the call is
manually deferred right after the function returns (the association stated
changes to SHUTDOWNSENT)
2) Side A crashes ungracefully
3) Side A restarts and initiates the association to
B using the same source and destination ports
4) Side B continues and the ULP receives the
RESTART notification
I was wondering if this is the correct behavior.
The RFC states (in 5.2.4) that the restart rules apply in any state, however in
this case it does not make much sense.
Any suggestions?
thanks
oleg
- [SCTP-Discussion] Peer restart question, buskila@gmail,com, 08/14/2006
- Re: [SCTP-Discussion] Peer restart question, Michael Tuexen, 08/15/2006
Archive powered by MHonArc 2.6.19+.
