[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54C6418E.1010408@redhat.com>
Date: Mon, 26 Jan 2015 14:30:54 +0100
From: Daniel Borkmann <dborkman@...hat.com>
To: Sun Paul <paulrbk@...il.com>
CC: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
Michael Tuexen <tuexen@...muenster.de>,
Vlad Yasevich <vyasevich@...il.com>,
linux-sctp@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Question on SCTP ABORT chunk is generated when the association_max_retrans
is reached
On 01/26/2015 02:17 PM, Sun Paul wrote:
> When an ABORT is sent to side-A, side-A INIT a new connection again.
Even if the ABORT is not being sent, the peer (the one who would send
his ABORT) closes the TCB from his side silently then. Any messages that
would afterwards arrive on this dead connection would be answered with
an oob ABORT just as well. I'm still missing the bigger picture on your
use-case scenario here, I guess ... why is the recommended rtx limit not
sufficient?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists