[{"name":"S2-2100004","title":"LS from SA WG3: Reply LS on Reply PAP\/CHAP and other point-to-point protocols usage in 5GS","source":"SA WG3","contact":"Alf Zugenmaier","contact-id":52494,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank SA WG2 for their LS Reply PAP\/CHAP and other point-to-point protocols usage in 5GS (S3-201509\/S2-2004481). SA WG3 would like to make the following observations: - EAP based secondary authentication in 5GS is a replacement for PAP\/CHAP in EPC. Therefore SA WG3 recommends use of secondary authentication instead of PAP\/CHAP using ePCO unless there are legacy applications requiring it. - PAP is outdated and should not be used any more (RFC 1334 (PAP) has been obsoleted by RFC 1994). Therefore, the warning should be in any 5G spec referring to PAP as well. - CHAP also comes with disadvantages, such as being amenable to brute force attacks if the password is guessable. - It is up to the external network operator to perform the risk assessment if PAP\/CHAP is used for authentication. Action: SA WG3 kindly asks SA WG2, CT WG1 and CT WG3 to take the above into consideration.","secretary_remarks":"Revision of postponed S2-2008339 from S2#142E. Response drafted in S2-2100074. Final response in S2-2101309","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10540,"status":"replied to","reservation_date":"2021-01-13 10:03:17","uploaded":"2021-01-13 14:55:02","revisionof":"S2-2008339","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, CT WG3","Cc":"CT WG4","lsoriginalls":"S3-202190","lsreply":"S2-2101309","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100004.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100005","title":"LS from CT WG1: LS on NSSAA at inter-PLMN mobility","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":85785,"tdoctype":"LS in","for":"Action","abstract":"In the case of inter-VPLMN mobility, CT WG1 has discussed how the target VPLMN should perform NSSAA for a UE that first enters the target VPLMN. CT WG1 kindly requests guidance on the following question: \u00a7 If the target VPLMN decides to run NSSAA for an S-NSSAI whose NSSAA status is EAP-Success when a UE accesses the target VPLMN for the first time, how will the target VPLMN handle the S-NSSAI that is subject to NSSAA: will it be put in the pending NSSAI or will it be put in the allowed NSSAI included in the registration accept message sent to the UE, and how are existing PDU sessions associated with the S-NSSAI handled?. Action: SA WG2 is kindly requested to answer the question above.","secretary_remarks":"Revision of postponed S2-2008347 from S2#142E. Response drafted in S2-2100682. Final response in S2-2101052","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10650,"status":"replied to","reservation_date":"2021-01-13 10:03:17","uploaded":"2021-01-13 14:55:02","revisionof":"S2-2008347","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4, SA WG3","lsoriginalls":"C1-206508","lsreply":"S2-2101052","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100005.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100014","title":"LS from RAN WG3: LS to SA2 on Immediate Suspension","source":"RAN WG3","contact":"Zijiang Ma","contact-id":36270,"tdoctype":"LS in","for":"Action","abstract":"In Rel-16, immediate Suspension has been supported in NGAP. That means if the Suspend Request Indication IE is included in the UE CONTEXT RESUME REQUEST message, the AMF shall, if supported, consider that the NG-RAN node is requesting immediate transition to RRC IDLE with Suspend as specified in TS 23.502. If the Suspend Response Indication IE is included in the UE CONTEXT RESUME RESPONSE message, the NG-RAN node shall suspend the UE context, the UE-associated logical NG-connection and the related PDU session contexts and transitions the UE to RRC_IDLE. Thus, there is not additional UE Context Suspend procedure during immediate Suspension case. To support immediate Suspension procedure, RAN WG3 has agreed to introduce Information on Recommended Cells and RAN Nodes for Paging IE and Paging Assistance Data for CE Capable UE IE in NGAP: UE CONTEXT RESUME REQUEST message. Action: RAN WG3 respectfully asks SA WG2 to take the above information into account and update their related specification.","secretary_remarks":"Revision of postponed S2-2009098 from S2#142E. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10530,"status":"postponed","reservation_date":"2021-01-13 10:03:18","uploaded":"2021-01-13 14:55:02","revisionof":"S2-2009098","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-207138","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100014.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100021","title":"LS from CT WG4: LS on Service Operation used during EPS to 5GS Handover with AMF re-allocation","source":"CT WG4","contact":"Zhijun Li","contact-id":39295,"tdoctype":"LS in","for":"Action","abstract":"During developing stage 3 protocols for the EPS to 5GS handover with AMF re-allocation, CT WG4 observed several issues. After discussion, CT WG4 reached some conclusion on one issue while still has questions to SA WG2 on the remaining issues. {. . .} Action: CT WG4 kindly asks SA WG2 to take CT WG4 discussion into account and provide feedback to these issues.","secretary_remarks":"Revision of postponed S2-2009110 from S2#142E. Response drafted in S2-2100070. Final response in S2-2101301","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"replied to","reservation_date":"2021-01-13 10:03:18","uploaded":"2021-01-13 14:55:02","revisionof":"S2-2009110","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-205702","lsreply":"S2-2101301","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100021.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100033","title":"LS from NGMN: Liaison Statement on the NGMN 5G End-to-End Architecture Framework (Phase-3)","source":"NGMN","contact":"Klaus Moschner","contact-id":59428,"tdoctype":"LS in","for":"Information","abstract":"Intention of the LS and required actions: NGMN is pleased to inform the recipient of this liaison statement for information sharing on the NGMN 5G End-to-End Architecture Framework (Phase-3) that includes requirements together with considerations and concepts emerging in the industry. This builds on the themes described in NGMN 5G End-to-End Architecture Framework (Phase-2) that was published in 2019 and shared subsequently. The topics of interest the NGMN 5G End-to-End Architecture Framework (Phase-3) include: The new topics and advancements of interest include: ? Autonomic Networking ? Network Data Layer ? Artificial Intelligence and Machine Learning ? Virtualization in the Radio Access Network ? Multi-access Edge Computing ? Distributed Ledger Technology ? Vertical Market ? End-to-End Security This NGMN liaison is intended for information sharing in terms of the new topics that have been introduced in the attached document.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2021-01-13 10:03:18","uploaded":"2021-01-13 14:55:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG5, SA WG6, TSG RAN, ETSI-MANO, ONAP","Cc":"","lsoriginalls":"201117 NGMN_liaison_E2E_architecture_framework_pha","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100033.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100034","title":"LS from IEEE 802.1: Withdrawal of IEEE Std 802.1D-2004","source":"IEEE 802.1","contact":"Glenn Parsons","contact-id":17960,"tdoctype":"LS in","for":"Information","abstract":"Dear Colleagues, The IEEE 802.1 Working Group would like to inform you of our plans to withdraw IEEE Std 802.1D-2004 IEEE Standard for Local and metropolitan area networks\u2014Media Access Control (MAC) Bridges. It is our intention to withdraw this standard by the end of 2021. The status of the standard will become inactive-withdrawn, and inactive standards remain available from the IEEE. The technical specifications, protocols, procedures, and managed objects of IEEE Std 802.1D-2004 are completely subsumed within IEEE 802.1Q-2018 IEEE Standard for Local and Metropolitan Area Networks\u2014Bridges and Bridged Networks. The withdrawal of IEEE Std 802.1D-2004 will not result in any loss of functionality as we are actively maintaining and amending IEEE Std 802.1Q-2018. There is currently an IEEE 802.1Q revision project underway that can address any concerns with this transition. We are informing you of these plans because you have current references to IEEE Std 802.1D in your specifications. We recommend you review your specifications for references to IEEE Std 802.1D and consider whether updates to your specifications are needed. Our quick review of your active specifications revealed a preliminary, and possibly incomplete, list of 2 specifications with normative reference to IEEE Std 802.1D. We recommend you determine whether any action is required (e.g., to update your normative references from IEEE Std 802.1D to IEEE Std 802.1Q). The list of active references our search revealed includes: 3GPP TR 23.836 Quality of Service (QoS) and policy aspects of 3GPP - Wireless Local Area Network (WLAN) interworking 3GPP TS 23.234 3GPP system to Wireless Local Area Network (WLAN) interworking; System description The procedure for withdrawing the standard involves IEEE 802.1 initiating an IEEE Standards Association (SA) ballot to confirm the withdrawal. We plan to initiate this process by July 2021 at the latest. While only IEEE-SA members may join the SA ballot to vote on this withdrawal, we would take your liaison response into account. Thank you for your consideration on this topic. We look forward to continued collaboration between our organizations. Respectfully submitted, Glenn Parsons Chair, IEEE 802.1 Working Group","secretary_remarks":"Response drafted in S2-2101049. Final response in S2-2101300","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"replied to","reservation_date":"2021-01-13 10:03:18","uploaded":"2021-01-13 14:55:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"IEEE 802","lsoriginalls":"liaison-3gpp-sa2-8021D-withdrawal-1120-v01","lsreply":"S2-2101300","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100034.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100036","title":"LS from ITU-T SG11: LS on initiation of new work item Q.Sig_Req_ETS_IMS_roaming 'Signalling requirements for emergency telecommunication service in IMS roaming environment'","source":"ITU-T SG11","contact":"Xiaojie ZHU","contact-id":40586,"tdoctype":"LS in","for":"Action","abstract":"At the ITU-T SG11 Working Party 1 meeting (virtual, 19 November 2020), a new work item was proposed by Q3\/11 and finally agreed: - Draft Recommendation ITU-T Q.Sig_Req_ETS_IMS_roaming 'Signalling requirements for emergency telecommunication service in IMS roaming environment' aims to specify signalling architecture, interfaces, functional description, signalling requirements, signalling procedures and security consideration of Emergency Telecommunication Service (ETS) in IMS roaming architecture over LTE. The A.1 justification is included as Annex B in the Q3\/11 meeting report (SG11-TD59\/WP1) and the baseline text is contained in SG11-TD58\/WP1. We would like to receive your comments and collaborations on this draft Recommendation and hope you can share your related works with us if you have similar studies in this area.","secretary_remarks":"Forwarded to SA WG2 from TSG CT#90-e. Response drafted in S2-2101006. Final response in S2-2101310","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10570,"status":"replied to","reservation_date":"2021-01-13 10:03:18","uploaded":"2021-02-04 06:31:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T Study Group 2, SA WG6","Cc":"","lsoriginalls":"sp16-sg11-oLS-00165","lsreply":"S2-2101310","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100036.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100039","title":"LS on stage 3 aspects for Reliable Data Service Serialization Indication","source":"CT WG1","contact":"Vivek Gupta","contact-id":74448,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has agreed the RDSSI WID in Rel-17 to implement the Reliable Data Service Serialization Indication feature in stage 3, whereas the corresponding stage 2 requirements are in Rel-16. Action: CT WG1 kindly asks TSG SA, TSG CT and SA WG2 to take above into account.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10520,"status":"postponed","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-01-13 14:55:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, TSG CT, TSG SA","Cc":"CT WG3","lsoriginalls":"C1-207769","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100039.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100044","title":"LS from SA WG3: Reply LS on IP address to GPSI translation","source":"SA WG3","contact":"Rajavelsamy Rajadurai","contact-id":33521,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG6 for the Reply LS on IP address to GPSI translation (S6-202008\/S3-202849) and SA WG2 for the LS on IP address to GPSI translation (S2-2005923\/ S3-202839). SA WG3 acknowledges the SA WG6 requirement to enable exposure of network services to AF (e.g. EAS\/EES) using a static identifier, when only an IP address of the UE is known. Using 3GPP system specific permanent identities (e.g. SUPI) for network external identification purposes should be avoided. However, using a public identity like the GPSI outside the 3GPP operator domain for external identification purposes can be possible. As SA WG6 and SA WG2 are aware of, a GPSI can be an MSISDN or an External Identifier. A user may not be comfortable with sharing its MSISDN with the external AF. However, an External Identifier can be exposed to the AF. Therefore, SA WG2 can consider studying on reliable identification of the UE using the IP address with a corresponding public identity for CN capability exposure APIs. Action: SA WG3 requests SA WG6 and SA WG2 to take the above response in to account.","secretary_remarks":"Response drafted in S2-2100747. Final response in S2-2101307","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"replied to","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-01-13 14:55:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, SA WG2","Cc":"","lsoriginalls":"S3-203360","lsreply":"S2-2101307","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100044.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100045","title":"LS from SA WG3: LS on AKMA Anchor Function selection","source":"SA WG3","contact":"Vlasios Tsiatsis","contact-id":76181,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 has defined the architecture and procedures of a new feature called Authentication and Key Management for Application using 3GPP Credentials (AKMA) in 3GPP TS 33.535. AKMA introduces a new network function called the AKMA Anchor Function (AAnF) which interacts with the AUSF and an AKMA Application Function (AF in the architecture) directly or via the NEF depending on whether the AF is internal or external to the network respectively. Upon successful primary authentication the AUSF needs to discover and select an AAnF in order to store the AKMA context for the UE (SUPI, KAKMA, A-KID). Upon an application session request from the UE to the AF, the AF (if internal to the network) or NEF (if the AF is external to the network) needs to discover the same AAnF that holds the AKMA context for the UE. The UE provides for this purpose the A-KID (AKMA key identifier) to the AF. The A-KID is in the form of username@realm, where the username part shall include the Routing Indicator (RID) and the A-TID (AKMA Temporary UE Identifier), while the realm part shall include the Home Network Identifier. The A-TID in turn is A-TID=KDF(KAUSF, SUPI, 'A-TID'), KDF stands for Key Derivation Function. Please observe that the TS 33.535 mentions the RID as 'Routing Identifier'. SA WG3 agreed before that either one AAnF is included in the PLMN or the RID used for AAnF selection. SA WG3 assumes that the NF Set concept is applicable for the multiple AAnFs sharing the same RID. The attached contribution was presented in SA WG3 in order to clarify how the AUSF and the AF\/NEF can discover and select the same AAnF for the same UE. SA WG3 would like SA WG2 to review the AAnF selection clause and provide feedback. Action: SA WG3 kindly asks SA WG2 to take the above information into account and provide feedback.","secretary_remarks":"Responses drafted in S2-2100207 and S2-2100671. Final response in S2-2101304","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"replied to","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-01-13 14:55:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-203494","lsreply":"S2-2101304","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100045.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100046","title":"LS from SA WG4: LS Reply on New service type of NR QoE","source":"SA WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks RAN WG3 for their LS in (R3-205724\/ S4-201460). It is appreciated that RAN WG3 agreed to support Video Streaming, VR, MTSI and MBMS service types in the NR QoE study item, which covers media related services in SA WG4. Currently SA WG4 has only specified QMC functionality (for QoE configuration and reporting) for UMTS and LTE. When the RAN WG3 NR QoE work has concluded, SA WG4 will also expand the specified QMC support to include 5G NR accordingly. Due to the low-latency and high-reliability requirements, XR-related services may require URLLC support in some scenarios, especially for industrial or medical usage, but also for certain entertainment and business applications such as cloud gaming and split rendering. Currently, there are several ongoing XR-related Rel-17 activities in SA WG4, such as ITT4RT, FS_XRTraffic and FS_5GSTAR.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"postponed","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-01-13 14:55:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG5, SA WG2","lsoriginalls":"S4-201576","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100046.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100050","title":"LS from SA WG1: LS on MINT requirements","source":"SA WG1","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for their LS on MINT requirements, and the questions asked to SA WG1, copied here: Question 1: Which level of services are the PLMNs not subject to disaster required to provide to 'Disaster Inbound Roamers'? Emergency services only, a limited set of services hosted by the PLMN not subject to disaster (e.g. internet connectivity provided using local break-out), or the same set of services that the 'Disaster Inbound Roamers' would receive in their HPLMN? Question 2: If the answer to Question 1 is: a limited set of services hosted by the PLMN not subject to disaster, can it be assumed that the NFs of the PLMM subject to disaster required to support those services (the UDM and the AUSF) are still operational? Question 3: If the answer to Question 1 is: the same set of services that the 'Disaster Inbound Roamers' would receive in their HPLMN, can it be assumed that the NFs (network functions) of the PLMM subject to disaster required to support those services (the UDM, the AUSF, the SMF and UPF for any DNN requiring home-routed PDU session, and the IMS) are still operational? ------------ SA WG1 would like to provide the following answers: Answer 1: In principle 'Disaster Inbound Roamers' can receive the same services as normal inbound roamers can receive in the VPLMN, subject to agreements between HPLMN and VPLMN, regulations, VPLMN constraints, etc. Answer 2&3: according to the initial stage-1 study and use cases, which refer mostly to RAN unavailability due to disaster situations, SA WG1 understanding is that the network functions of the PLMN subject to disaster can be assumed to be still operational.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-01-20 08:56:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"S1-204329","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100050.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100051","title":"LS from ATIS IoT Group: Request that a standardised SST value for this S-NEST new Slice Service Type (SST) be added to TS 23.501","source":"ATIS IoT Group","contact":"Farrokh Khatibi","contact-id":79662,"tdoctype":"LS in","for":"Action","abstract":"As requested by 3GPP, the ATIS IoT Group worked with GSMA 5GJA to define a new Standardised Network Slice Type (S-NEST) in PRD NG.116. ATIS would like to inform TSG SA and SA WG2 that the new Slice Service Type (SST) for High-Performance Machine-Type Communications (HMTC) has been added in NG.116 Generic Network Slice Template v4. Interested member companies plan to submit a CR to SA WG2 requesting that a standardised SST value for this S-NEST new Slice Service Type (SST) be added to TS 23.501 in order to meet the described IoT characteristics matrix. Action: SA WG2 to take the above information into account and, if there is no further feedback, document the new defined SST in TS 23.501.","secretary_remarks":"Response drafted in S2-2100417. Final response in S2-2101051","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"status":"replied to","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-02-01 09:51:46","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"","lsoriginalls":"IoT_CAT_Liaison_Letter_to_SA_and_SA2","lsreply":"S2-2101051","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100051.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100055","title":"LS from SA WG3-LI: LS on Clarification on support of MAP messages at the UDM for SMS in 5GS","source":"SA WG3-LI","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"LS in","for":"Action","abstract":"The architecture to support SMS in the 5GS is illustrated in TS 23.501 clause 4.4.2. The network architecture in figure 4.4.2.1-2 displays the assumed interfaces between the UDM and SMS-GMSC\/IWMSC\/SMS Router; however, there are no specific references to stage 3 MAP support at the UDM. Note 2 of clause 4.4.2.1 states that the 'UDM may be connected to the SMS-GMSC\/IWMSC\/SMS Router via one of the standardized interfaces as shown in TS 23.040'. TS 23.040 Annex K states that SMS in 5GS can be supported by replacing the HLR with the UDM\/HLR. TS 23.632 indicates that a standalone 5GC scenario exists where the UDM may have the MAP interface. However, related figures in TS 23.632 (e.g. figure 5.5.6.2-1 and figure 5.5.6.2-2) show a separate HSS as well in the flows. A review of TS 29.002 (MAP) highlights the issue of no requirements for stage 3 MAP support at the UDM. In addition, SA WG3-LI observes that UDM Stage 3 description in TS 29.503 is restricted to the serviced based Nudm interface only. SA WG3-LI would like to ask CT WG1\/CT WG4\/SA WG2 to confirm how and through which specifications the UDM supports a MAP interface (e.g. through use of a MAP reference point directly on the UDM). Action: SA WG3-LI kindly asks CT WG1\/CT WG4\/SA WG2 to address the above request and to inform SA WG3-LI accordingly.","secretary_remarks":"Response drafted in S2-2100260. Final response in S2-2101311","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10600,"status":"replied to","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-02-01 15:37:42","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4, SA WG2","Cc":"","lsoriginalls":"S3i210061","lsreply":"S2-2101311","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100055.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100056","title":"LS from CT WG3: LS on NSI ID on N7 interface","source":"CT WG3","contact":"Abdessamad EL MOATAMID","contact-id":80517,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 has observed that Stage 2 specified the network slice identifier (i.e. NSI ID) as an optional input parameter to be provided by the SMF to the PCF when requesting the creation of an SM Policy Association (i.e. within the Npcf_SMPolicyControl_Create service operation) in the frame of PDU session procedures, both in TS 23.502 (clauses 4.16.4 and 5.2.5.4.2), and TS 23.503 (clause 6.2.1.2). Cf. extract hereinafter from clause 4.16.4 of TS 23.502. '1. The SMF determines that the PCC authorization is required and requests to establish an SM Policy Association with the PCF by invoking Npcf_SMPolicyControl_Create operation (see clause 5.2.5.4.2). The SMF includes the following information: SUPI, PDU Session id, PDU Session Type, S-NSSAI, NSI ID (if available), DNN, DNN Selection Mode, GPSI (if available), Access Type, RAT Type, AMF instance identifier and if available, the IPv4 address and\/or IPv6 network prefix, PEI, User Location Information, UE Time Zone, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501 [2]), Charging Characteristics, Session AMBR, default QoS information, Trace Requirements, Internal Group Identifier (see TS 23.501 [2], clause 5.9.7).' CT WG3 has not considered this parameter in TS 29.512 (within the Npcf_SMPolicyControl_Create service operation) so far, mainly because it is not specified how the SMF gets \/ is aware of NSI ID allocated for the PDU session and the use case(s) behind it. Therefore, CT WG3 would like to ask SA WG2 for clarification on this point, so as to resolve this remaining misalignment between Stage 2 and Stage 3 specifications: Q1: How does the SMF determine the NSI ID in this context? In this sense, please also clarify the meaning of the mention 'if available'. Q2: What is the foreseen use case behind it? In other words, how this parameter is expected to be used by the PCF in the frame of the Npcf_SMPolicyControl service?. Action: CT WG3 kindly asks SA WG2 to provide answers and clarifications on the above questions and update the related Stage 2 specifications accordingly, if necessary.","secretary_remarks":"Response drafted in S2-2100124. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10630,"status":"postponed","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-02-01 15:37:42","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-210310","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100056.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100057","title":"LS from CT WG3: LS on Secondary AUTH for 5GS interworking with EPS","source":"CT WG3","contact":"Tianmei Liang","contact-id":69846,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 has observed that EAP based Secondary Authentication and Authorization for 5GS interworking with EPS has not been described in 3GPP TS 23.501, 3GPP TS 23.502 in SA WG2 and 3GPP TS 33.501 in SA WG3. Correspondingly 3GPP TS 29.561 does not include descriptions on how to support EAP based secondary authentication and authorization interworking with the external DN-AAA server, when the UE is under 5GS and EPS interworking scenarios. Current specifications define EAP based secondary authentication\/authorization for the PDU Session, if the UE provides authentication\/ authorization information corresponding to a DN-specific identity during the PDU Session establishment, and the SMF determines that authentication\/authorization of the PDU Session Establishment is required based on the SMF policy associated with the DN. Hence CT WG3 has several questions for the 5GS and EPS interworking scenarios: 1) Whether EAP based secondary authorization\/ authentication is also applicable for EPS, when the UE supports EAP. 2) When the DN-AAA server initiates EAP based re-authorization but UE has moved from 5GS to EPS, whether such re-authorization will be supported. 3) If only PAP\/CHAP based secondary authorization\/ authentication is applicable in EPS, how to handle the case when the DN-AAA server initiates EAP based re-authorization but UE has moved from 5GS to EPS. Action: CT WG3 kindly asks SA WG2 and SA WG3 to answer above questions.","secretary_remarks":"Responses drafted in S2-2100103, S2-2100223 and S2-2100406. Final response in S2-2101305","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"replied to","reservation_date":"2021-01-13 10:03:19","uploaded":"2021-02-01 15:37:42","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"CT WG1","lsoriginalls":"C3-210377","lsreply":"S2-2101305","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100057.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100069","title":"Introduction of AKMA into the reference architecture","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds the abbreviation, the SBI(s) and references points related to AKMA in 23.501 with suitable references to 33.535.","secretary_remarks":"Revision of (noted) S2-2006931 from S2#141E. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"agreed","reservation_date":"2021-01-18 09:18:01","uploaded":"2021-02-18 08:04:05","revisionof":"S2-2006931","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"AKMA"}],"crnumber":2457.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210067","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100069.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100070","title":"[DRAFT] LS on Service Operation used during EPS to 5GS Handover with AMF re-allocation","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"LS on Service Operation used during EPS to 5GS Handover with AMF re-allocation","secretary_remarks":"Response to S2-2100021. Agreed. Revised to S2-2101301.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"revised","reservation_date":"2021-01-18 09:18:03","uploaded":"2021-02-18 19:04:26","revisionof":"","revisedto":"S2-2101301","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100070.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100071","title":"Corrections on EPS to 5GS Handover with AMF re-allocation","source":"Nokia, Nokia Shanghai Bell, ZTE, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When at EPS to 5GS handover using N26 interface (preparation phase) the Initial AMF reselects a target AMF, it invokes Namf_Communication_RelocateUEContext request and not Namf_Communication_CreateUEContext request Handover failure in target RAN handling with initial AMF and target AMF is added. Handover cancel from source RAN handling with initial AMF and target AMF is added. A NOTE is added to clarify that target AMF can be also the initial AMF when there is no AMF reallocation.","secretary_remarks":"r02 agreed. Revised to S2-2101303.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"revised","reservation_date":"2021-01-18 09:18:03","uploaded":"2021-02-18 19:04:26","revisionof":"","revisedto":"S2-2101303","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2456.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100071.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100074","title":"[DRAFT] LS on PAP\/CHAP and other point-to-point protocols usage in 5GS","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"LS on PAP\/CHAP and other point-to-point protocols usage in 5GS","secretary_remarks":"Response to S2-2100004. r01 agreed. Revised to S2-2101309.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10550,"status":"revised","reservation_date":"2021-01-18 09:18:06","uploaded":"2021-02-18 08:04:05","revisionof":"","revisedto":"S2-2101309","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG1, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100074.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100103","title":"[DRAFT] LS on Secondary AUTH for 5GS interworking with EPS","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS on Secondary AUTH for 5GS interworking with EPS","secretary_remarks":"Response to S2-2100057. Merged into S2-2101305","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"merged","reservation_date":"2021-02-07 17:16:28","uploaded":"2021-02-18 09:05:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, SA WG3, CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100103.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100104","title":"Secondary AUTH for 5GS interworking with EPS","source":"Nokia, Nokia Shanghai Bell, Deutsche Telekom","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the access to a DN is to be controlled by mechanisms defined in clause 5.6.6 (secondary authentication \/ autorization by a DN server), for a PDN connection allowed for mobility to 5GC, \u00a0the PDN connection establishment includes a phase of Secondary authentication\/authorization by a DN-AAA server. This is further defined in 23.502.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"withdrawn","reservation_date":"2021-02-07 17:16:28","uploaded":"2021-02-18 09:05:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2529.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100104.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100105","title":"Secondary AUTH for 5GS interworking with EPS","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the access to a DN is to be controlled by secondary authentication \/ autorization by a DN server, for a PDN connection allowed for mobility to 5GC, \u00a0the PDN connection establishment includes a phase of Secondary authentication\/authorization by a DN-AAA server Creating a new clause 4.11.0a.X Secondary authentication\/authorization by a DN server The new procedure in 4.11.0a.X is mirroring and referring to Figure 4.3.2.3-1. It focuses on the specific aspects related with the exchange of DN Authentication signalling (EAP signaling) between the UE and the SMF+PGW-c. This exchange uses PCO;","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"withdrawn","reservation_date":"2021-02-07 17:16:30","uploaded":"2021-02-18 09:05:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2466.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100105.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100109","title":"LS from RAN WG3: Remove the user message size limitation for DTLS over SCTP","source":"RAN WG3","contact":"Nianshan Shi","contact-id":45408,"tdoctype":"LS in","for":"Information","abstract":"From the first version of the 5G specification, 3GPP has specified to use DTLS over SCTP. RAN WG3 has found an issue related to RFC 6083 DTLS user message size limitation over SCTP that impacts several of TSG RAN application protocols. The RFC specifies a user message limit of approximate16k Bytes. This should be compared to the unlimited user message size that exists when SCTP is used without DTLS. There are several RAN application messages that can exceed the limit of approximate 16k Bytes. The same issue may exist for the other 3GPP groups using the DTLS over SCTP. A general solution to this issue is desirable rather than changing multiple different protocols. We understand the limitation in RFC 6083 is due to a lack of a secure fragmentation mechanism of user messages into multiple DTLS records. The DTLS over SCTP specification appear to be the right layer to resolve this issue and achieve feature parity between DTLS over SCTP and unsecured SCTP. RAN WG3 would like to ask the IETF TSVWG to investigate and would greatly appreciate a solution to the issue related to the size limitation for DTLS over SCTP.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2021-02-08 12:33:25","uploaded":"2021-02-08 12:41:58","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF TSVWG","Cc":"SA WG3, SA WG2, CT WG1, CT WG4","lsoriginalls":"R3-211274","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100109.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100124","title":"[DRAFT] LS Reply on NSI ID on N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To answer the LS on NSI ID on N7 interface from CT WG3","secretary_remarks":"Response to S2-2100056. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10640,"status":"postponed","reservation_date":"2021-02-10 09:41:51","uploaded":"2021-02-18 08:22:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100124.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100135","title":"LS from CT WG4: LS on the Security consideration to support L2TP with CUPS","source":"CT WG4","contact":"yong yang","contact-id":59744,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 is currently studying Sx\/N4 extensions to support L2TP tunneling over SGi\/N6 as part of WI BEPoP (BEst Practice of PFCP), and CT WG4 has discussed potential security issues (as documented in C4-210170) for supporting L2TP with CUPS. A security mechanism may be required to send following information from the CP function to the UP function e.g. when the CP function and UP function are in different security domains: - a Tunnel-Password for mutual authentication of LAC and LNS when establishing a L2TP tunnel; - the username and the password for PAP or the Challenge and the Challenge Response for CHAP to authenticate a UE when establishing a L2TP session for a PDU session or a PDN connection. Potential alternative mechanisms could be: - Relying on the Network domain security, e.g. using IPSec, as specified in 3GPP TS 33.210. If so, there is no need to develop any further security mechanism to protect the aforementioned information; - Using DTLS over N4\/Sxb when supporting L2TP, as described in IETF RFC 6347; - Using partial encryption of the sensitive data like RADIUS for transferring 'Tunnel Password', as described in IETF RFC 2868, section 3.5, where CP function and UP function is configured with a shared secret.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2021-02-10 11:07:06","uploaded":"2021-02-10 13:19:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, CT WG3","lsoriginalls":"C4-210171","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100135.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100148","title":"LS from SA WG3: LS on User Plane Integrity Protection for eUTRA connected to EPC","source":"SA WG3","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS in","for":"Action","abstract":"As part of their study on User Plane Integrity Protection for LTE (both 'option 1' and EN-DC\/'option 3(x)'), connected to EPC (documented in TR 33.853), SA WG3 have the following questions: a) (RAN 2 and RAN 3) when supporting UP IP do you have any feedback on whether it should be supported with NR PDCP or LTE PDCP or both? b) (SA WG2 and CT WG4) for the supply of UPIP policy to the RAN, is it preferred for the HSS to supply the policy to the MME (as in solution #11), or, for a 'combined SMF+PGW-C' to supply the policy to the MME (as outlined in solution #15)? c) (RAN 3 and CT 1) is a MME mandated to copy all the EEA\/EIA bits from NAS signalling into the S1-AP signalling? d) (RAN 3) is a legacy eNB mandated to copy all the EEA\/EIA bits from S1A-AP signalling into the X2-AP signalling at handover and secondary node addition? e) (SA WG2 and CT WG1)SA WG3 decides UE to send an indication to the network that the UE support UP IP with eNB, one of options is to reuse EEA\/EIA bits in UE EPS Security Capability (e.g. reuse EIA7 to indicate UE support UP IP with eNB), so that both eNB and MME can use the UE EPS Security Capability to know UE support UP IP with eNB. Does there any issue on this?. Action: SA WG3 politely request answers to the questions above from the identified working groups.","secretary_remarks":"Response drafted in S2-2100409. Final response in S2-2101306","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"replied to","reservation_date":"2021-02-10 11:07:06","uploaded":"2021-02-10 13:19:45","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, CT WG4, SA WG2","Cc":"CT WG1","lsoriginalls":"S3-210563","lsreply":"S2-2101306","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100148.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100151","title":"Reply-LS on Support of L2TP on SGi\/N6 with Control and User Plane Separation","source":"SA WG3","contact":"Christine Jost","contact-id":49662,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG4 for their LS S3-210024\/C4-205478 on Support of L2TP on SGi\/N6 with Control and User Plane Separation. SA WG3 believes that the procedures studied in CT WG4's work require an evaluation from a security point of view. Therefore, SA WG3 asks CT WG4 to keep SA WG3 informed of potential security related aspects of their work on Support of L2TP on SGi\/N6 with Control and User Plane Separation.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2021-02-10 11:07:06","uploaded":"2021-02-10 13:19:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3, SA WG2","lsoriginalls":"S3-210791","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100151.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100207","title":"[DRAFT] Reply LS on AKMA Anchor Function selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Ths document propsoes a reply to the LS from SA WG3","secretary_remarks":"Response to S2-2100045. Merged into S2-2101304","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"merged","reservation_date":"2021-02-12 03:25:15","uploaded":"2021-02-18 16:37:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"AKMA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100207.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100223","title":"[DRAFT] Reply LS on Secondary AUTH for 5GS interworking with EPS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This CR proposes a reply to CT WG3's LS on secondary authentication","secretary_remarks":"Response to S2-2100057. r03 agreed. Revised to S2-2101305, merging S2-2100103 and S2-2100406","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2021-02-12 15:16:12","uploaded":"2021-02-18 16:37:54","revisionof":"","revisedto":"S2-2101305","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, SA WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100223.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100229","title":"Support of the mapping from IP addressing information provided to an AF to the user identity","source":"Nokia, Nokia Shanghai Bell,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this case the 5GC first needs to retrieve the Permanent identifier of the UE before trying to fulfil the AF request. The 5GC may to determine the Permanent identifier of the UE based on: the UE IP address as provided by the AF the corresponding DNN and\/or S-NSSAI information: this may have been provided by the AF or determined by the NEF using the identity of the AF;","secretary_remarks":"Revision of (Endorsed DraftCR) S2-2009338 at SA2#142E. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"postponed","reservation_date":"2021-02-13 14:37:15","uploaded":"2021-02-18 08:29:05","revisionof":"S2-2009338","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":2385.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100229.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100230","title":"Support of the mapping from IP addressing information provided to an AF to the user identity","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An AF may request (via the NEF) information exposure or parameter provisioning targetting an individual UE, identifying the target UE by providing UE addressing information (e.g. IP address and port of the UE). In this case the 5GC (NEF) first needs to retrieve a Permanent Identifier of the UE Then the NEF Event exposure or the parameter provisioning as defined in R16 may apply. Nnef_EventExposure_Subscribe, Nnef_Location_LocationUpdateNotify and Nnef_ParameterProvision operations are modified accordingly. The NEF may deliver back to the AF an UE external Identifier for an Application. This UE external Identifier for an Application may later on be used by the AF to issue further requests about the same UE.","secretary_remarks":"Revision of (Postponed) S2-2009002 at SA WG2#142E. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"postponed","reservation_date":"2021-02-13 14:37:16","uploaded":"2021-02-18 08:29:05","revisionof":"S2-2009002","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"EDGEAPP"}],"crnumber":2329.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100230.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100260","title":"[DRAFT] LS on clarification on support of MAP message at the UDM for SMS and 5GS","source":"Nokia. Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"UDM interfaces with legacy SMS-GMSC\/IWMCS\/SMS Router","secretary_remarks":"Response to S2-2100055. r01 agreed. Revised to S2-2101311.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10610,"status":"revised","reservation_date":"2021-02-15 14:35:20","uploaded":"2021-02-18 15:12:04","revisionof":"","revisedto":"S2-2101311","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI, CT WG4, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100260.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100305","title":"LS From GSMA ACJA: Promotion of ACJA WebTalk The Power of Partnership - Clear Skies Ahead for Connected Drones","source":"GSMA AJCA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Introduction: Aerial Connectivity Joint Activity (ACJA)1 is the first initiative to result from the cooperation agreement signed last year by the GSMA and the Global UTM Association (GUTMA). ACJA has been conceived in large part to give relevant members o","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10510,"status":"noted","reservation_date":"2021-02-16 15:53:45","uploaded":"2021-02-16 16:07:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG6, TSG RAN","Cc":"","lsoriginalls":"LS_WebTalk 24 March 2021","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100305.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100398","title":"Handling of DN-AAA interactions in case of EPS IWK","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify DN-AAA interactions when UE is in EPS, e.g. how to handle a request for EAP-based re-authentication or re-authorization.","secretary_remarks":"Revision of S2-2100224. r08 agreed. Revised to S2-2101312.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10680,"status":"revised","reservation_date":"2021-02-17 12:49:03","uploaded":"2021-02-18 16:40:21","revisionof":"S2-2100224","revisedto":"S2-2101312","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2475.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100398.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100406","title":"[DRAFT] Reply LS on Secondary AUTH for 5GS interworking with EPS","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG3 LS on Secondary AUTH for 5GS interworking with EPS","secretary_remarks":"Response to S2-2100057. Merged into S2-2101305","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"merged","reservation_date":"2021-02-17 14:26:55","uploaded":"2021-02-18 21:19:00","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100406.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100409","title":"[DRAFT] Reply LS on User Plane Integrity Protection for eUTRA connected to EPC","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on User Plane Integrity Protection for eUTRA connected to EPC","secretary_remarks":"Response to S2-2100148. r03 agreed. Revised to S2-2101306.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2021-02-17 15:48:46","uploaded":"2021-02-18 21:19:00","revisionof":"","revisedto":"S2-2101306","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"RAN WG2, RAN WG3, CT WG4, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100409.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100416","title":"New SST for High-Performance Machine-Type Communications (HMTC)","source":"Qualcomm Incorprorated, Nokia, Nokia Shanghai Bell, AT&T, Convida Wireless, Futurewei","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds the new SST for High-Performance Machine-Type Communications (HMTC)","secretary_remarks":"r02 agreed. Revised to S2-2101308.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"revised","reservation_date":"2021-02-17 16:12:03","uploaded":"2021-02-18 21:19:01","revisionof":"","revisedto":"S2-2101308","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"TEI17"}],"crnumber":2571.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100416.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100417","title":"[DRAFT] Reply LS from ATIS IoT Group: Request that a standardised SST value for this S-NEST new Slice Service Type (SST)","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 approved the attached TS 23.501 CR 2571 for rel.17 that adds this new SST in TS 23.501. The CR if approved by SA#91 (18-22 March 2021) will be implemented in the latest rel.17 version of TS 23.501.","secretary_remarks":"Response to S2-2100051. For CC#2. r01 + changes agreed. Revised to S2-2101051.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10490,"status":"revised","reservation_date":"2021-02-17 16:16:26","uploaded":"2021-02-18 21:19:01","revisionof":"","revisedto":"S2-2101051","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ATIS IoT Group","Cc":"TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100417.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100670","title":"Discussion on AAnF Selection.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper aims at discussing the AAnF selection method.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10700,"status":"noted","reservation_date":"2021-02-18 09:51:51","uploaded":"2021-02-18 10:40:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"AKMA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100670.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100671","title":"[DRAFT] Reply LS on AKMA Anchor Function selection","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to the LS on AKMA Anchor Function selection","secretary_remarks":"Response to S2-2100045. r06 agreed. Revised to S2-2101304, merging and S2-2100207","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"revised","reservation_date":"2021-02-18 09:51:51","uploaded":"2021-02-18 10:40:04","revisionof":"","revisedto":"S2-2101304","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"AKMA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100671.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100677","title":"Clarification of UE configuration update procedure","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the AMF may update UE configuration at anytime.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10710,"status":"noted","reservation_date":"2021-02-18 10:00:58","uploaded":"2021-02-18 10:20:03","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2542.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100677.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100682","title":"[DRAFT] Reply LS on NSSAA at inter-PLMN mobility","source":"Samsung","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4, SA WG3","secretary_remarks":"Response to S2-2100005. For CC#2. r07 agreed. Revised to S2-2101052.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10660,"status":"revised","reservation_date":"2021-02-18 10:09:06","uploaded":"2021-02-18 12:10:21","revisionof":"","revisedto":"S2-2101052","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100682.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100695","title":"DP on AMF re-allocation during EPS to 5GS Handover .","source":"Samsung","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"discussion","for":"Discussion","abstract":"Investigate the AMF re-allocation during EPS to 5GS handover based on LS from CT WG4 on Service Operation used during EPS to 5GS Handover with AMF re-allocation (C4-205702).","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2021-02-18 10:13:37","uploaded":"2021-02-18 12:10:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100695.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100726","title":"AMF reallocation during EPS to 5GS handover using N26","source":"Samsung","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The initial AMF selects a target AMF that can support EPC interworking and has N26 interface with the source MME.","secretary_remarks":"r04 agreed. Revised to S2-2101302.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"revised","reservation_date":"2021-02-18 10:20:14","uploaded":"2021-02-18 12:10:21","revisionof":"","revisedto":"S2-2101302","release":"Rel-16","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"TEI16"},{"winame":" 5GS_Ph1"}],"crnumber":2636.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100726.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100728","title":"AMF reallocation during EPS to 5GS handover using N26","source":"Samsung","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The initial AMF selects a target AMF that can support EPC interworking and has N26 interface with the source MME.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2021-02-18 10:28:43","uploaded":"2021-02-18 12:10:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"TEI16"},{"winame":" 5GS_Ph1"}],"crnumber":2553.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100728.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100729","title":"GPSI translation based on UE IP address","source":"Samsung, Nokia, Nokia Shanghai Bell","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to return GPSI as a static UE identifiers when the static UE identifier is requested by AF using Nbsf_Management_Discovery service operation.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"postponed","reservation_date":"2021-02-18 10:30:18","uploaded":"2021-02-18 11:51:00","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":534.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100729.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100741","title":"GPSI translation based on UE IP address","source":"Samsung","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to return GPSI as a static UE identifiers when the static UE identifier is requested by AF using Nbsf_Management_Discovery service operation.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"postponed","reservation_date":"2021-02-18 10:37:06","uploaded":"2021-02-18 11:51:00","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"EDGEAPP"}],"crnumber":2555.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100741.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100747","title":"[DRAFT] Reply LS on IP address to GPSI translation","source":"Qualcomm Incoporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies to SA WG3 raising issues related to the exposure of UE permanent identifier","secretary_remarks":"Response to S2-2100044. r14 agreed. Revised to S2-2101307.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"revised","reservation_date":"2021-02-18 10:41:54","uploaded":"2021-02-18 18:09:13","revisionof":"","revisedto":"S2-2101307","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_enh_EC"},{"winame":" eEDGE_5GC"},{"winame":" EDGEAPP"},{"winame":" FS_eEDGE_Sec"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100747.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100748","title":"Security issues with exposure of UE permanent Identifier.","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"discussion","for":"Decision","abstract":"This paper elaborates on the ongoing discussions in SA WG2, SA WG3 and SA WG6 of the mapping between UE IP address and GPSI and proposes a way forward.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"postponed","reservation_date":"2021-02-18 10:41:54","uploaded":"2021-02-18 18:09:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_enh_EC"},{"winame":" eEDGE_5GC"},{"winame":" EDGEAPP"},{"winame":" FS_eEDGE_Sec"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100748.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101006","title":"[DRAFT] Reply LS on initiation of new work item Q.Sig_Req_ETS_IMS_roaming 'Signalling requirements for emergency telecommunication service in IMS roaming environment'","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"LS out","for":"Approval","abstract":"Reply to ITU-T SG11","secretary_remarks":"Response to S2-2100036. r01 agreed. Revised to S2-2101310.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10580,"status":"revised","reservation_date":"2021-02-18 19:20:00","uploaded":"2021-02-18 21:49:30","revisionof":"","revisedto":"S2-2101310","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG11","Cc":"ITU-T SG2, TSG SA, TSG CT, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101006.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101011","title":"Discussion related to 'LS on User Plane Integrity Protection for eUTRA connected to EPC' in S2-2100148.","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"discussion","for":"Decision","abstract":"-","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"noted","reservation_date":"2021-02-18 20:21:33","uploaded":"2021-02-18 20:25:20","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101011.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101046","title":"LS from GSMA WSOLU: on 5G charging architecture for wholesale scenarios","source":"GSMA WSOLU","contact":"Marc BALON","contact-id":49009,"tdoctype":"LS in","for":"Information","abstract":"Context: GSMA has started last year the analysis of different roaming use cases based on 5G SA networks. Problem statement: 1) Use of Local breakout to deliver services to roaming users. 2) Issue with wholesale charging. 3) Issue with retail charging and service control. Business requirements: 1) Roaming cases. 2) Home cases with additional actors. 3) Roaming and Home cases with additional actors. 4) Important change to wholesale charging","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2021-02-22 17:08:05","uploaded":"2021-02-22 17:09:41","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"SA WG2","lsoriginalls":"WSOLU57 Doc 004_Rev1_LS 3GPP SA5 5G charging archi","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101046.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101049","title":"[DRAFT] Reply LS to Withdrawal of IEEE Std 802.1D-2004","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: IEEE 802.1","secretary_remarks":"Created at CC#1. Response to S2-2100034. Agreed. Revised to S2-2101300.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"revised","reservation_date":"2021-02-25 05:58:39","uploaded":"2021-02-25 08:28:52","revisionof":"","revisedto":"S2-2101300","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IEEE 802.1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101049.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101051","title":"Reply LS from ATIS IoT Group: Request that a standardised SST value for this S-NEST new Slice Service Type (SST)","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"To: ATIS IoT Group. CC: TSG SA, GSMA 5GJA. Attachments: TS 23.501 CR2571 (Rel-17)","secretary_remarks":"Revision of S2-2100417r01 + changes. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10500,"status":"approved","reservation_date":"2021-03-05 08:04:37","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100417","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100051","lsto":"ATIS IoT Group","Cc":"TSG SA, GSMA 5GJA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101051.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101052","title":"Reply LS on NSSAA at inter-PLMN mobility","source":"SA WG2","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4, SA WG3","secretary_remarks":"Revision of S2-2100682r07. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10670,"status":"approved","reservation_date":"2021-03-05 08:04:37","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100682","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100005","lsto":"CT WG1","Cc":"CT WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101052.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101300","title":"Reply LS on withdrawal of IEEE Std 801.1D-2004","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: IEEE 802.1","secretary_remarks":"Revision of S2-2101049. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"approved","reservation_date":"2021-03-05 08:04:45","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2101049","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100034","lsto":"IEEE 802.1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101300.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101301","title":"LS on Service Operation used during EPS to 5GS Handover with AMF re-allocation","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachments: 23.502 CR 2456","secretary_remarks":"Revision of S2-2100070. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"approved","reservation_date":"2021-03-05 08:04:45","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100070","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100021","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101301.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101302","title":"AMF reallocation during EPS to 5GS handover using N26","source":"Samsung","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The MME need have N26 interface with the corresponding AMF.","secretary_remarks":"Revision of S2-2100726r04. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"agreed","reservation_date":"2021-03-05 08:04:45","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100726","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2636.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210081","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101302.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101303","title":"Corrections on EPS to 5GS Handover with AMF re-allocation","source":"Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Huawei,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When at EPS to 5GS handover using N26 interface (preparation phase) the Initial AMF reselects a target AMF, it invokes Namf_Communication_RelocateUEContext request and not Namf_Communication_CreateUEContext request Handover failure in target RAN handling with initial AMF and target AMF is added. Handover cancel from source RAN handling with initial AMF and target AMF is added. A NOTE is added to clarify that target AMF can be also the initial AMF when there is no AMF reallocation.","secretary_remarks":"Revision of S2-2100071r02. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"agreed","reservation_date":"2021-03-05 08:04:46","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100071","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"eNS"}],"crnumber":2456.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210075","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101303.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101304","title":"Reply LS on AKMA Anchor Function selection","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"Reply to the LS on AKMA Anchor Function selection","secretary_remarks":"Revision of S2-2100671r06, merging and S2-2100207. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"approved","reservation_date":"2021-03-05 08:04:47","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100671","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"AKMA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100045","lsto":"SA WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101304.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101305","title":"Reply LS on Secondary AUTH for 5GS interworking with EPS","source":"SA WG2","contact":"Stefan Rommer","contact-id":25950,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG3. Attachment: TS 23.502 CR2475 (Rel-16)","secretary_remarks":"Revision of S2-2100223r03, merging S2-2100103 and S2-2100406. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"approved","reservation_date":"2021-03-05 08:04:47","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100223","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100057","lsto":"CT WG3","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101305.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101306","title":"Reply LS on User Plane Integrity Protection for eUTRA connected to EPC","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, CT WG1. CC: RAN WG2, RAN WG3, CT WG4","secretary_remarks":"Revision of S2-2100409r03. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"approved","reservation_date":"2021-03-05 08:04:47","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100409","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100148","lsto":"SA WG3, CT WG1","Cc":"RAN WG2, RAN WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101306.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101307","title":"Reply LS on IP address to GPSI translation","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, SA WG6. CC: SA WG1","secretary_remarks":"Revision of S2-2100747r14. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"approved","reservation_date":"2021-03-05 08:04:47","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100747","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_enh_EC"},{"winame":" eEDGE_5GC"},{"winame":" EDGEAPP"},{"winame":" FS_eEDGE_Sec"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100044","lsto":"SA WG3, SA WG6","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101307.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101308","title":"New SST for High-Performance Machine-Type Communications (HMTC)","source":"Qualcomm Incorprorated, Nokia, Nokia Shanghai Bell, AT&T, Convida Wireless, Futurewei, Ericsson","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds the new SST for High-Performance Machine-Type Communications (HMTC)","secretary_remarks":"Revision of S2-2100416r02. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10480,"status":"agreed","reservation_date":"2021-03-05 08:04:47","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100416","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"TEI17"}],"crnumber":2571.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210087","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101308.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101309","title":"LS on PAP\/CHAP and other point-to-point protocols usage in 5GS","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: CT WG1, CT WG3, CT WG4","secretary_remarks":"Revision of S2-2100074r01. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10560,"status":"approved","reservation_date":"2021-03-05 08:04:49","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100074","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100004","lsto":"SA WG3","Cc":"CT WG1, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101309.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101310","title":"Reply LS on initiation of new work item Q.Sig_Req_ETS_IMS_roaming 'Signalling requirements for emergency telecommunication service in IMS roaming environment'","source":"SA WG2","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"LS out","for":"Approval","abstract":"To: ITU-T Study Group 11. CC: ITU-T Study Group 2, TSG SA, TSG CT, SA WG6","secretary_remarks":"Revision of S2-2101006r01. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10590,"status":"approved","reservation_date":"2021-03-05 08:04:49","uploaded":"2021-03-05 09:01:16","revisionof":"S2-2101006","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100036","lsto":"ITU-T Study Group 11","Cc":"ITU-T Study Group 2, TSG SA, TSG CT, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101310.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101311","title":"Reply LS on clarification on support o MAP messages at the UDM for SMS in 5GS","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI, CT WG4, CT WG1","secretary_remarks":"Revision of S2-2100260r01. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10620,"status":"approved","reservation_date":"2021-03-05 08:04:49","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100260","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100055","lsto":"SA WG3-LI, CT WG4, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101311.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101312","title":"Handling of DN-AAA interactions in case of EPS IWK","source":"Ericsson, Nokia, Nokia Shanghai Bell, Cisco","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify DN-AAA interactions when UE is in EPS, e.g. how to handle a request for EAP-based re-authentication or re-authorization.","secretary_remarks":"Revision of S2-2100398r08. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10690,"status":"agreed","reservation_date":"2021-03-05 08:04:49","uploaded":"2021-03-05 08:31:18","revisionof":"S2-2100398","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2475.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-210082","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101312.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]