1.	How to address the ENs in clause 4 (Architecture and security assumptions) and clause 5.1 (Key issue #1: Security protection in Store and Forward Satellite Operation) of TR 33.700-29
	--> Longhua has shared two contributions for this and Alec has made some changes on top of these.
	--> Also, Wei has contributions for the same.
	--> Xaiomi's contributions

Clause 4:
	--> The physical security is assumed to be secure.: Already captured

	--> It is assumed that onboard 3GPP system is sufficiently secure. : Adrian (QC) : This assumption and below NOTE is OK for Alec (IDCC)
	--> Dependent on operator's policy and implementation : Niraj (Ericsson), Huawei(Longhua), Adrian (QC): can be a NOTE

--> Longhua can merge and share with other companies.

Clause 5.1:
Convert the EN for dependency on SA2 solution into an assumption.: Niraj, Alec
Also remove incomplete AKA as only cause. Can be more than this.
CATT proposal: Huawei OK to remove ENs
--> Longhua can merge and share with other companies.

--> KI TDocs not treated in Athens: S3‑240702, S3‑240810
S3‑240702 : Partial attach related privacy issue which includes GUTI.
	- Alec : SA2 is yet to agree on arch. Can be conditional.
	- A generic KI for privacy: Rakshesh, Alec
	- KI is too specific to solutions in SA2: Niraj

Below topics could not be discussed:
====================================
Not treated document : S3‑240810
2.	Privacy related KI for Store-and-forward: In Athens we could not discuss this in more details. 
3.	KI for UE-Sat-UE communications: In Athens we could not discuss this in more details.
4.	[Depending on time available]: If companies plan to bring in solutions, and would like to share, we can also discuss if time permits.

5.	Do we need another offline call between 8th – 12th April to discuss merger plans? Let’s hear from companies what they have to say and we’ll plan accordingly.