[{"name":"SP-200858","title":"Status report of TSG CT#89-e","source":"TSG CT Chairman","contact":"Lionel Morand","contact-id":25150,"tdoctype":"report","for":"Presentation","abstract":"Status report of TSG CT#89-e. Yvette Koza, CT WG4 Vicechair has announced her retirement and the Vice Chairman ship for CT WG4 will remain vacant for the time-being. For Information to SA E-meetings in 1H 2021: - Based on the current situation, it is assumed that meetings in 1H\/2021 will be in electronic format - TSG plenary dates are confirmed and will not be changed - WG meetings scheduled taking into account the plenary dates - If it appears that F2F meetings for one group or all the WGs can be safely resumed in the upcoming months, e-meetings will be converted to F2F meetings when feasible. Rel-17 timeline: - SA#89 may decide to shift stage 2 completion date to SA#91 - Could be 3-month delay - CT will check the SA#89 final output and decide on: - Stage 3 freeze date: Stage 2 freeze date + 9 months? - OpenAPI freeze date: Stage 3 freeze date + 3 months? - The final decision for CT will be taken in December - Any decision on the stage 2 freeze date should be considered as firm and definitive - A moving target makes difficult to correctly plan the stage 3 work Resuming the ToR Update process: - Work on a common description form for all working groups - Work on a common style for all working groups (Template) - Present draft version to the WG - Target for completion: TSG#90 For Action to SA Handling of TEI17-x WI: - TEI17-X created in SA WG2 have to be treated as normal WI in CT - If stage 3 work needed, a corresponding WI will be created in CT - Reusing the same WI code would ease the tracking of the all the CRs agreed - However, it should be made clear that any TEI17 CR in SA WG2 should not require a specific WI - Especially when TEI17 CRs are triggered based on work on done in CT - Example: LS on AUSF\/UDM discovery based on SUCI information (CP-202214) - Moreover, CT can approve TEI17 cat B CR without WID - Need for cross-TSG alignment CR: Procedure updates relating to WI: - Aim: Add guidance on the use of TEI. - SA#82 - SP-181188: First presentation - SA#83 - SP-190270: Approval - No LS has been sent to CT - Therefore, CT was not able to - evaluate the proposal - provide a formal feedback to SA before the update of TS 21.900 AUSF\/UDM discovery based on SUCI information: - LS in CP-202214 (C4-204337) - CT WG4 has analyzed the issue of insufficient length of Routing Indicator within SUCI, currently it is only 4 digits which is too short. - CT WG4 has also discussed the solution enabling to use the Home Public Key ID as an additional parameter (that allows to encode e.g. a 5th digit, in addition to the key ID on 4 bits) for the discovery of the AUSF\/UDM. - SA WG2 should provide corresponding stage-2 requirements first - SA WG2 is kindly asked to handle this topic in Q4 2020. AKMA Stage 3 issue: - Authentication and key management for applications based on 3GPP credential in 5G - Stage 2 completed in Rel-16 in SA WG3 - CT approved a WID for Rel-17 (too late for rel-16) - Stage 2 and stage 3 should be part of the same release - Stage 2 without stage 3 implies vendor-specific implementation - SA and SA WG3 are kindly requested to shift AKMA from Rel-16 to Rel-17 Acknowledgement: - Thanks to CT vice chairs, CT WG chairs and vice chairs and rapporteurs for excellent coordination of and work. 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.","secretary_remarks":"Noted","agenda_item_sort_order":26,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10630,"status":"noted","reservation_date":"2020-09-16 15:47:18","uploaded":"2020-09-21 13:21:46","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200858.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200859","title":"Draft report of TSG CT#89-e","source":"TSG CT Secretary (MCC)","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"report","for":"Information","abstract":"Draft meeting report of TSG CT#88E","secretary_remarks":"Noted","agenda_item_sort_order":26,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10640,"status":"noted","reservation_date":"2020-09-16 15:47:18","uploaded":"2020-09-17 13:01:15","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200859.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200860","title":"IETF Status report","source":"TSG CT Chairman","contact":"Lionel Morand","contact-id":25150,"tdoctype":"report","for":"Presentation","abstract":"IETF Status report. Summary: - 1 ongoing request for IANA port number assignment - 15 drafts have become RFC already - final CR in 3GPP still needed, for some of them - 19 drafts are in the RFC Editors Queue, - 4 drafts still under IESG review, - 4 individual drafts and - 4 drafts that have expired. IANA number Assignment: - Thanks to IESG, IANA has allocated the port 37472 to W1 interface - 3GPP is tasked to work on alternative solutions to avoid the need for port assignment for (private) 3GPP interfaces - A study has been initiated in CT WG4 (WID approved at CT#89-e) New published RFCs - RFC 8684 Title: TCP Extensions for Multipath Operation with Multiple Addresses - Was: draft-ietf-mptcp-rfc6824bis To be updated: TS 23.501 Rel-16 - RFC 8693 Title: OAuth 2.0 Token Exchange Was: draft-ietf-oauth-token-exchange To be updated: TS 24.482 (since rel-14) - RFC 8787 (NEW) Title: Location Source Parameter for the SIP Geolocation Header Field Was: draft-ietf-sipcore-locparam To be updated: TS 24.229 Rel-16 - RFC 8898 Title: Third-Party Token-based Authentication and Authorization for Session Initiation Protocol (SIP) Was: draft-ietf-sipcore-sip-token-authnz To be updated: TS 24.371 (since rel-12) - RFC 8803 Title: 0-RTT TCP Convert Protocol Was: draft-ietf-tcpm-converters To be updated: TS 23.501, 24.193, 29.244 (since rel-16) Drafts in RFC Editor queue: - draft-ietf-rtcweb-overview Title: Overview: Real Time Protocols for Browser-based Applications - draft-ietf-rtcweb-data-channel Title: WebRTC Data Channels - draft-ietf-rtcweb-data-protocol WebRTC Data Channel Establishment Protocol - draft-ietf-rtcweb-security Title: Security Considerations for WebRTC - draft-ietf-clue-framework Title: Framework for Telepresence Multi-Streams - draft-ietf-clue-signaling Title: Session Signaling for Controlling Multiple Streams for Telepresence (CLUE) - draft-ietf-clue-datachannel (NEW) Title: CLUE Protocol data channel - draft-ietf-clue-data-model-schema Title: An XML Schema for the CLUE data model - draft-ietf-clue-rtp-mapping Title: Mapping RTP streams to CLUE Media Captures - draft-ietf-clue-protocol (NEW) Title: Protocol for Controlling Multiple Streams for Telepresence (CLUE) - draft-ietf-mmusic-sctp-sdp Title: SDP Offer\/Answer Procedures For SCTP over DTLS Transport. - draft-ietf-mmusic-sdp-simulcast Title: Using Simulcast in SDP and RTP Sessions - draft-ietf-mmusic-data-channel-sdpneg Title: SDP-based Data Channel Negotiation - draft-ietf-mmusic-rid Title: RTP Payload Format Restrictions - draft-ietf-mmusic-dtls-sdp Title: SDP Offer\/Answer Considerations for DTLS and TLS - draft-ietf-mmusic-t140-usage-data-channel Title: T.140 Real-time Text Conversation over WebRTC Data Channels - draft-ietf-mmusic-mux-exclusive Indicating Exclusive Support of RTP\/RTCP Multiplexing using SDP - draft-ietf-mmusic-sdp-bundle-negotiation Title: Negotiating Media Multiplexing Using the SDP - draft-ietf-mmusic-msrp-usage-data-channel (NEW) Title: MSRP over Data Channels - draft-ietf-ice-trickle Title: Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol - draft-ietf-stir-passport-divert Title: PASSporT Extension for Diverted Calls Drafts under IESG review: - draft-ietf-emu-rfc5448bis Title: Improved Extensible Authentication Protocol Method for 3GPP Mobile Network Authentication and Key Agreement (EAP-AKA') Individual submission: - Managed by https:\/\/json-schema.org\/ Status: it seems a controversial topic in IETF. Not sure one of them get RFCized - draft-handrews-json-schema-validation [REST_SS] Title: JSON Schema Validation: A Vocabulary for Structural Validation of JSON - Published : 2019-09-17 - draft-handrews-json-schema [REST_SS] Title: JSON Schema: A Media Type for Describing JSON Documents - Published : 2019-09-17 - draft-handrews-json-schema-hyperschema [REST_SS] Title: JSON Hyper-Schema: A Vocabulary for Hypermedia Annotation of JSON Expired Drafts: - draft-schwarz-mmusic-sdp-for-gw - Still to","secretary_remarks":"Noted","agenda_item_sort_order":26,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10650,"status":"noted","reservation_date":"2020-09-16 15:47:18","uploaded":"2020-09-21 13:21:46","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200860.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200861","title":"LS from TSG CT: LS on information of stage 3 aspects for AKMA","source":"TSG CT","contact":"Zhenning Huang","contact-id":79939,"tdoctype":"LS in","for":"Action","abstract":"TSG CT has approved the WID AKMA-CT in Release 17 to implement the AKMA in stage 3, whereas the corresponding stage 2 requirements are in Rel-16. Action: TSG CT kindly ask TSG SA and SA WG3 to take above into account.","secretary_remarks":"SA WG3 and SA WG1 will work on CRs that will propose to shift AKMA SA WG3 to Rel-17. Additional changes for separate discussions. Proposal to change BB to Feature for discussion in SA WG3. Noted","agenda_item_sort_order":26,"ainumber":"4.8","ainame":"TSG CT reporting","tdoc_agenda_sort_order":10610,"status":"noted","reservation_date":"2020-09-17 05:02:43","uploaded":"2020-09-17 05:03:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG3","Cc":"CT WG1, CT WG3, CT WG4, CT WG6","lsoriginalls":"CP-202255","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200861.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]