|
|
| 33.122 | 0110 | - | B | 19.0.0 | Rel-19 | Onboarding API Invoker Residing in the UE |
S3-252431
| agreed | SA3#122 | Lenovo, Nokia, ... |
SP-250658
| approved | SA#108 | SA WG3 | 19.1.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0109 | - | B | 19.0.0 | Rel-19 | CR on Nested API |
S3-252430
| agreed | SA3#122 | Ericsson, Samsu... |
SP-250658
| approved | SA#108 | SA WG3 | 19.1.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0108 | - | B | 19.0.0 | Rel-19 | CR on Cross UE authorization |
S3-252429
| agreed | SA3#122 | Xiaomi, Ericsso... |
SP-250658
| approved | SA#108 | SA WG3 | 19.1.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0107 | - | B | 19.0.0 | Rel-19 | Security procedures for CAPIF interconnection |
S3-252428
| agreed | SA3#122 | Samsung, China ... |
SP-250658
| approved | SA#108 | SA WG3 | 19.1.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0106 | - | B | 19.0.0 | Rel-19 | Authorization for finer level service API access |
S3-252427
| agreed | SA3#122 | Nokia, Huawei |
SP-250658
| approved | SA#108 | SA WG3 | 19.1.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0105 | - | B | 19.0.0 | Rel-19 | Resource Owner authentication revocation |
S3-252426
| agreed | SA3#122 | China Telecom C... |
SP-250658
| approved | SA#108 | SA WG3 | 19.1.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0104 | - | B | 19.0.0 | Rel-19 | CR on RO authorization |
S3-252396
| agreed | SA3#122 | Huawei, HiSilic... |
SP-250658
| approved | SA#108 | SA WG3 | 19.1.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0103 | - | F | 19.0.0 | Rel-19 | RO definition |
S3-252247
| not pursued | SA3#122 | Nokia, Lenovo |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0102 | - | A | 19.0.0 | Rel-19 | Clarification on client credential flow |
S3-252221
| not pursued | SA3#122 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0101 | - | F | 18.4.0 | Rel-18 | Clarification on client credential flow – Rel-18 |
S3-252220
| not pursued | SA3#122 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0100 | - | F | 19.0.0 | Rel-19 | Clarification on resource owner ID in the token |
S3-252219
| not pursued | SA3#122 | Ericsson |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0099 | 1 | F | 18.4.0 | Rel-18 | Fixing API invoker onboarding – Rel18 |
S3-251689
| withdrawn | SA3#121 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0099 | - | F | 18.4.0 | Rel-18 | Fixing API invoker onboarding – Rel18 |
S3-251481
| not pursued | SA3#121 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0098 | 1 | B | 19.0.0 | Rel-19 | Authentication of ROF and CCF for CAPIF-8 reference point |
S3-251711
| agreed | SA3#121 | Huawei, HiSilicon |
SP-250658
| approved | SA#108 | SA WG3 | 19.1.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0098 | - | B | 19.0.0 | Rel-19 | Authentication of ROF and CCF for CAPIF-8 reference point |
S3-251386
| revised | SA3#121 | Huawei, HiSilicon |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0097 | - | F | 19.0.0 | Rel-19 | Correction of existing text in TS 33.122 |
S3-251357
| agreed | SA3#121 | ZTE |
SP-250658
| approved | SA#108 | SA WG3 | 19.1.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0096 | - | B | 18.4.0 | Rel-19 | Security procedures for CAPIF-8 reference points |
S3-251033
| withdrawn | SA3#120 | ZTE Corporation |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0095 | - | B | 18.4.0 | Rel-19 | Updates for CAPIF interconnection |
S3-250608
| not pursued | SA3#120 | Ericsson |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0094 | 1 | F | 18.4.0 | Rel-18 | Fixing API invoker onboarding – Rel18 |
S3-251132
| not pursued | SA3#120 | Ericsson |
| | | | | CAPIF-Sec, TEI18 |
|
|
|
| 33.122 | 0094 | - | A | 18.4.0 | Rel-18 | Fixing API invoker onboarding – Rel18 |
S3-250596
| revised | SA3#120 | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0093 | - | A | 17.1.0 | Rel-17 | Fixing API invoker onboarding – Rel17 |
S3-250595
| not pursued | SA3#120 | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0092 | - | A | 16.4.0 | Rel-16 | Fixing API invoker onboarding – Rel16 |
S3-250594
| not pursued | SA3#120 | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0091 | - | F | 15.4.0 | Rel-15 | Fixing API invoker onboarding – Rel15 |
S3-250593
| not pursued | SA3#120 | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0090 | - | B | 18.4.0 | Rel-19 | CR of Resource owner authorization management |
S3-250495
| withdrawn | SA3#120 | China Telecom |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0089 | - | B | 18.4.0 | Rel-19 | CR on Authentication and authorization for CAPIF interconnection |
S3-250494
| withdrawn | SA3#120 | China Telecom |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0088 | 1 | F | 18.4.0 | Rel-19 | Correction of existing text in section 6.10 |
S3-251118
| agreed | SA3#120 | Nokia |
SP-250101
| approved | SA#107 | SA WG3 | 19.0.0 | TEI19 |
|
|
|
| 33.122 | 0088 | - | F | 18.4.0 | Rel-19 | Correction of existing text in section 6.10 |
S3-250484
| revised | SA3#120 | Nokia |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0087 | 1 | F | 18.4.0 | Rel-19 | RNAA authentication and authorization - mapping of API Invoker ID and GPSI |
S3-251117
| agreed | SA3#120 | Nokia |
SP-250100
| approved | SA#107 | SA WG3 | 19.0.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0087 | - | B | 18.4.0 | Rel-19 | RNAA authentication and authorization - mapping of API Invoker ID and GPSI |
S3-250480
| revised | SA3#120 | Nokia |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0086 | - | B | 18.4.0 | Rel-19 | Security solution for revocation at CAPIF-8 |
S3-250479
| not pursued | SA3#120 | Nokia |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0085 | - | B | 18.4.0 | Rel-19 | CAPIF-8 - Authorization for finer level service API access |
S3-250478
| not pursued | SA3#120 | Nokia |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0084 | - | B | 18.4.0 | Rel-19 | CAPIF-8 - Security aspects of RO authorization |
S3-250477
| merged | SA3#120 | Nokia |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0083 | - | B | 18.4.0 | Rel-19 | Security solution for interconnect |
S3-250476
| not pursued | SA3#120 | Nokia |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0082 | - | B | 18.4.0 | Rel-19 | Security requirements on CAPIF-8 reference points |
S3-250475
| merged | SA3#120 | Nokia |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0081 | 1 | B | 18.4.0 | Rel-19 | Security requirements on CAPIF-6 and -6e reference points |
S3-251030
| agreed | SA3#120 | Nokia, ZTE, Xiaomi |
SP-250100
| approved | SA#107 | SA WG3 | 19.0.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0081 | - | B | 18.4.0 | Rel-19 | Security requirements on CAPIF-6 and -6e reference points |
S3-250474
| revised | SA3#120 | Nokia |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0080 | 1 | B | 18.4.0 | Rel-19 | RNAA and Interconnect aspects in function security model |
S3-251115
| agreed | SA3#120 | Samsung, Nokia |
SP-250100
| approved | SA#107 | SA WG3 | 19.0.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0080 | - | B | 18.4.0 | Rel-19 | RNAA and Interconnect aspects in function security model |
S3-250473
| revised | SA3#120 | Nokia |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0079 | - | B | 18.4.0 | Rel-19 | Finer granularity support for security procedures |
S3-250412
| merged | SA3#120 | Huawei, HiSilicon |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0078 | 1 | B | 18.4.0 | Rel-19 | Security requirements and procedures for CAPIF-8 reference point |
S3-251032
| agreed | SA3#120 | Huawei, HiSilicon |
SP-250100
| approved | SA#107 | SA WG3 | 19.0.0 | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0078 | - | B | 18.4.0 | Rel-19 | Security requirements and procedures for CAPIF-8 reference point |
S3-250411
| revised | SA3#120 | Huawei, HiSilicon |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0077 | - | B | 18.4.0 | Rel-19 | Authorization revocation through CAPIF-8 reference point |
S3-250410
| not pursued | SA3#120 | Huawei, HiSilicon |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0076 | - | B | 18.4.0 | Rel-19 | RO authentication and authorization information for CAPIF-8 reference point |
S3-250409
| not pursued | SA3#120 | Huawei, HiSilicon |
| | | | | CAPIF_Ph3_sec |
|
|
|
| 33.122 | 0075 | - | F | 18.3.0 | Rel-18 | Alignment on resource definition |
S3-242206
| not pursued | SA3#116 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0074 | 1 | F | 18.3.0 | Rel-18 | Corrections and removing token claim related EN |
S3-242385
| agreed | SA3#116 | Huawei, HiSilic... |
SP-240655
| approved | SA#104 | SA WG3 | 18.4.0 | SNAAPPY |
|
|
|
| 33.122 | 0074 | - | F | 18.3.0 | Rel-18 | Corrections and removing token claim related EN |
S3-241965
| revised | SA3#116 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0073 | - | F | 18.3.0 | Rel-18 | Addressing EN on claim versus scope |
S3-241859
| merged | SA3#116 | Nokia |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0072 | - | F | 18.3.0 | Rel-18 | Resource owner function |
S3-241858
| agreed | SA3#116 | Nokia |
SP-240655
| approved | SA#104 | SA WG3 | 18.4.0 | SNAAPPY |
|
|
|
| 33.122 | 0071 | - | F | 18.2.0 | Rel-18 | Resolve ENs related to API invoker ID mapping |
S3-240795
| not pursued | SA3#115 | Xiaomi |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0070 | - | F | 18.2.0 | Rel-18 | Resolve EN related to authorization request or token request |
S3-240794
| agreed | SA3#115 | Xiaomi |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
|
| 33.122 | 0069 | - | F | 18.2.0 | Rel-18 | Resolve ENs related to token claims |
S3-240793
| merged | SA3#115 | Xiaomi |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0068 | 1 | F | 18.2.0 | Rel-18 | Add revocation procedure for RNAA-related tokens |
S3-240850
| agreed | SA3#115 | Xiaomi |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
|
| 33.122 | 0068 | - | F | 18.2.0 | Rel-18 | Add revocation procedure for RNAA-related tokens |
S3-240792
| revised | SA3#115 | Xiaomi |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0067 | 1 | F | 18.2.0 | Rel-18 | Update for CAPIF 8 |
S3-240851
| agreed | SA3#115 | Xiaomi |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
|
| 33.122 | 0067 | - | F | 18.2.0 | Rel-18 | Update for CAPIF 8 |
S3-240791
| revised | SA3#115 | Xiaomi |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0066 | - | F | 18.2.0 | Rel-18 | Revocation procedure for RNAA |
S3-240695
| merged | SA3#115 | Samsung |
| | | | | TEI18 |
|
|
|
| 33.122 | 0065 | - | F | 18.2.0 | Rel-18 | Details for RNAA token |
S3-240636
| merged | SA3#115 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0064 | - | F | 18.2.0 | Rel-18 | Security Negotiation for RNAA |
S3-240635
| merged | SA3#115 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0063 | - | F | 18.2.0 | Rel-18 | SNAAPPY - Update to RNAA functional security model description |
S3-240625
| agreed | SA3#115 | Nokia, Nokia Sh... |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
|
| 33.122 | 0062 | 1 | F | 18.2.0 | Rel-18 | Alignment of 33.122 for RNAA |
S3-241039
| agreed | SA3#115 | NTT DOCOMO |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
|
| 33.122 | 0062 | - | F | 18.2.0 | Rel-18 | Alignment of 33.122 for RNAA |
S3-240475
| revised | SA3#115 | NTT DOCOMO |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0061 | 1 | F | 18.2.0 | Rel-18 | Clarification to flow selection for RNAA |
S3-240849
| agreed | SA3#115 | Huawei, HiSilicon |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
|
| 33.122 | 0061 | - | F | 18.2.0 | Rel-18 | Clarification to flow selection for RNAA |
S3-240427
| revised | SA3#115 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0060 | 1 | F | 18.2.0 | Rel-18 | Access token profile for Annex C |
S3-240852
| agreed | SA3#115 | Huawei, HiSilicon |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
|
| 33.122 | 0060 | - | F | 18.2.0 | Rel-18 | Access token profile for Annex C |
S3-240426
| revised | SA3#115 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0059 | - | F | 18.2.0 | Rel-18 | Correction on authentication and authorization for RNAA |
S3-240425
| agreed | SA3#115 | Huawei, HiSilicon |
SP-240370
| approved | SA#103 | SA WG3 | 18.3.0 | SNAAPPY |
|
|
|
| 33.122 | 0058 | - | F | 18.2.0 | Rel-18 | Revocation procedures invoked by API invoker |
S3-240424
| merged | SA3#115 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0057 | - | F | 18.2.0 | Rel-18 | Revocation procedure invoked by resource owner client |
S3-240423
| merged | SA3#115 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0056 | 1 | F | 18.1.0 | Rel-18 | Resolving stage 2 editor's notes |
S3-234961
| not pursued | SA3#113 | NTT DOCOMO |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0056 | - | F | 18.1.0 | Rel-18 | resolving RNA stage 2 editor's notes |
S3-234945
| revised | SA3#113 | NTT DOCOMO INC. |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0055 | - | C | 18.1.0 | Rel-18 | Resolve EN related to API invoker ID and GPSI |
S3-234911
| not pursued | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0054 | - | F | 18.1.0 | Rel-18 | Update for authorization revocation procedure for RNAA |
S3-234910
| not pursued | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0053 | - | D | 18.1.0 | Rel-18 | Streamline the Editor's Notes for RNAA |
S3-234909
| not pursued | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0052 | 1 | F | 18.1.0 | Rel-18 | Resolve EN related to authorization flow |
S3-235114
| agreed | SA3#113 | Xiaomi,Nokia, N... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
|
| 33.122 | 0052 | - | F | 18.1.0 | Rel-18 | Resolve EN related to authorization flow |
S3-234908
| revised | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0051 | 1 | F | 18.1.0 | Rel-18 | Clarification for CAPIF-8 |
S3-235111
| agreed | SA3#113 | Xiaomi,Nokia, N... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
|
| 33.122 | 0051 | - | F | 18.1.0 | Rel-18 | Clarification for CAPIF-8 |
S3-234907
| revised | SA3#113 | Xiaomi |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0050 | 1 | F | 18.1.0 | Rel-18 | Detailed functional security model description for support of RNAA |
S3-235104
| agreed | SA3#113 | Nokia, Nokia Sh... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
|
| 33.122 | 0050 | - | F | 18.1.0 | Rel-18 | Detailed functional security model description for support of RNAA |
S3-234868
| revised | SA3#113 | Nokia, Nokia Sh... |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0049 | - | B | 18.1.0 | Rel-18 | Revocation procedure for RNAA |
S3-234832
| not pursued | SA3#113 | Samsung |
| | | | | TEI18 |
|
|
|
| 33.122 | 0048 | - | F | 18.1.0 | Rel-18 | Optimization in the authorization code flow usage |
S3-234790
| not pursued | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0047 | 1 | F | 18.1.0 | Rel-18 | Clarification on the scope of the Rel-18 RNAA specification |
S3-235060
| withdrawn | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0047 | - | F | 18.1.0 | Rel-18 | Clarification on the scope of the Rel-18 RNAA specification |
S3-234787
| not pursued | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0046 | 1 | F | 18.1.0 | Rel-18 | Clarification on resource owner ID |
S3-235059
| agreed | SA3#113 | Ericsson |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
|
| 33.122 | 0046 | - | F | 18.1.0 | Rel-18 | Clarification on resource owner ID |
S3-234786
| revised | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0045 | 1 | F | 18.1.0 | Rel-18 | Optimizations for accessing own resources |
S3-235065
| withdrawn | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0045 | - | F | 18.1.0 | Rel-18 | Optimizations for accessing own resources |
S3-234785
| not pursued | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0044 | 1 | F | 18.1.0 | Rel-18 | Identification of RNAA token |
S3-235064
| withdrawn | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0044 | - | F | 18.1.0 | Rel-18 | Identification of RNAA token |
S3-234784
| merged | SA3#113 | Ericsson |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0043 | - | F | 18.1.0 | Rel-18 | Refreshing Token for RNAA |
S3-234622
| merged | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0042 | - | F | 18.1.0 | Rel-18 | Obtaining Tokens Procedure for RNAA |
S3-234621
| merged | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0041 | 1 | F | 18.1.0 | Rel-18 | Access token profile for RNAA |
S3-235115
| agreed | SA3#113 | Huawei, HiSilic... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
|
| 33.122 | 0041 | - | F | 18.1.0 | Rel-18 | Access token profile for RNAA |
S3-234620
| revised | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0040 | - | F | 18.1.0 | Rel-18 | Security negotiation for RNAA |
S3-234619
| merged | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0039 | 1 | F | 18.1.0 | Rel-18 | Correction on authentication and authorization for RNAA |
S3-235113
| agreed | SA3#113 | Huawei, HiSilic... |
SP-231340
| approved | SA#102 | SA WG3 | 18.2.0 | SNAAPPY |
|
|
|
| 33.122 | 0039 | - | F | 18.1.0 | Rel-18 | Correction on authentication and authorization for RNAA |
S3-234618
| revised | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0038 | - | F | 18.1.0 | Rel-18 | Revocation procedure invoked by resource owner client |
S3-234617
| not pursued | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0037 | - | F | 18.1.0 | Rel-18 | Revocation procedures invoked by API invoker |
S3-234616
| not pursued | SA3#113 | Huawei, HiSilicon |
| | | | | SNAAPPY |
|
|
|
| 33.122 | 0036 | - | B | 18.0.0 | Rel-18 | CR on security for resource owner aware northbound access to APIs |
S3-234360
| agreed | SA3#112 | NTT DOCOMO INC. |
SP-230907
| approved | SA#101 | SA WG3 | 18.1.0 | SNAAPPY |
|
|
|
| 33.122 | 0035 | 1 | F | 18.0.0 | Rel-18 | CR to 33.122 CAPIF Vendor specific security methods |
S3-234312
| agreed | SA3#112 | Nokia, Nokia Sh... |
SP-230900
| approved | SA#101 | SA WG3 | 18.1.0 | TEI18, CAPIF-Sec |
|
|
|
| 33.122 | 0035 | - | F | 18.0.0 | Rel-18 | CR to 33.122 CAPIF Vendor specific security methods |
S3-233788
| revised | SA3#112 | Nokia, Nokia Sh... |
| | | | | TEI18, CAPIF-Sec |
|
|
|
| 33.122 | 0034 | 1 | F | 17.1.0 | Rel-18 | CAPF 33.122 Vendor specific Security Methods |
S3-233350
| agreed | SA3#111 | Nokia, Nokia Sh... |
SP-230599
| approved | SA#100 | SA WG3 | 18.0.0 | CAPIF-Sec, TEI18 |
|
|
|
| 33.122 | 0034 | - | B | 17.1.0 | Rel-18 | CAPF 33.122 Vendor specific Security Methods |
S3-232604
| revised | SA3#111 | Nokia, Nokia Sh... |
| | | | | eCAPIF, TEI18 |
|
|
|
| 33.122 | 0033 | 1 | A | 17.0.0 | Rel-17 | Rel-17 Correcting the OAuth 2.0 roles in CAPIF |
S3-223924
| agreed | SA3#109 | Ericsson |
SP-221149
| approved | SA#98-e | SA WG3 | 17.1.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0033 | - | A | 17.0.0 | Rel-17 | Rel-17 Correcting the OAuth 2.0 roles in CAPIF |
S3-223648
| revised | SA3#109 | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0032 | 1 | A | 16.3.0 | Rel-16 | Rel-16 Correcting the OAuth 2.0 roles in CAPIF |
S3-223923
| agreed | SA3#109 | Ericsson |
SP-221149
| approved | SA#98-e | SA WG3 | 16.4.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0032 | - | A | 16.3.0 | Rel-16 | Rel-16 Correcting the OAuth 2.0 roles in CAPIF |
S3-223647
| revised | SA3#109 | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0031 | 1 | F | 15.3.0 | Rel-15 | Rel-15 Correcting the OAuth 2.0 roles in CAPIF |
S3-223922
| agreed | SA3#109 | Ericsson |
SP-221149
| approved | SA#98-e | SA WG3 | 15.4.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0031 | - | F | 15.3.0 | Rel-15 | Rel-15 Correcting the OAuth 2.0 roles in CAPIF |
S3-223646
| revised | SA3#109 | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0030 | - | A | 17.0.0 | Rel-17 | Rel-17 Correcting the OAuth 2.0 roles in CAPIF |
S3-221961
| not pursued | SA3#108-e | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0029 | - | A | 16.3.0 | Rel-16 | Rel-16 Correcting the OAuth 2.0 roles in CAPIF |
S3-221960
| not pursued | SA3#108-e | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0028 | - | F | 15.3.0 | Rel-15 | Rel-15 Correcting the OAuth 2.0 roles in CAPIF |
S3-221959
| not pursued | SA3#108-e | Ericsson |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0027 | - | B | 16.2.0 | Rel-16 | Usage of TLS profiles for CAPIF |
S3-201299
| agreed | SA3#99-e | Samsung |
SP-200359
| approved | SA#88-e | SA WG3 | 16.3.0 | eCAPIF |
|
|
|
| 33.122 | 0026 | 1 | B | 16.1.0 | Rel-16 | Description of CAPIF reference point: 3e,4e,5e,7 and 7e |
S3-194464
| agreed | SA3#97 | Samsung |
SP-191133
| approved | SA#86 | SA WG3 | 16.2.0 | eCAPIF |
|
|
|
| 33.122 | 0026 | - | B | 16.1.0 | Rel-16 | Description of CAPIF reference point: 3e,4e,5e,7 and 7e |
S3-194360
| revised | SA3#97 | Samsung |
| | | | | eCAPIF |
|
|
|
| 33.122 | 0025 | - | B | 16.0.0 | Rel-16 | Security procedures for CAPIF-3e/4e/5e reference points |
S3-192956
| agreed | SA3#96 | Samsung |
SP-190678
| approved | SA#85 | SA WG3 | 16.1.0 | eCAPIF |
|
|
|
| 33.122 | 0024 | - | B | 16.0.0 | Rel-16 | Security procedures for CAPIF-7/7e reference points |
S3-192955
| agreed | SA3#96 | Samsung |
SP-190678
| approved | SA#85 | SA WG3 | 16.1.0 | eCAPIF |
|
|
|
| 33.122 | 0023 | - | D | 16.0.0 | Rel-16 | Editorial correction of CAPIF-3e/4e/5e requirements clause |
S3-192215
| agreed | SA3#95-BIS | Samsung |
SP-190678
| approved | SA#85 | SA WG3 | 16.1.0 | eCAPIF |
|
|
|
| 33.122 | 0022 | 1 | B | 16.0.0 | Rel-16 | Security aspects of CAPIF-7/7e reference points |
S3-192339
| agreed | SA3#95-BIS | Samsung |
SP-190678
| approved | SA#85 | SA WG3 | 16.1.0 | eCAPIF |
|
|
|
| 33.122 | 0022 | - | B | 16.0.0 | Rel-16 | Security aspects of CAPIF-7/7e reference points |
S3-192214
| revised | SA3#95-BIS | Samsung |
| | | | | eCAPIF |
|
|
|
| 33.122 | 0021 | - | B | 16.0.0 | Rel-16 | Security procedures for CAPIF-3e/4e/5e reference points |
S3-192213
| not pursued | SA3#95-BIS | Samsung |
| | | | | eCAPIF |
|
|
|
| 33.122 | 0020 | - | B | 16.0.0 | Rel-16 | Requirement on authenticating unpublish requests |
S3-191937
| not pursued | SA3#95-BIS | Ericsson |
| | | | | eCAPIF |
|
|
|
| 33.122 | 0019 | - | B | 15.3.0 | Rel-16 | Security Requirements for CAPIF-3e/4e/5e reference points |
S3-191547
| agreed | SA3#95 | Samsung |
SP-190362
| approved | SA#84 | SA WG3 | 16.0.0 | eCAPIF |
|
|
|
| 33.122 | 0018 | - | F | 15.2.0 | Rel-15 | Editorial corrections in CAPIF TS |
S3-190321
| agreed | SA3#94 | Ericsson |
SP-190097
| approved | SA#83 | SA WG3 | 15.3.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0017 | - | F | 15.1.0 | Rel-15 | Missing subclause headings |
S3-183558
| agreed | SA3#93 | Samsung |
SP-181029
| approved | SA#82 | SA WG3 | 15.2.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0016 | - | F | 15.1.0 | Rel-15 | Association of security context |
S3-183557
| not pursued | SA3#93 | Samsung |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0015 | - | C | 15.1.0 | Rel-16 | Security requirements on the CAPIF-3e/4e/5e reference points |
S3-183439
| not pursued | SA3#93 | China Telecommu... |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0014 | 1 | F | 15.1.0 | Rel-15 | Delete information during API invoker offboarding |
S3-183716
| agreed | SA3#93 | Huawei, Hisilicon |
SP-181029
| approved | SA#82 | SA WG3 | 15.2.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0014 | - | F | 15.1.0 | Rel-15 | Delete information during API invoker offboarding |
S3-183421
| revised | SA3#93 | Huawei, Hisilicon |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0013 | 1 | F | 15.1.0 | Rel-15 | Correction/enhancement in CAPIF TS |
S3-183713
| agreed | SA3#93 | NEC Corporation |
SP-181029
| approved | SA#82 | SA WG3 | 15.2.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0013 | - | F | 15.1.0 | Rel-15 | Correction/enhancement in CAPIF TS |
S3-183341
| revised | SA3#93 | NEC Corporation |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0012 | - | C | 15.0.0 | Rel-15 | Security requirements on the CAPIF-3e/4e/5e reference points |
S3-182517
| withdrawn | SA3#92 | China Telecommu... |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0011 | - | F | 15.0.0 | Rel-15 | Assignment of FC values to AEFPSK derivation |
S3-182472
| merged | SA3#92 | Samsung |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0010 | - | F | 15.0.0 | Rel-15 | Access token profile |
S3-182282
| merged | SA3#92 | Huawei, Hisilicon |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0009 | 1 | F | 15.0.0 | Rel-15 | Adding FC value to TS 33.122 |
S3-182624
| agreed | SA3#92 | Huawei, Hisilicon |
SP-180699
| approved | SA#81 | SA WG3 | 15.1.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0009 | - | F | 15.0.0 | Rel-15 | Adding FC value to TS 33.122 |
S3-182281
| revised | SA3#92 | Huawei, Hisilicon |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0008 | 1 | F | 15.0.0 | Rel-15 | Clarification on access token verification |
S3-182621
| agreed | SA3#92 | Huawei, Hisilicon |
SP-180699
| approved | SA#81 | SA WG3 | 15.1.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0008 | - | F | 15.0.0 | Rel-15 | Clarification on access token verification |
S3-182278
| revised | SA3#92 | Huawei, Hisilicon |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0007 | 1 | F | 15.0.0 | Rel-15 | Clarification on Security protections in CAPIF-1 and CAPIF-2 reference point |
S3-182619
| agreed | SA3#92 | Huawei, Hisilicon |
SP-180699
| approved | SA#81 | SA WG3 | 15.1.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0007 | - | F | 15.0.0 | Rel-15 | Clarification on Security protections in CAPIF-1 and CAPIF-2 reference point |
S3-182277
| revised | SA3#92 | Huawei, Hisilicon |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0006 | 1 | F | 15.0.0 | Rel-15 | Modifications on Security procedures for API invoker onboarding |
S3-182610
| agreed | SA3#92 | Huawei, Hisilicon |
SP-180699
| approved | SA#81 | SA WG3 | 15.1.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0006 | - | F | 15.0.0 | Rel-15 | Modifications on Security procedures for API invoker onboarding |
S3-182276
| revised | SA3#92 | Huawei, Hisilicon |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0005 | 1 | B | 15.0.0 | Rel-15 | Security requirements for API invoker onboarding and offboarding |
S3-182618
| agreed | SA3#92 | Huawei, Hisilicon |
SP-180699
| approved | SA#81 | SA WG3 | 15.1.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0005 | - | F | 15.0.0 | Rel-15 | Security requirements for API invoker onboarding and offboarding |
S3-182275
| revised | SA3#92 | Huawei, Hisilicon |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0004 | - | D | 15.0.0 | Rel-15 | Removal of comment texts |
S3-182236
| not pursued | SA3#92 | NEC Corporation |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0003 | 1 | F | 15.0.0 | Rel-15 | [CAPIF-Sec] 33122 correct note in clause 6.5.2.1 |
S3-182622
| agreed | SA3#92 | Motorola Soluti... |
SP-180699
| approved | SA#81 | SA WG3 | 15.1.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0003 | - | F | 15.0.0 | Rel-15 | [CAPIF-Sec] 33122 correct note in clause 6.5.2.1 |
S3-182218
| revised | SA3#92 | Motorola Soluti... |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0002 | - | F | 15.0.0 | Rel-15 | [CAPIF-Sec] 33122 R15 FC values for CAPIF |
S3-182217
| withdrawn | SA3#92 | Motorola Soluti... |
| | | | | CAPIF-Sec |
|
|
|
| 33.122 | 0001 | 1 | B | 15.0.0 | Rel-15 | [CAPIF_Sec] 33122 R15 access token profile |
S3-182620
| agreed | SA3#92 | Motorola Soluti... |
SP-180699
| approved | SA#81 | SA WG3 | 15.1.0 | CAPIF-Sec |
|
|
|
| 33.122 | 0001 | - | F | 15.0.0 | Rel-15 | [CAPIF_Sec] 33122 R15 access token profile |
S3-182216
| revised | SA3#92 | Motorola Soluti... |
| | | | | CAPIF-Sec |
|