202  * Process the final SHUTDOWN COMPLETE.
205  * Upon reception of the SHUTDOWN COMPLETE chunk the endpoint will verify
206  * that it is in SHUTDOWN-ACK-SENT state, if it is not the chunk should be
207  * discarded. If the endpoint is in the SHUTDOWN-ACK-SENT state the endpoint
208  * should stop the T2-shutdown timer and remove all knowledge of the
212  * C) Rules for packet carrying SHUTDOWN COMPLETE:
214  * - The receiver of a SHUTDOWN COMPLETE shall accept the packet
222  *   SHUTDOWN COMPLETE if it is not in the SHUTDOWN-ACK-SENT state.
247 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_4_C()
259 	 * H) SHUTDOWN COMPLETE notification  in sctp_sf_do_4_C()
261 	 * When SCTP completes the shutdown procedures (section 9.2) this  in sctp_sf_do_4_C()
270 	/* Upon reception of the SHUTDOWN COMPLETE chunk the endpoint  in sctp_sf_do_4_C()
271 	 * will verify that it is in SHUTDOWN-ACK-SENT state, if it is  in sctp_sf_do_4_C()
273 	 * the SHUTDOWN-ACK-SENT state the endpoint should stop the  in sctp_sf_do_4_C()
274 	 * T2-shutdown timer and remove all knowledge of the  in sctp_sf_do_4_C()
332 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_5_1B_init()
534 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_5_1C_ack()
1426  * Note: Do not use in CLOSED or SHUTDOWN-ACK-SENT state.
1448 	 * COOKIE-WAIT and SHUTDOWN-ACK-SENT  in sctp_tietags_populate()
1528 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_unexpected_init()
1890 	/* If the endpoint is in the SHUTDOWN-ACK-SENT state and recognizes  in sctp_sf_do_dupcook_a()
1892 	 * association but instead resend the SHUTDOWN ACK and send an ERROR  in sctp_sf_do_dupcook_a()
1950 		 * transition to ESTABLISHED. Instead trigger SHUTDOWN  in sctp_sf_do_dupcook_a()
2330  * Process an ABORT.  (SHUTDOWN-PENDING state)
2376  * Process an ABORT.  (SHUTDOWN-SENT state)
2418 	/* Stop the T2-shutdown timer. */  in sctp_sf_shutdown_sent_abort()
2422 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_sent_abort()
2430  * Process an ABORT.  (SHUTDOWN-ACK-SENT state)
2443 	 * common function with the SHUTDOWN-SENT state.  in sctp_sf_shutdown_ack_sent_abort()
2823  * Upon the reception of the SHUTDOWN, the peer endpoint shall
2824  *  - enter the SHUTDOWN-RECEIVED state,
2830  *    SHUTDOWN sender.
2832  * Once an endpoint as reached the SHUTDOWN-RECEIVED state it MUST NOT
2833  * send a SHUTDOWN in response to a ULP request. And should discard
2834  * subsequent SHUTDOWN chunks.
2836  * If there are still outstanding DATA chunks left, the SHUTDOWN
2839  * are acknowledged; however, the SHUTDOWN receiver MUST NOT accept
2869 	/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shutdown()
2895 	 * When a peer sends a SHUTDOWN, SCTP delivers this notification to  in sctp_sf_do_9_2_shutdown()
2905 	/* Upon the reception of the SHUTDOWN, the peer endpoint shall  in sctp_sf_do_9_2_shutdown()
2906 	 *  - enter the SHUTDOWN-RECEIVED state,  in sctp_sf_do_9_2_shutdown()
2925 	 *    received by the SHUTDOWN sender.  in sctp_sf_do_9_2_shutdown()
2937  * Once an endpoint has reached the SHUTDOWN-RECEIVED state,
2938  * it MUST NOT send a SHUTDOWN in response to a ULP request.
2939  * The Cumulative TSN Ack of the received SHUTDOWN chunk
2957 	/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shut_ctsn()
2981 	 * received by the SHUTDOWN sender.  in sctp_sf_do_9_2_shut_ctsn()
2990  * If an endpoint is in SHUTDOWN-ACK-SENT state and receives an INIT chunk
2991  * (e.g., if the SHUTDOWN COMPLETE was lost) with source and destination
2994  * retransmit the SHUTDOWN ACK chunk.
3012 	 * the SHUTDOWN ACK.  in __sctp_sf_do_9_2_reshutack()
3018 	/* Set the transport for the SHUTDOWN ACK chunk and the timeout for  in __sctp_sf_do_9_2_reshutack()
3019 	 * the T2-SHUTDOWN timer.  in __sctp_sf_do_9_2_reshutack()
3023 	/* and restart the T2-shutdown timer. */  in __sctp_sf_do_9_2_reshutack()
3299  * (4) In SHUTDOWN-SENT state the endpoint MUST acknowledge any received
3354 	 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately  in sctp_sf_eat_data_fast_4_4()
3356 	 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer  in sctp_sf_eat_data_fast_4_4()
3598  * Process an inbound SHUTDOWN ACK.
3601  * Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall
3602  * stop the T2-shutdown timer, send a SHUTDOWN COMPLETE chunk to its
3625 	/* 10.2 H) SHUTDOWN COMPLETE notification  in sctp_sf_do_9_2_final()
3627 	 * When SCTP completes the shutdown procedures (section 9.2) this  in sctp_sf_do_9_2_final()
3635 	/* ...send a SHUTDOWN COMPLETE chunk to its peer, */  in sctp_sf_do_9_2_final()
3645 	/* Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall  in sctp_sf_do_9_2_final()
3646 	 * stop the T2-shutdown timer,  in sctp_sf_do_9_2_final()
3673  * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3674  *    respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3675  *    When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3677  *    packet with the Verification Tag received in the SHUTDOWN ACK and
3765  * Handle an "Out of the blue" SHUTDOWN ACK.
3769  * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3770  *    respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3771  *    When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3773  *    packet with the Verification Tag received in the SHUTDOWN ACK and
3832  * Handle SHUTDOWN ACK in COOKIE_ECHOED or COOKIE_WAIT state.
3834  * Verification Tag:  8.5.1 E) Rules for packet carrying a SHUTDOWN ACK
4323 	 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately  in sctp_sf_eat_fwd_tsn_fast()
4325 	 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer  in sctp_sf_eat_fwd_tsn_fast()
4897  * SHUTDOWN-COMPLETE, our peer is clearly violating the "MUST NOT bundle"
5100  * Process the SHUTDOWN primitive.
5103  * C) Shutdown
5105  * Format: SHUTDOWN(association id)
5135 	/* From 9.2 Shutdown of an Association  in sctp_sf_do_9_2_prm_shutdown()
5136 	 * Upon receipt of the SHUTDOWN primitive from its upper  in sctp_sf_do_9_2_prm_shutdown()
5137 	 * layer, the endpoint enters SHUTDOWN-PENDING state and  in sctp_sf_do_9_2_prm_shutdown()
5256  * state table when someone issues a shutdown while in COOKIE_WAIT state.
5291  * state table when someone issues a shutdown while in COOKIE_ECHOED state.
5394  * state table when someone issues an abort while in SHUTDOWN-PENDING state.
5407 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_pending_prm_abort()
5421  * state table when someone issues an abort while in SHUTDOWN-SENT state.
5434 	/* Stop the T2-shutdown timer.  */  in sctp_sf_shutdown_sent_prm_abort()
5438 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_sent_prm_abort()
5466 	 * common function with the SHUTDOWN-SENT state.  in sctp_sf_shutdown_ack_sent_prm_abort()
5605  * Start the shutdown negotiation.
5609  * shall send a SHUTDOWN chunk to its peer including in the Cumulative
5611  * It shall then start the T2-shutdown timer and enter the SHUTDOWN-SENT
5612  * state. If the timer expires, the endpoint must re-send the SHUTDOWN
5628 	 * endpoint shall send a SHUTDOWN chunk to its peer including  in sctp_sf_do_9_2_start_shutdown()
5636 	/* Set the transport for the SHUTDOWN chunk and the timeout for the  in sctp_sf_do_9_2_start_shutdown()
5637 	 * T2-shutdown timer.  in sctp_sf_do_9_2_start_shutdown()
5641 	/* It shall then start the T2-shutdown timer */  in sctp_sf_do_9_2_start_shutdown()
5646 	 * The sender of the SHUTDOWN MAY also start an overall guard timer  in sctp_sf_do_9_2_start_shutdown()
5647 	 * 'T5-shutdown-guard' to bound the overall time for shutdown sequence.  in sctp_sf_do_9_2_start_shutdown()
5656 	/* and enter the SHUTDOWN-SENT state.  */  in sctp_sf_do_9_2_start_shutdown()
5662 	 * HEARTBEAT ... is discontinued after sending either SHUTDOWN  in sctp_sf_do_9_2_start_shutdown()
5663 	 * or SHUTDOWN-ACK.  in sctp_sf_do_9_2_start_shutdown()
5676  * Generate a SHUTDOWN ACK now that everything is SACK'd.
5680  * If it has no more outstanding DATA chunks, the SHUTDOWN receiver
5681  * shall send a SHUTDOWN ACK and start a T2-shutdown timer of its own,
5682  * entering the SHUTDOWN-ACK-SENT state. If the timer expires, the
5683  * endpoint must re-send the SHUTDOWN ACK.
5699 	 *    1) called in response to a SHUTDOWN chunk  in sctp_sf_do_9_2_shutdown_ack()
5710 		/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shutdown_ack()
5717 	/* If it has no more outstanding DATA chunks, the SHUTDOWN receiver  in sctp_sf_do_9_2_shutdown_ack()
5718 	 * shall send a SHUTDOWN ACK ...  in sctp_sf_do_9_2_shutdown_ack()
5724 	/* Set the transport for the SHUTDOWN ACK chunk and the timeout for  in sctp_sf_do_9_2_shutdown_ack()
5725 	 * the T2-shutdown timer.  in sctp_sf_do_9_2_shutdown_ack()
5729 	/* and start/restart a T2-shutdown timer of its own, */  in sctp_sf_do_9_2_shutdown_ack()
5737 	/* Enter the SHUTDOWN-ACK-SENT state.  */  in sctp_sf_do_9_2_shutdown_ack()
5743 	 * HEARTBEAT ... is discontinued after sending either SHUTDOWN  in sctp_sf_do_9_2_shutdown_ack()
5744 	 * or SHUTDOWN-ACK.  in sctp_sf_do_9_2_shutdown_ack()
5808 			 * shutdown guard timer to give the receiver one last  in sctp_sf_do_6_3_3_rtx()
6011 /* RFC2960 9.2 If the timer expires, the endpoint must re-send the SHUTDOWN
6015  * SHUTDOWN chunk to the protocol parameter 'Association.Max.Retrans'.
6021  * the T2-Shutdown timer,  giving its peer ample opportunity to transmit
6069 	 * If we remove the transport an SHUTDOWN was last sent to, don't  in sctp_sf_t2_timer_expire()
6076 	/* Set the transport for the SHUTDOWN/ACK chunk and the timeout for  in sctp_sf_t2_timer_expire()
6077 	 * the T2-shutdown timer.  in sctp_sf_t2_timer_expire()
6081 	/* Restart the T2-shutdown timer.  */  in sctp_sf_t2_timer_expire()
6162  * The sender of the SHUTDOWN MAY also start an overall guard timer
6163  * 'T5-shutdown-guard' to bound the overall time for shutdown sequence.
6200  * the association is automatically closed by starting the shutdown process.
6201  * The work that needs to be done is same as when SHUTDOWN is initiated by
6216 	/* From 9.2 Shutdown of an Association  in sctp_sf_autoclose_timer_expire()
6217 	 * Upon receipt of the SHUTDOWN primitive from its upper  in sctp_sf_autoclose_timer_expire()
6218 	 * layer, the endpoint enters SHUTDOWN-PENDING state and  in sctp_sf_autoclose_timer_expire()