IETF-3GPP coordination meeting at IETF 125 === Monday, 16 March 2026, Time: 12:45 to 13:45, Room: Jiangsu (Futian Shangri-La Hotel), Online: Meetecho Agenda - Welcome, notes, agenda bash - Liaison statements - Dependencies - RFC 3113 update - AoB Notes --- Welcome, notes, agenda bash - Add discussion around draft-ietf-tls-mlkem and preference of 3GPP for RFCs rather than Internet drafts for all dependencies/references Liaison statements - LS on need for modeling isInvariant and SystemCreated in YANG (2023/03/09) - Long running exchange between SA5 and NETMOD - SA5 encouraged to be active in NETMOD to represent their needs - Nothing more for IETF to do. - Reply LS on DTLS for SCTP (2023/08/21) from SA3 - Long running exchange between TSVWG and SA3/RAN3 - TSVWG to send another LS when make publication request for solution drafts - LS on PQC transition for RFC 6509 (2025/10/30) - IETF not planning to update - 3GPP will handle themselves - SA3 approved a new work item to work on mission critical communication. - Nothing more for IETF to do. - LS on “IETF Network Slice Application in 3GPP 5G End-to-End Network Slice” (2025/09/11) - SA and RAN3 provided feedback - Draft authors to send email about how feedback was addressed - Feedback from SA was accidentally overlooked - LS to be sent by TEAS once all feedback has been addressed Dependencies - draft-ietf-mimi-content - Zahed concerned about lack of progress here - Miraj agrees - Used for RCS in 3GPP - Charles to follow up with draft authors to see if it is stalled, next steps - Peter to get more details on 3GPP use - General feedback that would be useful to include more detail about what info with drafts 3GPP is referencing, similar to the level of detail provided for draft-ietf-moq-transport - Qlog - No depenceny at this time - Zahed: coud be very useful for troubleshooting with QUIC. Potential LS to SA. - Peter: could be helpful for CT to consider as part of their Release 20 study phase. - Dependencies for 3GPP studies (TRs) in addition to normative (TSs) - can be helpful to have some coordination on these things, e.g., Qlog RFC 3113 update - Updates to RFC 4052 and 4053 happening in parallel - Create wiki to track things not covered in, or are being moved out of, RFC 3113 - Mirja: Update to draft-kes-rfc3113bis to be published soon AoB - 3GPP Release 19, 20, 21 timelines - 3GPP is looking for progress on AI-related topics, such as AI proto, that they can point to and start to incorporate into their plans for 6G - 3GPP preference for RFCs for IETF dependencies/normative references - Concern from other other SDOs (IEEE, 3GPP) that IETF will consider Internet drafts sufficient and choose to not publish RFCs for some dependencies (i.e., draft-ietf-tls-mlkem). Discussion in TLS and also in IANABIS and SAAG - PQC study in SA3 has potential dependencies on lots of IETF drafts - 3GPP could include content from IETF draft in Annex for specification, but this is not preferred approach - Deb highlights that Internet draft has a version number, and that version is stable even if expires or another version is later provided - Lionel highlights that for code points, as long as requirements of adding to IANA registry are met, 3GPP is ok - Flo D points out the downside that allowing 3GPP to reference drafts in some cases while it is not appropriate in others has downside of requiring 3GPP participants to understand the nuances of IETF procedures MEETING CLOSED