rfc_6458_sctp_socket_api_issues
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| rfc_6458_sctp_socket_api_issues [2020/04/20 15:36] – tuexen | rfc_6458_sctp_socket_api_issues [2020/04/20 15:42] (current) – tuexen | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Section 3.2 Non-Blocking Mode | Section 3.2 Non-Blocking Mode | ||
| - | * ... by the SCTP_ASSOC_CHANGE event with SCTP_COMM_UP or SCTP_CANT_START_ASSOC. If user data could not be sent (due to an SCTP_CANT_START_ASSOC), | + | * ... by the '' |
| * [[https:// | * [[https:// | ||
| Section 6.1.1 SCTP_ASSOC_CHANGE | Section 6.1.1 SCTP_ASSOC_CHANGE | ||
| - | * sac_info: If sac_state is SCTP_COMM_LOST or SCTP_CANT_STR_ASSOC and an ABORT chunk was... | + | * '' |
| * [[https:// | * [[https:// | ||
| Section 6.1.2 SCTP_PEER_ADDR_CHANGE | Section 6.1.2 SCTP_PEER_ADDR_CHANGE | ||
| - | * spc_state: A definition for SCTP_ADDR_CONFIRMED is missing. This is supported by FreeBSD and Linux, not by Solaris (yet). | + | * '' |
| * [[https:// | * [[https:// | ||
| Section 6.1.7 SCTP_PARTIAL_DELIVERY_EVENT | Section 6.1.7 SCTP_PARTIAL_DELIVERY_EVENT | ||
| - | * uint16_t pdapi_stream; | + | * '' |
| - | * uint16_t pdapi_seq; | + | * '' |
| + | * Linux and Solaris implement it using '' | ||
| Section 8.2.1 SCTP_STATUS | Section 8.2.1 SCTP_STATUS | ||
| - | * SCTP_BOUND doesn' | + | * '' |
| * [[https:// | * [[https:// | ||
| Section 9.5 sctp_getladdrs() | Section 9.5 sctp_getladdrs() | ||
| - | * If the id field is set to the value SCTP_FUTURE_ASSOC, | + | * If the '' |
| * [[https:// | * [[https:// | ||
rfc_6458_sctp_socket_api_issues.1587397015.txt.gz · Last modified: by tuexen
