From: Vlad Yasevich <vyasevich@gmail.com>
To: David Laight <David.Laight@ACULAB.COM>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: SCTP connect() both ways
Date: Mon, 09 Jun 2014 14:40:55 -0400 [thread overview]
Message-ID: <5395FFB7.4060604@gmail.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1725978A@AcuExch.aculab.com>
On 06/09/2014 05:41 AM, David Laight wrote:
> When SCTP is used for protocols like M3UA it seems common
> to configure both port numbers for a connection (typically
> to the same value).
>
> Rather than having one system call connect() and the other
> listen(), both systems really want to try to establish the
> connection by sending out INIT chunks.
The correct way to do this is to not used connect() call.
Both systems should do a listen() and then use an implicit
connect by using an sctp_sendmsg() or similar calls to
send the data.
>
> The connection then gets established as soon as the second of the
> two systems attempts to establish it.
>
> However if the remote system responds with an ABORT (or maybe
> an ICMP error is received) the Linux SCTP stack immediately
> reports 'connect failed'.
> For these sorts of connections it would be much better if the
> received ABORT just increased the retry timer to large value.
>
> Thoughts?
We don't know why the remote ABORTED. There could be a lot of
reasons. It is up to the application to retry. This is no
different then receiving an RST in response to a SYN.
-vlad
>
> David
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-06-09 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 9:41 SCTP connect() both ways David Laight
2014-06-09 18:40 ` Vlad Yasevich [this message]
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=5395FFB7.4060604@gmail.com \
--to=vyasevich@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).