From: David Miller <davem@davemloft.net>
To: lucien.xin@gmail.com
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
marcelo.leitner@gmail.com, nhorman@tuxdriver.com,
david.laight@aculab.com
Subject: Re: [PATCHv4 net-next 0/5] sctp: update from rfc7829
Date: Fri, 08 Nov 2019 14:18:51 -0800 (PST) [thread overview]
Message-ID: <20191108.141851.574550170546220386.davem@davemloft.net> (raw)
In-Reply-To: <cover.1573190212.git.lucien.xin@gmail.com>
From: Xin Long <lucien.xin@gmail.com>
Date: Fri, 8 Nov 2019 13:20:31 +0800
> SCTP-PF was implemented based on a Internet-Draft in 2012:
>
> https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
>
> It's been updated quite a few by rfc7829 in 2016.
>
> This patchset adds the following features:
>
> 1. add SCTP_ADDR_POTENTIALLY_FAILED notification
> 2. add pf_expose per netns/sock/asoc
> 3. add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt
> 4. add ps_retrans per netns/sock/asoc/transport
> (Primary Path Switchover)
> 5. add spt_pathcpthld for SCTP_PEER_ADDR_THLDS sockopt
>
> v1->v2:
> - See Patch 2/5 and Patch 5/5.
> v2->v3:
> - See Patch 1/5, 2/5 and 3/5.
> v3->v4:
> - See Patch 1/5, 2/5, 3/5 and 4/5.
Series applied, thank you.
prev parent reply other threads:[~2019-11-08 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 5:20 [PATCHv4 net-next 0/5] sctp: update from rfc7829 Xin Long
2019-11-08 5:20 ` [PATCHv4 net-next 1/5] sctp: add pf_expose per netns and sock and asoc Xin Long
2019-11-08 5:20 ` [PATCHv4 net-next 2/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification Xin Long
2019-11-08 5:20 ` [PATCHv4 net-next 3/5] sctp: add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt Xin Long
2019-11-08 5:20 ` [PATCHv4 net-next 4/5] sctp: add support for Primary Path Switchover Xin Long
2019-11-08 5:20 ` [PATCHv4 net-next 5/5] sctp: add SCTP_PEER_ADDR_THLDS_V2 sockopt Xin Long
2019-11-08 22:18 ` David Miller [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=20191108.141851.574550170546220386.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david.laight@aculab.com \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/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).