[{"name":"S6-251008","title":"LS on Metaverse application enablement","source":"SA [SP-241935]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2025-03-25 01:14:49","uploaded":"2025-03-26 23:18:04","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"Metaverse_App"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T TSAG, MSF DAM-WG","Cc":"ITU-T SG21, SA4, SA6","lsoriginalls":"SP-241935","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_066_Gothenburg\/docs\/S6-251008.zip","group":"S6","meeting":"S6-66","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-251009","title":"LS to 3GPP TSG SA About New Procedures and API Development","source":"GSMA TSG IMSDCAS [IMSDCAS22_011]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. \tBackground \nGSMA TSG IMSDCAS and GSMA NG UPG wishes to thank for SP-241404 provided clarifications and the confirmation that there is no relationship, conflict or overlaps between the Application Programming Interface (API) specified by GSMA TSG IMSDCAS and the APIs already existing or planned to be specified by 3GPP SA6. And for outlining the work that has been undertaken with 3GPP TR 23.700-92 and 3GPP TS 23.392. GSMA TSG IMSDCAS and GSMA NG UPG finds most interesting and relevant 3GPP SA6 work related to the UE profile definition and the use of such profile to control the data channel content download to DCMTSI client in terminal. Those aspects are directly related to the mobile device functionalities and the content delivery over User Network Interface which are the key interest of both groups.\nIn addressing 3GPP SA6 questions GSMA TSG IMSDCAS, jointly with GSMA NG UPG,  would like to provide the following clarifications: \n\n  1.\tGSMA invites collaboration with 3GPP SA6 on aspects related to downloading procedures of data channel applications referred in SP-241404. The Terminal Steering Group should be contacted on UE related aspects of the procedures in question, including the definition of specific UE profiles to control such download. Network Group and specifically GSMA NG UPG should be contacted when network UNI aspects of the download need to be defined and GSMA NG NRG should be contacted when cooperation is required on the roaming aspects. \n\n  2.\tGSMA NG has NO plans to develop any network side Application Programming Interfaces (API) including APIs used by External Server\/content or APIs used by other elements to interact or control the External server. And in general NG and its subgroups don\u2019t develop network side APIs.\n\n  3. \tGSMA NG and GSMA TSG are not able to provide the list of standardisation gaps in the APIs needed by the External Server. The process to establish the related requirements and use cases is still to be initiated.  UPG#13 decided that a separate LS will be prepared to 3GPP explaining some specific implementation aspects linked to the external content access. The external access use case, once described and agreed, will be captured in GSMA PRD NG.129.\n  4. During the technical analysis and development of Annex C and Annex D of GSMA PRD NG.134 the main and broad conclusion concerned the lack of standards allowing data channel content interworking between 3GPP TS 26.114 defined IMS Data Channel subsystem and non-3GPP systems that might host such content, e.g. HTTP Server, from  the public internet and\/or in any private network. \n\n2\t. Request to 3GPP TSG SA\nGSMA TSG IMSDCAS and GSMA NG UPG jointly request 3GPP TSG SA and 3GPP SA6 to note the above responses. Further information will be provided at a later time.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":10090,"status":"postponed","reservation_date":"2025-03-25 01:14:49","uploaded":"2025-03-26 23:18:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA, SA6","Cc":"","lsoriginalls":"IMSDCAS22_011","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_066_Gothenburg\/docs\/S6-251009.zip","group":"S6","meeting":"S6-66","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-251010","title":"LS on the scope attribute of the access token standard claims","source":"SA5 [S5-251112]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2025-03-25 01:14:49","uploaded":"2025-03-26 23:18:04","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"MExpo"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3","Cc":"CT3, SA6","lsoriginalls":"S5-251112","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_066_Gothenburg\/docs\/S6-251010.zip","group":"S6","meeting":"S6-66","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-251011","title":"LS on withdrawal of Rel-17 version of TS 24.549","source":"CT [CP-250261]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nDuring CT1#153, CT1 had a discussion on TS 24.549 (Network slice capability enablement- Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification; Stage 3) and concluded that the Rel-17 and the Rel-18 versions of that specification are incompatible, due to the following:\n-\tTS 24.549 was introduced in Rel-17 under the eSEAL Work Item and followed the same structure and design layout as any other SEAL-related specification, i.e., procedures based on HTTP and CoAP were described.\n\n-\tIn Rel-18, TS 24.549 was updated under the NSCALE Work item. As part of this update, the structure and layout of the specification were changed to be based on 3GPP northbound interfaces and application layer APIs (NBI) specification. This means that the Rel-18 version of TS 24.549 defines APIs based on the OpenAPI specification and provides corresponding representations of all APIs defined in YAML format. At the same time, the procedures based on HTTP and CoAP were removed.\nCT1 discussed how to address this and concluded that CT1\u2019s preference is to withdraw the Rel-17 version of TS 24.549.\n\nSince the stage 2 for the stage 3 in TS 24.549 comes from SA6, CT would like to get SA6\u2019s feedback before proceeding with the withdrawal of the Rel-17 version of TS 24.549.\n\n2. Actions:\nTo SA6 group.\nACTION: \tCT asks SA6 to provide feedback on CT1\u2019s preference to withdraw the Rel-17 version of TS 24.549, and, if this preference is acceptable to SA6, to consider aligning their Rel-17 stage 2 specification accordingly.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":10110,"status":"postponed","reservation_date":"2025-03-25 01:14:49","uploaded":"2025-03-26 23:18:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eSEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"CT1, CT3, SA","lsoriginalls":"CP-250261","lsreply":"S6-252259, S6-252510, S6-252528","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_066_Gothenburg\/docs\/S6-251011.zip","group":"S6","meeting":"S6-66","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]