Tdoc List
2024-02-02 17:25
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Agenda and Meeting Objectives | S3‑240000 | Agenda | SA WG3 Chair | agenda | Yes |
Yes
| approved | No | |||
S3‑240001 | Detailed agenda | SA WG3 Chair | agenda | Yes |
Yes
| noted | No | |||||
S3‑240002 | Emeeting process | SA WG3 | agenda | Yes |
Yes
| noted | No | |||||
2 | Meeting Reports | S3‑240137 | SA3 leadership notes | SA WG3 Chair | report | Information | Yes |
No
| available | No | ||
3 | Reports and Liaisons from other Groups ( related to SCAS) |   | ||||||||||
4 | Work areas |   | ||||||||||
4.1 | Maintenance (Rel-15/16/17/18) |   | ||||||||||
4.1.1 | Security Assurance | S3‑240003 | GSMA clarification: no unused software | BSI (DE) | CR | Approval | Yes |
Yes
| revised | No | S3‑240080 | |
S3‑240120 | Updates to Section 4.3.6.4 of TS 33.117 for clarification | IIT Bombay | CR | Approval | Yes |
Yes
| agreed | No | S3‑240074 | |||
S3‑240004 | GSMA clarification: no unused functions | BSI (DE) | CR | Approval | Yes |
Yes
| revised | No | S3‑240081 | |||
S3‑240005 | GSMA clarification: no unsupported components | BSI (DE) | CR | Approval | Yes |
Yes
| revised | No | S3‑240082 | |||
S3‑240006 | GSMA clarification: Filesystem Authorization privileges | BSI (DE) | CR | Yes |
Yes
| revised | No | S3‑240083 | ||||
S3‑240007 | Correct RRC connection reconfiguration to RRC reconfiguration | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| merged | No | S3‑240085 | |||
S3‑240008 | Test Case on Password Storage Support | Nokia, Nokia Shanghai Bell, BSI | CR | Approval | Yes |
Yes
| revised | No | S3‑240098 | |||
S3‑240009 | Test Case on No Default Content | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S3‑240099 | |||
S3‑240010 | Test Case on No Directory Listings | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S3‑240100 | |||
S3‑240011 | Test Case on No Web Server Header Info | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S3‑240101 | |||
S3‑240012 | Test Case on No Web Server Error Pages Info | Nokia, Nokia Shanghai Bell | CR | Yes |
Yes
| revised | No | S3‑240102 | ||||
S3‑240013 | Test Case on No Web Server File Type Mappings | Nokia, Nokia Shanghai Bell | CR | Yes |
Yes
| revised | No | S3‑240103 | ||||
S3‑240014 | Assessment tool definition | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| revised | No | S3‑240109 | |||
S3‑240015 | Discussion Paper on PCF SCAS contents | BSI (DE) | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S3‑240016 | Improving the SCAS specification way of work | Nokia, Nokia Shanghai Bell | discussion | Yes |
Yes
| noted | No | |||||
S3‑240017 | Minimized kernel network functions (TC_ IP_MULTICAST_HANDLING) | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| revised | No | S3‑240088 | |||
S3‑240018 | No automatic launch of removable media [TC_NO_AUTO_LAUNCH_OF_REMOVABLE_MEDIA] | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| revised | No | S3‑240089 | |||
S3‑240019 | Syn Flood Prevention [TC_SYN_FLOOD_PREVENTION] | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| revised | No | S3‑240090 | |||
S3‑240020 | External file system mount restrictions (TC_EXTERNAL_FILE_SYSTEM _MOUNT_RESTRICTIONS) | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| revised | No | S3‑240091 | |||
S3‑240026 | Clarification of bootable memory device test | BSI (DE) | CR | Approval | Yes |
Yes
| revised | No | S3‑240084 | |||
S3‑240027 | Clarification of UP Integrity Protection test cases for eNB | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑240028 | Clarification of UP IP selection and bidding down prevention of eNB | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑240029 | Added parameters to NRF discovery authorization | BSI (DE) | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑240030 | Added parameters to NRF discovery authorization threat reference | BSI (DE) | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑240031 | Clarification and simplification of test cases regarding UP CP and IP activation at split-gNB | BSI (DE) | CR | Approval | Yes |
Yes
| revised | No | S3‑240085 | |||
S3‑240032 | Clarification of test cases on user data IP and CP in split-gNB | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑240033 | Removal of note in GVNP lifecyle management | BSI (DE) | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑240034 | Fixed typo in VNF traffic separation test case | BSI (DE) | CR | Approval | Yes |
Yes
| revised | No | S3‑240087 | |||
S3‑240035 | Clarifications to Basic Vulnerability test cases | MITRE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑240036 | Update to the clause 4.2.2.2.2 - Protection at the transport layer | Samsung | CR | Agreement | Yes |
Yes
| revised | No | S3‑240092 | |||
S3‑240037 | Update to the clause 4.2.3.2.4 - Protecting data and information in transfer | Samsung | CR | Agreement | Yes |
Yes
| revised | No | S3‑240094 | |||
S3‑240038 | Update to the clause 4.2.3.3.2 - Boot from intended memory devices only | Samsung | CR | Agreement | Yes |
Yes
| revised | No | S3‑240095 | |||
S3‑240039 | Update to the clause 4.2.3.4.1.1 - System functions shall not be used without successful authentication and authorization | Samsung | CR | Agreement | Yes |
Yes
| revised | No | S3‑240096 | |||
S3‑240040 | Update to the clause 4.2.3.4.3.1 - Password Structure | Samsung | CR | Agreement | Yes |
Yes
| revised | No | S3‑240097 | |||
S3‑240041 | Updates threat references to TS 33.117 - clauses 4.2.2 to 4.2.3 | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S3‑240111 | |||
S3‑240042 | Updates threat references to TS 33.117 - clauses 4.2.4 to 4.2.6 | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S3‑240112 | |||
S3‑240043 | Updates threat references to TS 33.117 - clauses 4.3.2 | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑240044 | Updates threat references to TS 33.117 - clauses 4.3.3 | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑240045 | Updates threat references to TS 33.117 - clauses 4.3.4 to 4.3.5 | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S3‑240113 | |||
S3‑240046 | Updates threat references to TS 33.117 - clause 4.4.2 to 4.4.4 | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S3‑240114 | |||
S3‑240047 | Changes to 4.2.4.1.2.1 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240123 | |||
S3‑240048 | TS33.117_Changes to 4.2.4.2.2 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240124 | |||
S3‑240049 | TS33.117_Changes to 4.2.5.3 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240125 | |||
S3‑240050 | TS33.117_Changes to 4.2.6.2.1 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240126 | |||
S3‑240051 | Changes to 4.3.2.1 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240127 | |||
S3‑240052 | Changes to 4.2.2.1.8 in TS 33.511 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240128 | |||
S3‑240053 | Changes to 4.2.2.1.12 in TS 33.511 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240129 | |||
S3‑240054 | TS33.117_Changes to 4.2.2.2.2 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240130 | |||
S3‑240055 | Add certificate enrolment to TS 33.511 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑240056 | Peer certificate checking at gNB to TS 33.511 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑240057 | Add threat to certificate enrolment | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑240058 | Add threat to peer certificate checking at gNB | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑240059 | Test case update to TS 33.511 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240131 | |||
S3‑240060 | Change RRC SQN to PDCP COUNT | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240132 | |||
S3‑240061 | [mirror] correction to TS 33.511 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S3‑240062 | [mirror] correction to TS 33.511 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S3‑240063 | Clarification for 4.3.4.2 - 33.117 | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| revised | No | S3‑240115 | |||
S3‑240064 | Change RRC SQN to PDCP COUNT | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240133 | |||
S3‑240065 | Change RRC SQN to PDCP COUNT | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑240134 | |||
S3‑240066 | Clarification for 4.3.4.3 - 33.117 | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| revised | No | S3‑240116 | |||
S3‑240067 | Log transfer to centralized storage | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑240104 | |||
S3‑240068 | Growing content shall not influence system functions | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑240105 | |||
S3‑240069 | Processing of ICMPv4 and ICMPv6 packets | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑240106 | |||
S3‑240070 | Handling of IP options and extensions | Ericsson | CR | Yes |
Yes
| revised | No | S3‑240107 | ||||
S3‑240071 | Editorial Updates to Section 4.3.5.1 of TS 33.117 for clarification | IIT Bombay | CR | Approval | Yes |
Yes
| revised | No | S3‑240117 | |||
S3‑240072 | Editorial Updates to Section 4.3.6.2 of TS 33.117 for clarification | IIT Bombay | CR | Approval | Yes |
Yes
| revised | No | S3‑240117 | |||
S3‑240073 | Editorial Updates to Section 4.3.6.3 of TS 33.117 for clarification | IIT Bombay | CR | Approval | Yes |
Yes
| revised | No | S3‑240119 | |||
S3‑240074 | Editorial Updates to Section 4.3.6.4 of TS 33.117 for clarification | IIT Bombay | CR | Approval | Yes |
Yes
| revised | No | S3‑240120 | |||
S3‑240080 | GSMA clarification: no unused software | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | S3‑240003 | |||
S3‑240081 | GSMA clarification: no unused functions | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | S3‑240004 | |||
S3‑240082 | GSMA clarification: no unsupported components | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | S3‑240005 | |||
S3‑240083 | GSMA clarification: Filesystem Authorization privileges | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | S3‑240006 | |||
S3‑240084 | Clarification of bootable memory device test | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | S3‑240026 | |||
S3‑240085 | Clarification and simplification of test cases regarding UP CP and IP activation at split-gNB | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | S3‑240031 | |||
S3‑240086 | Removal of note in GVNP lifecyle management | BSI (DE) | CR | Approval | Yes |
Yes
| withdrawn | Yes | S3‑240033 | |||
S3‑240087 | Fixed typo in VNF traffic separation test case | BSI (DE) | CR | Approval | Yes |
Yes
| agreed | No | S3‑240034 | |||
S3‑240088 | Minimized kernel network functions (TC_ IP_MULTICAST_HANDLING) | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| not pursued | No | S3‑240017 | |||
S3‑240089 | No automatic launch of removable media [TC_NO_AUTO_LAUNCH_OF_REMOVABLE_MEDIA] | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| agreed | No | S3‑240018 | |||
S3‑240090 | Syn Flood Prevention [TC_SYN_FLOOD_PREVENTION] | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| agreed | No | S3‑240019 | |||
S3‑240091 | External file system mount restrictions (TC_EXTERNAL_FILE_SYSTEM _MOUNT_RESTRICTIONS) | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| not pursued | No | S3‑240020 | |||
S3‑240092 | Update to the clause 4.2.2.2.2 - Protection at the transport layer | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240036 | |||
S3‑240093 | Update to the clause 4.2.2.2.2 - Protection at the transport layer | Samsung | CR | Agreement | No |
Yes
| withdrawn | Yes | S3‑240036 | |||
S3‑240094 | Update to the clause 4.2.3.2.4 - Protecting data and information in transfer | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240037 | |||
S3‑240095 | Update to the clause 4.2.3.3.2 - Boot from intended memory devices only | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240038 | |||
S3‑240096 | Update to the clause 4.2.3.4.1.1 - System functions shall not be used without successful authentication and authorization | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240039 | |||
S3‑240097 | Update to the clause 4.2.3.4.3.1 - Password Structure | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240040 | |||
S3‑240098 | Test Case on Password Storage Support (TC_PSW_STOR_SUPPORT) | Nokia, Nokia Shanghai Bell, BSI | CR | Approval | Yes |
Yes
| agreed | No | S3‑240008 | |||
S3‑240099 | GSMA review - Test Case on No Default Content (TC_NO_DEFAULT_CONTENT) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S3‑240009 | |||
S3‑240100 | GSMA Review - Test Case on No Directory Listings (TC_NO_DIRECTORY_LISTINGS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S3‑240010 | |||
S3‑240101 | GSMA review - Test Case on No Web Server Header Info (TC_NO_WEB_SERVER_ HEADER_INFORMATION) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S3‑240011 | |||
S3‑240102 | GSMA review - Test Case on No Web Server Error Pages Info (TC_NO_WEB_SERVER_ERROR_ PAGES_INFORMATION) | Nokia, Nokia Shanghai Bell | CR | Yes |
Yes
| agreed | No | S3‑240012 | ||||
S3‑240103 | GSMA review - Test Case on No Web Server File Type Mappings (TC_NO_WEB_SERVER_FILE_TYPE MAPPINGS) | Nokia, Nokia Shanghai Bell | CR | Yes |
Yes
| agreed | No | S3‑240013 | ||||
S3‑240104 | Log transfer to centralized storage | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240067 | |||
S3‑240105 | Growing content shall not influence system functions | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240068 | |||
S3‑240106 | Processing of ICMPv4 and ICMPv6 packets | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240069 | |||
S3‑240107 | Handling of IP options and extensions | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240070 | |||
S3‑240108 | Removal of note in GVNP lifecyle management | BSI (DE) | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | S3‑240033 | |||
S3‑240109 | Assessment tool definition | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | S3‑240014 | |||
S3‑240110 | Clarifications to Basic Vulnerability test cases | MITRE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S3‑240035 | |||
S3‑240111 | Updates threat references to TS 33.117 - clauses 4.2.2 to 4.2.3 | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S3‑240041 | |||
S3‑240112 | Updates threat references to TS 33.117 - clauses 4.2.4 to 4.2.6 | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S3‑240042 | |||
S3‑240113 | Updates threat references to TS 33.117 - clauses 4.3.4 to 4.3.5 | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S3‑240045 | |||
S3‑240114 | Updates threat references to TS 33.117 - clause 4.4.2 to 4.4.4 | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S3‑240046 | |||
S3‑240115 | Clarification for 4.3.4.2 - 33.117 | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | S3‑240063 | |||
S3‑240116 | Clarification for 4.3.4.3 - 33.117 | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | S3‑240066 | |||
S3‑240117 | Updates to Section 4.3.5.1 of TS 33.117 for clarification | IIT Bombay | CR | Approval | Yes |
Yes
| agreed | No | S3‑240071 | |||
S3‑240118 | Updates to Section 4.3.6.2 of TS 33.117 for clarification | IIT Bombay | CR | Approval | Yes |
Yes
| agreed | No | S3‑240072 | |||
S3‑240119 | Updates to Section 4.3.6.3 of TS 33.117 for clarification | IIT Bombay | CR | Approval | Yes |
Yes
| agreed | No | S3‑240073 | |||
S3‑240123 | Addressing subjective comments from GSMA and comments in BSI AIS-N2to 4.2.4.1.2.1 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240047 | |||
S3‑240124 | Adding expected format of evidence to clause 4.2.4.2.2 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240048 | |||
S3‑240125 | Address GSMA comments and add pre-condition excution steps and evidence to 4.2.5.3 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240049 | |||
S3‑240126 | Add evidence to clause 4.2.6.2.1 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240050 | |||
S3‑240127 | Addressing subjective comments from GSMA and comments in BSI AIS-N2 to 4.3.2.1 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240051 | |||
S3‑240128 | Correct the Requirement from RRC signalling to User data | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240052 | |||
S3‑240129 | Change serving network name to gNB | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240053 | |||
S3‑240130 | Remove the additional can in the evidence | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240054 | |||
S3‑240131 | Test case update to TS 33.511 | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240059 | |||
S3‑240132 | Change RRC SQN to PDCP COUNT | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240060 | |||
S3‑240133 | Change RRC SQN to PDCP COUNT | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240064 | |||
S3‑240134 | Change RRC SQN to PDCP COUNT | Huawei; HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S3‑240065 | |||
4.1.2 | Service Based Architecture |   | ||||||||||
4.1.3 | Security Aspects of Proximity based services in 5GS ProSe |   | ||||||||||
4.1.4 | Mission Critical |   | ||||||||||
4.1.5 | Authentication and key management for applications based on 3GPP credential in 5G |   | ||||||||||
4.1.6 | Enhancements to User Plane Integrity Protection Support in 5GS |   | ||||||||||
4.1.7 | Security Aspects of Enhancements for 5G Multicast-Broadcast Services |   | ||||||||||
4.1.8 | Security for enhanced support of Industrial IoT |   | ||||||||||
4.1.9 | Security Aspects of eNPN |   | ||||||||||
4.1.10 | Security Aspects of Enhancement of Support for Edge Computing in 5GC |   | ||||||||||
4.1.11 | Security aspects of Uncrewed Aerial Systems |   | ||||||||||
4.1.12 | Security Aspects of Ranging Based Services and Sidelink Positioning |   | ||||||||||
4.1.13 | Security Aspects of eNA |   | ||||||||||
4.1.14 | Modified PRINS for roaming service providers in 5G |   | ||||||||||
4.1.15 | All other maintenance topics (not listed above) |   | ||||||||||
4.2 | New WID on 5G Security Assurance Specification (SCAS) for the Unified Data Repository (UDR). | S3‑240021 | Security Assurance Specification (SCAS) for the Unified Data Repository (UDR) | BSI (DE) | draft TS | Approval | Yes |
Yes
| approved | No | ||
S3‑240022 | Scope definition for draft TS 33.530 | BSI (DE) | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑240023 | Introduction for draft TS 33.530 clause 4 | BSI (DE) | pCR | Approval | Yes |
Yes
| revised | No | S3‑240079 | |||
S3‑240024 | UDR-specific security requirements and related test cases for draft TS 33.530 | BSI (DE) | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑240025 | Discussion of the protection mechanism of the permanent key leaving the UDR environment. | BSI (DE) | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S3‑240079 | Introduction for draft TS 33.530 clause 4 | BSI (DE) | pCR | Approval | Yes |
Yes
| approved | No | S3‑240023 | |||
S3‑240136 | Draft TS 33.530 | BSI (DE) | draft TS | Yes |
Yes
| approved | No | |||||
4.3 | New WID on SCAS for Rel-18 features on existing functions. |   | ||||||||||
4.4 | New WID on 5G Security Assurance Specification (SCAS) for the Short Message Service Function (SMSF). | S3‑240075 | Discussion of Diameter interface at SMSF to define requirements for Security Assurance Specifications for SMSF | IIT Bombay | discussion | Discussion | Yes |
Yes
| noted | No | ||
S3‑240076 | Add annexure to Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes specific to SMSF | IIT Bombay | CR | Approval | Yes |
Yes
| revised | No | S3‑240121 | |||
S3‑240077 | New requirement in SCAS for SMSF draft TS 33.529 | IIT Bombay | pCR | Approval | Yes |
Yes
| revised | No | S3‑240122 | |||
S3‑240078 | SMSF Specific Security requirement and test case for draft TS 33.529 | IIT Bombay | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑240121 | Add annexure to Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes specific to SMSF | IIT Bombay | CR | Approval | Yes |
Yes
| agreed | No | S3‑240076 | |||
S3‑240122 | New requirement in SCAS for SMSF draft TS 33.529 | IIT Bombay | pCR | Approval | Yes |
Yes
| approved | No | S3‑240077 | |||
S3‑240135 | Draft TS 33.529 | IIT Bombay | draft TS | Yes |
Yes
| approved | No | |||||
4.5 | New WID on Addition of 256-bit security Algorithms. |   | ||||||||||
5 | Rel-19 Studies |   | ||||||||||
6 | New Study/Work item proposals |   | ||||||||||
6.1 | Release/TU management |   | ||||||||||
6.2 | SID/WID proposals for SA3 prime topics |   | ||||||||||
6.3 | SID/WID proposals for feature security dependent on other WGs |   | ||||||||||
7 | CVD and research |   | ||||||||||
8 | Any Other Business |   |