Question: When releasing a CLUE data channel, what is the expected behavior of the MRFP regarding SCTP Stream Reconfiguration procedures?
Option 1: The MRFP initiates Sender-Side Procedures for the RE-CONFIG Chunk for outgoing directions and allows Receiver-Side Procedures for incoming directions.
Option 2: The MRFP only denies incoming SCTP re-configuration requests but may initiate outgoing RE-CONFIG Chunks.
Option 3: The MRFP prevents SCTP Stream Reconfiguration by not initiating Sender-Side Procedures for outgoing directions and denying all Receiver-Side Procedures for incoming directions.
Option 4: The MRFP automatically triggers an SCTP association shutdown without preventing SCTP Stream Reconfiguration procedures.
Explanation: When releasing a CLUE data channel, to prevent potential misuse of SCTP stream reset requests later on, the MRFP is required to block any reconfiguration attempts. This means for outgoing communications, it should not start the reconfiguration process, and for incoming communications, it must reject any reconfiguration requests, aligning with preventative measures for SCTP Stream Reconfiguration.