SA2 meeting process 

1.	SA2#166AH E-MEETING will be an electronic ad hoc meeting.
2.	SA2#166AH E-MEETING will not count toward the maintenance of voting rights.

3.	Please follow the following steps for SA2#166AH E-MEETING registration and check-in -  
-	STEP 1: To participate in SA2#166AHE the delegates should register before the registration deadline –. Registration Link: https://portal.3gpp.org/Home.aspx#/meeting?MtgId=60815.
Once registered, delegates will receive a registration confirmation email with a "sign-in" Token. 
NOTE: Registrations after this deadline will still be processed, but timely receipt of meeting related information is not guaranteed for late registrants. 
-	STEP 2: The delegates should check-in themselves between the start and the close of the meeting using the Token received in the registration confirmation email. 
-	Please note registration only is not enough to be listed in the attendees list. During SA2#166AH E-MEETING you also need to check in at SA2#166AH E-MEETING by clicking on the link provided in the registration confirmation email and entering the Token received in the registration confirmation email. 
-	If a delegate does not check in themselves between the start and the close of the meeting, it shall be assumed that the individual did not attend. 

4.	SA2#166AH e-meeting will be conducted by e-mail and conference calls. All discussions will be public and conducted via the 3GPP_TSG_SA_WG2_EMEET@LIST.ETSI.ORG mailing list. There is no subscription to this list, people registered for the meeting will be added to the EMEET list at the submission deadline.
5.	The following CC’s (Chaired by SA2 leadership) may be organized during SA2#166AH e-meeting – 
	CC#1	Monday 20 January 2024		1400 – 1600 UTC
	CC#2	Wednesday 22 January 2024	1400 – 1600 UTC
	CC#3	Thursday 23 January 2024	1400 – 1600 UTC
	CC#4	Friday 24 January 2024		1400 – 1600 UTC
-	The objective of these conference calls would be to find a way forward on any controversial topics. They won't be used to discuss/process documents.
-	These CC during e-meeting will have approval power. 
-	No recording of CC is allowed, like the 3GPP rules for the F2F meeting. 
-	Additional conference calls may be organized during the e-meeting, if necessary.
6.	Only TDocs requested and submitted via 3GU before the "TDocs submission" deadline will be considered during the meeting. At this deadline, 3GU closes and no further tdocs can be requested or submitted.
7.	Companies are encouraged to use the SA2 DISCUSSION list to provide comments after the submission deadline. It is better to provide consolidated comments. The author may consider those comments and provide a revision (addressing those comments) at the start of the e-meeting.
8.	Tdoc numbers for mirror CRs should be requested and documents submitted by the "Tdocs submission" deadline. Revisions of mirror CRs should not be produced until the CR to the earliest release is Approved. New Tdoc numbers will be allocated to the approved revisions at the Final comments deadline. 24 hours grace period after the Final deadline will be provided to the authors to upload/email final approved documents (along with any mirrors CRs, if applicable).
9.	Any comments or revisions prior to the start of the e-meeting will not be considered.
10.	If the Technical Document (TDoc) is not available by the "Docs submission" deadline, it will be marked as LATE. LATE documents will have lower priority and may not get handled. 
11.	If there are no comments/objections on a document for approval by the "Revision by" deadline, it is APPROVED at that time.
12.	Revisions may be proposed until the "Revision by" deadline. Comments in the email will not be automatically considered under revisions, so please provide a revision document with your changes.
13.	If there are no comments/objections on a certain revision by the "Final" deadline, it is APPROVED at the final deadline.
14.	Any revision of the document can be approved as long as there are no objections. Having concerns/issues is not implicitly considered an "objection". Therefore, please phrase any potential objections clearly. Providing a revision is not implicitly considered as an "objection" to the older revision(s). Please explicitly state if you have an "objection" to a specific revision and/or if there is another (older) revision that you can "accept".
15.	Please clearly indicate "[SA2#166AHE, AI#, S2-25xxxxx] <TDoc Title>" in the e-mail subject line, when distributing the documents or commenting on the documents for e-mail approval. Everything between the quotation marks shall be shown as an e-mail subject, including the squared brackets. Don't add any other info like the revision number to the e-mail subject. Do not include any other document number in the subject line.
    -	E-mail without the tag "[SA2#166AHE, AI#, S2-25xxxxx]" will NOT be considered as part of the email approval.
    -	Please DO NOT make changes to the subject line of ongoing e-mails to avoid breaking an e-mail thread. 
    -	Email servers from some companies include new tags in the email subject e.g. "[External]" or other characters. This breaks the email thread. Please try to avoid inserting unwanted tags in the email subject.
    -	Please don't forget to indicate Agenda Item number "AI#" according to the Agenda Items shown in the Agenda table. Example: "[SA2#166AHE, AI#8.1, S2-2599999] Update of references in 23.501" 
