lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 15 Oct 2019 17:56:39 -0700 (PDT) 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: [PATCHv3 net-next 0/5] sctp: update from rfc7829 From: Xin Long <lucien.xin@...il.com> Date: Mon, 14 Oct 2019 14:14:43 +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 I would like to see some SCTP expert ACKs here. Thank you.
Powered by blists - more mailing lists