[{"name":"SP-230822","title":"Status report of TSG CT#101","source":"TSG CT Chair","contact":"Peter Schmitt","contact-id":13753,"tdoctype":"report","for":"Presentation","abstract":"Status report of TSG CT#101. Release Status (Rel-8 - Rel-17) (Cat F CRs): - Approved Rel-8 CRs 0 - Approved Rel-9 CRs 0 - Approved Rel-9 CRs 0 - Approved Rel-10 CRs 0 - Approved Rel-11 CRs 1 - Approved Rel-12 CRs 1 - Approved Rel-13 CRs 0 - Approved Rel-14 CRs 1 - Rel-15 CRs (Category F) are less than in last plenary 1 (2) - Rel-16 CRs (Category F) 11 (42) - Rel-17 CRs (Category F) 64 (101 in previous TSG) Release 18 Status: - CRs (Category B\/C\/F\/D) 794 (1205 in previous TSG) - Approved New SID\/WID 4 - New Specification numbers allocated 1 - New TS\/TR presented for information\/approval 4 For Information to SA: - CT has received LS from IEEE Registration Authority Committee (RAC) - regarding allocation of an EtherType value per TS 24.193 v18.0.0. and ask on how to handle these kind of request. - CT has send an LS back clarifying the request. - We should handle requests to IEEE in same way as request to IETF\/IANA means creating web page in the same with a contact person and listing there all request done so far and also maintain this in future - Voting on working agreement (#57) on eUEPO work on UE policy provisioning took place the WA did not get 71% support. So related CRs are not approved by CT plenary. - CT discussed the proposal to split the WID template in a SID and WID template and the related changes to the working procedures. - CT is not in favour of this they do not see the benefit e.g. on submitting a SID paper in addition to the WID when it was noted that in WID some topics needs to be studied first e.g. BEPoP (TR29.820) - It was not clear how external TR29.9xx reports should be handled - TR 29.893 on \"Study on IETF QUIC Transport for 5GC Service Based Interfaces\" is now approved with the conclusion not to change the protocol stack for SBI interfaces. - Backward Incompatible Changes: - No backward incompatible changes have been approved by CT this time For Action to SA: - Documenting code in Forge-GitLab triggered by the LS from SA5 send to LS. - CT shall not be impacted by introducing the possibility to store OpenAPI source files only in Forge. In CT the current way of handling OpenAPI files works very well. - On the proposal to split the WID template in templates for SID and WID. - SA should take into account that CT is not in favour of the split - This should be a consolidated decision in RAN, CT and SA 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 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 chair) and Wanshi (RAN chair) for the excellent coordination during the plenary week and in-between.","secretary_remarks":"Noted","agenda_item_sort_order":25,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10930,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-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_101_Bangalore_2023-09\/Docs\/SP-230822.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230823","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 - Last: @IETF#117 (San Francisco) - 2023, July 24, 11:45 - 12:45 (PDT, UTC-7)(remote access provided) - With CT chair, IETF liaison, IESG members, IAB members, WG chairs and delegates. About 40 attendees - Some issues with the LS sent by IETF. - Reminder to IETF: LS from IETF have to be sent in a formatted document attached to the email sent to the 3GPP Liaison coordinator - Recommend IETG WG chairs work with Charles and Peter to post LSs in future - Remaining dependencies (about 7) under control - Next: @IETF#118 (Prague) - Will be held on 2023, November 6 - Remote access will be provided Ongoing Liaison Statements exchanged between IETF and 3GPP - Created in April 2023, similar to the IETF-IEEE IAB group - Group description - The purpose of this group is to support coordination activities 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: - Update the dependency list tool or create a new one (with IETF support) - Update RFC 3113: \"3GPP-IETF Standardization Collaboration\" (2001) - 3GPP->IETF: - Reply LS on DTLS for SCTP - isInvariant and SystemCreated in YANG - IETF->3GPP - None. Tracking requests to IANA: - IANA assignment request handling - Triggered by review of Rel-17 specifications : - A lot of IANA assignment requests have been done - Any IANA assignment request must be indicated to the IETF liaison - Template for IANA assignment request as an Appendix included in the 3GPP spec requiring the assignment - To track the requests MCC has created a web page: Status of the 3GPP-IETF dependencies: New Published RFCs: - Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR), RFC 9410 - Published 07\/2023 - CRs to 24.229 and 29.165 approved - Extension of the Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE) to Transport Layer Security (TLS), RFC 9430 - Published 07\/2023 - Next step: - CRs to 33.434 IETF reference updates: - None Drafts in RFC Editor queue: - draft-ietf-stir-passport-rcd-26 - Title: PASSporT Extension for Rich Call Data - Last update: 06\/2023 - Next steps: Publish as Proposed Standard RFC, CRs to 33.127 and 33.128 - draft-ietf-stir-messaging-08 - Title: Messaging Use Cases and Extensions for STIR - Last update: 08\/2023 - Next steps: Publish as Proposed Standard RFC, CRs to 33.127 - !!! WARNING !!! Wrong draft reference in 33.127 - IETF draft-ietf-stir-passport-messaging-00, \"Messaging Use Cases and Extensions for STIR\". Drafts under IESG review: - draft-ietf-detnet-yang-18 - Title: Deterministic Networking (DetNet) YANG Model - Last update: 07\/2023, addressing AD evaluation and feedback - Next step: - Publish as Proposed Standard RFC - CRs to 23.501, 23.503 and 29.565 Active WG documents: - draft-ietf-quic-multipath - Title: Multipath Extension for QUIC - Status: WG document, draft-ietf-quic-multipath-05 posted 07\/2023 - Next step: draft update, IESG review, RFC publication, SA2 CR to 23.501 - draft-jesske-update-p-visited-network - Title: Update to P-Visited-Network-ID in SIP Requests and Responses - Agreement to handle within SIPCORE at IETF 116 coordination meeting - Status: WG Last Call completed, draft-jesske-update-p-visited-network-05 posted 06\/2023 - Next steps: Additional WG review, IESG review, RFC publication, CT1 CR to 24.229 Individual submissions: - draft-boro-opsawg-teas-attachment-circuit - Title: YANG Data Models for 'Attachment Circuits'-as-a-Service (ACaaS) - Status: draft-boro-opsawg-teas-attachment-circuit-07 posted 07\/2023 - Next steps: WG adoption updates, IESG review, RFC publication, SA5 CR to 28.541","secretary_remarks":"Noted","agenda_item_sort_order":25,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10940,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-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_101_Bangalore_2023-09\/Docs\/SP-230823.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230824","title":"Draft report of TSG CT#101","source":"TSG CT Secretary (MCC)","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"report","for":"Information","abstract":"Draft report of TSG CT#101","secretary_remarks":"Noted","agenda_item_sort_order":25,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10950,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-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_101_Bangalore_2023-09\/Docs\/SP-230824.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]