SCTP Discussions

Text archives Help


Re: [SCTP-Discussion] Shutdown


Chronological Thread 
  • From: Michael Tuexen <Michael.Tuexen AT micmac.franken.de>
  • To: Karel Zabloudil <karel.zabloudil AT sde.cz>
  • Cc: discussion AT sctp.de
  • Subject: Re: [SCTP-Discussion] Shutdown
  • Date: Fri Feb 24 11:22:02 2006
  • List-id: SCTP Discussions <discussion.sctp.de>

Hi Karel,

see my comments in-line.

Best regards
Michael

On Feb 24, 2006, at 10:55 Uhr, Karel Zabloudil wrote:

Michael,

can we avoid this ? if we call sctp_receiveUnacked/Unsent we get
the SCTP_WRONG_STATE error.
Yes, you can only call that in the CLOSED state.

I'm not sure, but what happens if you ABORT the association (sctp_abort)?

thanks,
Karel

On Thu, 23 Feb 2006, Michael Tuexen wrote:
Hi Karel,

the sctplib should wait for all DATA to be SACKed and then
send the SHUTDOWN. This is required by the SCTP state engine.

Best regards
Michael

On Feb 23, 2006, at 16:56 Uhr, Karel Zabloudil wrote:

and if it waits for ACKs, is it possible do discard any unsent
and unacked data so the SCTP library sends the SHUTDOWN imediatelly ?
thanks
Karel
On Thu, 23 Feb 2006, Karel Zabloudil wrote:
we control the size of send queue. the queue is full because the remote
end does not read. we call the sctp_shutdown.
is the shutdown send immediatelly or does SCTP library wait for ACKs
for already sent chunks ?
thanks
Karel Zabloudil
_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion
_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion

_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion







Archive powered by MHonArc 2.6.19+.

Top of page