[{"name":"SP-241055","title":"Status report of TSG CT#105","source":"TSG CT Chair","contact":"Peter Schmitt","contact-id":13753,"tdoctype":"report","for":"Presentation","abstract":"Status report of TSG CT#105. TSG CT Meeting Statistics: - Number of handled documents 259 - Approved CRs 842 - Approved New SID\/WID 28 - Approved Revised SID\/WID 2 - Noted or Approved TS\/TR 0 - Attendances: 287 registered - 226 confirmed participation - CRs for conditional approval listed in the Annex CT WG Statistics: Approved CRs by WG: - CT WG1 CRs for approval 256 - CT WG3 CRs for approval 290 - CT WG4 CRs for approval 256 - CT WG6 CRs for approval 40 Information to TSG SA: - At last meeting we had small open issues on Ranging_SL, ADAES work items. Those are now covered. - We started to apply FASMO rule for Rel-18 - CT has started the work on Rel-19 first set of CRs are approved Action to TSG SA: - At SA#104, SA tasked CT WG1 with taking the lead in analysing the gaps in LS SP-240522 from CEN on eCall over IMS (see SA LS in SP-240973). CT WG1 has performed this analysis and has asked SA to confirm that CT WG1 can start normative work a set of CRs where technically endorsed by CT WG1 and conditionally approved by CT which start the work' to 'CT WG1 has performed this analysis and has asked SA to confirm that CT WG1 can start normative work. A set of CRs where technically endorsed by CT WG1 and conditionally approved by CT, which starts the work e.g. there is one CR conditionally approved which is based on the assumption that PSAP callback for test eCall is not supported (question-6). - CT WGs have send LSs on Rel-18 topics SA WG should handle them with priority. Acknowledgement: - Thanks to CT vice chairs, CT WG chairs\/vice chairs and rapporteurs for the great coordination before and during the meeting. Special thanks to MCC Kimmo Kymalainen for excellent meeting support. - Thanks to the delegates in CT WGs and CT for achieving all deadlines as promised and delivering an enormous amount of CRs and input papers. - Thanks to Puneet (SA) and Wanshi (RAN) for the excellent coordination during the plenary week and in-between.","secretary_remarks":"Noted","agenda_item_sort_order":24,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10900,"status":"noted","reservation_date":"2024-08-07 13:10:10","uploaded":"2024-09-15 11:31:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_105_Melbourne_2024-09\/Docs\/SP-241055.zip","group":"SP","meeting":"SP-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-241056","title":"IETF Status report","source":"TSG CT Chair","contact":"Peter Schmitt","contact-id":13753,"tdoctype":"report","for":"Presentation","abstract":"IETF Status report. 3GPP-IETF Coordination meeting: - @IETF#120 (Vancover, CAN) - Monday 22nd July 2024 - Remote access was provided - One topic was handling of expired IETF drafts - @IETF#121 (Dublin, IRE) - Planned for 2024, November 4 - Remote access will be provided IETF - 3GPP IAB group: - Created in April 2023, similar to the IETF-IEEE IAB group - Group description - Support coordination between IETF and 3GPP as documented in RFC 3113. - Led jointly by the 3GPP and IETF liaison managers. - No fixed membership but participation from relevant IETF Area Directors, IETF WG Chairs, 3GPP WG Chairs, and document authors\/editors is encouraged. - See: https:\/\/datatracker.ietf.org\/group\/ietf3gpp\/about\/ - Action Points: - Tutorial and technical deep dive (TDD) on 3GPP planned for IETF 121 - Update the dependency list tool or create a new one (with IETF support) - Update RFC 3113: '3GPP-IETF Standardization Collaboration' (2001) IETF-3GPP Liaison Statements: - 3GPP SA -> QUIC - 3GPP SA WG3 and RAN WG3 -> IETF TSVWG - 3GPP SA WG5 -> NETMOD - TEAS -> SA WG2, SA WG3, SA WG5, RAN WG3 - DRIP WG Chairs -> 3GPP SA WG2, SA WG3 - TEAS -> SA WG2, SA WG3, SA WG5, RAN WG3 - 3GPP SA WG2 -> MASQUE - 3GPP SA WG4 -> IETF Tracking requests to IANA: - IANA assignment request handling - Overview: - A lot of IANA assignment requests have been done - Any IANA assignment request must be indicated to the IETF liaison and Specification Manager - Template for IANA assignment request as an Appendix included in the 3GPP specifications requiring the assignment - Diameter application identifier request needs to be added\/covered. - The requests are tracked by MCC on the 3GPP web page under Delegates Corner: IETF Dependencies: New Published RFCs: - Messaging Use Cases and Extensions for Secure Telephone Identity Revisited (STIR) RFC 9475 IETF reference updates: - None - IETF is working on a revision of RFC 6265 Drafts in RFC Editor queue: - draft-ietf-stir-passport-rcd-26 - draft-ietf-detnet-yang-20 Drafts under IESG review: - draft-ietf-opsawg-teas-attachment-circuit Active WG document: - draft-ietf-quic-multipath - draft-ietf-mimi-content-04 - draft-ietf-sipcore-rfc7976bis Expired drafts: - draft-holmberg-sipcore-auth-id-01 Individual submissions: - draft-newton-json-content-rules-09 - draft-bhutton-json-schema-validation - draft-bhutton-json-schema-01 - draft-handrews-json-schema-hyperschema - draft-kelly-json-hal-11 (ietf.org) AOB: Reminder - To allow tracing of all IETF drafts referenced in 3GPP specifications - IETF dependencies newly introduced in a 3GPP specification should be reported to the workplan manager by the 3GPP WG chairs. - IETF Coordinator will trace the progress of the IETF draft - The workplan manager will add a line to the workplan for each IETF draft. - The workplan manager will mark the task as completed once the IETF draft becomes an RFC and the RFC is referenced in the TS","secretary_remarks":"Noted","agenda_item_sort_order":24,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10910,"status":"noted","reservation_date":"2024-08-07 13:10:10","uploaded":"2024-09-15 11:31:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_105_Melbourne_2024-09\/Docs\/SP-241056.zip","group":"SP","meeting":"SP-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-241057","title":"Draft report of TSG CT#105","source":"TSG CT Secretary (MCC)","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"report","for":"Information","abstract":"Draft report of TSG CT#105","secretary_remarks":"Noted","agenda_item_sort_order":24,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10920,"status":"noted","reservation_date":"2024-08-07 13:10:10","uploaded":"2024-09-15 11:31:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_105_Melbourne_2024-09\/Docs\/SP-241057.zip","group":"SP","meeting":"SP-105","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]