[{"name":"S2-2600006","title":"LS from SA WG3: LS reply on LI requirements on IMS Data Channel","source":"SA WG3","contact":"Jing Ping","contact-id":106393,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for the LS regarding LI requirements on IMS Data Channel. {. .} Feedback from SA WG3: Since SA WG2 has not identified any gaps in supporting LI for these scenarios, SA WG3 will not explore them further. Action: SA WG3 kindly asks SA WG2, SA WG3-LI take the above answer for scenario 1 into account and requests SA WG2 to answer the question on the scenario 2.","secretary_remarks":"Revision of (postponed) S2-2509874. Responses drafted in S2-2600681, S2-2600750. Postponed in parallel session","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10590,"status":"postponed","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"S2-2509874","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI, SA WG2","Cc":"CT WG1, SA WG4","lsoriginalls":"S3-253806","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600006.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600012","title":"LS from SA WG3-LI: Reply LS on IMS Data Channel","source":"SA WG3-LI","contact":"Nagaraja Rao","contact-id":77267,"tdoctype":"LS in","for":"Action","abstract":"SA WG3-LI thanks SA WG2 and SA WG3 for the Reply LS on IMS Data Channel in tdocs S2-2507657 and S3-253806 respectively. SA WG3-LI would like to request SA WG2 additional clarifications on the IMS Data Channel related aspects. {. .} Action: SA WG3-LI kindl","secretary_remarks":"Revision of (postponed) S2-2510779. Should have been addressed to TSG SA instead of SA WG6. Responses drafted in S2-2600682, S2-2600750, S2-2600782. Postponed in parallel session","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10600,"status":"postponed","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"S2-2510779","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, CT WG4, SA WG3","Cc":"SA WG6","lsoriginalls":"S3i250674","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600012.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600042","title":"LS from SA WG3: Reply LS on the status of the IMS Avatar Security Aspects","source":"SA WG3","contact":"Vlasios Tsiatsis","contact-id":76181,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank SA WG2 for the Reply LS on Avatar Security Aspects. SA WG3 has completed the Rel-19 Security for IMS avatar communication as part of the work item NG_RTC_SEC_Ph2 with normative work in TS 33.328, Annex R. SA WG3 agreed the last CR084 for TS 33.328, Annex R in SA WG3#124 (Oct 17-21, 2025) which is expected to be approved during the SA#110. Action: SA WG3 asks SA WG2 to take the above information into account","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10920,"status":"noted","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG4","lsoriginalls":"S3-254551","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600042.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600046","title":"LS from SA WG4: Reply LS on clarification on reply SDP for standalone DC","source":"SA WG4","contact":"Daniel Philip VENMANI","contact-id":100768,"tdoctype":"LS in","for":"Action","abstract":"Question from SA WG2: SA WG2 has discussed one scenario of standalone IMS data channel session in which an originating UE initiates SIP INVITE request towards terminating UE with an initial SDP offer including BDC media, ADC media, and APP ID associated with the ADC. In this scenario, if the DC application is not available, i.e., needs to be downloaded by the terminating UE, it needs to indicate in the SDP answer to the initial SDP offer that the ADC is not able to be established due to downloading required. SA WG2 would like to ask SA WG4 to provide feedback on how to specify the required response as depicted above, in the SDP response to the received SDP offer. Answer from SA WG4: SA WG4 kindly responds to SA WG2 to the above question as follows: In this particular case when the DC application is not available at the terminating UE, i.e., needs to be downloaded by the terminating UE, the terminating UE needs to indicate in the SDP answer to the initial SDP offer that the ADC is not able to be established due to downloading required; the SDP offer shall indicate this via the newly defined 'a=3gpp-req-app' line 'app-dc-status' parameter with an 'app-dc-status-value' of 'pending' shall be included in an SDP offer, as defined by clause 6.2.10 of TS 26.114, to indicate the offering UE by the terminating UE as part of the media description creating application data channels for that application before the data channels are to be created. The terminating UE re-sends an offer to the originating UE once the app is downloaded. A detailed description of the above is included as CR in attachment. Action: SA WG4 kindly asks SA WG2 to take the above reply into account in response to the feedback on how to specify the required response in the SDP response to the received SDP offer.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10800,"status":"noted","reservation_date":"2026-01-14 14:27:35","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S4-252110","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600046.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600047","title":"LS from SA WG4: LS on avatar Communications","source":"SA WG4","contact":"Gaelle Martin-Cocher","contact-id":91571,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 has completed its work on the WID Avatar Communications in AR Calls [SP-250264] and the approved CR [SP-250926] has been integrated in TS 26.264. The work has been conducted consistently with the IMS architecture and clause AC.11 of TS 23.228. {. . .} Action: SA WG4 asks SA WG2 to review the above information and consider addressing these aspects in TS 23.228.","secretary_remarks":"Response drafted in S2-2600560. Agreed response in S2-2601222. Final response in S2-2601222","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10860,"status":"replied to","reservation_date":"2026-01-14 14:27:35","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3","lsoriginalls":"S4-252113","lsreply":"S2-2601222","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600047.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600176","title":"Modification on UEs behavior when the IMS Datachannel service timer expires","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-19 mirror CR: Summary of change: Add a Note in section AC.7.6: When the IMS Data Channel service times out, the UE sends a Reinvite request, in which the port number in the 'm=' line of the corresponding service is set to 0 to stop the service request.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10980,"status":"noted","reservation_date":"2026-01-26 10:21:15","uploaded":"2026-01-30 15:13:15","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC"}],"crnumber":1691.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600176.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.6","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600560","title":"[DRAFT] Reply LS on avatar Communications","source":"InterDigital, Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to SA WG4.","secretary_remarks":"Response to S2-2600047. Revised in parallel session to S2-2601222.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10870,"status":"revised","reservation_date":"2026-01-27 17:58:41","uploaded":"2026-01-30 15:37:35","revisionof":"","revisedto":"S2-2601222","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"AvCall-MED"},{"winame":" NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600560.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600562","title":"Support for Avatar calls in IMS","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added the abbreviations for ADC and BDC in clause 3.3. Updated NOTE 3 in clause AC.2.1 to say that the APIs that are specified in clause B.1 of TS 26.264 [104] can be used on the MDC2 reference point. Removed the editor's note in clause AC.11.3.2.2 and added a reference to clause 7.4 of TS 26.264.","secretary_remarks":"Check WI Code! Revised in parallel session to S2-2601221.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10890,"status":"revised","reservation_date":"2026-01-27 18:02:38","uploaded":"2026-01-30 15:37:35","revisionof":"","revisedto":"S2-2601221","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"AvCall-MED"},{"winame":" NG_RTC_Ph2"}],"crnumber":1692.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600562.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600676","title":"Correction to MTSI UE originated DC interworking","source":"Qualcomm Incorporated","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The procedures specified in clause AC.7.9.4. are corrected with following changes. The 'Application Data Channel requires interworking is established' event is detected when the application DC is initiated. The application DC is initiated either by the DCMTSI UE or the DC AS after the IMS session with only audio\/video is established. The DCSF instructs the IMS AS to trigger the DC interworking toward the DC AS and DCMTSI UE","secretary_remarks":"Revision of (Unhandled) S2-2508785. Revised in parallel session to S2-2601228.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10840,"status":"revised","reservation_date":"2026-01-29 04:45:57","uploaded":"2026-01-30 07:47:56","revisionof":"S2-2508785","revisedto":"S2-2601228","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1662.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600676.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600677","title":"Correction on the usage scenarios of DC Application Proxy for LI","source":"Qualcomm Incorporated, Nokia","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that 'DC Application Proxy' mode is used for network-initiated data channels or used according to local NW configuration. Clarify the supported proxy modes of MF in P2P application data channel establishment. Add DC Application Proxy mode in the Media proxy configuration of DC media description.","secretary_remarks":"Revision of (Endorsed) S2-2510949. Revised in parallel session to S2-2601223, merging S2-2600749,","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10680,"status":"revised","reservation_date":"2026-01-29 04:49:57","uploaded":"2026-01-30 07:49:31","revisionof":"S2-2510949","revisedto":"S2-2601223","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1686.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600677.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600678","title":"Correction on the usage scenarios of DC Application Proxy for LI","source":"Qualcomm Incorporated, Nokia?","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add 'DC Application Proxy' mode in MF for DC media setup (the same as specified in Rel-19), which is used for network-initiated data channels or used according to local NW configuration. Clarify the supported proxy modes of MF in P2P application data channel establishment. Add DC Application Proxy mode in the Media proxy configuration of DC media description.","secretary_remarks":"Not Handled","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10670,"status":"not treated","reservation_date":"2026-01-29 05:00:18","uploaded":"2026-01-30 07:49:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.228","crspecversion":"18.11.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1693.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600678.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600679","title":"Correction on supporting of IMS DC in roaming scenario","source":"Qualcomm Incorporated, Ericsson, Nokia","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in home-routed roaming scenarios, the home network ensures that the media packets of IMS DC are not encrypted take into consideration the regulatory and security requirements applicable to the involved networks.","secretary_remarks":"Revision of (Endorsed) S2-2510911. Revised in parallel session to S2-2601224.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10720,"status":"revised","reservation_date":"2026-01-29 05:04:05","uploaded":"2026-01-30 07:50:29","revisionof":"S2-2510911","revisedto":"S2-2601224","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1687.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600679.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600680","title":"Correction on supporting of IMS DC in roaming scenario","source":"Qualcomm Incorporated, Ericsson?, Nokia?","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in home-routed roaming scenarios, the home network ensures that the media packets of IMS DC are not encrypted taking into consideration the regulatory and security requirements applicable to the involved networks.","secretary_remarks":"Not Handled","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10710,"status":"not treated","reservation_date":"2026-01-29 05:08:27","uploaded":"2026-01-30 07:50:29","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.228","crspecversion":"18.11.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1694.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600680.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600681","title":"[DRAFT] Reply LS on LI requirements on IMS Data Channel","source":"Qualcomm","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 would like to notify SA WG3 that the use of 'DC Application Proxy' mode to fulfil LI requirements is clarified in the attached agreed CR against TS 23.228.","secretary_remarks":"Response to S2-2600006. Not Handled","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10610,"status":"not treated","reservation_date":"2026-01-29 05:20:06","uploaded":"2026-01-30 07:51:18","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG3-LI","Cc":"CT WG1, SA WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600681.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600682","title":"[DRAFT] Reply LS to SA WG3-LI on IMS Data Channel","source":"Qualcomm","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 provides feedback regarding the points 1 to 7.","secretary_remarks":"Response to S2-2600012. Not Handled","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10620,"status":"not treated","reservation_date":"2026-01-29 05:26:16","uploaded":"2026-01-30 07:51:18","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI","Cc":"CT WG1, CT WG4, SA WG3, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600682.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600694","title":"Clarification on Standalone IMS DC Session Procedure","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the standalone IMS DC session procedures in the scenario the requested application for establishing ADC is not available in the UE and the UE needs to download the application.","secretary_remarks":"Revised in parallel session to S2-2601227.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10810,"status":"revised","reservation_date":"2026-01-29 07:45:58","uploaded":"2026-01-30 07:18:13","revisionof":"","revisedto":"S2-2601227","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1695.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600694.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.10.2.2, AC.10.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600695","title":"Add Avatar ID in Avatar Media Specification","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the service definition of Nimsas_MediaControl_MediaInstruction service and Nmf_MRM_Create to include Avatar ID in Avatar media specification.","secretary_remarks":"Revised in parallel session to S2-2601229.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10930,"status":"revised","reservation_date":"2026-01-29 07:45:59","uploaded":"2026-01-30 07:18:13","revisionof":"","revisedto":"S2-2601229","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1696.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600695.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.3.2, AA.2.5.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600749","title":"Correction on the usage of DC Application Proxy","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that 'DC Application Proxy' mode is can be used for network-initiatedany kind of application data channels or used according to local NetworkW configuration. Clarify the supported proxy modes of MF in P2P application data channel establishment. Add DC Application Proxy mode in the Media proxy configuration of DC media description.","secretary_remarks":"Revision of (Endorsed) S2-2510949. Merged into S2-2601223","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10700,"status":"merged","reservation_date":"2026-01-29 15:18:37","uploaded":"2026-01-30 13:51:57","revisionof":"S2-2510949","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1686.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600749.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.6, AC.7.2.1, AA.2.4.3.2, AC.2.5.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600750","title":"[DRAFT] Reply LS on IMS Data Channel","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on IMS Data Channel","secretary_remarks":"Response to S2-2600012 and S2-2600006. Revised in parallel session to S2-2601226.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10630,"status":"revised","reservation_date":"2026-01-29 15:18:38","uploaded":"2026-01-30 13:51:57","revisionof":"","revisedto":"S2-2601226","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI, CT WG1, CT WG4","Cc":"SA WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600750.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600780","title":"Adding the DTLS Proxy configuration in IMS-AGW \/ TrGW for IMS DC LI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the DTLS Proxy configuration that is applicable for IMS AGW and TrGW.","secretary_remarks":"Revised in parallel session to S2-2601225.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10750,"status":"revised","reservation_date":"2026-01-29 20:08:21","uploaded":"2026-01-30 21:06:21","revisionof":"","revisedto":"S2-2601225","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1698.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600780.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600781","title":"Update Fig. AC.2.1-1 to show N91 and N92","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Include the reference points N91 & N92 in architecture representation.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10790,"status":"agreed","reservation_date":"2026-01-29 20:08:24","uploaded":"2026-01-30 21:06:21","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1699.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600781.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.2.1, AC.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600782","title":"[DRAFT] Reply LS on IMS Data Channel Response to: S2-2600012 \/ S3i250674 on LI requirements on IMS Data Channel","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Replies to SA WG3-LI on LI requirements on IMS Data Channel","secretary_remarks":"Response to S2-2600012. Not Handled","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10660,"status":"not treated","reservation_date":"2026-01-29 20:08:26","uploaded":"2026-01-30 21:06:21","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI, CT WG1, CT WG4, SA WG3","Cc":"SA WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600782.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600903","title":"Correction on the incorrect description on multiplexing data channel","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the incorrect description in clause AC.1.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10950,"status":"agreed","reservation_date":"2026-01-30 08:53:19","uploaded":"2026-01-30 13:09:24","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1700.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600903.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600904","title":"Correction on the inaccurate description on P2A2P procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the inaccurate description on P2A2P procedure in Annex AC.7.2.3.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":11000,"status":"noted","reservation_date":"2026-01-30 08:53:33","uploaded":"2026-01-30 13:09:24","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1701.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600904.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600905","title":"Updating the Mapping of Sh messages to HSS SBI services","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the mapping of Sh messages to HSS SBI services specifed in TS 23.228 Annex AA.2.2.3.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":11010,"status":"agreed","reservation_date":"2026-01-30 08:53:35","uploaded":"2026-01-30 13:09:24","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1702.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600905.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601003","title":"Corrections the procedure for Multiplexing multiple DC streams over single SCTP connection","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the 'MRF' in step 7 & 8 in Figure AC.7.10.4.1.1-1, step 6 & step 15 in Figure AC.7.10.4.2.1-1 and step 6 in Figure AC.7.10.4.2.2a-1. Correct the incorrect parts in the SDP offer and answer between the terminating side network and UE #2 from step 18 to 21 in Figure AC.7.10.4.2.1-1. Add 'capability indication' in step 1 & step 11 & step 12 & step 13 & step 14 & step 15 in Figure AC.7.10.4.1.1-1, step 2 & step 11 ~ step 15 & step 18 ~ 21 in Figure AC.7.10.4.1.2-1, step 1 & step 9, step 24 in Figure AC.7.10.4.2.1-1, step 1 & step 9 & step 19 in Figure AC.7.10.4.2.2a-1 and step 1, step 9 & step 25 in Figure AC.7.10.4.2.3-1. Correct the incorrect parts in the SDP answer transmitted from the terminating side network in step 17 & step 18 in Figure AC.7.10.4.2.2a-1 and step 22 in Figure AC.7.10.4.2.3-1. Remove the reserve media resource for multiplexed bootstrap DC in step 8 in Figure AC.7.10.4.1.1-1. Also, modify the SDP offer within the SIP message in Step 1 and modify the related description in AC.7.10.4.1.1.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10960,"status":"agreed","reservation_date":"2026-01-30 12:52:26","uploaded":"2026-01-30 13:54:20","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1703.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601003.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.10.4.1.1, AC.7.10.4.1.2, AC.7.10.4.2.1, AC.7.10.4.2.2a, AC.7.10.4.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601004","title":"Corrections to general description of Data Channel services in IMS","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the description of 'Multiplexing of multiple IMS Data Channel streams with different endpoints onto a single SCTP association is not supported in this Release of the specification.' in AC.1.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10990,"status":"noted","reservation_date":"2026-01-30 12:54:09","uploaded":"2026-01-30 13:54:33","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1704.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601004.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601005","title":"Clarification for determination of multiplexing and de-multiplexing","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Regarding the event notified to DCSF by IMS AS, separate the Standalone IMS DC session part and the general IMS DC session part. Describe the decision criteria for releasing the session or retrying based on a normal SDP offer, based on the content of the SIP message transmitted from the terminating side network.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10970,"status":"agreed","reservation_date":"2026-01-30 12:56:21","uploaded":"2026-01-30 13:55:08","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1705.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601005.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.10.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601221","title":"Support for Avatar calls in IMS","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added the abbreviations for ADC and BDC in clause 3.3. Updated NOTE 3 in clause AC.2.1 to say that the APIs that are specified in clause B.1 of TS 26.264 [104] can be used on the MDC2 reference point. Added text to AC.11.2 to point out","secretary_remarks":"Revision of S2-2600562. Revised in parallel session to S2-2601438.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10900,"status":"revised","reservation_date":"2026-02-16 09:16:43","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600562","revisedto":"S2-2601438","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"},{"winame":" AvCall-MED"}],"crnumber":1692.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601221.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601222","title":"Reply LS on avatar Communications","source":"SA WG2","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: SA WG3. Attachments: TS 23.228 CR 1692","secretary_remarks":"Revision of S2-2600560. Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10880,"status":"approved","reservation_date":"2026-02-16 09:16:44","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600560","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"AvCall-MED"},{"winame":" NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2600047","lsto":"SA WG4","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601222.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601223","title":"Correction on the usage of DC Application Proxy","source":"Qualcomm Incorporated, Nokia, Ericsson","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that 'DC Application Proxy' mode can be used for any kind of application data channels according to network configuration. Clarify the supported proxy modes of MF in P2P application data channel establishment. Add DC Application","secretary_remarks":"Revision of S2-2600677, merging S2-2600749, Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10690,"status":"agreed","reservation_date":"2026-02-16 09:16:44","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600677","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1686.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601223.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601224","title":"Correction on supporting of IMS DC in roaming scenario","source":"Qualcomm Incorporated, Ericsson, Nokia","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the support of IMS DC in home-routed roaming scenarios is determined by the home network taking into consideration the regulatory and security requirements applicable in both home and visited networks.","secretary_remarks":"Revision of S2-2600679. Revised in parallel session to S2-2601435.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10730,"status":"revised","reservation_date":"2026-02-16 09:16:44","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600679","revisedto":"S2-2601435","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1687.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601224.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601225","title":"Adding the DTLS Proxy configuration in IMS-AGW \/ TrGW for IMS DC LI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the DTLS Proxy configuration that is applicable for IMS AGW and TrGW.","secretary_remarks":"Revision of S2-2600780. Revised in parallel session to S2-2601436.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10760,"status":"revised","reservation_date":"2026-02-16 09:16:45","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600780","revisedto":"S2-2601436","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1698.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601225.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601226","title":"[DRAFT] Reply LS on IMS Data Channel","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on IMS Data Channel","secretary_remarks":"Revision of S2-2600750. Revised in parallel session to S2-2601439.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10640,"status":"revised","reservation_date":"2026-02-16 09:16:46","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600750","revisedto":"S2-2601439","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI, CT WG1, CT WG4","Cc":"SA WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601226.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601227","title":"Clarification on Standalone IMS DC Session Procedure","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the standalone IMS DC session procedures in the scenario the requested application for establishing ADC is not available in the UE and the UE needs to download the application.","secretary_remarks":"Revision of S2-2600694. Revised in parallel session to S2-2601437.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10820,"status":"revised","reservation_date":"2026-02-16 09:16:46","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600694","revisedto":"S2-2601437","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1695.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601227.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.10.2.2, AC.10.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601228","title":"Correction to MTSI UE originated DC interworking","source":"Qualcomm Incorporated","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The procedures specified in clause AC.7.9.4. are corrected with following changes. The 'Application Data Channel requires interworking is established' event is detected when the application DC is initiated. The application DC is initiat","secretary_remarks":"Revision of S2-2600676. Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10850,"status":"agreed","reservation_date":"2026-02-16 09:16:47","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600676","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1662.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601228.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601229","title":"Add Avatar ID in Avatar Media Specification","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the service definition of Nimsas_MediaControl_MediaInstruction service and Nmf_MRM_Create to include Avatar ID in Avatar media specification.","secretary_remarks":"Revision of S2-2600695. Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10940,"status":"agreed","reservation_date":"2026-02-16 09:16:47","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600695","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1696.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601229.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.3.2, AA.2.5.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601435","title":"Correction on supporting of IMS DC in roaming scenario","source":"Qualcomm Incorporated, Ericsson, Nokia, Deutsche Telekom","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the support of IMS DC in home-routed roaming scenarios is determined by the home network taking into consideration the regulatory and security requirements applicable in both home and visited networks.","secretary_remarks":"Revision of S2-2601224. Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10740,"status":"agreed","reservation_date":"2026-02-16 09:18:21","uploaded":"2026-02-16 09:31:07","revisionof":"S2-2601224","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1687.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601435.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601436","title":"Adding the DTLS Proxy configuration in IMS-AGW \/ TrGW for IMS DC LI","source":"Ericsson, Deutsche Telekom, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the DTLS Proxy configuration that is applicable for IMS AGW and TrGW.","secretary_remarks":"Revision of S2-2601225. Revised in parallel session to S2-2601480.","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10770,"status":"revised","reservation_date":"2026-02-16 09:18:22","uploaded":"2026-02-16 09:31:07","revisionof":"S2-2601225","revisedto":"S2-2601480","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1698.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601436.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601437","title":"Clarification on Standalone IMS DC Session Procedure","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the standalone IMS DC session procedures in the scenario the requested application for establishing ADC is not available in the UE and the UE needs to download the application.","secretary_remarks":"Revision of S2-2601227. Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10830,"status":"agreed","reservation_date":"2026-02-16 09:18:23","uploaded":"2026-02-16 09:31:07","revisionof":"S2-2601227","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1695.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601437.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.10.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601438","title":"Support for Avatar calls in IMS","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added the abbreviations for ADC and BDC in clause 3.3. Updated NOTE 3 in clause AC.2.1 to say that the APIs that are specified in clause B.1 of TS 26.264 [104] can be used on the MDC2 reference point. Added text to AC.11.2 to point out","secretary_remarks":"Revision of S2-2601221. Agreed in parallel session. Block approved","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10910,"status":"agreed","reservation_date":"2026-02-16 09:18:24","uploaded":"2026-02-16 09:31:07","revisionof":"S2-2601221","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"},{"winame":" AvCall-MED"}],"crnumber":1692.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-260084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601438.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601439","title":"[DRAFT] Reply LS on IMS Data Channel","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on IMS Data Channel","secretary_remarks":"Revision of S2-2601226. Postponed in parallel session","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10650,"status":"postponed","reservation_date":"2026-02-16 09:18:24","uploaded":"2026-02-16 09:31:07","revisionof":"S2-2601226","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI, CT WG1, CT WG4","Cc":"SA WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601439.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601480","title":"Adding the DTLS Proxy configuration in IMS-AGW \/ TrGW for IMS DC LI","source":"Ericsson, Deutsche Telekom, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the DTLS Proxy configuration that is applicable for IMS AGW and TrGW.","secretary_remarks":"Revision of S2-2601436. Postponed in parallel session","agenda_item_sort_order":113,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":10780,"status":"postponed","reservation_date":"2026-02-16 09:18:32","uploaded":"2026-02-16 09:41:04","revisionof":"S2-2601436","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.5.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1698.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601480.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]