|
| 23.502 | 1823 | - | F | 16.2.0 | Rel-16 | AMF redirection in case of slice isolation |
S2-1909570
| merged | SA2#135 | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.102 | 0279 | - | F | 15.1.0 | Rel-16 | Mandating time based generation of SQNs |
S3-192052
| not pursued | SA3#95-BIS | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.102 | 0277 | 1 | F | 15.1.0 | Rel-15 | Adding MACS as an input parameter to the calculation of AK* to provide freshness |
S3-191529
| revised | SA3#95 | Qualcomm Incorp... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.102 | 0277 | - | F | 15.1.0 | Rel-15 | Adding MACS as an input parameter to the calculation of AK* to provide freshness |
S3-190376
| revised | SA3#94 | Qualcomm Incorp... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.102 | 0276 | - | F | 15.0.0 | Rel-15 | Adding reference to 33.501 in 33.102 |
S3-183240
| agreed | SA3#93 | Nokia, Nokia Sh... |
SP-181022
| approved | SA#82 | SA WG3 | 15.1.0 | 5GS_Ph1-SEC |
|
|
| 33.210 | 0055 | - | F | 15.1.0 | Rel-15 | CR to 33210 r15 adding references for the TLS Protocol Profiles clause |
S3-183255
| agreed | SA3#93 | Juniper Network... |
SP-181022
| approved | SA#82 | SA WG3 | 15.2.0 | 5GS_Ph1-SEC |
|
|
| 33.210 | 0053 | - | F | 15.1.0 | Rel-15 | Adding references for the TLS Protocol Profiles clause |
S3-183230
| withdrawn | SA3#93 | Juniper Network... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.210 | 0050 | 1 | B | 15.0.0 | Rel-15 | Update NDS/IP scope with application layer crypto profiles |
S3-182606
| agreed | SA3#92 | Juniper Networks |
SP-180706
| approved | SA#81 | SA WG3 | 15.1.0 | 5GS_Ph1-SEC |
|
|
| 33.220 | 0197 | - | F | 15.3.0 | Rel-15 | Assigning additional FC values to TS 33.501 |
S3-183830
| agreed | SA3#93 | Qualcomm |
SP-181022
| approved | SA#82 | SA WG3 | 15.4.0 | 5GS_Ph1-SEC |
|
|
| 33.220 | 0191 | - | F | 15.1.0 | Rel-15 | 5G FC values in 33.220 |
S3-181883
| merged | SA3#91-Bis | LG Electronics |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.220 | 0190 | 1 | F | 15.1.0 | Rel-15 | Assigning FC values to TS 33.501 |
S3-181928
| agreed | SA3#91-Bis | Qualcomm Incorp... |
SP-180452
| approved | SA#80 | SA WG3 | 15.2.0 | 5GS_Ph1-SEC |
|
|
| 33.220 | 0190 | - | F | 15.1.0 | Rel-15 | Assigning FC values to TS 33.501 |
S3-181771
| revised | SA3#91-Bis | Qualcomm Incorp... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.303 | 0138 | - | F | 17.0.0 | Rel-17 | Correction figure in ProSe Discovery in TS33.303 |
S3-222004
| agreed | SA3#108-e | China Telecom C... |
SP-220881
| approved | SA#97-e | SA WG3 | 17.1.0 | 5GS_Ph1-SEC, TEI17 |
|
|
| 33.303 | 0137 | - | A | 16.0.0 | Rel-16 | Correction figure in ProSe Discovery in TS33.303(R16) - mirror |
S3-222003
| not pursued | SA3#108-e | China Telecom C... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.303 | 0136 | - | F | 15.0.0 | Rel-15 | Correction figure in ProSe Discovery in TS33.303(R15) |
S3-222002
| not pursued | SA3#108-e | China Telecom C... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.310 | 0095 | 1 | C | 15.0.0 | Rel-15 | Clarify NDS/AF intro regarding crypto profiles |
S3-182608
| agreed | SA3#92 | Juniper Networks |
SP-180706
| approved | SA#81 | SA WG3 | 15.1.0 | 5GS_Ph1-SEC |
|
|
| 33.401 | 0683 | 1 | C | 16.0.0 | Rel-16 | 33401-CR on CHO key derivation |
S3-194602
| not pursued | SA3#97 | Apple |
| | | | | TEI16, 5GS_Ph1-SEC |
|
|
| 33.401 | 0683 | - | C | 16.0.0 | Rel-16 | 33401-CR on CHO key derivation |
S3-193968
| revised | SA3#97 | Apple |
| | | | | 5GS_Ph1-SEC, TEI16 |
|
|
| 33.401 | 0652 | - | F | 15.2.0 | Rel-15 | Setting EEA7 and EIA7 to enable AMF to force MME to run a NAS SMC |
S3-180792
| not pursued | SA3#90-Bis | Qualcomm Incorp... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.401 | 0642 | - | F | 15.1.0 | Rel-15 | Making the NAS layer bidding down in EPC automatically cover new security features |
S3-173292
| | SA3#89 | Qualcomm Incorp... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.402 | 0144 | - | B | 14.3.0 | Rel-15 | Addition of EAP-5G method ID |
S3-180013
| agreed | SA3#90 | Lenovo, Motorol... |
SP-180049
| approved | SA#79 | SA WG3 | 15.0.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1978 | - | F | 18.5.0 | Rel-18 | UPU Header Security |
S3-241723
| merged | SA3#116 | Lenovo |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1967 | - | F | 15.17.0 | Rel-15 | Correction of UDM service naming |
S3-240844
| agreed | SA3#115 | BSI (DE) |
SP-240342
| approved | SA#103 | SA WG3 | 15.18.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1966 | - | A | 16.17.0 | Rel-16 | Correction of UDM service naming |
S3-240843
| agreed | SA3#115 | BSI (DE) |
SP-240342
| approved | SA#103 | SA WG3 | 16.18.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1965 | - | A | 17.12.0 | Rel-17 | Correction of UDM service naming |
S3-240842
| agreed | SA3#115 | BSI (DE) |
SP-240342
| approved | SA#103 | SA WG3 | 17.13.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1962 | 1 | F | 18.4.0 | Rel-18 | UPU Header Security |
S3-240991
| not pursued | SA3#115 | Lenovo |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1962 | - | F | 18.4.0 | Rel-18 | UPU Header Security |
S3-240754
| revised | SA3#115 | Lenovo |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1900 | 1 | A | 18.4.0 | Rel-18 | Correction of UDM service naming |
S3-240857
| agreed | SA3#115 | BSI (DE) |
SP-240342
| approved | SA#103 | SA WG3 | 18.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1900 | - | A | 18.4.0 | Rel-18 | Correction of UDM service naming |
S3-240329
| revised | SA3#115 | BSI (DE) |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1896 | 1 | F | 18.3.0 | Rel-18 | UPU Header Security |
S3-235047
| withdrawn | SA3#113 | Lenovo |
| | | | | TEI18, 5GS_Ph1-SEC |
|
|
| 33.501 | 1896 | - | F | 18.3.0 | Rel-18 | UPU Header Security |
S3-234421
| not pursued | SA3#113 | Lenovo |
| | | | | 5GS_Ph1-SEC, TEI18 |
|
|
| 33.501 | 1894 | - | F | 18.3.0 | Rel-19 | Correction in trusted non-3GPP access authentication |
S3-234419
| not pursued | SA3#113 | Lenovo |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1669 | - | A | 16.14.0 | Rel-16 | Clarification to the UPU procedures |
S3-233390
| agreed | SA3#111 | Qualcomm Incorp... |
SP-230614
| approved | SA#100 | SA WG3 | 16.15.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1668 | - | F | 15.16.0 | Rel-15 | Clarification to the UPU procedures |
S3-233389
| agreed | SA3#111 | Qualcomm Incorp... |
SP-230614
| approved | SA#100 | SA WG3 | 15.17.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1612 | 3 | F | 18.4.0 | Rel-18 | Protection of UPU header |
S3-240731
| merged | SA3#115 | Qualcomm Incorp... |
| | | | | TEI18, 5GS_Ph1-SEC |
|
|
| 33.501 | 1612 | 2 | F | 18.3.0 | Rel-18 | Protection of UPU header |
S3-234702
| revised | SA3#113 | Qualcomm Incorp... |
| | | | | TEI18, 5GS_Ph1-SEC |
|
|
| 33.501 | 1612 | 1 | F | 18.2.0 | Rel-18 | Protection of UPU header |
S3-233870
| revised | SA3#112 | Qualcomm Incorp... |
| | | | | TEI18, 5GS_Ph1-SEC |
|
|
| 33.501 | 1612 | - | F | 18.1.0 | Rel-18 | Protection of UPU header |
S3-232551
| revised | SA3#111 | Qualcomm Incorp... |
| | | | | TEI18, 5GS_Ph1-SEC |
|
|
| 33.501 | 1611 | 1 | A | 18.1.0 | Rel-18 | Clarification to the UPU procedures |
S3-233388
| agreed | SA3#111 | Qualcomm Incorp... |
SP-230614
| approved | SA#100 | SA WG3 | 18.2.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1611 | - | A | 18.1.0 | Rel-18 | Clarification to the UPU procedures |
S3-232550
| revised | SA3#111 | Qualcomm Incorp... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1488 | 3 | A | 17.9.0 | Rel-17 | Clarification to the UPU procedures |
S3-233329
| agreed | SA3#111 | Qualcomm Incorp... |
SP-230614
| approved | SA#100 | SA WG3 | 17.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1488 | 2 | F | 17.9.0 | Rel-17 | Clarification to the UPU procedures |
S3-232549
| revised | SA3#111 | Qualcomm Incorp... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1488 | 1 | F | 17.8.0 | Rel-17 | Clarification to the UPU procedures |
S3-230804
| revised | SA3#110 | Qualcomm Incorp... |
| | | | | TEI17, 5GS_Ph1-SEC |
|
|
| 33.501 | 1488 | - | F | 17.7.0 | Rel-17 | Clarification to the UPU procedures |
S3-223331
| revised | SA3#109 | Qualcomm Incorp... |
| | | | | TEI17, 5GS_Ph1-SEC |
|
|
| 33.501 | 1479 | - | A | 17.6.0 | Rel-17 | 33.501: R17 Update EAP based secondary authentication by an external DN-AAA server (mirror) |
S3-222230
| not pursued | SA3#108-e | Xiaomi Communication |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1478 | - | A | 16.11.0 | Rel-16 | 33.501: R16 Update EAP based secondary authentication by an external DN-AAA server (mirror) |
S3-222229
| not pursued | SA3#108-e | Xiaomi Communication |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1477 | - | F | 15.16.0 | Rel-15 | 33.501: R15 Update EAP based secondary authentication by an external DN-AAA server |
S3-222228
| not pursued | SA3#108-e | Xiaomi Communication |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1470 | - | F | 17.6.0 | Rel-17 | UP IP security |
S3-222132
| not pursued | SA3#108-e | China Mobile |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1441 | - | A | 17.6.0 | Rel-17 | Clarification on ResumeMAC-IshortResumeMAC-I check failed in clause 6.8.2.1.3-R17 |
S3-221891
| not pursued | SA3#108-e | ZTE Corporation |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1440 | - | A | 16.11.0 | Rel-16 | Clarification on ResumeMAC-IshortResumeMAC-I check failed in clause 6.8.2.1.3-R16 |
S3-221890
| not pursued | SA3#108-e | ZTE Corporation |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1439 | - | F | 15.16.0 | Rel-15 | Clarification on ResumeMAC-IshortResumeMAC-I check failed in clause 6.8.2.1.3-R15 |
S3-221889
| not pursued | SA3#108-e | ZTE Corporation |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1420 | - | A | 17.5.0 | Rel-17 | Clarification on handling of the incoming N32-f message in the pSEPP side – R17 |
S3-221105
| not pursued | SA3#107-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1419 | - | A | 16.10.0 | Rel-16 | Clarification on handling of the incoming N32-f message in the pSEPP side – R16 |
S3-221104
| not pursued | SA3#107-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1418 | - | F | 15.15.0 | Rel-15 | Clarification on handling of the incoming N32-f message in the pSEPP side – R15 |
S3-221103
| not pursued | SA3#107-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1417 | - | A | 17.5.0 | Rel-17 | Clarification on IV usage on N32-f protection-R17 |
S3-221102
| not pursued | SA3#107-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1416 | - | A | 16.10.0 | Rel-16 | Clarification on IV usage on N32-f protection-R16 |
S3-221101
| not pursued | SA3#107-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1415 | - | F | 15.15.0 | Rel-15 | Clarification on IV usage on N32-f protection-R15 |
S3-221100
| not pursued | SA3#107-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1359 | 1 | A | 17.5.0 | Rel-17 | Clarifications to secondary authentication PDU Session Container |
S3-221293
| agreed | SA3#107-e | Intel Corporati... |
SP-220559
| approved | SA#96 | SA WG3 | 17.6.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1359 | - | A | 17.5.0 | Rel-17 | Clarifications to secondary authentication PDU Session Container |
S3-220687
| revised | SA3#107-e | Intel Corporati... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1358 | 1 | A | 16.10.0 | Rel-16 | Clarifications to secondary authentication PDU Session Container |
S3-221292
| agreed | SA3#107-e | Intel Corporati... |
SP-220559
| approved | SA#96 | SA WG3 | 16.11.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1358 | - | A | 16.10.0 | Rel-16 | Clarifications to secondary authentication PDU Session Container |
S3-220686
| revised | SA3#107-e | Intel Corporati... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1357 | 1 | F | 15.15.0 | Rel-15 | Clarifications to secondary authentication PDU Session Container |
S3-221291
| agreed | SA3#107-e | Intel Corporati... |
SP-220559
| approved | SA#96 | SA WG3 | 15.16.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1357 | - | F | 15.15.0 | Rel-15 | Clarifications to secondary authentication PDU Session Container |
S3-220685
| revised | SA3#107-e | Intel Corporati... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1356 | - | A | 17.4.2 | Rel-17 | Remove ambiguous phrase for rekeying error scenario in clause 6.9.2.3.2. |
S3-220502
| agreed | SA3#106-e | NTT DOCOMO INC. |
SP-220206
| approved | SA#95-e | SA WG3 | 17.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1355 | - | A | 16.9.1 | Rel-16 | Remove ambiguous phrase for rekeying error scenario in clause 6.9.2.3.2. |
S3-220501
| agreed | SA3#106-e | NTT DOCOMO INC. |
SP-220206
| approved | SA#95-e | SA WG3 | 16.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1351 | 1 | F | 15.14.1 | Rel-15 | Remove ambiguous phrase for rekeying error scenario in clause 6.9.2.3.2 |
S3-220500
| agreed | SA3#106-e | NTT DOCOMO INC. |
SP-220206
| approved | SA#95-e | SA WG3 | 15.15.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1351 | - | F | 15.14.1 | Rel-15 | Deletion of the usage of NGAP PATH SWITCH REQUEST ACKNOWLEDGE message for AS rekeying during Xn-Handover |
S3-220423
| revised | SA3#106-e | NTT DOCOMO INC. |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1325 | - | F | 15.14.1 | Rel-15 | Correct NAS uplink COUNT for KgNB/KeNB derivation |
S3-220334
| agreed | SA3#106-e | Qualcomm Incorp... |
SP-220206
| approved | SA#95-e | SA WG3 | 15.15.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1312 | - | A | 17.4.2 | Rel-17 | Rel-17 - Updating reference to RFC 9048 (EAP-AKA’) in TS 33.501 |
S3-220260
| agreed | SA3#106-e | Ericsson |
SP-220206
| approved | SA#95-e | SA WG3 | 17.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1311 | - | A | 16.9.1 | Rel-16 | Rel-16 - Updating reference to RFC 9048 (EAP-AKA’) in TS 33.501 |
S3-220259
| agreed | SA3#106-e | Ericsson |
SP-220206
| approved | SA#95-e | SA WG3 | 16.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1310 | - | F | 15.14.1 | Rel-15 | Rel-15 - Updating reference to RFC 9048 (EAP-AKA’) in TS 33.501 |
S3-220258
| agreed | SA3#106-e | Ericsson |
SP-220206
| approved | SA#95-e | SA WG3 | 15.15.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1299 | - | A | 17.4.1 | Rel-17 | Clarification on IV usage on N32-f protection-R17 |
S3-220235
| not pursued | SA3#106-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1298 | - | A | 16.9.1 | Rel-16 | Clarification on IV usage on N32-f protection-R16 |
S3-220234
| not pursued | SA3#106-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1297 | - | F | 15.14.1 | Rel-15 | Clarification on IV usage on N32-f protection-R15 |
S3-220233
| not pursued | SA3#106-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1251 | - | A | 17.3.0 | Rel-17 | Avoiding unencrypted radio interface data transfer |
S3-214331
| not pursued | SA3#105-e | Vodafone |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1250 | - | F | 16.8.0 | Rel-16 | Avoiding unencrypted radio interface data transfer |
S3-214329
| not pursued | SA3#105-e | Vodafone |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1235 | - | A | 17.3.0 | Rel-17 | SBA CR Alignment for Oauth2.0 validation R17 |
S3-214193
| not pursued | SA3#105-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1234 | - | A | 16.8.0 | Rel-16 | SBA CR Alignment for Oauth2.0 validation R16 |
S3-214192
| not pursued | SA3#105-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1233 | - | F | 15.14.0 | Rel-15 | SBA CR Alignment for Oauth2.0 validation R15 |
S3-214191
| not pursued | SA3#105-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1224 | - | F | 17.3.0 | Rel-17 | Resolving the EN on the authorization between SCPs |
S3-214074
| withdrawn | SA3#105-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1223 | - | F | 17.3.0 | Rel-17 | Clarification on the TLS mechanism betwee SEPPs |
S3-214073
| not pursued | SA3#105-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC, TEI17 |
|
|
| 33.501 | 1221 | - | A | 17.3.0 | Rel-17 | clarification on NAS count handling-R17 |
S3-214059
| not pursued | SA3#105-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC, TEI16 |
|
|
| 33.501 | 1220 | - | F | 16.8.0 | Rel-16 | clarification on NAS count handling-R16 |
S3-214058
| not pursued | SA3#105-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC, TEI16 |
|
|
| 33.501 | 1219 | - | A | 17.3.0 | Rel-17 | removal of unspecified validity of AV-R17 |
S3-214057
| revised | SA3#105-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC, TEI16 |
|
|
| 33.501 | 1218 | - | F | 16.8.0 | Rel-16 | removal of unspecified validity of AV-R16 |
S3-214056
| revised | SA3#105-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC, TEI16 |
|
|
| 33.501 | 1217 | - | F | 17.3.0 | Rel-17 | clarification on handling the security context in MR |
S3-214048
| not pursued | SA3#105-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1216 | - | F | 16.8.0 | Rel-16 | clarification on handling the security context in MR |
S3-214047
| not pursued | SA3#105-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1215 | - | F | 15.14.0 | Rel-15 | clarification on handling the security context in MR |
S3-214046
| not pursued | SA3#105-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1191 | 1 | A | 17.2.1 | Rel-17 | OAuth misalignment - R17 |
S3-213189
| agreed | SA3#104-e | Nokia, Nokia Sh... |
SP-210840
| approved | SA#93-e | SA WG3 | 17.3.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1170 | - | F | 17.2.1 | Rel-17 | Editorial Clarifications for Trusted non-3GPP Access using TNGF |
S3-212683
| revised | SA3#104-e | Intel Corporati... |
| | | | | 5GS_Ph1-SEC, TEI17 |
|
|
| 33.501 | 1146 | 1 | F | 15.13.0 | Rel-15 | OAuth2.0 misalignmnet |
S3-213178
| agreed | SA3#104-e | Mavenir, Huawei... |
SP-210840
| approved | SA#93-e | SA WG3 | 15.14.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1146 | - | F | 15.13.0 | Rel-15 | OAuth2.0 misalignmnet |
S3-212451
| revised | SA3#104-e | Mavenir, Huawei... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1145 | 1 | A | 16.7.0 | Rel-16 | OAuth2.0 misalignmnet |
S3-213177
| agreed | SA3#104-e | Mavenir, Huawei... |
SP-210840
| approved | SA#93-e | SA WG3 | 16.8.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1145 | - | A | 16.7.0 | Rel-16 | OAuth2.0 misalignmnet |
S3-212450
| revised | SA3#104-e | Mavenir, Huawei... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1135 | 1 | A | 17.1.0 | Rel-17 | Removal of ENs for draft-ietf-emu-rfc5448bis- Rel-17 |
S3-212346
| agreed | SA3#103-e | Ericsson |
SP-210434
| approved | SA#92-e | SA WG3 | 17.2.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1135 | - | A | 17.1.0 | Rel-17 | Removal of ENs for draft-ietf-emu-rfc5448bis- Rel-17 |
S3-211991
| revised | SA3#103-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1134 | 1 | A | 16.6.0 | Rel-16 | Removal of ENs for draft-ietf-emu-rfc5448bis -Rel-16 |
S3-212331
| agreed | SA3#103-e | Ericsson |
SP-210434
| approved | SA#92-e | SA WG3 | 16.7.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1134 | - | A | 16.6.0 | Rel-16 | Removal of ENs for draft-ietf-emu-rfc5448bis -Rel-16 |
S3-211990
| revised | SA3#103-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1133 | 1 | F | 15.12.0 | Rel-15 | Removal of ENs for draft-ietf-emu-rfc5448bis - Rel-15 |
S3-212330
| agreed | SA3#103-e | Ericsson |
SP-210434
| approved | SA#92-e | SA WG3 | 15.13.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1133 | - | F | 15.12.0 | Rel-15 | Removal of ENs for draft-ietf-emu-rfc5448bis - Rel-15 |
S3-211988
| revised | SA3#103-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1125 | - | A | 16.6.0 | Rel-16 | Clarification on the Oauth client registration and authorization |
S3-211889
| not pursued | SA3#103-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1124 | - | F | 15.12.0 | Rel-15 | Clarification on the Oauth client registration |
S3-211888
| not pursued | SA3#103-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1112 | - | A | 17.1.0 | Rel-17 | Downlink NAS COUNT handling after creating NAS container in EPS to 5GS Handover |
S3-211797
| agreed | SA3#103-e | Qualcomm Incorp... |
SP-210434
| approved | SA#92-e | SA WG3 | 17.2.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1111 | - | A | 16.6.0 | Rel-16 | Downlink NAS COUNT handling after creating NAS container in EPS to 5GS Handover |
S3-211796
| agreed | SA3#103-e | Qualcomm Incorp... |
SP-210434
| approved | SA#92-e | SA WG3 | 16.7.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1110 | - | F | 15.12.0 | Rel-15 | Downlink NAS COUNT handling after creating NAS container in EPS to 5GS Handover |
S3-211795
| agreed | SA3#103-e | Qualcomm Incorp... |
SP-210434
| approved | SA#92-e | SA WG3 | 15.13.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1107 | 1 | A | 17.1.0 | Rel-17 | Clarify the usage of TLS and PRINS between SEPPs |
S3-212369
| agreed | SA3#103-e | Ericsson, Nokia... |
SP-210434
| approved | SA#92-e | SA WG3 | 17.2.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1107 | - | A | 17.1.0 | Rel-17 | Clarify the usage of TLS and PRINS between SEPPs |
S3-211761
| revised | SA3#103-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1106 | 1 | A | 16.6.0 | Rel-16 | Clarify the usage of TLS and PRINS between SEPPs |
S3-212368
| agreed | SA3#103-e | Ericsson, Nokia... |
SP-210434
| approved | SA#92-e | SA WG3 | 16.7.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1106 | - | A | 16.6.0 | Rel-16 | Clarify the usage of TLS and PRINS between SEPPs |
S3-211760
| revised | SA3#103-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1105 | 1 | F | 15.12.0 | Rel-15 | Clarify the usage of TLS and PRINS between SEPPs |
S3-212367
| agreed | SA3#103-e | Ericsson, Nokia... |
SP-210434
| approved | SA#92-e | SA WG3 | 15.13.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1105 | - | F | 15.12.0 | Rel-15 | Clarify the usage of TLS and PRINS between SEPPs |
S3-211759
| revised | SA3#103-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1104 | - | A | 17.1.0 | Rel-17 | Clarification on the OAuth 2.0 client registration |
S3-211758
| not pursued | SA3#103-e | Ericsson, Nokia... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1103 | - | A | 16.6.0 | Rel-16 | Clarification on the OAuth 2.0 client registration |
S3-211757
| not pursued | SA3#103-e | Ericsson, Nokia... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1102 | - | F | 15.12.0 | Rel-15 | Clarification on the OAuth 2.0 client registration |
S3-211756
| not pursued | SA3#103-e | Ericsson, Nokia... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1101 | - | A | 17.1.0 | Rel-17 | Clarification on the NRF services authorization |
S3-211755
| not pursued | SA3#103-e | Ericsson, Nokia... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1100 | - | F | 16.6.0 | Rel-16 | Clarification on the NRF services authorization |
S3-211754
| not pursued | SA3#103-e | Ericsson, Nokia... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1099 | - | F | 15.12.0 | Rel-15 | Clarification on the NRF services authorization |
S3-211753
| not pursued | SA3#103-e | Ericsson, Nokia... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1072 | - | A | 17.0.0 | Rel-17 | resolving ed note on protection policy mismatch |
S3-210552
| merged | SA3#102-e | NTT DOCOMO INC. |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1071 | - | A | 16.5.0 | Rel-16 | resolving ed note on protection policy mismatch |
S3-210551
| merged | SA3#102-e | NTT DOCOMO INC. |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1070 | - | A | 16.5.0 | Rel-16 | Typo correction in clause 6.9.4.4 |
S3-210550
| agreed | SA3#102-e | Xidian University |
SP-210113
| approved | SA#91-e | SA WG3 | 16.6.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1069 | - | A | 16.5.0 | Rel-16 | Typo correction in clause 6.9.4.4 |
S3-210549
| withdrawn | SA3#102-e | Xidian University |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1068 | - | A | 16.5.0 | Rel-16 | Typo correction in clause 6.9.4.4 |
S3-210548
| withdrawn | SA3#102-e | Xidian University |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1067 | - | A | 16.5.0 | Rel-16 | Typo correction in clause 6.9.4.4 |
S3-210547
| withdrawn | SA3#102-e | Xidian University |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1066 | - | A | 16.5.0 | Rel-16 | Typo correction in clause 6.9.4.4 |
S3-210546
| withdrawn | SA3#102-e | Xidian University |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1065 | 1 | F | 15.11.0 | Rel-15 | Resolving editor's note on encryption policy mismatch between SEPPs |
S3-210792
| agreed | SA3#102-e | NTT DOCOMO INC.... |
SP-210113
| approved | SA#91-e | SA WG3 | 15.12.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1065 | - | F | 15.11.0 | Rel-15 | resolving ed note on protection policy mismatch |
S3-210545
| revised | SA3#102-e | NTT DOCOMO INC. |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1064 | - | F | 15.11.0 | Rel-15 | Typo correction in clause 6.9.4.4 |
S3-210532
| agreed | SA3#102-e | Xidian University |
SP-210113
| approved | SA#91-e | SA WG3 | 15.12.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1061 | - | A | 16.5.0 | Rel-16 | Typo correction in clause 6.9.9.4 |
S3-210467
| withdrawn | SA3#102-e | Xidian University |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1053 | - | A | 16.5.0 | Rel-16 | Clarification on PLMN ID verification in Rel16 |
S3-210396
| not pursued | SA3#102-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1052 | - | F | 15.11.0 | Rel-15 | Clarification on PLMN ID verification in Rel15 |
S3-210395
| not pursued | SA3#102-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1051 | - | A | 17.0.0 | Rel-17 | Mirror Adding the security requirement with encBlockIndex in Rel17 |
S3-210387
| revised | SA3#102-e | Huawei, HiSilic... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1050 | - | A | 16.5.0 | Rel-16 | Mirror Adding the security requirement with encBlockIndex in Rel16 |
S3-210386
| revised | SA3#102-e | Huawei, HiSilic... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1049 | - | F | 15.11.0 | Rel-15 | Adding the security requirement with encBlockIndex in Rel15 |
S3-210385
| not pursued | SA3#102-e | Huawei, HiSilic... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1048 | 1 | A | 17.0.0 | Rel-17 | Mirror: align the JSON format on encryption IE with CT4 in Rel17 |
S3-210750
| agreed | SA3#102-e | Huawei, HiSilic... |
SP-210113
| approved | SA#91-e | SA WG3 | 17.1.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1048 | - | A | 17.0.0 | Rel-17 | Mirror: align the JSON format on encryption IE with CT4 in Rel17 |
S3-210384
| revised | SA3#102-e | Huawei, HiSilic... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1047 | 1 | A | 16.5.0 | Rel-16 | Mirror: align the JSON format on encryption IE with CT4 in Rel16 |
S3-210749
| agreed | SA3#102-e | Huawei, HiSilic... |
SP-210113
| approved | SA#91-e | SA WG3 | 16.6.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1047 | - | A | 16.5.0 | Rel-16 | Mirror: align the JSON format on encryption IE with CT4 in Rel16 |
S3-210383
| revised | SA3#102-e | Huawei, HiSilic... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1046 | 1 | F | 15.11.0 | Rel-15 | Align the JSON format on encryption IE with CT4 in Rel15 |
S3-210748
| agreed | SA3#102-e | Huawei, HiSilic... |
SP-210113
| approved | SA#91-e | SA WG3 | 15.12.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1046 | - | F | 15.11.0 | Rel-15 | Align the JSON format on encryption IE with CT4 in Rel15 |
S3-210382
| revised | SA3#102-e | Huawei, HiSilic... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1042 | - | A | 17.0.0 | Rel-17 | Typo correction in clause 6.9.9.4 |
S3-210339
| not pursued | SA3#102-e | Xidian University |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1040 | - | F | 16.5.0 | Rel-16 | Clarification on security protection in AMF reallocation(direct NAS reroute) |
S3-210294
| revised | SA3#102-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1035 | - | A | 17.0.0 | Rel-17 | Correction to the access token storage in NF service consumer |
S3-210240
| revised | SA3#102-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1034 | - | A | 16.5.0 | Rel-16 | Correction to the access token storage in NF service consumer |
S3-210239
| revised | SA3#102-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1033 | - | F | 15.11.0 | Rel-15 | Correction to the access token storage in NF service consumer |
S3-210238
| not pursued | SA3#102-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1026 | - | A | 17.0.0 | Rel-17 | Optional registration of NF Service Consumer to NRF |
S3-210104
| not pursued | SA3#102-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1025 | - | A | 16.5.0 | Rel-16 | Optional registration of NF Service Consumer to NRF |
S3-210103
| not pursued | SA3#102-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1024 | - | F | 15.11.0 | Rel-15 | Optional registration of NF Service Consumer to NRF |
S3-210102
| not pursued | SA3#102-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1019 | 1 | A | 17.0.0 | Rel-17 | Resolving editor's note on encryption policy mismatch between SEPPs |
S3-210724
| agreed | SA3#102-e | NTT Docomo, Nok... |
SP-210113
| approved | SA#91-e | SA WG3 | 17.1.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1011 | - | A | 16.4.0 | Rel-16 | [Mirror]Correction to derivation of KSN for dual connectivity |
S3-203250
| agreed | SA3#101-e | Samsung |
SP-201012
| approved | SA#90-e | SA WG3 | 16.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1010 | - | F | 15.10.0 | Rel-15 | [Rel-15]Correction to derivation of KSN for dual connectivity |
S3-203249
| agreed | SA3#101-e | Samsung |
SP-201012
| approved | SA#90-e | SA WG3 | 15.11.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1004 | 1 | A | 16.4.0 | Rel-16 | R16 Authorization of NF service access - service requst process steps |
S3-203503
| agreed | SA3#101-e | Nokia, Nokia Sh... |
SP-201012
| approved | SA#90-e | SA WG3 | 16.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1004 | - | A | 16.4.0 | Rel-16 | R16 Authorization of NF service access - service requst process steps |
S3-203201
| revised | SA3#101-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1003 | 1 | F | 15.10.0 | Rel-15 | R15 Authorization of NF service access - service requst process steps |
S3-203502
| agreed | SA3#101-e | Nokia, Nokia Sh... |
SP-201012
| approved | SA#90-e | SA WG3 | 15.11.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1003 | - | F | 15.10.0 | Rel-15 | R15 Authorization of NF service access - service requst process steps |
S3-203200
| revised | SA3#101-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 1002 | - | A | 16.4.0 | Rel-16 | R16 Authorization of NF service access - removal of ambigious terminology |
S3-203199
| agreed | SA3#101-e | Nokia, Nokia Sh... |
SP-201012
| approved | SA#90-e | SA WG3 | 16.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1001 | - | F | 15.10.0 | Rel-15 | R15 Authorization of NF service access - removal of ambigious terminology |
S3-203198
| agreed | SA3#101-e | Nokia, Nokia Sh... |
SP-201012
| approved | SA#90-e | SA WG3 | 15.11.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 1000 | - | A | 16.4.0 | Rel-16 | R16 Access Token Get Service - removal of ambigiouty |
S3-203197
| merged | SA3#101-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0999 | - | F | 15.10.0 | Rel-15 | R15 Access Token Get Service - removal of ambigiouty |
S3-203196
| merged | SA3#101-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0998 | - | A | 16.4.0 | Rel-16 | R16 NFc and NFp alignment in static authorization |
S3-203195
| agreed | SA3#101-e | Nokia, Nokia Sh... |
SP-201012
| approved | SA#90-e | SA WG3 | 16.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0997 | - | F | 15.10.0 | Rel-15 | R15 NFc and NFp alignment in static authorization |
S3-203194
| agreed | SA3#101-e | Nokia, Nokia Sh... |
SP-201012
| approved | SA#90-e | SA WG3 | 15.11.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0986 | - | A | 16.4.0 | Rel-16 | SEPP including PLMN-ID and verification of Serving Network Name in AUSF |
S3-203145
| not pursued | SA3#101-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0985 | - | F | 15.10.0 | Rel-15 | Verification of Serving Network Name in AUSF |
S3-203144
| not pursued | SA3#101-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0984 | 1 | A | 16.4.0 | Rel-16 | Corrections for the NRF token request service |
S3-203538
| agreed | SA3#101-e | Ericsson |
SP-201012
| approved | SA#90-e | SA WG3 | 16.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0984 | - | A | 16.4.0 | Rel-16 | Corrections for the NRF token request service |
S3-203143
| revised | SA3#101-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0983 | 1 | F | 15.10.0 | Rel-15 | Corrections for the NRF token request service |
S3-203537
| agreed | SA3#101-e | Ericsson |
SP-201012
| approved | SA#90-e | SA WG3 | 15.11.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0983 | - | F | 15.10.0 | Rel-15 | Corrections for the NRF token request service |
S3-203142
| revised | SA3#101-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0976 | 1 | F | 16.4.0 | Rel-16 | Modification policy clarification in Rel16 |
S3-203523
| withdrawn | SA3#101-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC, TEI16 |
|
|
| 33.501 | 0976 | - | F | 16.4.0 | Rel-16 | Modification policy clarification in Rel16 |
S3-203057
| agreed | SA3#101-e | Huawei, Hisilicon |
SP-201009
| approved | SA#90-e | SA WG3 | 16.5.0 | 5GS_Ph1-SEC, TEI16 |
|
|
| 33.501 | 0975 | - | F | 15.10.0 | Rel-15 | Modification policy clarification in Rel15 |
S3-203056
| not pursued | SA3#101-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0974 | - | A | 16.4.0 | Rel-16 | Clarification on PLMN ID verification in Rel16 |
S3-203054
| not pursued | SA3#101-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0973 | - | F | 15.10.0 | Rel-15 | Clarification on PLMN ID verification in Rel15 |
S3-203053
| not pursued | SA3#101-e | Huawei, Hisilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0968 | 1 | A | 16.4.0 | Rel-16 | Secondary authentication revocation rel16 |
S3-203516
| agreed | SA3#101-e | Huawei, HiSilicon |
SP-201012
| approved | SA#90-e | SA WG3 | 16.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0968 | - | A | 16.4.0 | Rel-16 | Secondary authentication revocation rel16 |
S3-203021
| revised | SA3#101-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0967 | 1 | F | 15.10.0 | Rel-15 | Secondary authentication revocation rel15 |
S3-203515
| agreed | SA3#101-e | Huawei, HiSilicon |
SP-201012
| approved | SA#90-e | SA WG3 | 15.11.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0967 | - | F | 15.10.0 | Rel-15 | Secondary authentication revocation rel15 |
S3-203020
| revised | SA3#101-e | Huawei, HiSilicon |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0961 | - | F | 16.4.0 | Rel-16 | NAS COUNT storage for multiple PLMN |
S3-202889
| revised | SA3#101-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC, TEI16 |
|
|
| 33.501 | 0957 | - | F | 15.10.0 | Rel-15 | Clarification to SEAF |
S3-202814
| agreed | SA3#101-e | Nokia, Nokia Sh... |
SP-201012
| approved | SA#90-e | SA WG3 | 15.11.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0956 | 1 | F | 15.10.0 | Rel-15 | NRF authorization during NF service consumer Access Token Get Request |
S3-203496
| agreed | SA3#101-e | Mavenir, Nokia,... |
SP-201012
| approved | SA#90-e | SA WG3 | 15.11.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0956 | - | F | 15.10.0 | Rel-15 | NRF authorization during NF service consumer Access Token Get Request |
S3-202809
| revised | SA3#101-e | Mavenir |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0955 | 1 | A | 16.4.0 | Rel-16 | NRF authorization during NF service consumer Access Token Get Request |
S3-203497
| agreed | SA3#101-e | Mavenir, Nokia,... |
SP-201012
| approved | SA#90-e | SA WG3 | 16.5.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0955 | - | A | 16.4.0 | Rel-16 | NRF authorization during NF service consumer Access Token Get Request |
S3-202808
| revised | SA3#101-e | Mavenir |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0954 | - | F | 15.9.0 | Rel-15 | Clarification to 5G AV |
S3-202254
| agreed | SA3#100-e | Nokia,Nokia Sha... |
SP-200773
| approved | SA#89-e | SA WG3 | 15.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0953 | - | A | 16.3.0 | Rel-16 | OAuth 2.0 based authorization |
S3-202198
| not pursued | SA3#100-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0952 | - | F | 15.9.0 | Rel-15 | OAuth 2.0 based authorization |
S3-202197
| not pursued | SA3#100-e | Nokia, Nokia Sh... |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0951 | - | A | 16.3.0 | Rel-16 | NF Service Producer authorization |
S3-202195
| agreed | SA3#100-e | Nokia, Nokia Sh... |
SP-200773
| approved | SA#89-e | SA WG3 | 16.4.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0950 | - | F | 15.9.0 | Rel-15 | NF Service Producer authorization |
S3-202194
| agreed | SA3#100-e | Nokia, Nokia Sh... |
SP-200773
| approved | SA#89-e | SA WG3 | 15.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0949 | - | F | 15.9.0 | Rel-15 | N32 interface |
S3-202167
| agreed | SA3#100-e | Nokia, Nokia Sh... |
SP-200773
| approved | SA#89-e | SA WG3 | 15.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0948 | - | F | 15.9.0 | Rel-15 | Static authorization details |
S3-202166
| agreed | SA3#100-e | Mavenir,Deutsch... |
SP-200773
| approved | SA#89-e | SA WG3 | 15.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0947 | - | A | 16.3.0 | Rel-16 | Error handling by the receiving NF |
S3-202165
| agreed | SA3#100-e | Nokia, Nokia Sh... |
SP-200773
| approved | SA#89-e | SA WG3 | 16.4.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0946 | - | F | 15.9.0 | Rel-15 | Error handling by the receiving NF |
S3-202164
| agreed | SA3#100-e | Nokia, Nokia Sh... |
SP-200773
| approved | SA#89-e | SA WG3 | 15.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0945 | - | F | 15.9.0 | Rel-15 | Access Token Signature using MAC with symmetric key |
S3-202162
| agreed | SA3#100-e | Mavenir, Deutsc... |
SP-200709
| approved | SA#89-e | SA WG3 | 15.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0944 | 1 | A | 16.3.0 | Rel-16 | Clarifications to SoR integrity protection mechanism |
S3-202249
| agreed | SA3#100-e | Orange, Ericsso... |
SP-200773
| approved | SA#89-e | SA WG3 | 16.4.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0944 | - | A | 16.3.0 | Rel-16 | Clarifications to SoR integrity protection mechanism |
S3-202050
| revised | SA3#100-e | Orange |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0943 | 1 | F | 15.9.0 | Rel-15 | Clarifications to SoR integrity protection mechanism |
S3-202248
| agreed | SA3#100-e | Orange, Ericsso... |
SP-200773
| approved | SA#89-e | SA WG3 | 15.10.0 | 5GS_Ph1-SEC |
|
|
| 33.501 | 0943 | - | F | 15.9.0 | Rel-15 | Clarifications to SoR integrity protection mechanism |
S3-202049
| revised | SA3#100-e | Orange |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0938 | - | F | 16.3.0 | Rel-16 | Removal of response from gNB to the AMF after inter-gNB-CU HO |
S3-201980
| not pursued | SA3#100-e | Samsung |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0936 | - | A | 16.3.0 | Rel-16 | Alignment of SoR procedures to Stage-3 |
S3-201976
| merged | SA3#100-e | Samsung |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0935 | - | F | 15.9.0 | Rel-15 | Alignment of SoR procedures to Stage-3 |
S3-201975
| merged | SA3#100-e | Samsung |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0932 | - | A | 16.3.0 | Rel-16 | Aligning TS 33.501 with TS 29.573 regarding N32-f context ID |
S3-201923
| merged | SA3#100-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|
|
| 33.501 | 0931 | - | F | 15.9.0 | Rel-15 | Aligning TS 33.501 with TS 29.573 regarding N32-f context ID |
S3-201922
| merged | SA3#100-e | Ericsson |
| | | | | 5GS_Ph1-SEC |
|