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()
336 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_5_1B_init()
532 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_5_1C_ack()
1420  * Note: Do not use in CLOSED or SHUTDOWN-ACK-SENT state.
1442 	 * COOKIE-WAIT and SHUTDOWN-ACK-SENT  in sctp_tietags_populate()
1527 	 * SHUTDOWN COMPLETE with any other chunks.  in sctp_sf_do_unexpected_init()
1884 	/* If the endpoint is in the SHUTDOWN-ACK-SENT state and recognizes  in sctp_sf_do_dupcook_a()
1886 	 * association but instead resend the SHUTDOWN ACK and send an ERROR  in sctp_sf_do_dupcook_a()
1944 		 * transition to ESTABLISHED. Instead trigger SHUTDOWN  in sctp_sf_do_dupcook_a()
2315  * Process an ABORT.  (SHUTDOWN-PENDING state)
2361  * Process an ABORT.  (SHUTDOWN-SENT state)
2403 	/* Stop the T2-shutdown timer. */  in sctp_sf_shutdown_sent_abort()
2407 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_sent_abort()
2415  * Process an ABORT.  (SHUTDOWN-ACK-SENT state)
2428 	 * common function with the SHUTDOWN-SENT state.  in sctp_sf_shutdown_ack_sent_abort()
2808  * Upon the reception of the SHUTDOWN, the peer endpoint shall
2809  *  - enter the SHUTDOWN-RECEIVED state,
2815  *    SHUTDOWN sender.
2817  * Once an endpoint as reached the SHUTDOWN-RECEIVED state it MUST NOT
2818  * send a SHUTDOWN in response to a ULP request. And should discard
2819  * subsequent SHUTDOWN chunks.
2821  * If there are still outstanding DATA chunks left, the SHUTDOWN
2824  * are acknowledged; however, the SHUTDOWN receiver MUST NOT accept
2854 	/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shutdown()
2880 	 * When a peer sends a SHUTDOWN, SCTP delivers this notification to  in sctp_sf_do_9_2_shutdown()
2890 	/* Upon the reception of the SHUTDOWN, the peer endpoint shall  in sctp_sf_do_9_2_shutdown()
2891 	 *  - enter the SHUTDOWN-RECEIVED state,  in sctp_sf_do_9_2_shutdown()
2910 	 *    received by the SHUTDOWN sender.  in sctp_sf_do_9_2_shutdown()
2922  * Once an endpoint has reached the SHUTDOWN-RECEIVED state,
2923  * it MUST NOT send a SHUTDOWN in response to a ULP request.
2924  * The Cumulative TSN Ack of the received SHUTDOWN chunk
2942 	/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shut_ctsn()
2966 	 * received by the SHUTDOWN sender.  in sctp_sf_do_9_2_shut_ctsn()
2975  * If an endpoint is in SHUTDOWN-ACK-SENT state and receives an INIT chunk
2976  * (e.g., if the SHUTDOWN COMPLETE was lost) with source and destination
2979  * retransmit the SHUTDOWN ACK chunk.
2997 	 * the SHUTDOWN ACK.  in __sctp_sf_do_9_2_reshutack()
3003 	/* Set the transport for the SHUTDOWN ACK chunk and the timeout for  in __sctp_sf_do_9_2_reshutack()
3004 	 * the T2-SHUTDOWN timer.  in __sctp_sf_do_9_2_reshutack()
3008 	/* and restart the T2-shutdown timer. */  in __sctp_sf_do_9_2_reshutack()
3284  * (4) In SHUTDOWN-SENT state the endpoint MUST acknowledge any received
3339 	 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately  in sctp_sf_eat_data_fast_4_4()
3341 	 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer  in sctp_sf_eat_data_fast_4_4()
3583  * Process an inbound SHUTDOWN ACK.
3586  * Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall
3587  * stop the T2-shutdown timer, send a SHUTDOWN COMPLETE chunk to its
3610 	/* 10.2 H) SHUTDOWN COMPLETE notification  in sctp_sf_do_9_2_final()
3612 	 * When SCTP completes the shutdown procedures (section 9.2) this  in sctp_sf_do_9_2_final()
3620 	/* ...send a SHUTDOWN COMPLETE chunk to its peer, */  in sctp_sf_do_9_2_final()
3630 	/* Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall  in sctp_sf_do_9_2_final()
3631 	 * stop the T2-shutdown timer,  in sctp_sf_do_9_2_final()
3658  * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3659  *    respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3660  *    When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3662  *    packet with the Verification Tag received in the SHUTDOWN ACK and
3750  * Handle an "Out of the blue" SHUTDOWN ACK.
3754  * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3755  *    respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3756  *    When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3758  *    packet with the Verification Tag received in the SHUTDOWN ACK and
3817  * Handle SHUTDOWN ACK in COOKIE_ECHOED or COOKIE_WAIT state.
3819  * Verification Tag:  8.5.1 E) Rules for packet carrying a SHUTDOWN ACK
4308 	 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately  in sctp_sf_eat_fwd_tsn_fast()
4310 	 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer  in sctp_sf_eat_fwd_tsn_fast()
4882  * SHUTDOWN-COMPLETE, our peer is clearly violating the "MUST NOT bundle"
5088  * Process the SHUTDOWN primitive.
5091  * C) Shutdown
5093  * Format: SHUTDOWN(association id)
5123 	/* From 9.2 Shutdown of an Association  in sctp_sf_do_9_2_prm_shutdown()
5124 	 * Upon receipt of the SHUTDOWN primitive from its upper  in sctp_sf_do_9_2_prm_shutdown()
5125 	 * layer, the endpoint enters SHUTDOWN-PENDING state and  in sctp_sf_do_9_2_prm_shutdown()
5244  * state table when someone issues a shutdown while in COOKIE_WAIT state.
5279  * state table when someone issues a shutdown while in COOKIE_ECHOED state.
5382  * state table when someone issues an abort while in SHUTDOWN-PENDING state.
5395 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_pending_prm_abort()
5409  * state table when someone issues an abort while in SHUTDOWN-SENT state.
5422 	/* Stop the T2-shutdown timer.  */  in sctp_sf_shutdown_sent_prm_abort()
5426 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_sent_prm_abort()
5454 	 * common function with the SHUTDOWN-SENT state.  in sctp_sf_shutdown_ack_sent_prm_abort()
5593  * Start the shutdown negotiation.
5597  * shall send a SHUTDOWN chunk to its peer including in the Cumulative
5599  * It shall then start the T2-shutdown timer and enter the SHUTDOWN-SENT
5600  * state. If the timer expires, the endpoint must re-send the SHUTDOWN
5616 	 * endpoint shall send a SHUTDOWN chunk to its peer including  in sctp_sf_do_9_2_start_shutdown()
5624 	/* Set the transport for the SHUTDOWN chunk and the timeout for the  in sctp_sf_do_9_2_start_shutdown()
5625 	 * T2-shutdown timer.  in sctp_sf_do_9_2_start_shutdown()
5629 	/* It shall then start the T2-shutdown timer */  in sctp_sf_do_9_2_start_shutdown()
5634 	 * The sender of the SHUTDOWN MAY also start an overall guard timer  in sctp_sf_do_9_2_start_shutdown()
5635 	 * 'T5-shutdown-guard' to bound the overall time for shutdown sequence.  in sctp_sf_do_9_2_start_shutdown()
5644 	/* and enter the SHUTDOWN-SENT state.  */  in sctp_sf_do_9_2_start_shutdown()
5650 	 * HEARTBEAT ... is discontinued after sending either SHUTDOWN  in sctp_sf_do_9_2_start_shutdown()
5651 	 * or SHUTDOWN-ACK.  in sctp_sf_do_9_2_start_shutdown()
5664  * Generate a SHUTDOWN ACK now that everything is SACK'd.
5668  * If it has no more outstanding DATA chunks, the SHUTDOWN receiver
5669  * shall send a SHUTDOWN ACK and start a T2-shutdown timer of its own,
5670  * entering the SHUTDOWN-ACK-SENT state. If the timer expires, the
5671  * endpoint must re-send the SHUTDOWN ACK.
5687 	 *    1) called in response to a SHUTDOWN chunk  in sctp_sf_do_9_2_shutdown_ack()
5698 		/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shutdown_ack()
5705 	/* If it has no more outstanding DATA chunks, the SHUTDOWN receiver  in sctp_sf_do_9_2_shutdown_ack()
5706 	 * shall send a SHUTDOWN ACK ...  in sctp_sf_do_9_2_shutdown_ack()
5712 	/* Set the transport for the SHUTDOWN ACK chunk and the timeout for  in sctp_sf_do_9_2_shutdown_ack()
5713 	 * the T2-shutdown timer.  in sctp_sf_do_9_2_shutdown_ack()
5717 	/* and start/restart a T2-shutdown timer of its own, */  in sctp_sf_do_9_2_shutdown_ack()
5725 	/* Enter the SHUTDOWN-ACK-SENT state.  */  in sctp_sf_do_9_2_shutdown_ack()
5731 	 * HEARTBEAT ... is discontinued after sending either SHUTDOWN  in sctp_sf_do_9_2_shutdown_ack()
5732 	 * or SHUTDOWN-ACK.  in sctp_sf_do_9_2_shutdown_ack()
5796 			 * shutdown guard timer to give the receiver one last  in sctp_sf_do_6_3_3_rtx()
5999 /* RFC2960 9.2 If the timer expires, the endpoint must re-send the SHUTDOWN
6003  * SHUTDOWN chunk to the protocol parameter 'Association.Max.Retrans'.
6009  * the T2-Shutdown timer,  giving its peer ample opportunity to transmit
6057 	 * If we remove the transport an SHUTDOWN was last sent to, don't  in sctp_sf_t2_timer_expire()
6064 	/* Set the transport for the SHUTDOWN/ACK chunk and the timeout for  in sctp_sf_t2_timer_expire()
6065 	 * the T2-shutdown timer.  in sctp_sf_t2_timer_expire()
6069 	/* Restart the T2-shutdown timer.  */  in sctp_sf_t2_timer_expire()
6150  * The sender of the SHUTDOWN MAY also start an overall guard timer
6151  * 'T5-shutdown-guard' to bound the overall time for shutdown sequence.
6188  * the association is automatically closed by starting the shutdown process.
6189  * The work that needs to be done is same as when SHUTDOWN is initiated by
6204 	/* From 9.2 Shutdown of an Association  in sctp_sf_autoclose_timer_expire()
6205 	 * Upon receipt of the SHUTDOWN primitive from its upper  in sctp_sf_autoclose_timer_expire()
6206 	 * layer, the endpoint enters SHUTDOWN-PENDING state and  in sctp_sf_autoclose_timer_expire()