[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191108.141851.574550170546220386.davem@davemloft.net>
Date: Fri, 08 Nov 2019 14:18:51 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: lucien.xin@...il.com
Cc: netdev@...r.kernel.org, linux-sctp@...r.kernel.org,
marcelo.leitner@...il.com, nhorman@...driver.com,
david.laight@...lab.com
Subject: Re: [PATCHv4 net-next 0/5] sctp: update from rfc7829
From: Xin Long <lucien.xin@...il.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.
Powered by blists - more mailing lists