[{"name":"S2-2203626","title":"LS from CT WG1: LS on ECS provider identification in ECS address provisioning","source":"CT WG1","contact":"Lazaros Gkatzikis","contact-id":78831,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 while working on stage-3 protocol implementation of the ECS Address Configuration Information provisioning to the UE (over PCO with Session Management procedures) has identified the following conflict on stage-2 specifications: 1. TS 23.548 Subclau","secretary_remarks":"Revision of Postponed S2-2201930 from S2#150E. Response drafted in S2-2204692. Final response in S2-2204734","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11720,"status":"replied to","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-21 14:49:13","revisionof":"S2-2201930","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2, CT WG3","lsoriginalls":"C1-220854","lsreply":"S2-2204734","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203626.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203642","title":"LS from CT WG3: LS on handling of FQDN ranges in AF influence on traffic routing procedures","source":"CT WG3","contact":"Susana Fernandez","contact-id":42321,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is discussing the support of FQDN ranges as defined in TS 23.501 for AF influence on traffic routing procedures. According to that TS the FQDN range is considered one example of traffic filtering information and when provided, 'it may be used by SMF as one of the triggers for retrieving EAS Deployment Information from NEF. Retrieval of EAS Deployment Information is defined in TS 23.548 [130]'. CT WG3 has the following questions: Question 1: Is the FQDN range only used as a trigger to initiate the retrieval of EAS Deployment Information from NEF or is it also used to identify the traffic for influencing SMF routing decisions? Question 2: If it is used to identify the traffic for influencing SMF routing decisions, can SA WG2 clarify how it works? Is the FQDN range(s) used to identify the sessions\/users for which the EDIs apply, and if yes, how is this applicability exactly determined? Question 3: If it is only used as a trigger for the retrieval of EAS Deployment Information, why an FQDN range is required? Could a specific indicator or the application identifier included to identify the traffic satisfy the same purpose?. Action: CT WG3 kindly requests SA WG2 to answer the questions above and update their Specifications if considered necessary.","secretary_remarks":"Responses drafted in S2-2203880, S2-2204407. Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11760,"status":"postponed","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-22 05:13:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-222419","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203642.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203653","title":"LS from SA WG6: Reply LS on ECS provider identification in ECS address provisioning","source":"SA WG6","contact":"Nishant Gupta","contact-id":62473,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 thanks CT WG1 for their LS in S6-220044 (C1-220854). To resolve the concerns with ECS provider ID, SA WG6 has agreed the attached CR (S6-220857). SA WG6 kindly requests CT WG1 and SA WG2 to update the ECS configuration information in CT WG1 and SA WG2 specifications accordingly. Action: SA WG6 kindly requests CT WG1 and SA WG2 to take the above information into account and make relevant changes in their specifications.","secretary_remarks":"Response drafted in S2-2203928. Final response in S2-2204734","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11790,"status":"replied to","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-22 05:13:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"CT WG4, CT WG3","lsoriginalls":"S6-220930","lsreply":"S2-2204734","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203653.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203875","title":"Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New indication for EAS discovery. Removal of FQDNs as Traffic Descriptors.","secretary_remarks":"Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11800,"status":"postponed","reservation_date":"2022-05-05 18:15:23","uploaded":"2022-05-06 22:28:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3634.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203875.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203876","title":"Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New indication for EAS discovery. Transfer of EASDF subscription information from SMF to PCF.","secretary_remarks":"Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11810,"status":"postponed","reservation_date":"2022-05-05 18:15:25","uploaded":"2022-05-06 22:28:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3474.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203876.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203877","title":"Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New indication for EAS discovery.","secretary_remarks":"Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11820,"status":"postponed","reservation_date":"2022-05-05 18:15:26","uploaded":"2022-05-06 22:28:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":721.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203877.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203878","title":"Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Inclusion of a the new indicator Dynamic SM Policy control required","secretary_remarks":"Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11830,"status":"postponed","reservation_date":"2022-05-05 18:15:27","uploaded":"2022-05-06 22:28:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":59.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203878.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203879","title":"DP on PCF influence on EAS discovery procedure related to LS S2-2203642\/C3-222419.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Approval","abstract":"This DP is triggered by the LS S2-2203642\/C3-222419 and discusses how and what PCF can influence EAS discovery procedure based on AF influence traffic.","secretary_remarks":"Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11840,"status":"postponed","reservation_date":"2022-05-05 18:15:28","uploaded":"2022-05-06 22:28:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_EDGE_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203879.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203880","title":"[DRAFT] Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures","source":"Ericsson [to be SA WG2]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures. Response to S2-2203642","secretary_remarks":"Response to S2-2203642. Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11770,"status":"postponed","reservation_date":"2022-05-05 18:15:28","uploaded":"2022-05-06 22:28:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203880.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204128","title":"Corrections to the ECS configuration information","source":"Vivo","contact":"Huazhang Lyu","contact-id":88594,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the explaination of ECSP ID in the ECS configuration information that the ECSP ID shall be included if the ECS configuration information is delivered by the 5GC to UE.","secretary_remarks":"Merged into S2-2204972","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11850,"status":"merged","reservation_date":"2022-05-06 07:22:41","uploaded":"2022-05-06 12:17:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3482.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204128.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204129","title":"Corrections to the ECS configuration information for ECS provider ID in TS 23.548","source":"Vivo","contact":"Huazhang Lyu","contact-id":88594,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the explaination of ECSP ID in the ECS configuration information that the ECSP ID shall be included if the ECS configuration information is delivered by the 5GC to UE.","secretary_remarks":"Merged into S2-2204945","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11860,"status":"merged","reservation_date":"2022-05-06 07:22:42","uploaded":"2022-05-06 12:17:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":60.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204129.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204407","title":"[DRAFT] Reply LS on handling of FQDN ranges in AF influence on traffic routing procedures","source":"CATT","contact":"Yuan Tao","contact-id":94861,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on handling of FQDN ranges in AF influence on traffic routing procedures (S2-2203642\/C3-222419). Response to S2-2203642","secretary_remarks":"Response to S2-2203642. Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11780,"status":"postponed","reservation_date":"2022-05-06 11:57:48","uploaded":"2022-05-06 12:17:31","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"C3-222419","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204407.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204408","title":"Clarification on handling of FQDN ranges","source":"CATT","contact":"Yuan Tao","contact-id":94861,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the usage of FQDN ranges in AF influence on traffic routing procedures.","secretary_remarks":"Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11870,"status":"postponed","reservation_date":"2022-05-06 11:57:48","uploaded":"2022-05-06 12:17:30","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3651.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204408.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204690","title":"Alignment of ECS Address Configuration Information to SA WG6's definition","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The definition of Table 4.15.6.3d-1 is updated to refer TS 23.558. Description of ECS address configuration informaiton in table 5.2.3.3.1-1 to refer TS 23.558.","secretary_remarks":"r01 agreed. Revised to S2-2204736, merging S2-2204682","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11880,"status":"revised","reservation_date":"2022-05-06 20:49:09","uploaded":"2022-05-06 21:14:08","revisionof":"","revisedto":"S2-2204736","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3498.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204690.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204691","title":"Alignment of ECS Address Configuration Information to SA WG6's definition","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 6.5.2.1 is updated to refer to the ECS configuration information defined in TS 23.558. Details of spatial validity conditions are also included. This information is referenced by TS 23.558.","secretary_remarks":"r02 agreed. Revised to S2-2204737, merging S2-2204688","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11900,"status":"revised","reservation_date":"2022-05-06 20:49:10","uploaded":"2022-05-06 21:14:08","revisionof":"","revisedto":"S2-2204737","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":61.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204691.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204692","title":"[DRAFT] Reply LS on ECS provider identification in ECS address provisioning","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6, CT WG1. CC: CT WG3, CT WG4. Response to S2-2203626","secretary_remarks":"Response to S2-2203626 and S2-2203653. r02 agreed. Revised to S2-2204734.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11730,"status":"revised","reservation_date":"2022-05-06 20:49:11","uploaded":"2022-05-06 21:14:08","revisionof":"","revisedto":"S2-2204734","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, CT WG1 CT WG3, CT WG4","Cc":"CC: CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204692.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204734","title":"[DRAFT] Reply LS on ECS provider identification in ECS address provisioning","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6, CT WG1. CC: CT WG3, CT WG4. Response to S2-2203626","secretary_remarks":"Revision of S2-2204692r02. Approved. CC#3: Corrections needed. Revised to S2-2205387.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11740,"status":"revised","reservation_date":"2022-05-23 07:09:40","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2204692","revisedto":"S2-2205387","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, CT WG1 CT WG3, CT WG4","Cc":"CC: CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204734.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204736","title":"Alignment of ECS Address Configuration Information to SA WG6's definition","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The definition of Table 4.15.6.3d-1 is updated to refer TS 23.558. Description of ECS address configuration informaiton in table 5.2.3.3.1-1 to refer TS 23.558.","secretary_remarks":"Revision of S2-2204690r01, merging S2-2204682. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11890,"status":"agreed","reservation_date":"2022-05-23 07:09:40","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2204690","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3498.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204736.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204737","title":"Alignment of ECS Address Configuration Information to SA WG6's definition","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 6.5.2.1 is updated to refer to the ECS configuration information defined in TS 23.558. Details of spatial validity conditions are also included. This information is referenced by TS 23.558.","secretary_remarks":"Revision of S2-2204691r02, merging S2-2204688. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11910,"status":"agreed","reservation_date":"2022-05-23 07:09:41","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2204691","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":61.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204737.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205387","title":"Reply LS on ECS provider identification in ECS address provisioning","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6, CT WG1. CC: CT WG3, CT WG4","secretary_remarks":"Revision of S2-2204734. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11750,"status":"approved","reservation_date":"2022-05-23 07:13:30","uploaded":"2022-05-24 08:11:39","revisionof":"S2-2204734","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203626","lsto":"SA WG6, CT WG1","Cc":"CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2205387.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]