Lines Matching full:shutdown
201 * Process the final SHUTDOWN COMPLETE.
204 * Upon reception of the SHUTDOWN COMPLETE chunk the endpoint will verify
205 * that it is in SHUTDOWN-ACK-SENT state, if it is not the chunk should be
206 * discarded. If the endpoint is in the SHUTDOWN-ACK-SENT state the endpoint
207 * should stop the T2-shutdown timer and remove all knowledge of the
211 * C) Rules for packet carrying SHUTDOWN COMPLETE:
213 * - The receiver of a SHUTDOWN COMPLETE shall accept the packet
221 * SHUTDOWN COMPLETE if it is not in the SHUTDOWN-ACK-SENT state.
246 * SHUTDOWN COMPLETE with any other chunks. in sctp_sf_do_4_C()
258 * H) SHUTDOWN COMPLETE notification in sctp_sf_do_4_C()
260 * When SCTP completes the shutdown procedures (section 9.2) this in sctp_sf_do_4_C()
269 /* Upon reception of the SHUTDOWN COMPLETE chunk the endpoint in sctp_sf_do_4_C()
270 * will verify that it is in SHUTDOWN-ACK-SENT state, if it is in sctp_sf_do_4_C()
272 * the SHUTDOWN-ACK-SENT state the endpoint should stop the in sctp_sf_do_4_C()
273 * T2-shutdown timer and remove all knowledge of the in sctp_sf_do_4_C()
331 * SHUTDOWN COMPLETE with any other chunks. in sctp_sf_do_5_1B_init()
533 * SHUTDOWN COMPLETE with any other chunks. in sctp_sf_do_5_1C_ack()
1425 * Note: Do not use in CLOSED or SHUTDOWN-ACK-SENT state.
1447 * COOKIE-WAIT and SHUTDOWN-ACK-SENT in sctp_tietags_populate()
1527 * SHUTDOWN COMPLETE with any other chunks. in sctp_sf_do_unexpected_init()
1889 /* If the endpoint is in the SHUTDOWN-ACK-SENT state and recognizes in sctp_sf_do_dupcook_a()
1891 * association but instead resend the SHUTDOWN ACK and send an ERROR in sctp_sf_do_dupcook_a()
1949 * transition to ESTABLISHED. Instead trigger SHUTDOWN in sctp_sf_do_dupcook_a()
2329 * Process an ABORT. (SHUTDOWN-PENDING state)
2375 * Process an ABORT. (SHUTDOWN-SENT state)
2417 /* Stop the T2-shutdown timer. */ in sctp_sf_shutdown_sent_abort()
2421 /* Stop the T5-shutdown guard timer. */ in sctp_sf_shutdown_sent_abort()
2429 * Process an ABORT. (SHUTDOWN-ACK-SENT state)
2442 * common function with the SHUTDOWN-SENT state. in sctp_sf_shutdown_ack_sent_abort()
2822 * Upon the reception of the SHUTDOWN, the peer endpoint shall
2823 * - enter the SHUTDOWN-RECEIVED state,
2829 * SHUTDOWN sender.
2831 * Once an endpoint as reached the SHUTDOWN-RECEIVED state it MUST NOT
2832 * send a SHUTDOWN in response to a ULP request. And should discard
2833 * subsequent SHUTDOWN chunks.
2835 * If there are still outstanding DATA chunks left, the SHUTDOWN
2838 * are acknowledged; however, the SHUTDOWN receiver MUST NOT accept
2868 /* Make sure that the SHUTDOWN chunk has a valid length. */ in sctp_sf_do_9_2_shutdown()
2894 * When a peer sends a SHUTDOWN, SCTP delivers this notification to in sctp_sf_do_9_2_shutdown()
2904 /* Upon the reception of the SHUTDOWN, the peer endpoint shall in sctp_sf_do_9_2_shutdown()
2905 * - enter the SHUTDOWN-RECEIVED state, in sctp_sf_do_9_2_shutdown()
2924 * received by the SHUTDOWN sender. in sctp_sf_do_9_2_shutdown()
2936 * Once an endpoint has reached the SHUTDOWN-RECEIVED state,
2937 * it MUST NOT send a SHUTDOWN in response to a ULP request.
2938 * The Cumulative TSN Ack of the received SHUTDOWN chunk
2956 /* Make sure that the SHUTDOWN chunk has a valid length. */ in sctp_sf_do_9_2_shut_ctsn()
2980 * received by the SHUTDOWN sender. in sctp_sf_do_9_2_shut_ctsn()
2989 * If an endpoint is in SHUTDOWN-ACK-SENT state and receives an INIT chunk
2990 * (e.g., if the SHUTDOWN COMPLETE was lost) with source and destination
2993 * retransmit the SHUTDOWN ACK chunk.
3011 * the SHUTDOWN ACK. in __sctp_sf_do_9_2_reshutack()
3017 /* Set the transport for the SHUTDOWN ACK chunk and the timeout for in __sctp_sf_do_9_2_reshutack()
3018 * the T2-SHUTDOWN timer. in __sctp_sf_do_9_2_reshutack()
3022 /* and restart the T2-shutdown timer. */ in __sctp_sf_do_9_2_reshutack()
3298 * (4) In SHUTDOWN-SENT state the endpoint MUST acknowledge any received
3353 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately in sctp_sf_eat_data_fast_4_4()
3355 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer in sctp_sf_eat_data_fast_4_4()
3597 * Process an inbound SHUTDOWN ACK.
3600 * Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall
3601 * stop the T2-shutdown timer, send a SHUTDOWN COMPLETE chunk to its
3624 /* 10.2 H) SHUTDOWN COMPLETE notification in sctp_sf_do_9_2_final()
3626 * When SCTP completes the shutdown procedures (section 9.2) this in sctp_sf_do_9_2_final()
3634 /* ...send a SHUTDOWN COMPLETE chunk to its peer, */ in sctp_sf_do_9_2_final()
3644 /* Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall in sctp_sf_do_9_2_final()
3645 * stop the T2-shutdown timer, in sctp_sf_do_9_2_final()
3672 * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3673 * respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3674 * When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3676 * packet with the Verification Tag received in the SHUTDOWN ACK and
3764 * Handle an "Out of the blue" SHUTDOWN ACK.
3768 * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3769 * respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3770 * When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3772 * packet with the Verification Tag received in the SHUTDOWN ACK and
3831 * Handle SHUTDOWN ACK in COOKIE_ECHOED or COOKIE_WAIT state.
3833 * Verification Tag: 8.5.1 E) Rules for packet carrying a SHUTDOWN ACK
4322 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately in sctp_sf_eat_fwd_tsn_fast()
4324 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer in sctp_sf_eat_fwd_tsn_fast()
4896 * SHUTDOWN-COMPLETE, our peer is clearly violating the "MUST NOT bundle"
5099 * Process the SHUTDOWN primitive.
5102 * C) Shutdown
5104 * Format: SHUTDOWN(association id)
5134 /* From 9.2 Shutdown of an Association in sctp_sf_do_9_2_prm_shutdown()
5135 * Upon receipt of the SHUTDOWN primitive from its upper in sctp_sf_do_9_2_prm_shutdown()
5136 * layer, the endpoint enters SHUTDOWN-PENDING state and in sctp_sf_do_9_2_prm_shutdown()
5255 * state table when someone issues a shutdown while in COOKIE_WAIT state.
5290 * state table when someone issues a shutdown while in COOKIE_ECHOED state.
5393 * state table when someone issues an abort while in SHUTDOWN-PENDING state.
5406 /* Stop the T5-shutdown guard timer. */ in sctp_sf_shutdown_pending_prm_abort()
5420 * state table when someone issues an abort while in SHUTDOWN-SENT state.
5433 /* Stop the T2-shutdown timer. */ in sctp_sf_shutdown_sent_prm_abort()
5437 /* Stop the T5-shutdown guard timer. */ in sctp_sf_shutdown_sent_prm_abort()
5465 * common function with the SHUTDOWN-SENT state. in sctp_sf_shutdown_ack_sent_prm_abort()
5604 * Start the shutdown negotiation.
5608 * shall send a SHUTDOWN chunk to its peer including in the Cumulative
5610 * It shall then start the T2-shutdown timer and enter the SHUTDOWN-SENT
5611 * state. If the timer expires, the endpoint must re-send the SHUTDOWN
5627 * endpoint shall send a SHUTDOWN chunk to its peer including in sctp_sf_do_9_2_start_shutdown()
5635 /* Set the transport for the SHUTDOWN chunk and the timeout for the in sctp_sf_do_9_2_start_shutdown()
5636 * T2-shutdown timer. in sctp_sf_do_9_2_start_shutdown()
5640 /* It shall then start the T2-shutdown timer */ in sctp_sf_do_9_2_start_shutdown()
5645 * The sender of the SHUTDOWN MAY also start an overall guard timer in sctp_sf_do_9_2_start_shutdown()
5646 * 'T5-shutdown-guard' to bound the overall time for shutdown sequence. in sctp_sf_do_9_2_start_shutdown()
5655 /* and enter the SHUTDOWN-SENT state. */ in sctp_sf_do_9_2_start_shutdown()
5661 * HEARTBEAT ... is discontinued after sending either SHUTDOWN in sctp_sf_do_9_2_start_shutdown()
5662 * or SHUTDOWN-ACK. in sctp_sf_do_9_2_start_shutdown()
5675 * Generate a SHUTDOWN ACK now that everything is SACK'd.
5679 * If it has no more outstanding DATA chunks, the SHUTDOWN receiver
5680 * shall send a SHUTDOWN ACK and start a T2-shutdown timer of its own,
5681 * entering the SHUTDOWN-ACK-SENT state. If the timer expires, the
5682 * endpoint must re-send the SHUTDOWN ACK.
5698 * 1) called in response to a SHUTDOWN chunk in sctp_sf_do_9_2_shutdown_ack()
5709 /* Make sure that the SHUTDOWN chunk has a valid length. */ in sctp_sf_do_9_2_shutdown_ack()
5716 /* If it has no more outstanding DATA chunks, the SHUTDOWN receiver in sctp_sf_do_9_2_shutdown_ack()
5717 * shall send a SHUTDOWN ACK ... in sctp_sf_do_9_2_shutdown_ack()
5723 /* Set the transport for the SHUTDOWN ACK chunk and the timeout for in sctp_sf_do_9_2_shutdown_ack()
5724 * the T2-shutdown timer. in sctp_sf_do_9_2_shutdown_ack()
5728 /* and start/restart a T2-shutdown timer of its own, */ in sctp_sf_do_9_2_shutdown_ack()
5736 /* Enter the SHUTDOWN-ACK-SENT state. */ in sctp_sf_do_9_2_shutdown_ack()
5742 * HEARTBEAT ... is discontinued after sending either SHUTDOWN in sctp_sf_do_9_2_shutdown_ack()
5743 * or SHUTDOWN-ACK. in sctp_sf_do_9_2_shutdown_ack()
5807 * shutdown guard timer to give the receiver one last in sctp_sf_do_6_3_3_rtx()
6010 /* RFC2960 9.2 If the timer expires, the endpoint must re-send the SHUTDOWN
6014 * SHUTDOWN chunk to the protocol parameter 'Association.Max.Retrans'.
6020 * the T2-Shutdown timer, giving its peer ample opportunity to transmit
6068 * If we remove the transport an SHUTDOWN was last sent to, don't in sctp_sf_t2_timer_expire()
6075 /* Set the transport for the SHUTDOWN/ACK chunk and the timeout for in sctp_sf_t2_timer_expire()
6076 * the T2-shutdown timer. in sctp_sf_t2_timer_expire()
6080 /* Restart the T2-shutdown timer. */ in sctp_sf_t2_timer_expire()
6161 * The sender of the SHUTDOWN MAY also start an overall guard timer
6162 * 'T5-shutdown-guard' to bound the overall time for shutdown sequence.
6199 * the association is automatically closed by starting the shutdown process.
6200 * The work that needs to be done is same as when SHUTDOWN is initiated by
6215 /* From 9.2 Shutdown of an Association in sctp_sf_autoclose_timer_expire()
6216 * Upon receipt of the SHUTDOWN primitive from its upper in sctp_sf_autoclose_timer_expire()
6217 * layer, the endpoint enters SHUTDOWN-PENDING state and in sctp_sf_autoclose_timer_expire()