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()
2319  * Process an ABORT.  (SHUTDOWN-PENDING state)
2365  * Process an ABORT.  (SHUTDOWN-SENT state)
2407 	/* Stop the T2-shutdown timer. */  in sctp_sf_shutdown_sent_abort()
2411 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_sent_abort()
2419  * Process an ABORT.  (SHUTDOWN-ACK-SENT state)
2432 	 * common function with the SHUTDOWN-SENT state.  in sctp_sf_shutdown_ack_sent_abort()
2812  * Upon the reception of the SHUTDOWN, the peer endpoint shall
2813  *  - enter the SHUTDOWN-RECEIVED state,
2819  *    SHUTDOWN sender.
2821  * Once an endpoint as reached the SHUTDOWN-RECEIVED state it MUST NOT
2822  * send a SHUTDOWN in response to a ULP request. And should discard
2823  * subsequent SHUTDOWN chunks.
2825  * If there are still outstanding DATA chunks left, the SHUTDOWN
2828  * are acknowledged; however, the SHUTDOWN receiver MUST NOT accept
2858 	/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shutdown()
2884 	 * When a peer sends a SHUTDOWN, SCTP delivers this notification to  in sctp_sf_do_9_2_shutdown()
2894 	/* Upon the reception of the SHUTDOWN, the peer endpoint shall  in sctp_sf_do_9_2_shutdown()
2895 	 *  - enter the SHUTDOWN-RECEIVED state,  in sctp_sf_do_9_2_shutdown()
2914 	 *    received by the SHUTDOWN sender.  in sctp_sf_do_9_2_shutdown()
2926  * Once an endpoint has reached the SHUTDOWN-RECEIVED state,
2927  * it MUST NOT send a SHUTDOWN in response to a ULP request.
2928  * The Cumulative TSN Ack of the received SHUTDOWN chunk
2946 	/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shut_ctsn()
2970 	 * received by the SHUTDOWN sender.  in sctp_sf_do_9_2_shut_ctsn()
2979  * If an endpoint is in SHUTDOWN-ACK-SENT state and receives an INIT chunk
2980  * (e.g., if the SHUTDOWN COMPLETE was lost) with source and destination
2983  * retransmit the SHUTDOWN ACK chunk.
3001 	 * the SHUTDOWN ACK.  in __sctp_sf_do_9_2_reshutack()
3007 	/* Set the transport for the SHUTDOWN ACK chunk and the timeout for  in __sctp_sf_do_9_2_reshutack()
3008 	 * the T2-SHUTDOWN timer.  in __sctp_sf_do_9_2_reshutack()
3012 	/* and restart the T2-shutdown timer. */  in __sctp_sf_do_9_2_reshutack()
3288  * (4) In SHUTDOWN-SENT state the endpoint MUST acknowledge any received
3343 	 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately  in sctp_sf_eat_data_fast_4_4()
3345 	 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer  in sctp_sf_eat_data_fast_4_4()
3587  * Process an inbound SHUTDOWN ACK.
3590  * Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall
3591  * stop the T2-shutdown timer, send a SHUTDOWN COMPLETE chunk to its
3614 	/* 10.2 H) SHUTDOWN COMPLETE notification  in sctp_sf_do_9_2_final()
3616 	 * When SCTP completes the shutdown procedures (section 9.2) this  in sctp_sf_do_9_2_final()
3624 	/* ...send a SHUTDOWN COMPLETE chunk to its peer, */  in sctp_sf_do_9_2_final()
3634 	/* Upon the receipt of the SHUTDOWN ACK, the SHUTDOWN sender shall  in sctp_sf_do_9_2_final()
3635 	 * stop the T2-shutdown timer,  in sctp_sf_do_9_2_final()
3662  * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3663  *    respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3664  *    When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3666  *    packet with the Verification Tag received in the SHUTDOWN ACK and
3754  * Handle an "Out of the blue" SHUTDOWN ACK.
3758  * 5) If the packet contains a SHUTDOWN ACK chunk, the receiver should
3759  *    respond to the sender of the OOTB packet with a SHUTDOWN COMPLETE.
3760  *    When sending the SHUTDOWN COMPLETE, the receiver of the OOTB
3762  *    packet with the Verification Tag received in the SHUTDOWN ACK and
3821  * Handle SHUTDOWN ACK in COOKIE_ECHOED or COOKIE_WAIT state.
3823  * Verification Tag:  8.5.1 E) Rules for packet carrying a SHUTDOWN ACK
4312 	 * While in SHUTDOWN-SENT state, the SHUTDOWN sender MUST immediately  in sctp_sf_eat_fwd_tsn_fast()
4314 	 * with a SACK, a SHUTDOWN chunk, and restart the T2-shutdown timer  in sctp_sf_eat_fwd_tsn_fast()
4886  * SHUTDOWN-COMPLETE, our peer is clearly violating the "MUST NOT bundle"
5089  * Process the SHUTDOWN primitive.
5092  * C) Shutdown
5094  * Format: SHUTDOWN(association id)
5124 	/* From 9.2 Shutdown of an Association  in sctp_sf_do_9_2_prm_shutdown()
5125 	 * Upon receipt of the SHUTDOWN primitive from its upper  in sctp_sf_do_9_2_prm_shutdown()
5126 	 * layer, the endpoint enters SHUTDOWN-PENDING state and  in sctp_sf_do_9_2_prm_shutdown()
5245  * state table when someone issues a shutdown while in COOKIE_WAIT state.
5280  * state table when someone issues a shutdown while in COOKIE_ECHOED state.
5383  * state table when someone issues an abort while in SHUTDOWN-PENDING state.
5396 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_pending_prm_abort()
5410  * state table when someone issues an abort while in SHUTDOWN-SENT state.
5423 	/* Stop the T2-shutdown timer.  */  in sctp_sf_shutdown_sent_prm_abort()
5427 	/* Stop the T5-shutdown guard timer.  */  in sctp_sf_shutdown_sent_prm_abort()
5455 	 * common function with the SHUTDOWN-SENT state.  in sctp_sf_shutdown_ack_sent_prm_abort()
5594  * Start the shutdown negotiation.
5598  * shall send a SHUTDOWN chunk to its peer including in the Cumulative
5600  * It shall then start the T2-shutdown timer and enter the SHUTDOWN-SENT
5601  * state. If the timer expires, the endpoint must re-send the SHUTDOWN
5617 	 * endpoint shall send a SHUTDOWN chunk to its peer including  in sctp_sf_do_9_2_start_shutdown()
5625 	/* Set the transport for the SHUTDOWN chunk and the timeout for the  in sctp_sf_do_9_2_start_shutdown()
5626 	 * T2-shutdown timer.  in sctp_sf_do_9_2_start_shutdown()
5630 	/* It shall then start the T2-shutdown timer */  in sctp_sf_do_9_2_start_shutdown()
5635 	 * The sender of the SHUTDOWN MAY also start an overall guard timer  in sctp_sf_do_9_2_start_shutdown()
5636 	 * 'T5-shutdown-guard' to bound the overall time for shutdown sequence.  in sctp_sf_do_9_2_start_shutdown()
5645 	/* and enter the SHUTDOWN-SENT state.  */  in sctp_sf_do_9_2_start_shutdown()
5651 	 * HEARTBEAT ... is discontinued after sending either SHUTDOWN  in sctp_sf_do_9_2_start_shutdown()
5652 	 * or SHUTDOWN-ACK.  in sctp_sf_do_9_2_start_shutdown()
5665  * Generate a SHUTDOWN ACK now that everything is SACK'd.
5669  * If it has no more outstanding DATA chunks, the SHUTDOWN receiver
5670  * shall send a SHUTDOWN ACK and start a T2-shutdown timer of its own,
5671  * entering the SHUTDOWN-ACK-SENT state. If the timer expires, the
5672  * endpoint must re-send the SHUTDOWN ACK.
5688 	 *    1) called in response to a SHUTDOWN chunk  in sctp_sf_do_9_2_shutdown_ack()
5699 		/* Make sure that the SHUTDOWN chunk has a valid length. */  in sctp_sf_do_9_2_shutdown_ack()
5706 	/* If it has no more outstanding DATA chunks, the SHUTDOWN receiver  in sctp_sf_do_9_2_shutdown_ack()
5707 	 * shall send a SHUTDOWN ACK ...  in sctp_sf_do_9_2_shutdown_ack()
5713 	/* Set the transport for the SHUTDOWN ACK chunk and the timeout for  in sctp_sf_do_9_2_shutdown_ack()
5714 	 * the T2-shutdown timer.  in sctp_sf_do_9_2_shutdown_ack()
5718 	/* and start/restart a T2-shutdown timer of its own, */  in sctp_sf_do_9_2_shutdown_ack()
5726 	/* Enter the SHUTDOWN-ACK-SENT state.  */  in sctp_sf_do_9_2_shutdown_ack()
5732 	 * HEARTBEAT ... is discontinued after sending either SHUTDOWN  in sctp_sf_do_9_2_shutdown_ack()
5733 	 * or SHUTDOWN-ACK.  in sctp_sf_do_9_2_shutdown_ack()
5797 			 * shutdown guard timer to give the receiver one last  in sctp_sf_do_6_3_3_rtx()
6000 /* RFC2960 9.2 If the timer expires, the endpoint must re-send the SHUTDOWN
6004  * SHUTDOWN chunk to the protocol parameter 'Association.Max.Retrans'.
6010  * the T2-Shutdown timer,  giving its peer ample opportunity to transmit
6058 	 * If we remove the transport an SHUTDOWN was last sent to, don't  in sctp_sf_t2_timer_expire()
6065 	/* Set the transport for the SHUTDOWN/ACK chunk and the timeout for  in sctp_sf_t2_timer_expire()
6066 	 * the T2-shutdown timer.  in sctp_sf_t2_timer_expire()
6070 	/* Restart the T2-shutdown timer.  */  in sctp_sf_t2_timer_expire()
6151  * The sender of the SHUTDOWN MAY also start an overall guard timer
6152  * 'T5-shutdown-guard' to bound the overall time for shutdown sequence.
6189  * the association is automatically closed by starting the shutdown process.
6190  * The work that needs to be done is same as when SHUTDOWN is initiated by
6205 	/* From 9.2 Shutdown of an Association  in sctp_sf_autoclose_timer_expire()
6206 	 * Upon receipt of the SHUTDOWN primitive from its upper  in sctp_sf_autoclose_timer_expire()
6207 	 * layer, the endpoint enters SHUTDOWN-PENDING state and  in sctp_sf_autoclose_timer_expire()