diff --git a/TP_ideas_and_status.md b/TP_ideas_and_status.md
index 5e63b559ad2e591ddf14d004a543f33792b42a71..31635e26d73955a8065e72a91cf307d091ae7136 100644
--- a/TP_ideas_and_status.md
+++ b/TP_ideas_and_status.md
@@ -96,8 +96,14 @@
 
 - Verify that the IUT initiates network de-registration by sending a DEREGISTRATION REQUEST message containing De-registration type IE with re-registration not required and the access type based on the UE’s registration status (3GPP access only).
 
+[KSCH]: Trigger for NW Initiated De-Registration missing. Chapter 5.5.2.3.1 mentions some triggers to perform NW-Initiation De-Registraton e.g. network slice-specific authentication and authorization failure or revocation as specified in subclause 4.6.2.4 
+
 - Verify that the IUT initiates network de-registration by sending a DEREGISTRATION REQUEST message and if UE does not send DEREGISTRATION ACCEPT then IUT retransmits DEREGISTRATION REQUEST message after timer T3522 expiration.
 
+[KSCH]: See above or rephrase to "Verify the in case of T3522 Timeout the IUT re-sends DEREGISTRATION REQUEST" More appropriate reference would be 5.5.2.3.5 Abnormal cases in the network side case a) T3522 time-out 
+
 - Verify that the IUT initiates network de-registration by sending DEREGISTRATION REQUEST message containing De-registration type IE with re-registration required and the access type based on the UE’s registration status (3GPP access only). NOTE: UE sends DEREGISTRATION ACCEPT and starts with re-registration procedure.(also used ref 5.5.2.3.2 1st paragraph)
 
+[KSCH]: Trigger for NW Initiated De-Registration missing. Under what circumstances the IUT has to trigger De-Registration and has to include Re-Registration Required and Access Type.  
+
 - Verify that if de-registration is triggered due to IUT slice-specific authentication and authorization failure or revocation, the network sets the 5GMM cause value to #62 "No network slices available" and includes the rejected NSSAI IE in the DEREGISTRATION REQUEST message.