188  * Process the final SHUTDOWN COMPLETE.
191  * Upon reception of the SHUTDOWN COMPLETE chunk the endpoint will verify
192  * that it is in SHUTDOWN-ACK-SENT state, if it is not the chunk should be
193  * discarded. If the endpoint is in the SHUTDOWN-ACK-SENT state the endpoint
194  * should stop the T2-shutdown timer and remove all knowledge of the
198  * C) Rules for packet carrying SHUTDOWN COMPLETE:
200  * - The receiver of a SHUTDOWN COMPLETE shall accept the packet
208  *   SHUTDOWN COMPLETE if it is not in the SHUTDOWN-ACK-SENT state.
233 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_4_C()
245 	 * H) SHUTDOWN COMPLETE notification  in sctp_sf_do_4_C()
247 	 * When SCTP completes the shutdown procedures (section 9.2) this  in sctp_sf_do_4_C()
256 	/* Upon reception of the SHUTDOWN COMPLETE chunk the endpoint  in sctp_sf_do_4_C()
257 	 * will verify that it is in SHUTDOWN-ACK-SENT state, if it is  in sctp_sf_do_4_C()
259 	 * the SHUTDOWN-ACK-SENT state the endpoint should stop the  in sctp_sf_do_4_C()
260 	 * T2-shutdown timer and remove all knowledge of the  in sctp_sf_do_4_C()
323 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_5_1B_init()
519 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_5_1C_ack()
1366  * Note: Do not use in CLOSED or SHUTDOWN-ACK-SENT state.
1388 	 * COOKIE-WAIT and SHUTDOWN-ACK-SENT  in sctp_tietags_populate()
1473 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_unexpected_init()
1806 	/* If the endpoint is in the SHUTDOWN-ACK-SENT state and recognizes  in sctp_sf_do_dupcook_a()
1808 	 * association but instead resend the SHUTDOWN ACK and send an ERROR  in sctp_sf_do_dupcook_a()
1864 		 * transition to ESTABLISHED. Instead trigger SHUTDOWN  in sctp_sf_do_dupcook_a()
2230  * Process an ABORT.  (SHUTDOWN-PENDING state)
2276  * Process an ABORT.  (SHUTDOWN-SENT state)
2318 	/* Stop the T2-shutdown timer. */  in sctp_sf_shutdown_sent_abort()
2322 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_sent_abort()
2330  * Process an ABORT.  (SHUTDOWN-ACK-SENT state)
2343 	 * common function with the SHUTDOWN-SENT state.  in sctp_sf_shutdown_ack_sent_abort()
2723  * Upon the reception of the SHUTDOWN, the peer endpoint shall
2724  *  - enter the SHUTDOWN-RECEIVED state,
2730  *    SHUTDOWN sender.
2732  * Once an endpoint as reached the SHUTDOWN-RECEIVED state it MUST NOT
2733  * send a SHUTDOWN in response to a ULP request. And should discard
2734  * subsequent SHUTDOWN chunks.
2736  * If there are still outstanding DATA chunks left, the SHUTDOWN
2739  * are acknowledged; however, the SHUTDOWN receiver MUST NOT accept
2769 	/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shutdown()
2795 	 * When a peer sends a SHUTDOWN, SCTP delivers this notification to  in sctp_sf_do_9_2_shutdown()
2805 	/* Upon the reception of the SHUTDOWN, the peer endpoint shall  in sctp_sf_do_9_2_shutdown()
2806 	 *  - enter the SHUTDOWN-RECEIVED state,  in sctp_sf_do_9_2_shutdown()
2825 	 *    received by the SHUTDOWN sender.  in sctp_sf_do_9_2_shutdown()
2837  * Once an endpoint has reached the SHUTDOWN-RECEIVED state,
2838  * it MUST NOT send a SHUTDOWN in response to a ULP request.
2839  * The Cumulative TSN Ack of the received SHUTDOWN chunk
2857 	/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shut_ctsn()
2881 	 * received by the SHUTDOWN sender.  in sctp_sf_do_9_2_shut_ctsn()
2890  * If an endpoint is in SHUTDOWN-ACK-SENT state and receives an INIT chunk
2891  * (e.g., if the SHUTDOWN COMPLETE was lost) with source and destination
2894  * retransmit the SHUTDOWN ACK chunk.
2914 	 * the SHUTDOWN ACK.  in sctp_sf_do_9_2_reshutack()
2920 	/* Set the transport for the SHUTDOWN ACK chunk and the timeout for  in sctp_sf_do_9_2_reshutack()
2921 	 * the T2-SHUTDOWN timer.  in sctp_sf_do_9_2_reshutack()
2925 	/* and restart the T2-shutdown timer. */  in sctp_sf_do_9_2_reshutack()
3181  * (4) In SHUTDOWN-SENT state the endpoint MUST acknowledge any received
3236 	 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately  in sctp_sf_eat_data_fast_4_4()
3238 	 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer  in sctp_sf_eat_data_fast_4_4()
3441  * Process an inbound SHUTDOWN ACK.
3444  * Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall
3445  * stop the T2-shutdown timer, send a SHUTDOWN COMPLETE chunk to its
3468 	/* 10.2 H) SHUTDOWN COMPLETE notification  in sctp_sf_do_9_2_final()
3470 	 * When SCTP completes the shutdown procedures (section 9.2) this  in sctp_sf_do_9_2_final()
3478 	/* ...send a SHUTDOWN COMPLETE chunk to its peer, */  in sctp_sf_do_9_2_final()
3488 	/* Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall  in sctp_sf_do_9_2_final()
3489 	 * stop the T2-shutdown timer,  in sctp_sf_do_9_2_final()
3516  * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3517  *    respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3518  *    When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3520  *    packet with the Verification Tag received in the SHUTDOWN ACK and
3605  * Handle an "Out of the blue" SHUTDOWN ACK.
3609  * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3610  *    respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3611  *    When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3613  *    packet with the Verification Tag received in the SHUTDOWN ACK and
3678  * Handle SHUTDOWN ACK in COOKIE_ECHOED or COOKIE_WAIT state.
3680  * Verification Tag:  8.5.1 E) Rules for packet carrying a SHUTDOWN ACK
4168 	 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately  in sctp_sf_eat_fwd_tsn_fast()
4170 	 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer  in sctp_sf_eat_fwd_tsn_fast()
4942  * Process the SHUTDOWN primitive.
4945  * C) Shutdown
4947  * Format: SHUTDOWN(association id)
4977 	/* From 9.2 Shutdown of an Association  in sctp_sf_do_9_2_prm_shutdown()
4978 	 * Upon receipt of the SHUTDOWN primitive from its upper  in sctp_sf_do_9_2_prm_shutdown()
4979 	 * layer, the endpoint enters SHUTDOWN-PENDING state and  in sctp_sf_do_9_2_prm_shutdown()
5098  * state table when someone issues a shutdown while in COOKIE_WAIT state.
5133  * state table when someone issues a shutdown while in COOKIE_ECHOED state.
5236  * state table when someone issues an abort while in SHUTDOWN-PENDING state.
5249 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_pending_prm_abort()
5263  * state table when someone issues an abort while in SHUTDOWN-SENT state.
5276 	/* Stop the T2-shutdown timer.  */  in sctp_sf_shutdown_sent_prm_abort()
5280 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_sent_prm_abort()
5308 	 * common function with the SHUTDOWN-SENT state.  in sctp_sf_shutdown_ack_sent_prm_abort()
5447  * Start the shutdown negotiation.
5451  * shall send a SHUTDOWN chunk to its peer including in the Cumulative
5453  * It shall then start the T2-shutdown timer and enter the SHUTDOWN-SENT
5454  * state. If the timer expires, the endpoint must re-send the SHUTDOWN
5470 	 * endpoint shall send a SHUTDOWN chunk to its peer including  in sctp_sf_do_9_2_start_shutdown()
5478 	/* Set the transport for the SHUTDOWN chunk and the timeout for the  in sctp_sf_do_9_2_start_shutdown()
5479 	 * T2-shutdown timer.  in sctp_sf_do_9_2_start_shutdown()
5483 	/* It shall then start the T2-shutdown timer */  in sctp_sf_do_9_2_start_shutdown()
5488 	 * The sender of the SHUTDOWN MAY also start an overall guard timer  in sctp_sf_do_9_2_start_shutdown()
5489 	 * 'T5-shutdown-guard' to bound the overall time for shutdown sequence.  in sctp_sf_do_9_2_start_shutdown()
5498 	/* and enter the SHUTDOWN-SENT state.  */  in sctp_sf_do_9_2_start_shutdown()
5504 	 * HEARTBEAT ... is discontinued after sending either SHUTDOWN  in sctp_sf_do_9_2_start_shutdown()
5505 	 * or SHUTDOWN-ACK.  in sctp_sf_do_9_2_start_shutdown()
5518  * Generate a SHUTDOWN ACK now that everything is SACK'd.
5522  * If it has no more outstanding DATA chunks, the SHUTDOWN receiver
5523  * shall send a SHUTDOWN ACK and start a T2-shutdown timer of its own,
5524  * entering the SHUTDOWN-ACK-SENT state. If the timer expires, the
5525  * endpoint must re-send the SHUTDOWN ACK.
5541 	 *    1) called in response to a SHUTDOWN chunk  in sctp_sf_do_9_2_shutdown_ack()
5552 		/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shutdown_ack()
5559 	/* If it has no more outstanding DATA chunks, the SHUTDOWN receiver  in sctp_sf_do_9_2_shutdown_ack()
5560 	 * shall send a SHUTDOWN ACK ...  in sctp_sf_do_9_2_shutdown_ack()
5566 	/* Set the transport for the SHUTDOWN ACK chunk and the timeout for  in sctp_sf_do_9_2_shutdown_ack()
5567 	 * the T2-shutdown timer.  in sctp_sf_do_9_2_shutdown_ack()
5571 	/* and start/restart a T2-shutdown timer of its own, */  in sctp_sf_do_9_2_shutdown_ack()
5579 	/* Enter the SHUTDOWN-ACK-SENT state.  */  in sctp_sf_do_9_2_shutdown_ack()
5585 	 * HEARTBEAT ... is discontinued after sending either SHUTDOWN  in sctp_sf_do_9_2_shutdown_ack()
5586 	 * or SHUTDOWN-ACK.  in sctp_sf_do_9_2_shutdown_ack()
5650 			 * shutdown guard timer to give the receiver one last  in sctp_sf_do_6_3_3_rtx()
5853 /* RFC2960 9.2 If the timer expires, the endpoint must re-send the SHUTDOWN
5857  * SHUTDOWN chunk to the protocol parameter 'Association.Max.Retrans'.
5863  * the T2-Shutdown timer,  giving its peer ample opportunity to transmit
5911 	 * If we remove the transport an SHUTDOWN was last sent to, don't  in sctp_sf_t2_timer_expire()
5918 	/* Set the transport for the SHUTDOWN/ACK chunk and the timeout for  in sctp_sf_t2_timer_expire()
5919 	 * the T2-shutdown timer.  in sctp_sf_t2_timer_expire()
5923 	/* Restart the T2-shutdown timer.  */  in sctp_sf_t2_timer_expire()
6004  * The sender of the SHUTDOWN MAY also start an overall guard timer
6005  * 'T5-shutdown-guard' to bound the overall time for shutdown sequence.
6042  * the association is automatically closed by starting the shutdown process.
6043  * The work that needs to be done is same as when SHUTDOWN is initiated by
6058 	/* From 9.2 Shutdown of an Association  in sctp_sf_autoclose_timer_expire()
6059 	 * Upon receipt of the SHUTDOWN primitive from its upper  in sctp_sf_autoclose_timer_expire()
6060 	 * layer, the endpoint enters SHUTDOWN-PENDING state and  in sctp_sf_autoclose_timer_expire()