16.	Information on Email "Comment for notes START/END" tag for automated Chair's Note generation: 
    -	Each email SHALL start with a <<START>>/<<END>> tag as shown below 

Tag Format:
Comment for notes <<START>>
YourName (YourCompanyName) <Comment for Chair's Notes>
<<END>>

<comments to the document >

Example:
Comment for notes <<START>>
Michael (ABC Company) provides r01
<<END>>

Please find r01 here <hyperlink to document>. This includes changes XYZ on top of the original version. 

    -	These are <<START>>/<<END>> tags. Please note "<<" and ">>" are part of tags. Macro searches for these tags. Please DO NOT change anything related to tags. Each email SHALL have these tags. Please ensure that tags are formatted correctly, including when you are copying/pasting tags from another email.
    -	This text will be automatically captured in the Chair's Notes. This text should be very brief i.e., limited to 1 or 2 small sentences, and SHALL include YourName (YourCompanyName). If a revision is provided, then this SHALL be indicated within the "Comment for notes <<START>>/<<END>>" tags. Please DO NOT put a hyperlink to the revision document in this part. For the same email thread exactly the same "comments for notes" are not added in the Chair’s Notes. To avoid such a case please modify your comments slightly for the same email thread. 
    -	This text will NOT be captured in the Chair's Notes. This text should contain your normal comments/question to document. This should include a hyperlink to the new revision if provided. 
    -	Emails without "Comment for notes <<START>>/<<END>>" tags will be discarded.
17.	Information on 3GU upload/FTP server: 
    -	SA2#166AH e-meeting folder can be accessed at https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_166AH-e_Electronic_2025-01
    -	Delegates will need to log in (using an EOL account) to add files, anonymous access will allow download only.
    -	Please DO NOT attach documents to your e-mails but upload them to the meetings folder on the 3GPP server (see below for more details on e-meeting folders). If you have problems uploading your documents, please send them to SA2 leadership (not the whole SA2 list).
18.	Folders for sharing documents and File naming conventions: 
    -	Inbox https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_166AH-e_Electronic_2025-01/INBOX
-	Purpose: To upload final approved documents with new tdoc#. After the e-meeting FINAL deadline, all approved revisions will be assigned a new tdoc# by the e-meeting conveners. 
-	File Naming Convention: For Example - S2-25xxxxx.zip.
-	File Format: Files shall be in ZIP format. 
-	Rules: Strict file naming convention shall be followed in this folder. Documents not adhering to the file naming convention will be discarded. 
    -	Draft https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_166AH-e_Electronic_2025-01/INBOX/DRAFTS 
-	Purpose: To share any draft document prior to the start of the e-meeting.
-	File Naming Convention: None but using the "Draft_" prefix to a filename is recommended. 
-	File Format: Any. 
-	Rules: Please don't upload revisions in this folder during the e-meeting. Any revisions shared in the draft folder prior to the e-meeting shall be provided again in the revisions folder at the start of the e-meeting using the appropriate file naming convention.  
    -	Revisions https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_166AH-e_Electronic_2025-01/INBOX/Revisions
