SCTP Quick failover draft section 5.1, point 5 has been removed from rfc7829. Instead, "the sender SHOULD (i) notify the Upper Layer Protocol (ULP) about this state transition", as said in section 3.2, point 8. So this patch is to add SCTP_ADDR_POTENTIALLY_FAILED, defined in section 7.1, "which is reported if the affected address becomes PF". Also remove transport cwnd's update when moving from PF back to ACTIVE , which is no longer in rfc7829 either. Note that ulp_notify will be set to false if asoc->expose is not 'enabled', according to last patch. v2->v3: - define SCTP_ADDR_PF SCTP_ADDR_POTENTIALLY_FAILED. v3->v4: - initialize spc_state with SCTP_ADDR_AVAILABLE, as Marcelo suggested. - check asoc->pf_expose in sctp_assoc_control_transport(), as Marcelo suggested.
Showing the changes to include/uapi/linux (1 of 2 files). Show all
Unified · Split
| @@ -410,6 +410,8 @@ enum sctp_spc_state { · 409 unmodified lines | |||
| 410 | SCTP_ADDR_ADDED, | 410 | SCTP_ADDR_ADDED, |
| 411 | SCTP_ADDR_MADE_PRIM, | 411 | SCTP_ADDR_MADE_PRIM, |
| 412 | SCTP_ADDR_CONFIRMED, | 412 | SCTP_ADDR_CONFIRMED, |
| 413 | SCTP_ADDR_POTENTIALLY_FAILED, | ||
| 414 | #define SCTP_ADDR_PF SCTP_ADDR_POTENTIALLY_FAILED | ||
| 413 | }; | 415 | }; |
| 414 | 416 | ||
| 415 | 417 | ||