-	Purpose: To share revisions during e-meeting.
-	File Naming Convention: Please use "r01", "r02", etc suffix for revision (not "R01", not "rev1", not "r1", not "R1"). For Example - S2-25xxxxxr01.zip, S2-25xxxxxr02.zip, S2-25xxxxxr03.zip etc. 
Revisions shall start from r01 and should be increment by 1. Please check for the latest revision number before uploading your document as there may be clashes. 
-	File Format: Files shall be in ZIP format. 
-	Rules: Strict file naming convention shall be followed in this folder. Documents not adhering to the file naming convention will be discarded. Revisions will not be accepted before the start of the e-meeting.
    -	Chair_Notes https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_166AH-e_Electronic_2025-01/INBOX/Chair_Notes
-	Purpose: To share the Chair's Notes. 
-	File Naming Convention: ChairNotes_<convener_name>_<timestamp/status>.doc. For Example – ChairNotes_Andy_02-22-0900.doc, ChairNotes_Andy_02-27-0900_FINAL.doc etc. 
-	File Format: MS Doc.
-	Rules: File naming convention shall be followed in this folder. This folder shall only be used by SA2 leadership.
    -	SA2#166AHE_CC#xx https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_166AH-e_Electronic_2025-01/INBOX/CCs
-	Purpose: To share the way forward discussion/proposal on a controversial issue, the show of hands questions, Minor revision of the document marked as "For CC#xx" in the Chair_Notes.
-	File Naming Convention: None, but for revisions please follow the revisions file naming convention.
-	File Format: Any.
-	Rules: Please make a way forward discussion/proposal on a controversial issue, a show of hands questions, latest revisions available at least 1 hour before the start of the CC.
19.	Information on Uploading Approved Documents: 
    -	SA2 leadership will allocate new tdoc numbers to approved documents at the (or shortly after) FINAL deadline. 
    -	Authors need to upload/email final approved documents (along with any mirrors CRs, if applicable) in INBOX (https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_166AH-e_Electronic_2025-01/INBOX/DRAFTS) by Document Upload Deadline.
    -	If an approved document has no revision (i.e. original document), then it will NOT get a new tdoc number. Please do not upload the original document again in INBOX as they are already available in the DOC folder. 
    -	If an approved document has revision but the original document is approved, then it will NOT get a new tdoc number. Please do not upload the original document again in INBOX as they are already available in the DOC folder. 
    -	Revisions will not get a new tdoc number. All revisions will be maintained on the 3GPP server. 
20.	Input document control [Applies to AI# 5.X, 6.X, 7.X, 8.X, 9.X]
    -	Maximum 2 TDocs (CR) per company (as the first author) per agenda item indicated above will be handled, unless otherwise stated in the agenda in clause 2.1 above.
    -	Any additional TDocs (CR) will not be handled and removed from the initial Chair’s note.
    -	Following will not be counted towards the quota - 
-	Multi-company contribution with 10 or more co-signers
-	Any LS OUT and Discussion Papers
-	Any TDocs generated during the meeting
-	Planning documents/status reports from the Rapporteur
-	Multiple CRs on the same topics and with the same title but to different TSs (e.g., TS 23.501, 23.502, etc) will be counted as single CR. 
21.	TU enforcement for Rel-19 SID/WID [Applies to AI# 19.X only]
    -	A maximum of 30 TDocs per 1 TU will be handled. If a Rel-19 SID/WID is assigned 0.5 TU then a maximum of 15 TDocs will be handled. If a Rel-19 SID/WID is assigned .25 TU, then a maximum of 7 TDocs (P-CRs) will be handled. 
    -	If the SID is assigned 1 TU and it receives more than 30 papers then only 30 will be picked based on sorting (after the submission deadline but before the start of the e-meeting) by the SA2 leadership. Fairness criterion will be applied, and Rapporteur input will be required on such sorting. 
    -	Rapporteur’s input papers on TR skeleton, TR scope will be exempted. 
    -	Discussion Paper (for Information) will be exempted. 
    -	LS IN/OUT will be exempted. 
    -	One TD should contain only one solution to a KI.
22.	3GPP TOHRU will be used for the e-meeting CC’s. Please format your Affiliation/Name on TOHRU as "<Company Name> - <Delegate Name>".
-	TOHRU Link: https://tohru.3gpp.org/